• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 890 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.

AM3357: Boundary Scan Access

Patrick Ruf
Genius 5045 points

Part Number: AM3357
Other Parts Discussed in Thread: AM5716

Hi,

I try to get access to the boundary scan on a AM3357 device. The device runs fine in normal operation mode and access with JTAG and Code Composer Studio works fine as well.
When I try to access the boundary scan operation I get an error mesage from XJTAG software telling me that the JTAG chain is broken. With the same software I can access devices from the C2000 family without problems.
In a lot of different thread in E2E I can see that people have problems accessing boundary scan on Sitara devices. By the way: we have problems contacting a AM5716 as well.
It would help if an expert from TI could give a documenation on how boundary scan access has to be done. For example how to set signals like EMU0 and EMU1 while setting TRSTn high.

What about the pin "PMIC_POWER_EN" (C6). Does this pin stays in the same state when accessing boundary scan? (I think it is not controllable with boundary scan)

Any information on this topic is highly appreciated.

Thanks and best regards,

Patrick

  • 0
    TI__Genius 13567 points

    Hi Patrick,

    Sorry we do not have any guides for boundary scan on Sitara and we do not test it on our boards. Only the BSDL file is tested for syntax and correctness. 

    So far I have supported JTAG and BSDL questions for at least the past year on this forum and I have not seen support or inquiries with this problem elsewhere. Does this problem persist regardless of the EMU0 and EMU1 pin levels? EMU0 and EMU1 = 1 is the default config but EMU0 = 0 and EMU1 = 1 is the Wait-in-Reset Mode which may help with BSDL access.

    How to set these pin levels is up to you but boards with our standard 14-pin header typically have these EMU pins accessible by the debugger. I'm not sure about the PMIC_POWER_EN pin since this is part of the RTC domain. 

  • 0
    TI__Genius 13567 points

    Hi Patrick,

    Recalling from your other thread, it sounded like XJTAG was aware of this quirk and they had a work around. This same IP has been used across all the Sitara products to date. If XJTAG has faced this problem and developed a work around then it's possible other boundary scan software providers also discovered this and developed their own work arounds too. I have not seen anyone report issues while using Corelis for example.

    Regards,
    Ahmad