• State
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 32 views
  • Users 0 members are here
Support feedback
Options
Options
Related

CODECOMPOSER: Unable to debug BLE Wi-Fi Provisioning Example on Non-default Workspace

Suhani Tandle
Prodigy 10 points

Part Number: CODECOMPOSER

Hi,

I am trying to flash and debug the 'BLE Wifi Provisioning' example from the SimpleLink Wi-Fi SDK. When I import the example into my default workspace, it flashes and debugs perfectly fine. (Note that the workspace level launch.json file contains the "loadDebugSymbols" variable set as true for the default workspace) (See Screenshot 1)
However, when I import the project using the "Add folder to workspace" option, I am unable to load the program onto the board. When I open the folder level launch.json file (folder -> .theia -> launch.json), I find that there is not "loadDebugSymbols" variable set. (See Screenshot 2)
When I manually set the "loadDebugSymbols" as true in the folder level launch.json, the example loads onto the board.

Screenshot 1:
Screenshot 2026-06-01 215300.png

 

Screenshot 2:

Screenshot 2026-06-01 214123.png

 

 

 

 

 

 

 

May I know why the non-default workspace does not configure the same way as the default workspace and how this may be solved / any workaround to configure non-default workspaces properly?
Thank You

  • 0
    TI__Guru**** 481321 points

    Hello,

    Suhani Tandle said:
    I am trying to flash and debug the 'BLE Wifi Provisioning' example from the SimpleLink Wi-Fi SDK. When I import the example into my default workspace, it flashes and debugs perfectly fine. (Note that the workspace level launch.json file contains the "loadDebugSymbols" variable set as true for the default workspace) (See Screenshot 1)

    In screenshot 1, I see the "loadSymbolsOnly" parameter set to "true". That means only the debug symbols are loaded to the debugger. Nothing is loaded to the actual target/device.

    In screeshot 2, that parameter not set. So the debugger defaults to "false" - which means it will try to load both debug symbols to the debugger and program code to the device/target. It is the program load to the device that is failing (specifically a verification error).

    Suhani Tandle said:
    When I manually set the "loadDebugSymbols" as true in the folder level launch.json, the example loads onto the board.

    When you do this, NOTHING is loaded to the board.

    Suhani Tandle said:
    May I know why the non-default workspace does not configure the same way as the default workspace and how this may be solved / any workaround to configure non-default workspaces properly?

    I can't reproduce the issue you mentioned regarding the "loadSymbolsOnly" parameter when I create a multi-root workspace. That behavior is the same. I'm not sure how that happened in your environment. Somehow that loadSymbolsOnly option is being set. However, note that by adding that parameter, only symbols are loaded and no target code. I'm not sure if that is your desired intent. If it is not and then you are getting verification errors without it, then that is a different matter.