• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 661 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.

TMS570LC4357: Boundary scan test

Steven Su2
Prodigy 60 points
Part Number: TMS570LC4357


Hi Sir:

After running boundary scan test for each IC on PCB, one of TMS570LC4357 shows fail.

According to the log, pin V2 seems abnormal.

However, pin V2 is not used and connected in our schematics, and there is no abnormal appearance found after scanning X-ray for IC.

Could you help us analyze what's the problem inside IC ?

FAIL LOG

 

 

BSDL file from TI :

https://www.ti.com/product/TMS570LC4357?keyMatch=TMS5704357BZWTQQ1&tisearch=Search-EN-everything&usecase=OPN#design-development##design-tools-simulation


  • 0 in reply to Steven Su2
    TI__Mastermind 49120 points

    Hello,

    I do not have the tools required to run a boundary scan test on my LaunchPad setup. I am looking into this though, and will report back once I find the right tools.

    You can try to drive this terminal (N2HET1[1]/MIBSPI4NENA/N2HET2[8]/eQEP2A) High/Low as a general-purpose output using a debugger and make sure that the correct level is observed.

  • 0 in reply to Sunil Oak
    Prodigy 60 points

    Hi Sunil:

    What is LaunchPad setup ? Any new status ?

    (N2HET1[1]/MIBSPI4NENA/N2HET2[8]/eQEP2A) is not connected and used in our schematics, so we can't measure it level

    Thanks

    Steven

  • 0 in reply to Steven Su2
    TI__Mastermind 49120 points

    Hi Steven,

    TMS570LC4357 LaunchPad is the low-cost development kit we make for this part. It has an XDS110 JTAG emulator built on to the kit, so that no external JTAG emulator is required. Some of the boundary scan software tools have been defined to work with specific JTAG emulators such as xds100, jlink, etc.

    Is it possible to use a debugger to output a High on this terminal and see that the terminal state reads back as '1' in the "data-in" register in the N2HET1 module?

  • 0 in reply to Sunil Oak
    TI__Mastermind 49120 points

    Hi Steven,

    Since this terminal is unused in your application, can you check if it has been grounded or pulled down externally? That would also explain the "stuck at 0" identification by the boundary scan tool.

    You should get the same result by toggling the terminal using a debugger as well.

  • 0 in reply to Sunil Oak
    Prodigy 60 points

    Hi Sunil:

    We don't use this terminal and no test point reserved for it , so we can not check it externally

    We loaded the test firmware on the unit and confirmed that the pin is hard shorted to ground and software is unable to overcome the short: 

    * 150.912422 WARNING: GPIO output reads back wrong - electrical fault?: 9, 1, 1
    N2HET1[1] is now low

    However, checking on other same IC on board, the pin successfully toggles both high and low as commanded.

    Is this raw material issue ? Do you have any comment for next step?

    Thank you

    Steven

  • 0 in reply to Steven Su2
    TI__Mastermind 49120 points

    Hi Steven,

    Every part is checked before shipping from TI. Can you move this failing part to another location and see if it also fails? Or you can move another unit to this location and check if it still passes the test. Once you resolve that this single unit is failing, you can contact your TI field representative to determine the procedure to submit the failing part for failure analysis.

  • 0 in reply to Sunil Oak
    Prodigy 60 points

    Hi Sunil:

    (1) From data 150.912422 WARNING: GPIO output reads back wrong - electrical fault?: 9, 1, 1
    N2HET1[1] is now low, can you figure out anything wrong with the IC ?

    (2) Do you know how to add other people in the thread?

    Thank you

    Steven

  • 0 in reply to Steven Su2
    TI__Mastermind 49120 points

    Steven,

    There is not enough information to identify the issue with the IC. It will have to go through the return flow in order to determine the issue.

    Whom would you like to add to the thread? Anyone else can also post on this thread.