bluetooth lowenergy - SensorTag, iBeacon, Compiled firmware doesn't work -
Followed the instruction on this. IBeacon-enabled firmware was built with IAR and updated with OAD from OAD but stopped working after sensorag updating. No Ads by Side Button, No LED Blink
I tried identical / similar things several times and tried to upload the firmware directly from the IAR IDE via CC Debugger, but no luck.
I can keep it back by uploading the downloaded firmware with flash programmer for the previous working state.
I also tried to compile myself with the IAR with standard firmware (with no iBeacon from the SensorTag BLE stack), but it does not work, neither.
So I think compiling in IAR is my problem but the make can end successfully. A code was changed by me (only _NR_OF_VIRTUAL_REGISTERS to avoid a linker error).
I wonder if there are any who are successfully working on it while following the education at the above URL.
Thanks for the comment, Chris.
I found a solution on the TI E2E community.
IAR 8051 V8. There is a problem since updating from V8.20 to 30: This "8051 V8.30 Linker Error [E16] was recorded as: Segment is too long for the iTatec Segment definition". ().
After the modifications of the .xcl linker configuration, the build was correct without any errors but the firmware did not work on the SensorTag.
One of the posts on the TI E2E community said that the number of virtual registers from 16 to 12 is working in "Options" settings, working with IAR V8.30.3. Again, with an original .xcl file (not modified one) that tried any errors during the creation and also worked on SensorTag.
There are 3 packages in the SensorTag_Beacon project, that are CC2541DK-sensor, CC2541DK-sensor-OAD-ImgA and CC2514DK-Sensor-OAD-ImgB. What are the only options are CC2541DK-sensor with the number of virtual registers in the set without 12 and modified .xcl file.
CC2541DK- Sensor-OAD- ImgA and CC2514DK-Sensor-OAD-ImgB did not work
Hopefully, anyone else in the future helps.
Comments
Post a Comment