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)
I'm using the BCM20737S which is an BCM20737 with onboard eeprom, clock and antenna.
I use the NVRAM functions to store 16 bytes of configuration data - see the implementation of saveConfig() below, using bleprofile_WriteNVRAM(). When I program my chip using the WICED IDE, this function works and the nvramFailed flag is never set.
I just received some chips programmed by our distributor. The code running seems to be correct in all respects, and the correct firmware version is reported in my custom characteristic. However saveConfig() fails on the chip programmed by the distributor, setting the nvramFailed flag. If I then re-program the same chip using the WICED IDE the chip now works correctly.
Does anyone know if there's a lock-bit that perhaps the factory is setting on the nvram area? Or any other reason why bleprofile_WriteNVRAM() wouldn't work?