• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 29 subscribers
  • Views 895 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.

Original question:

MSPM0L1303: Issue with Debugger

MSPM0L1303: clearing Fatal error: Failed to connect to the XDS emulator (connect CPU)... (Error -614 @ 0x0) in IAR

xiao feng
Prodigy 120 points
Part Number: MSPM0L1303
Other Parts Discussed in Thread: LP-MSPM0L1306, MSPM0L1306, SEGGER

I am using IAR V9.32.2 and I encounter the error below when programming MSPM0L1303. It was working fine before.

Thu Jun 15, 2023 16:58:27: Fatal error: Failed to connect to the XDS emulator (connect CPU)... (Error -614 @ 0x0) The target indicates there is an error condition from a previous SWD request. Clear the error the condition, and try the SWD request again. (Emulation package 9.9.0.00040) Session aborted!

I tried to clear the error as requested, but could not find a button to do so in IAR. Most of the buttons are greyed out.

I also went to C:\ti\iar\ccs_base\common\uscif\xds110 to use xds110reset.exe to reset the device with this command(.\xds110reset.exe -a toggle -d 100 -s ML130000), but the error persists.

How can I clear this error?

Thank you.

  • 0
    TI__Mastermind 28426 points

    Hi,

    Have you used our LP-MSPM0L1306 Launchpad for this test?

    If yes, could you take a photo for this launchpad, I need know the LP version and device version.

    And have you tried use IAR 9.41 version?

    Thanks!

    Best Regards

    Johnson

  • 0 in reply to Johnson He
    Prodigy 120 points

    yes LP-MSPM0L1306 Launchpad. here is the pic

    both IAR 9.32.2 and IAR 9.10.1 does not work. should i install IAR 9.41 now?

    I also tried flashing "firmware_3.0.0.13.bin" and "firmware_3.0.0.22.bin" using ".\xdsdfu.exe -f .\firmware_3.0.0.13.bin", the firmware update is successful as correct firmware version appear in ".\xdsdfu.exe -e". but  (Error -614 @ 0x0) still persist when debugging with IAR


  • 0
    Prodigy 120 points

    I switch to code composer studio and used "DSSM Factory reset" method described here  [MSPM0L1304: MSPM0L1304 set core in halt - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums] and the MCU started running again.
    I wonder if it is possible to do the same in IAR?

    now since i am able to recover from the brick, i also replicate the brick scenario. so basically when i use

    1. IAR

    2. "timx_timer_mode_one_shot_standby_LP_MSPM0L1306_nortos_iar.ewp" from "mspm0_sdk_1_00_01_03"

    3. download and debug, and click stop debug

    4. repeat a few times until it gives me 

    Fri Jun 16, 2023 15:13:39: Fatal error: Failed to stop execution: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG

    i tried upload the curzed project here but i am not sure is it successful. let me know if you cannot see the project.

    Thanks 

  • +1 in reply to xiao feng
    TI__Mastermind 28426 points

    Hi Xiaofeng,

    This LP is the previous version, thus looks MCU enter LPM mode, and our RTM silicon don't have this issue, thus you can apply our new version Launchpad, or use the below method to reactive your board:

    Addendum A - Debugging in Low Power Modes

    Effects of DEBUGSS_02 limitation:

    The effect of this limitation depends on the IDE and debugger implementation.

    1. The debuggers ends abruptly after the device goes into low-power mode.

    This behavior is typically caused by the debugger continuously polling the AP interface and failing to communicate. The following shows the error in CCS, depending on project settings: 

    • Workaround:
      • In CCS, select View → Target Configurations and open the configuration for your project. Select the Advanced tab, then the CS_DAP_0 connection, and change Device Management to Power-AP. Select the subpath_0 configuration and select type to debug, check Force Configuration and uncheck Pseudo. Note: Creating new projects and importing SDK projects in CCS should have these settings by default, thus enabling low-power mode.

       

      • In some scenarios, the workaround above might not be sufficient and the debugger might behave abnormally or close abruptly. In such cases, it’s recommended to enable the debugger low-power running mode by opening the debugger and selecting Tools→Debugger Options→Misc/Other Options, then select Allow power transitions while running if supported (low power running).

      • No other debugger has been found to show this behavior; however, it’s important to note that the device is correctly going into STOP/STANDBY, so the behavior is expected to be correct when running in standalone; however, if this issue is observed when debugging on early samples, use SLEEP mode.

    2. The debugger shows a warning error when the device goes into STOP/STANDBY.

    This behavior is also caused by the debugger continuously polling the AP interface and failing to communicate; however, instead of returning an error, the debugger shows a warning or prompts the user to try to reconnect. The warning typically appears periodically while the device is in low-power mode. The following image shows a warning when using IAR with Segger J-Link: 

    • Workaround:
      • Ignore the warning or retry the connection. The debugger will reconnect once the device goes back to RUN or SLEEP modes either periodically or with a breakpoint.

    3. The debugger ends abruptly when the debugger tries to halt the device.

    The debugger will be unable to halt the device on-demand, and it can either show a warning similar to case #2, or it can end abruptly. The following image shows an error when halting using IAR with XDS-110:

    • Workaround:
      • Halt only when the device is in RUN mode.
      • If not possible, use hardware breakpoints or BKPT instruction to reconnect the debugger.

    Summary of tested IDEs and debuggers

    The following table shows a summary of some IDEs and debuggers tested:

    IDE Debugger tool Going into LPM Halting
    CCS XDS-110 OK (warnings) OK (warnings)
    IAR XDS-110 OK Error
    IAR Segger J-Link OK (warning prompt) OK (warning prompt)
    IAR IAR I-Jet OK (warnings) OK (warning prompt)
    IAR XDS-110 as CMSIS_DAP OK (warnings) OK (warning prompt)
    Keil Segger J-Link OK (warnings) OK (warnings)

    Thanks!

    Best Regards

    Johnson

  • 0 in reply to Johnson He
    Prodigy 120 points
    Johnson He said:
    This LP is the previous version, thus looks MCU enter LPM mode, and our RTM silicon

    let me check my understanding:
    this launchpad evaluation module is an old version, thus lock MCU when entering Low Power Management Mode. I shall apply for a new version of evaluation module called RTM silicon. Mind telling me what does RTM means?

    Thank you for the detailed reply, now I get what is happening. 

  • 0 in reply to xiao feng
    TI__Mastermind 28426 points

    Hi Xiaofeng,

    Your launchpad is samples, not final silicon. RTM means Release to Market, is means that final silicon.

    Thanks!

    Best Regards

    Johnson