• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 83 subscribers
  • Views 1200 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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:

LAUNCHXL-F28377S: Error connecting Blackhawk USB560v2 System Trace and Spectrum Digital XDS560v2 STM to the LAUNCHXL-F28...

LAUNCHXL-F28377S: Error Flashing the code using Blackhawk USB560v2 System Trace Emulator and Spectrum Digital XDS200 USB Emulator

Ankit Srivastava
Expert 1160 points

Part Number: LAUNCHXL-F28377S

My previous problem of connecting Blackhawk USB560v2 System Trace Emulator and Spectrum Digital XDS560v2 STM to the LAUNCHXL_F28377S was fixed in the following thread:

https://e2e.ti.com/support/microcontrollers/c2000/f/171/t/732161 

2. When I try to flash using Blackhawk USB560v2 System Trace Emulator, I get the following error:

C28xx_CPU1: Error: (Error -1 @ 0x0) Internal error: Invalid error code. Restart the application. If error persists, please report the error. (Emulation package 7.0.188.0) 

C28xx_CPU1: Trouble Halting Target CPU: (Error -1135 @ 0xC0EB) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 7.0.188.0)
C28xx_CPU1: Unable to determine target status after 20 attempts
C28xx_CPU1: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

2. When I try to flash using Spectrum Digital XDS200 USB Emulator, I get the following error:

C28xx_CPU1: Error: (Error -1135 @ 0xC095) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 7.0.188.0) 

C28xx_CPU1: Trouble Halting Target CPU: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 7.0.188.0)
C28xx_CPU1: Error: (Error -1135 @ 0xC095) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 7.0.188.0)
C28xx_CPU1: Unable to determine target status after 20 attempts
C28xx_CPU1: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

Note that in both of the above cases, Test Connection from CCS to respective debuggers passes successfully. Only Load Program fails.

Any suggestion how to solve this problem?

Thanks and Regards,

Ankit

  • 0
    TI__Intellectual 860 points

    Hello,

    Concerned experts have been notified of this query.

    Note that it is Thanksgiving week in US and most of the TI engineers are away.

    Please expect a delayed response, surely by early next week.

     

    Regards,

    Sudhakar

    ---------------------------------------------------------------------------------------------------

    If a post answers your question, please mark it with the "verify answer" button.

    Other useful links:

    C2000 Getting Started      C2000 Flash Common Issues/FAQs      Emulation FAQ

  • 0
    TI__Guru* 85290 points
    Ankit,
    I assume in the above cases you are trying to directly program the flash from the initial CCS view. I'd like to break out the connection and flashing steps as much as possible to root cause this.

    1)To connect, can you right click on the CCXML for the respective emulator/MCU and "Launch Selected Config"
    2)Assuming #1 is good, then right click on the main C28x core on the device and select "Connect"

    If the above works, then the issue is isolated to the flashing of the code vs connecting.

    3)Now, select "On Chip Flash" from the Tools menu item. Go ahead and verify things look correct in the settings, and attempt to "Erase Flash" and please note what happens after this step.

    Will pick back up once you have gotten through as many of the above steps as possible and reply back.

    Best,
    Matthew
  • 0 in reply to MatthewPate
    Expert 1160 points

    Hi Matthew,

    The above issue was due to some grounding issues in the circuit which we managed to fix.

    However I am always facing the below problem irrespective of whether we are using Blackhawk XDS560 v2 System Trace or XDS100 v2:

    C28xx_CPU1: GEL Output:

    Memory Map Initialization Complete

    C28xx_CPU1: Trouble Setting Breakpoint with the Action "Remain Halted" at 0xc056: (Error -1066 @ 0xC056) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 7.0.188.0)

    C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint

    The problem occurs irregularly. Below is my Debug Configuration (Note: I am using printf in my code):

    Any suggestion, how to get rid of this error?

    Thanks and Regards,

    Ankit

  • 0 in reply to Ankit Srivastava
    TI__Guru* 85290 points
    Ankit,
    It looks like the address in question: 0xC056 is trying to get a BP set potentially from a previous run of CCS. I see that you have selected to disable all BP if a different file is loaded; but I think that CCS may be trying to set the BP again since the source is the same. That memory, while in global shared RAM may not yet be intialized when CCS is trying to do this.

    On the same config page; can you go to the Auto Run and Launch Options and make sure that "Restore BP from previous session" is unchecked.

    On that same page take a look at the auto run options as well and note the "run to symbol" and its checkboxes. "On a program load or restart" is usually safe, "On a Reset" may not be desirabled.

    Another option would be to look under "View" - "breakpoints" to see if this address is showing up and is enabled.

    Best,
    Matthew