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.

LP-EM-CC35X1: Unable to flash network_terminal demo

Part Number: LP-EM-CC35X1


Tool/software:

CCS 2031

Project > Build All results in a successful build.

Run > Flash gives the following error message

CS_DAP_0: FlashDeviceOsprey:: Flash loader: CC35xx_FLASH_LIBRARY_VERSION 1.2.0.11
CS_DAP_0: FlashDeviceOsprey:: FlashDeviceOsprey.cpp last changed: Aug 14 2025 00:17:28
GEL: Encountered a problem loading file: /home/<my-user-name>/ti/simplelink_wifi_sdk_9_13_01_04_ea/examples/CC35xx_network_terminal/build_cc35xx_debug/CC35xx_network_terminal.out Could not open file



Taking the bin file and using the programmer, programs the board, so both the image and the board are ok.

Thank you!

  • Hi Tim,

    Please take a closer look in the user guide found in docs folder of the SDK. You need to make sure that the debugger configurations are properly set up in order to debug & flash the image into the device using CCS. This includes the debug file needing to be a .sym extension and you are loading symbols only in the debugger configurations of your project.

    A comprehensive guide can be found in Documentation Overview html file -> Introduction to SDK -> CCS Setup.

    Best,

    Brandon Liu

  • I forgot to note that you should be using the CCS 20.1.1 if you are using the 9.13 SDK. 

    Here is a section of the guide you should definitely pay attention to:

    Follow those steps and you should be good to go.

    If you want to use CCS 20.3, you will have to wait for a compatible SDK to be released.

    I hope this helps.

  • Dear Brandon,

    thank you for taking time to respond to my inquiry. I will attempt to downgrade the CCS and try again. In the meantime I have traced the inability to program the board to the following:

    As one of the last build steps, the .out file is being destructively converted to .sym file:

    Once it happens, the subsequent programming step fails as it cannot find the now-deleted .out file.

    Could you perhaps let me know how this step was intended to work and whether the .out file that gets converted is the same .out file that the programmer needs?

    Once again, thank you for your valuable input.

    Regards,

    Timothy

  • Hello Timothy,
    To generate the .out file, please refer to "docs/simplelink_mcu_sdk/html/cc35xx/programming.html," specifically 'step 8'. I encountered the same issue, and this resolved it.

    remove --new_out_ext .sym from the post-build steps.

    Best regards,
    Kapil




  • Yeah, you need to remove the --new_out_ext .sym as mentioned in step 8.