F29H850TU: BSDL model file does not match with device

Hello Patrick,

Apologies for the delayed response since I had to go back to our design team for their analysis.  Looks like they are seeing some duplicate channel assignment that broke the BSR count.  They are still doing the analysis and would update you on their findings.

Regards,

Joseph 

Hi Joseph,

Thanks for the interim report. Looking forward for the final findings.

Regards,
Patrick

Hello Patrick,

To get you going with your BSDL checkout, i have attached the re generated BSDL file from our design team.  It looks like there was a discrepancy with the pinmap used when the BSDL files were initially generated.  There was a last-minute change in the 256 ZEX pinmap that was not comprehended in the BSDL generation.  Let me know how your checkout goes so i can feedback to design team if there are issues.

Thanks,

Joseph

F29H85x_PKG_256_BGA.zip

Hi Joseph,

Thanks. It looks like they changed the Pin Map section in the BSDL file. So it looks like that matches the actual datasheet. I haven't even seen that this section wasn't correct. But no change in the boundary register or the length of it. Still a length of 420 bits. But Boundary Scan software detects only 419 bits.
That means that it is not possible to connect to the part.
Are they still investigating on that?

Regards,
Patrick

Hi Patrick,

Thanks for the quick response.  Let me send that feedback to our design team and get back with you.

Regards,

Joseph

Hi Patrick,

Just to have better information for our design team on the reported 419 scan length, is it through parsing the BSDL or is it what the tool is counting based on scan shifting (based on TDI/TDO activity after applying EXTEST/SAMPLE)?

Thanks,

Joseph

Hi Joseph,

It is what the tool is counting based on scan shifting. I try to connect to the F29H850TU with "JTAG Chain Debugger" from XJTAG. Please see the output from the tool in my first post.

Regards,

Patrick

Thanks Patrick.  Sent that info to them.  Is it also possible to share your scan shifting test case so they can evaluate this further?

Regards,

Joseph

Hi Joseph,

I don't exactly know what you mean by "to share your scan shifting test case". I just include the BSDL file in the parts library from the XJTAG tools and hit "Check Chain" function in the tool. The tool then reads the part ID code and if this ID code matches with an ID code in the parts library it then compares physical IR register length with the value from the BSDL file. After that, the tool compares the physical Boundary Scan Register length with the value from the BSDL file. This is where there is a mismatch so far.

Regards,
Patrick

HelloPatrick,  Got it.  So you have not done any scanning test yet it seems and chain length mismatch detected at initialization.  Passed this on to our design team.

Thanks,

Joseph

Hello Patrick,

Sent you a private message regarding this.

Regards,

Joseph

Hello Patrick,

Good to sync over the phone.  Let me close this post for now however we are still actively working on the BSDL issue that you reported.  We can sync back or update through email if needed.

Thanks,

joseph