• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 84 subscribers
  • Views 1962 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.

JTAG fails to connect to a MCU

Javier Romo
Prodigy 20 points

Other Parts Discussed in Thread: TMS320F28335, TMS320F2806

Hello forum,

we are working with our own boards controlled with TMS320F28335 MCU. We program and debug our boards with JTAG (Blackhawk USB2000).

A board worked fine so far. Suddenly, we can not connect to MCU. The JTAG works properly with other boards and it pass the dbgjtag.exe checks succesfully. Oscilloscope show us JTAG clock signal is ok, but oscilloscope resolution is not enough to show other signals. We saw that MCU is powered correctly. When we try to connect with Code Composer Studio 3.3, it shows the label 'CONNECTING' indefinitely.

Is there a way to check the MCU health and recover it? 


Thanks.

Regards

  • 0
    Prodigy 120 points

    Hi,

    I have almost the same problem. We use CCS 3.3, TMS320F28335 eZdsp Starter Kit and Blackhawk USB2000 JTAG.

    We had been working without problems but now we can't connect with the board. CCS keeps saying "connecting" until it times out showing the following message:

    Error connecting to the target:
    Error 0x00000220/-1156
    Error during: Execution, OCS,
    Lost processor clock. Device may be operating
    in a low-power mode.  Do you want to bring it
    out of this mode?

    Same PC with same CCS 3.3 and same JTAG works with another board. We have checked the board, and in the oscilloscope we see TCK, TMS, TDI and TDO. All signals seem to be OK. 

    Any ideas?

    Best regards.

  • 0 in reply to Andrew Mounts
    TI__Mastermind 22025 points

    Javier and Andrew,

    Assuming the device is correctly powered, is not being held in reset, and the correct connections are made from the emulator to the device the only reason the JTAG connection should fail is if the ECSL logic has been tripped.  Try using the "Wait" or "Loop to check" bootmode and then connecting the emulator.  This is discussed in a little more detail on the TI processor wiki:

    http://processors.wiki.ti.com/index.php/Code_Security_Module_FAQ_for_C2000

    Give this a shot and let me know if this resolves your issue.

    Trey

  • 0 in reply to Trey German289
    Prodigy 10 points

    Dear Trey,

    I'm experiencing the above mentioned symptoms, i.e. I'm suddenly not able to debug my device anymore through JTAG and I get the 'lost processor clock' error message in CCS4. The hardware setup hasn't been changed and the JTAG signals seem to be OK on the oscilloscope.

    As opposed to the other guys, I have a Spectrum Digital XDS510LC debugger and a TMS320F2806. I checked the datasheet but I didn't find anything about ECSL in this model.

    Do you have any idea how to solve this?

     

    Kind regards,

    Daniel

  • 0 in reply to Daniel Turi
    TI__Mastermind 22025 points

    Daniel,

    The F2806x has the ECSL protection as well.  Try using the wait bootmode and then connecting as described in the previous post.  If this doesn't fix it let me know and we'll do further debug.


    Trey

  • 0 in reply to Trey German289
    Prodigy 20 points

    Hi Trey,

    We tried your suggestion and we recovered the MCU

    Thanks a lot

    Javier