• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 101 subscribers
  • Views 140 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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-CC1352P: Cannot flash using CCS Theia

Ayush Singh
Prodigy 70 points
Part Number: LAUNCHXL-CC1352P
Other Parts Discussed in Thread: CC1352P7, LP-XDS110,

Tool/software:

I have been trying to flash my launchxl-cc1352p1 with the simple empty program, but it fails with the following error:

```

CS_DAP_0: Error connecting to the target:  DAP Connection Error. This could be caused by the device having gone to low power mode. Try forcing an external reset.If the error persists, try forcing BSL, a Mass erase or a Factory Reset. Check device FAQs for more information.

```

CCS Theia does detect the board correctly. It also updated the firmware on xds110 the first time I tried flashing.

I have all the jumpers connected in the middle JTAG header and the power is set to XDS110 power.

Here is my system information

CCS Theia: 1.5.1

OS: Fedora Sway Atomic 40

I was initially trying to use the launchxl xds110 for flashing a beagleconnect freedom cc1352p7, but it was also failing with the same error.

Am I missing something?

  • 0
    TI__Intellectual 2895 points

    Hi Ayush,

    I tried to flash the LAUNCHXL-CC1352P with CCS Theia using Ubuntu and I also got an error after CCS Theia updated the LP-XDS110 firmware. 

    The steps that I performed are the following:
    1. Unplug the LaunchPad and plug it in again so that it is again recognized by the os.
    2. Open the directory "ccs/ccs_base/common/uscif/xds110".
    3. Follow the readme to update the LP-XDS110 firmware using the xdsdfu utility. After the firmware update you will see an error with code -4 in the terminal which can be ignored.
    4. Unplug the LaunchPad and plug it in again so that it is again recognized by the os.
    5. Start the debug session with CCS Theia.

    Let me know if this fixes your issue. I will report this to R&D.

    Kind regards,
    Theo

  • 0 in reply to Theo Lange
    Prodigy 70 points

    Hi Theo,

    Just tried your steps. I was able to do a firmware update using xdsdfu, but I did not get any error. Here is my output:

    ```

    ❯ ./xdsdfu -f firmware_3.0.0.32.bin -r

    USB Device Firmware Upgrade Utility
    Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

    Scanning USB buses for supported XDS110 devices...

    Downloading firmware_3.0.0.32.bin to device...
    ```

    The firmware bin was already present in the xds110 dir. 

    However, I still get the same error when trying to use with CCS Theia.

    Here is more device info that I got from xdsdfu:


    ```

    ❯ ./xdsdfu -m

    USB Device Firmware Upgrade Utility
    Copyright (c) 2008-2019 Texas Instruments Incorporated. All rights reserved.

    Scanning USB buses for supported XDS110 devices...


    <<<< Device 0 >>>>

    VID: 0x0451 PID: 0xbef3
    Device Name: XDS110 Embed with CMSIS-DAP
    Version: 3.0.0.32
    Manufacturer: Texas Instruments
    Serial Num: L42002Y8
    Mode: Runtime
    Configuration: Standard


    ```

  • 0 in reply to Ayush Singh
    TI__Intellectual 2895 points

    Hi Ayush,

    that's great. So the firmware is up to date and now CCS Theia should be able to connect.

    Can you tell me exactly which steps you perform to flash the board with Theia? 

    I just imported the empty project, build the project and clicked debug and the board was flashed completely fine.

    Kind regards,
    Theo

  • 0 in reply to Theo Lange
    Prodigy 70 points

    Ok, so I was able to resolve my issue. 

    The problem was that `launch.json` file did not seem to get generated until I saved the workspace.

    And for some reason, if I tried to launch the program using the debug menu, it would give the above error. However, launching it from `Run->Debug Project` did complain about `launch.json` being missing and after saving the workspace, I guess the `launch.json` file was generated. So compiling works now.

    Thanks for the help.

  • 0 in reply to Ayush Singh
    TI__Intellectual 2895 points

    Hi Ayush,

    great that it works now. 

    Kind regards,
    Theo