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

TMS570LS3134: HDK stability problem with message "cross-triggering"

RH2248
Intellectual 290 points
Part Number: TMS570LS3134
Other Parts Discussed in Thread: HALCOGEN

Hi everybody,

I'm facing problems working with TMDS570LS31 HDK (in fact same Problems with two boards...) and things seem to get worse day by day:

After powerup, the uC sometimes doesn't seem to run correctly (looking at LEDs or using a scope on some GPIOs that should toggle). Repeating the powerup procedure severel times I usually get it to work some time.

With attached on board XDS100 and "active" problem, I get the message "Suspended - Cross-triggering" and I cannot debug the program.

What does "cross triggering" mean here and how can I avoid and get the system working?

Problem seems to be independant of CCS, CGT, HALCoGen versions and also occures with TI examples out of the box.

Regards,

Ralph

  • 0
    TI__Guru 72500 points
    Cross triggering is part of the debug logic. It sounds like corrupted JTAG debug scanning. Can you try a different USB port and USB cable?
  • 0 in reply to Bob Crosby
    Intellectual 290 points
    Yes, did that already but without success.
    As the board also has problems without XDS100 connected, I already thought about influence of the other JTAG sources like 20pin header or MIPI interface. Could they make a problem? Anything I could do to make sure these will not cause the problems?

    Regards,
    Ralph
  • 0 in reply to RH2248
    TI__Guru 72500 points
    I do not have any reports of problems from the unused JTAG connectors. Have you monitored the power to the board?
  • 0 in reply to Bob Crosby
    Intellectual 290 points

    I checked the 3V3 rise time at power up and it looks the same for both cases (~1ms without glitches or anything alike).

    Also 3V3 seems to be stable during further operation.

    Anything I can do to really disable the unused JTAG ports or other ideas what causes my problem (remember the CCS message during Debugging: not just "suspended" but "suspended  - cross-triggering")?

    Thanks

    Ralph