• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 81 subscribers
  • Views 2419 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.

CCS/TMS320F280049C: Jtag communication error xds100v2

david george1
Prodigy 50 points
Part Number: TMS320F280049C

Tool/software: Code Composer Studio

Hello
I have a tms320f280049c and trying to program using xds100v2

Currently the 280049c is in boot mode wait.

When programming in debug it looks like the progam is loaded and I get to the first break point.
when I hit run the following errors are shown.

C28xx_CPU1: JTAG Communication Error: (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 9.1.0.00001)
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

If I attempt to reconect to the processor without power cycling I get

Error connecting to the target:
(Error -2131 @ 0x0)
Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 9.1.0.00001)



If I try and just flash the processor it goes through the load process and hits the same errors.
The code is known to run properly on the launchpad development board.

  • 0
    TI__Mastermind 28275 points

    Hi David,

    Are you seeing these errors on the launchpad or is this from your custom board?

  • 0 in reply to Frank Ankapong
    Prodigy 50 points

    Im seeing the errors reported in  CCS.

    So I can connect and load target


    but it then when releast the target I get the following errors and am unable to reconect without power cycling.

  • 0 in reply to david george1
    TI__Mastermind 28275 points

    David,

    Are you seeing these issues from the launchpad or is this from a custom design?

  • 0 in reply to Frank Ankapong
    Prodigy 50 points

    Its a custom design, processor schematic with jtag below, decoupling not shown.

  • 0 in reply to david george1
    TI__Mastermind 28275 points
    David, A few points: 1. The XDS110 used on the launchpad is cJTAG. Is your design also using cJTAG? 2. This could be a power issue or clocking issue: i. Power issue in the sense that code loads fine but when you actually start running the application, there is a power spike from the device which dips the rails and causes the device to reset causing you to lose connection with the debug environment. Please check your design to make sure your power supplies are sized sufficiently. ii. Clocking issue in the sense that the clock input you are feeding from your custom design is higher than the launchpad and hence when run with the same settings, the device overclocks, code crashes and device resets. What is the frequency of the crystal you have on your design?
  • 0 in reply to Frank Ankapong
    Prodigy 50 points

    Hi Frank

    Just checked out the JTAG and its using a normal JTAG connection, not cJTAG.
    I believed the XDS100 would support this.

    The crystal and ciricuit are the same as the launchpad.

    Power supply
    3v3 rail regulator is rated for 1A and bypass caps as per the launchpad.
    5v rail is currently supplied from usb.

    EDIT
    I have swaped out 5v source
    and am now getting:-
    C28xx_CPU1: GEL: Error while executing OnRestart( 0 ): identifier not found: IER
         at IER=0 [f280049c.gel:64]
         at OnRestart(0)
    It may be an issue with crystal as its looks like its not running properly.
    I will check through this today

    Thanks

    David

  • 0 in reply to david george1
    TI__Mastermind 28275 points

    David,

    I'll add that the crystal you are using is not what is used on the launchpad. The part number for the launchpad crystal is ECS-200-18-30B-AGN-TR which is not the same as the part you have on the schematic you posted.

    Please step through your code line-by-line. If the line that is causing this to happen is the clock configuration code, then that most likely is the issue.

  • 0 in reply to Frank Ankapong
    Prodigy 50 points

    Hi Frank

    If I step through the program it will peripheral configs, then falls over,
    If I run the program with a breakpoint just before the peripheral config it dosent hit that section.

    Not entirly sure why I changed that part number for something totaly different.
    It definaly wont work with the a 8 meg 20pF crystal when its supposed to have a 20 meg 18 pF.
    Ill put the propper one on there and see what happens

  • 0 in reply to david george1
    TI__Mastermind 28275 points

    David,

    No problem. Let us know if you see anymore issues after the modifications.