Other Parts Discussed in Thread: CC2540
I have a CC2540 mini dev. kit revision 1.0.2 and the included keyfob does not function after being flashed with CC2540_keyfob_SimpleBLEPeripheral.hex included with BLE stack V1.3. I flashed the USB dongle from the dev. kit with CC2540_USBdongle_HostTestRelease_All.hex (also included with BLE stack V1.3) and it is functioning properly.
The keyfob was flashed (while powered from a coin cell) using TI SmartRF Flash Programmer by performing an "erase, program and verify". No errors occur during the programming process. Once programmed the keyfob is totally non-functional. No LED, no buzzer, button presses seem to do nothing, and it cannot be found by the USB dongle. Removing and re-inserting the battery produces no change in the behavior.
Thinking perhaps the keyfob hex file may have become corrupt during download I even tried uninstalling and re-installing the BLE stack and flashing the keyfob again, but to no avail. Further I opened the keyfob project (included in the BLE stack install) in IAR Workbench to try to build the hex file myself. When building in IAR with no changes to the keyfob project I get the following error:
Error[e16]: Segment SLEEP_CODE (size: 0x9 align: 0) is too long for segment definition. At least 0x1 more bytes needed. The problem occurred while processing the segment placement command
"-Z(CODE)SLEEP_CODE=_SLEEP_CODE_SPACE_START-_SLEEP_CODE_SPACE_END", where at the moment of placement the available memory ranges were "CODE:7ff8-7fff"
This is my first foray into the TI ecosystem so I am not familiar enough with the product to be able to efficiently troubleshoot the aforementioned error.
Just for kicks I flashed CC2540MiniDkDemoSlave.hex (again, included with BLE stack V1.3) to the keyfob. With this firmware the LED lights up and I can find the keyfob with the USB dongle. However, since this is not the correct firmware the functionality is not there.
All in all it seems there must be an error in this version of the keyfob firmware since my keyfob hardware seems to be working with the wrong firmware.
Am I missing something? Has anyone else experienced similar problems? Have a resolution?
