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.

CCS/LAUNCHXL-CC26X2R1: Socket error after failed firmware update

Part Number: LAUNCHXL-CC26X2R1

Tool/software: Code Composer Studio

Hello,

I just got my new CC26X2R1LP. I plugged it into my computer and using the TI cloud IDE I tried to download the BLESimplePeripheral stack, as I have done with other LPs. During the compile process, the IDE paused suggesting that the debugger needs a firmware update. The only option was OK, which I clicked. It warned me to not unplug the device while updating the firmware. After 3 hours, I was convinced that the process had failed. I had no choice but to restart the IDE. I then tried again to download and debug the stack. Compilation completed, but then exited with the "Socket error". No doubt the failed firmware update is the problem. Is there some way to recover? Typically an image of the firmware is saved that can be restored via a combination of button pushes, etc. Is there something like this for this launchpad.

help is appreciated,

Patrick

  • Hi Patrick,

    There is a factory image restoration mechanism build into the the CC26x2 LaunchPads, but it requires a bootloader to be present.
    If you have programmed the Simple BLE Peripheral example without OAD it is likely that you have wiped the bootloader from the device.

    One thing to note is that if you are using the simple BLE peripheral in its default configuration the stack is now built as a statically linked library (to be linked by the stack) and is not independently executable/flash-able as it was in previous SDKs. Likely you would not be able to flash the stack by itself.

    Another thing to test: are you able to flash the board using www.ti.com/.../UNIFLASH
  • Hi Sean,

    I was able to get the firmware updated via the cloud IDE. The TI Cloud Agent Bridge identified the launchpad. I used this tool to update the firmware. I then tried to debug the ProjectZero app. This progressed through a successful debug. When I clicked the start button, I got two errors related to JTAG. I presume that these are different problems, so let's call this topic closed.

    Thank you,

    Patrick