• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 145 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.

IAR-ARM: Failed to get CPU status after 4 retries Retry?

Rushikesh Porwal
Prodigy 40 points

Part Number: IAR-ARM
Other Parts Discussed in Thread: LAUNCHXL-TMS57004

I am currently working with the TMS5700714APZQQ1 device.
I installed IAR Embedded Workbench and imported the Blinking LED example project from the LAUNCHXL-TMS57004 (Hercules TMS570LS04x/03x LaunchPad Evaluation Kit).

 

For debugging, I am using a J-Link debugger and have connected the required JTAG and power pins (TCK, TMS, TDI, TDO, RESET, TRST, VCC, and GND). However, when I click Debug and Download, I encounter the error:

 

“Failed to get CPU status after 4 retries.”

 

I also tried switching to a TI XDS110 debugger, but I get the following error:

 

“Fatal error: No debug probe found connected to the USB port. Session aborted.”

 

Could you please help me identify what might be causing these issues?

  • 0
    TI__Guru* 77806 points

    Hi Rushikesh,

    Is it possible to test it your board on CCS once? Because this confirms whether the issue is with debug probe or IAR setup?

    The below are some suggestions from internal AI tool assistance:

    J-Link Issue: "Failed to get CPU status after 4 retries"

    This typically indicates a communication problem between the J-Link and your microcontroller. Here are possible causes and solutions:

    1. Power supply issues:

      • Verify the target board is properly powered (check voltage levels)
      • Ensure stable power without brownouts during debug attempts

    2. JTAG connection problems:

      • Double-check all pin connections (TCK, TMS, TDI, TDO, RESET, TRST)
      • Ensure correct pin mapping between J-Link and your TMS device
      • Verify signal integrity (try shorter/higher quality cables)

    3. J-Link configuration:

      • Update to the latest J-Link software
      • Check if your specific TMS5700714APZQQ1 device is supported by your J-Link version
      • Try adjusting JTAG clock speed (lower it to 100kHz for initial testing)

    4. Device state:

      • Try power cycling the entire setup
      • Hold RESET while connecting, then release

    XDS110 Issue: "No debug probe found connected to USB port"

    This suggests the PC isn't detecting the XDS110 hardware:

    1. Driver installation:

      • Verify XDS110 drivers are properly installed
      • Check Device Manager for any unknown devices or error indicators

    2. USB connectivity:

      • Try different USB ports (preferably direct connections, not through hubs)
      • Test the XDS110 on another computer if possible

    3. CCS/IAR configuration:

      • Ensure you've selected XDS110 as your debug probe in project settings
      • Check if you need to install additional TI components for XDS110 support

    Additional Verification Steps:

    1. Try running J-Link Commander (command line tool) to test basic communication
    2. Verify your IAR project is configured for the correct device variant
    3. Check if your TMS device has security features enabled that might block debugging

    --
    Thanks & regards,
    Jagadish.

  • 0
    Prodigy 40 points

    Hi Jagadish,

    Could you please help me identify which version includes support for the specific TMS5700714APZQQ1 device?

    Currently, I am using version 9.70.4, and I can only see the following device options available.




  • 0 in reply to Rushikesh Porwal
    TI__Guru* 77806 points

    Sincere apologies for the delayed response.

    You can use TMS5700714APZ.