BSDL files ID mismatch MKV56F1M0VLL24

[Deadman45]

I am using JTAG live to test the pins of the MKV56F1M0VLL24 connected to a CPLD connect with a jtag chain. The JTAG live is reporting a ID mismatch for the MCU see attached image, if I ignore this error I can continue testing without much of a problem.  The CPLD bsdl file ID matches the device ID. I would like to know what is the proper way of fixing this error?

Detected ID: 01011011101000000000010001110111

BSDL ID:      00001011001011111000000000011101

I found the BSDL file here (file name: KV5X_100LQFP.bsdl):

Microcontroller Symbols, Footprints and Models | NXP 

[giraffe508]

Hi @Deadman45 It seems like there is a mismatch between the detected ID and the BSDL ID for the MKV56F1M0VLL24. This could be due to an incorrect BSDL file being used or an issue with the JTAG live tool. To fix this error, please follow these steps:

1. Double-check that you are using the correct BSDL file for the MKV56F1M0VLL24. The BSDL file you mentioned (KV5X_100LQFP.bsdl) might not be the correct one for your specific device. You can find the BSDL files for NXP microcontrollers on the Microcontroller Symbols, Footprints and Models page. Make sure to download the correct BSDL file for your device and try again.
2. If you are using the correct BSDL file and still experiencing the ID mismatch issue, it could be a problem with the JTAG live tool. Ensure that the tool is configured correctly for your device and that it supports the MKV56F1M0VLL24.
3. If the issue persists, consider updating the firmware of your JTAG debugger, as it might be outdated and cause the ID mismatch.

If none of these steps resolve the issue, it might be necessary to further investigate the hardware connections and the JTAG live tool configuration. However, if you can continue testing without any problems after ignoring the error, it might not be a critical issue.

[Deadman45]

Hi @giraffe508 thanks for the reply.

This is how I downloaded the BSDL file (see attached picture) and I doubled checked again.

So there is a possibility that there might be something weird with the jtag debugger I am using a FT2232H controller for the boundary scan. The Jtag debugger jlink ultra+ give a ID of attached image.

Converted ID to binary:

ID:           01011011101000000000010001110111

CPUID:   01000001000011111100001001110010

From what I can see the ID reported form the jlink ultra+ and the FT2232H is the same. As you mentioned it is not critical error but for how we aim to use the JTAG live test software is to give the MCU module we created to someone with not necessarily all the knowledge of how they work to be able to test the module so this might cause problems in the future.

[vicentegomez]

Where did you buy the parts?