This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.


Part Number: CC2541

We made our own serial programmer to work faster in a production setting than the CCDEBUGGER. We must be missing something. About 33% of the boards we program do not run and need to be reprogrammed. The same programmer works when done the second time.

We are seeing that location 0x707C is 0x7F on a board that does not run and 0x02 on working boards.

It seems to be giving an EE_SECTOR_ERROR on EEPROM_READBlock, like it cannot find the sector.

Maybe there is a go packet that signals we are done programming that we are missing. Yet it works 66% of the time.

Maybe we need to wait longer before we pull the plug?

This seems to be consistent with various programs on various boards. We never had issues with the CCDEBUGGER, but it is not cost effective when we program thousands of boards at a time.

Any suggestions?


  • Hi Tim,

    Since this issue appears capable of occurring on any device/board and same programmer works the second time, this appears to be a timing issue with the serial bootloader.  Are you referencing the example project from BLE-STACK-1-X (located in Projects\ble\util) for your own implementation?  Here is an old Wiki page and I recommend that you verify whether this platform encounters any problems when attempting to program devices, then compare the differences.