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.

CC1350LP troubleshooting

Other Parts Discussed in Thread: CC1350

Hi,

1. After a couple of days playing with CC1350 Launchpad I can't  restore any more original FW via this link (Getting back to BLE stack/app mode).

Download process goes smoothly, I see red-green LED shining on CC1350LP XDS110 Debugger. Downloading finished OK. But original BLE application does not work.

2. OAD downloaded "Bual Band Node FW" also do not work. If I compile and flash it via CCS, it works.

3. If I compile and download sensortag_cc1350lp_app + sensortag_cc1350lp_stack from CCS, it works. But if I download the same apps output .hex files via Smart RF Programmer 2,  CC1350LP BLE Sensortag does not work

(I use these HEX-files:

C:\workspace_v6_1_3\sensortag_cc1350lp_stack\FlashROM\sensortag_cc1350lp_stack.hex 

C:\workspace_v6_1_3\sensortag_cc1350lp_app\FlashOnly_OAD\sensortag_cc1350lp_app.hex)

BR, Oleg

  

  • Hello Oleg,

    You need to build and program the bim_extflash project/hex as well when using Flash Programmer 2.

    Best wishes
  • Hi,

    I downloaded 3 files (see sreenshot below). CC1350Launchpad SensorTAG application started and worked well. But CC1350 SensorTAG firmware upgrade (to Node or Concentrator) still does not work. OAT downloadig process goes smoothly and finished with "Successful Firmware update..." message. But after HW reboot CC1350 Launchpad works in the same SensorTAG mode.

    Is it possible to get original Out of the Box Demo .hex (was downloaded into CC1350Launchpad from factory)? It seems original .hex was not equal to to the 3 files below, because OAT FW changing from SENSORTAG to sub-1GHz Coordinator/Node worked OK right out of box.

  • Hi Oleg,

    There were some issues with the previous .hex file, please go to dev.ti.com to the cc1350 page as you describe above, and try to re-flash the device again.

    New firmware 1.11 should work as expected.