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.
Thanks you for sharing your first hand experience with Rajesh Eric.
We spoke to the developers this afternoon and confirmed that the APIs serEepromRead() and serEepromWrite() are internal APIs and not designed to be used by customers.
If you go to the sample OTA app /WICED-Smart-SDK/Apps/ota_secure_firmware_upgrade, focus on using the APIs described within bleappfwu.h
NOTE: Reading and writing to hex 140 is very dangerous.