Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing as much memory devices as possible #3

Open
sosandroid opened this issue Nov 18, 2016 · 18 comments
Open

Testing as much memory devices as possible #3

sosandroid opened this issue Nov 18, 2016 · 18 comments

Comments

@sosandroid
Copy link
Owner

sosandroid commented Nov 18, 2016

I need some help to test the memory devices as I do not have all of them.

The strategy:

  • Verifying the device has / has not the Device IDs feature
  • Testing the proper adressing scheme by using Manual Mode example
  • If device has device IDs feature, check if this is recognized by the lib to set it up automatically.
  • Additionnal testing with all the methods of the lib.

Thank you for your help. Fell free to leave your results here

@Palatis
Copy link
Contributor

Palatis commented Jan 22, 2017

works for MB85RC16V :-)
thx for the hard work :-D

initialized as: FRAM_MB85RC_I2C fram(MB85RC_ADDRESS_A000, true, /* WP */ A7, 16 /* kb */);

@mrstew
Copy link

mrstew commented Mar 5, 2017

I just tested the library on the FM24C64B - works great!

No device ID, but initialized with the correct chip density (64) and all was good.

@sosandroid
Copy link
Owner Author

Thanks for those feedbacks

@JRDavisUF
Copy link

W10 + CCSv7+ Energia18 + MSP432 LaunchPad + MB85RC256V breakout from Adafruit +v1.2 libray works after a few minor mods:

  1. Due to a compiler error, had to modify the line taken from an example:
    FRAM_MB85RC_I2C mymemory(); to
    FRAM_MB85RC_I2C mymemory;

  2. Need to edit this line in getDeviceIDs (this issue is talked about elsewhere online)
    result = Wire.endTransmission(false); and replace with
    result = ERROR_0;

  3. When doing timing tests, needed to add some Serial.flush() lines before/after timing sections to get stability with results. I2C with Serial terminal-type output has caused me some issues elsewhere...I think this is related.

Timing Info:
100 bytes array write: 1952 us
100 bytes array read: 2103 us

@sosandroid
Copy link
Owner Author

@JRDavisUF Thx for those feedbacks

@MisterScience5
Copy link

Tested the Cypress FM24CL64B on a Particle Photon, works great in manual mode, initialized as:
FRAM_MB85RC_I2C memory(0x50, false, 13, 64);

@hyperion11
Copy link

test FM24C04B on Arduino stm32. Tests work fine.

@sosandroid
Copy link
Owner Author

Thanks

@Mythricia
Copy link

Tested FUJITSU MB85RC04V, on Arduino Uno. Seems to work perfectly! Thanks for this great library.

@sosandroid
Copy link
Owner Author

Thank you for sharing

@suremicro
Copy link

Tested Cypress FM24CL04B (4k) on ESP8266 12e (NodeMCU) and works fine.

(When reading all memory 1 byte at a time the ESP soft reset after around 220 reads which was probably due to heap/stack issues. Reading 8 byte arrays works fine.)

@ekuiter
Copy link

ekuiter commented Mar 1, 2020

I tested the Cypress FM24CL16B with an ESP32. Works like a charm.

@sosandroid
Copy link
Owner Author

Thank you for your feedback

sosandroid added a commit that referenced this issue Mar 31, 2020
reported as tested : #3 (comment)
@zebra1993
Copy link

zebra1993 commented Jan 22, 2021

I got a FM24C04B running on my Teensy 4.0. Had issues with the I2C as i thought the wire.begin() was in the libary (im quie new to programing MCUs). But with including/starting it in my code, the Beef example works now.

@sosandroid
Copy link
Owner Author

Good news
Thanks for the feedback.
The device was reported as supported

@hugovantriet
Copy link

Hello,

Thank you really much for making this library, you can't imagine how happy I was when I found this page!
I can confirm that the MB85RC64TA passes the first reading/writing test program!
I'm going to play with it for a bit, and when I find something interesting I will report it back to you.

@dstulken
Copy link

Just a quick note - you might consider changing the "Cypress" references on your main page to "Cypress/Infineon" to help more people find your library and verify that their chips are compatible.

Cypress was acquired by Infineon last year, and the chip brandings are slowly starting to change over to Infineon. Most are dual-named ("Cypress-Infineon", etc) on the vendor websites, but I have seen some chips that now just list Infineon as the manufacturer with no Cypress references at all anymore.

@OptifySudarshanPatil
Copy link

OptifySudarshanPatil commented Dec 30, 2022

FM24V05 generates followings result in example code FRAM_I2C
_readIDs

Starting...
....... .......
FRAM Device IDs
Manufacturer 0xFFF
ProductID 0xFFF
Density code 0xF
...... ...... ......

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests