Other Parts Discussed in Thread: CC2540
Hello All,
One of my customer is evaluating CC2540. He trying to modify SimpleBLEPeripheral and dump the .hex in device. But after dumping modified .hex the device is not getting detected on Mobile. Whereas, when they dump the prebuilt “Simple BLE Peripheral” HEX file provided by TI, we can detect/scan the BLE chip in the phone.
There is a file size difference too for the Prebuilt HEX file to the new generated HEX file.
They are using CC Debugger JTAG for dumping the HEX file.
They are using IAR workbench 9.10.1.
firstly After compiling, they were getting the following error:
Linking Error[e16]: Segment ISTACK (size: 0xc0 align: 0) is too long for segment definition. At least 0xe more bytes needed. The problem occurred while processing the segment placement command
"-Z(IDATA)ISTACK+_IDATA_STACK_SIZE#08-_IDATA_END", where at the moment of placement the available memory ranges were "IDATA:4e-ff"
Reserved ranges relevant to this placement:
IDATA:8-1f VREG
IDATA:21-40 VREG
IDATA:41-42 XSP
IDATA:43-43 DATA_I
IDATA:44-4b DATA_Z
IDATA:4c-4d IDATA_Z
IDATA:4e-ff ISTACK
BIT:0-7 BREG
BIT:80-97 SFR_AN
BIT:a0-af SFR_AN
BIT:b8-c7 SFR_AN
Error while running Linker
This error is eliminated by referring
http://supp.iar.com/Support/?Note=95811
http://e2e.ti.com/support/wireless_connectivity/f/538/p/303921/1061753
Kindly advice on the same. We are stucked.
