Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
We are trying to have our own OTA update scheme. For the purpose am trying to read/write a SS as well as DS area of the i2c EEPROM using APIs serEepromRead() and serEepromWrite(). In both cases the rAPI call returns fail. Do we need to do any initialization or where am wrong in calling the APIs. The shortage of documentation of the APIs make it hard to debug the issue.
Sample code with which i was trying to access i2c EEPROM:
Some initial thoughts: Is there a Write Protect line that needs to be turned of? We had difficulty with some of the higher level API and went to using the CFA and I2C.h functions which work, but unfortunately are limited to 14 bytes per transaction. No support for page-write, so we have to write 10 times to output one page of data that should go in a single write. 90% waste. Also, you may need to do your reads and writes in a loop and exit the loop only after the SUCCESS return code is received. We have observed that the writes frequently do not return success on the first try. It may be that the device just needs time to complete the write after it goes into it’s internally timed page write sequence. I found in one case 20 writes in a loop failed but when I put a 1 msec delay between the writes, it succeeded after two or three tries. I think this area of SDK could use some improvements but I think you should be able to get it to work. Keep trying.