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.

LAUNCHXL-CC2650: Serial Boot via UART By using STM32

Part Number: LAUNCHXL-CC2650
Other Parts Discussed in Thread: CC2650, CC2340R5

Tool/software:

hi team 

1. Any examples for serial boot via UART 
  Aim is to update the TI firmware via serila boot (UART Communiaction ) By using STM32 (This has the latest version of the bin file that needs to be flashed in TI)

 

Note TI Eval kit : TEXAS INSTRUMENT LAUNCHXL-CC2650 Development Boards & Kits

2. could please provide us the suitable  SDK examples 
got an SDK But it doesnt supports our Eval kit CC2650.

In the file "simplelink_cc13xx_cc26xx_sdk_7_41_00_17", we are unable to find our board series example, which specifically addresses the evaluation kit.

I am eagerly awaiting your reply.

Regards 
George 

  • Hi George, 

    Thank you for reaching out. 

    1- The following app note provides details on using the ROM bootloader of the device: https://www.ti.com/lit/pdf/swra466 it also includes some code that can be referenced. 

    2- To get started with CC2650, you should actually install the two following packages - the SDK you have installed is for newer devices. 

    Last but not least, you could consider replacing the CC2650 with the new CC2340R5 device as it could reduce your system costs and offer a more modern solution. For the CC2340R5 device, you'll need the following SDK (https://www.ti.com/tool/download/SIMPLELINK-LOWPOWER-F3-SDK) and you can reference the serial boot loader available here: https://github.com/TexasInstruments-Sandbox/ble_examples/tree/simplelink_low_power_f3_sdk-7.40.03/tools/TI_CC2340_Linux_SBL 

    I hope this will help,

    Best regards, 

  • Hi Clement, good evening!

    As per your pervious advice, we have installed the 2 supporting packages and we are using an existing sdk to run the LAUNCHXL-CC2650.
    We have made the following changes
    1. Running a blink LED code in the main application
    2. Changed the following code in ccfg.c file

    //#####################################
    // Bootloader settings
    //#####################################

    #ifndef SET_CCFG_BL_CONFIG_BOOTLOADER_ENABLE
    //#define SET_CCFG_BL_CONFIG_BOOTLOADER_ENABLE 0x00 // Disable ROM boot loader
    #define SET_CCFG_BL_CONFIG_BOOTLOADER_ENABLE 0xC5 // Enable ROM boot loader
    #endif

    #ifndef SET_CCFG_BL_CONFIG_BL_LEVEL
    #define SET_CCFG_BL_CONFIG_BL_LEVEL 0x0 // Active low to open boot loader backdoor
    //#define SET_CCFG_BL_CONFIG_BL_LEVEL 0x1 // Active high to open boot loader backdoor
    #endif

    #ifndef SET_CCFG_BL_CONFIG_BL_PIN_NUMBER
    #define SET_CCFG_BL_CONFIG_BL_PIN_NUMBER 0x0D // DIO number for boot loader backdoor
    #endif

    #ifndef SET_CCFG_BL_CONFIG_BL_ENABLE
    #define SET_CCFG_BL_CONFIG_BL_ENABLE 0xC5 // Enabled boot loader backdoor
    //#define SET_CCFG_BL_CONFIG_BL_ENABLE 0xFF // Disabled boot loader backdoor
    #endif

    With these settings, we are enabing the BSL, enabling backdoor access using DIO13 pin of the launchpad

    Case: The led is blinking on power on, when the boot button (DIO13) is pressed and power reset is performed, only then the LED is turning OFF. The stop of LED is how we are inferring that the uC has gone to BSL mode.
    After this, we are sending 0x55 twice (Host baudrate 9600, 115200) to auto baudrate detection and expecting a response 0xCC. We are not receiving the response from the ti side.

    Could you please guide us where we are lagging behind for the response from ti controller. Are there any additional changes to be made? Thank you

    Kind regards,
    George

  • Hi George, 

    These are great progress!

    May I kindly ask you to verify which pins are being used? Could you please check they match the device variant you have? 

    Below table is taken from the app note https://www.ti.com/lit/pdf/swra466

    Best regards,