F29H850TU: TZE package has issues with the BSDL model

Part Number: F29H850TU

The 256 BGA package (TZE) has an issue in its BSDL model:

Function

Datasheet

BSDL

JTAG TDI

T14

T12

JTAG TDO

R14

R12

JTAG TCK

R15

R13

JTAG TMS

T15

T13

Could you please comment? If is indeed an issue, could you provide a timeline for fixing the model?

Thank you!

  • Hi Lenio,

    Thanks for reaching out.  There is a known mapping issue on the BSDL file for the 256 BGA package in the F29 ti.com product folder.  Our DFT team has fixed that but we have not uploaded the file in the F29H85x product folder yet due to some ongoing debug on the number of scan chains that one customer is getting with XJTAG.  I'll attach the updated 256 BGA BSDL file here and maybe you can help check with your customer if they too are seeing the number of scan chain discrepancy.

    Our DFT team's checkout on the tester shows that the scan chain number is correct.  BSDL checkout result with another customer would certainly help our DFT team's debug.

    7180.F29H85x_PKG_256_BGA.zip

    Thanks and regards,

    Joseph   

  • Thank you! It seems the file you shared is the same I downloaded from ti.com. JTAG pins are still off, unless I'm missing something.

  • Hi Lenio,

    Here is what I see as JTAG assignments from the BSDL file:

    In summary:

    JTAG Terminal         GPIO#      256BGA Ball
    TAP_SCAN_IN (TDI)    GPIO222         T14
    TAP_SCAN_OUT (TDO)   GPIO223         R14
    TAP_SCAN_MODE (TMS)     --           T15
    TAP_SCAN_CLOCK (TCK)    --           R15

    The terminal assignment is consistent with the 256 BGA ball map.

    Maybe what happened is that the filenames from ti.com and the updated one is the same.  Renaming the updated BSDL with _002 in it for a different filename and reattaching it here again.

    F29H85x_PKG_256_BGA_002.zip

    Thanks,

    Joseph

  • Yes, maybe the naming was my issue. I see the changes now. I will send it to the customer and keep you posted - thank you!

  • Thank you Lenio!  Looking forward to hearing back from your customer.  Just in case, our first customer is seeing discrepancy between reported scan chain number in the BSDL vs what the debugger is counting  though our verification flow on the tester is consistent with what is in BSDL.

    Regards,

    Joseph