• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 100 subscribers
  • Views 176 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.

Original question:

TMS320VC5402: HPI BOOT

TMS320VC5402: the system does not switch to HPI boot mode.

YOSHIFUMI MARUYANA
Prodigy 100 points
Part Number: TMS320VC5402

Tool/software:

Thank you for your continued support.

My name is Maruyana.

I am having a problem where the system does not switch to HPI boot mode.

This is occurring in 1 out of 80 units.

I monitored DVDD +3.3V CVDD +1.8V 51-pin HINT 27-pin XF 66-pin INT2.

Why does 27-pin XF go Low?

XF remained Hi on the good unit. Why does 51-pin HINT go Hi→Low→Hi?

Any ideas?

Waveform of the defective unit

Waveform of the good unit

  • 0
    TI__Intellectual 1425 points

    Hi Maruyana,

    Thanks for reaching out to E2E. An expert has been contacted, and the response will take about a 1-2 weeks. In the meantime, can you confirm if the below post is a duplicate of your questions?

    https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1413090/tms320vc5402-hpi-boot

    Your answer will help avoid any confusion during future communications.

    Thanks,

    Haley

  • 0 in reply to Haley Alexander
    TI__Mastermind 22685 points

    Hi Maruyana,

    Apologies for the delayed response.  Can you provide some additional details:

    • You mention 1 out of 80 devices fail.  Is this out of 80 total units, or is the 1.25% failure rate extend across a larger quantity of units, and if so, how many total?
    • Is this using a TI designed board, or is this a custom board that you have designed?
    • Have you tried doing an A-B-A swap, of putting a known good device on this board that is failing and putting this failing device on a known good board to see if the problem tracks to the device or the board?

    Also, the post linked above by Haley appears to be on the same topic, so I will put a reply on that post linking to this thread, and then close that post.  This way we only have a single active thread for this discussion.

    Thanks,
    MIke