• State
  • Locked Locked
  • Replies 9 replies
  • Subscribers 82 subscribers
  • Views 1923 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.

Error on Custom Board: Can't Run Target CPU

Matthew Krenik
Intellectual 675 points
Other Parts Discussed in Thread: UNIFLASH

Hello, I built a custom C2000 board according to the schematics in Control Suite. I have been able to use CCS and a XDS100v2 external debugger to debug this C2000 board in the past.

I made a few adjustments to the SCI hardware, and now, when I try to debug and run the code, I receive an error that says "Can't Run Target CPU". I've copied and pasted the Console output below. Any ideas why this is happening? I have tried debugging it a dozen times or more, and one or two times, it has successfully debugged. The other times, this error comes up. I'm quite confused. Any help would be greatly appreciated.

Best,

Matthew

C28xx: GEL Output:
Device Calibration not complete, check if device is unlocked and recalibrate.C28xx: GEL Output:
Device Calibration not complete, check if device is unlocked and recalibrate.C28xx: GEL Output:
Device Calibration not complete, check if device is unlocked and recalibrate.C28xx: Breakpoint Manager: Retrying with a AET breakpoint
C28xx: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0x8000: (Error -1066 @ 0x8000) Unable to set requested breakpoint in memory. Verify that the breakpoint address is in writable memory. (Emulation package 5.0.872.0)
C28xx: Can't Run Target CPU: (Error -1156 @ 0x92E2) Device may be operating in low-power mode. Do you want to bring it out of this mode? (Emulation package 5.0.872.0)
C28xx: Can't Run Target CPU: (Error -2060 @ 0x0) Requested operation cannot be done while device is running. Halt the device, and retry the operation. (Emulation package 5.0.872.0)
C28xx: Trouble Halting Target CPU: (Error -1135 @ 0x92E2) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.0.872.0)
C28xx: Error: (Error -1135 @ 0x92E2) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Emulation package 5.0.872.0)

  • 0
    Intellectual 675 points

    Also, to further clarify, when I run the Test Connection on the Target Configuration, I get 0 failures and success for the JTAG connection. 

  • 0 in reply to Matthew Krenik
    Guru 192875 points

    Hi Matthew,

    Did your emulator get stuck in between loading the program? or did you disconnect the emulator while in mid of programming?

    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    Intellectual 675 points

    Hello Gautam,

    Now, when I use the emulator, it partially loads the program, and then this error appears and aborts. The error message says "Can't Run Target CPU. Device may be operating in low-power mode.Do you want to bring it out of this mode?" But no matter what option I select, it still fails. 

    When I was able to run the program in the past, I have accidentally disconnected the emulator, which terminated the debug session. This could have occurred while the program was still being loaded, although I don't remember any specific instances. 

    Best,

    Matthew

  • 0 in reply to Matthew Krenik
    Guru 192875 points

    When I was able to run the program in the past, I have accidentally disconnected the emulator, which terminated the debug session. This could have occurred while the program was still being loaded, although I don't remember any specific instances.

    I asked the above question because due to this, the controller goes into permanent lock mode and then it starts displaying all the error messages you're experiencing. Still I would like you to try CCS Uniflash -> Use the Unlock option present in the software -> then try programming the chip. Let me  know how it goes.

    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    Intellectual 675 points

    Hello Gautam, 

    Thanks for the advice. I did try CCS Uniflash --> Unlock, but unfortunately the operation failed. This is with all keys set to FFFF. Is the only solution that is left to remove the C2000 and solder a new one on? I will need to make sure my power connections are secure when I am loading programs onto my board.

    Best,

    Matthew 

  • 0 in reply to Matthew Krenik
    Guru 192875 points

    Is the only solution that is left to remove the C2000 and solder a new one on? I will need to make sure my power connections are secure when I am loading programs onto my board.

    Yes, please check all your power connections first before replacing the IC. Do keep us updated.

    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    Intellectual 675 points

    Hello Gautam,

    As discussed, I removed the C2000, checked all of the power connections, and then soldered a different C2000 chip. I tested all of the connections again and then I was able to successfully load code onto the device 5-6 times. I made sure that the device did not become unconnected at any point in time while the emulator was debugging.

    Unfortunately, after 5-6 times, the C2000 became locked up again (same error messages as before).  Are there any other reasons why the C2000 locks up? 

    I read on the TI E2E forums (for the F280335) that the reference design in Control Suite has changed from using inductors to resistors (this is for the VDDIO pins on the C2000). Is this also true for the F28069? Could this be causing the problems?

    Thanks for your continued help. 

     

    Best,

    Matthew 

  • 0 in reply to Matthew Krenik
    Guru 192875 points

    Hi Matthew,

     Unfortunately, after 5-6 times, the C2000 became locked up again (same error messages as before).  Are there any other reasons why the C2000 locks up?


    I would recommend you to check the JTAG connections thoroughly. The best way is to stick to eval board schematics for the JTAG interface while implementing your custom board.

    I read on the TI E2E forums (for the F280335) that the reference design in Control Suite has changed from using inductors to resistors (this is for the VDDIO pins on the C2000). Is this also true for the F28069? Could this be causing the problems?

    My F28335 custom controlCard has inductors placed and they absolutely have no problems! Your issue seems like controller getting locked and not damaged! I hope you're not fiddlind or fiddled with the CSM part in your project. Also, as you've thoroughly checked your board and have noticed no voltage discrepancies; I feel you need to check your schematics and compare it with F28069 controlCard or controlStick. If you feel allz well and are rightly placed.... then you should check your project once. 

    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    TI__Guru 57255 points

    Hi Matthew,

    In your first post, you mentioned that things were working well until you made some changes to the SCI hardware.  Can you elaborate a bit more on this?  If the SCI change is not made does the system work as expected (works > 5 or 6 times)?

    If the SCI change follows your issue then I'd recommend double-checking the connections and logic behind the SCI modification.


    Thank you,
    Brett