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.

DP83869HM: CORRECT BSDL, PLEASE!!!

Part Number: DP83869HM
Other Parts Discussed in Thread: DP83869,

Please provide correct BSDL file for QFN48 package

What I identified in older posts (3 years ago) it was twice wrong files posted for 64 pin!, also filenames was also wrong:

dp8356x_bsr_final.bsdl
dp8356x_bsr_final_48.bsdl

Even if it was packed into files:

dp83869_BSDL.zip
0755.dp83869_bsdl.zip

All of it looks like a big JOKE! Inside BSDL file there were DP83869HM identifiers, but number of pins for BGA (???) was 64, not 48.

So in general - nightmare and big mess, not support...

Can you fix it ???

  • In next thread I've found also something "better":

    dp8356x_bsr_final_48_ver_0p1.bsdl

    This one is 48-pin, but faults still remain:

    Why the filename is different than I can expect?

    Why BGA keyword is inside instead of correct QFN48?

  • Hello,

    This file can work for DP83869.

    Sincerely,

    Gerome

  • I think TI does not understand that this is a mess, not support. By the 1149.1 standard silicon vendor is obligated to create RIGHT BSDL file and provide it to anyone, who requests it. I see that after 3 years fighting with TI for right file, we get "something": BSDL-like product.

    I'm dissapointed. If the file has still some weird issues like wrong package name and wrong filename I think I should pray, what is the quality for the rest data inside file. Incorrect BSDL file means incorrect testing via JTAG Boundary-Scan. What for you implement it in silicon if you can't provide 2nd side: BSDL file coherent with silicon?

    I think all of other requestors was "happy" to get finally "anything", but the truth is: TI disregards this topic. Shame... 3 years, no any reflection.

  • Hello,

    Are you seeing any issues when you are implementing the file outside of the title of the file being misslabled?

    Sincerely,

    Gerome

  • I'm sorry, it is not the right stage to answer you Now I can only check if syntax checker PASSES / FAILS. But the true test is running the hardware. It is the future action, without fixed date yet. All my irritation is caused by unprofessional support. After so many complaints from my precedors, TI had enough time to make proffesional BSDL file. No excuses.