FRDM-KE17ZVLL9 is not getting detected in Ozone J-Link Debugger

[vediyappan_villali]

We are using the MKE17Z512VLL9 evaluation board for our PoC. But it it not detecting in Ozone J-Link debugger. Please find the attached snapshots. Please find the attached snapshots. We tried to resolve this issue by following steps provided in https://www.segger.com/products/debug-probes/j-link/models/other-j-links/opensda-sda-v2/. But, when we connect MKE17Z512VLL9 evaluation board to the PC via USB while keeping the reset button of the board pushed, it is not starting the OpenSDA platform in MSD mode. The OpenSDA platform is not show up as mass storage device (MSD) on the PC just like an USB stick. To be informed, the similar issue we found in MKE15Z256VLL7 evaluation board, but we were able to resolve the issue by following the steps mentioned in the above link. Please guide us - how can we make the MKE17Z512VLL9 board is getting detected on the Ozone J-Link debugger?

[Celeste_Liu]

Hello @vediyappan_villali , @hasim__khan ,

Thanks for your post.

First, please pay attention to your jumper switch. You can find the relevant information about it at FRDM-KE17Z512 Board User Manual.

Secondly, if there is no problem with the jumpers, please try to flash or update the firmware of the mcu-link. The details are as follows:

The on-board debugger of the FRDM-KE17Z512 uses the LPC55s69 chip. It is different from the FRDM-KE15Z/FRDM-KE17Z. The FRDM-KE15Z/17Z uses the K20 chip. These two have different mechanisms.

For boards with the K20 as the on-board debugger, we need to update the Opensda firmware refer to OpenSDA V2 Firmware, just like what you do for FRDM-KE15Z.

However, for boards with the LPC55s69 as the on-board debugger (we call it mcu-link), for the introduction of the mcu-link, you can refer to section "3 MCU-Link OB debug probe" of FRDM-KE17Z512 Board User Manual. For the firmware upgrade, you can refer to section "3.4 MCU-Link host driver and utility installation" and section "3.5 Updating MCU-Link firmware using the firmware utility" of it.

After the above two attempts, you should be able to use external debuggers, such as JLink, normally.
If there are still problems, please let me know and I will continue to help you.

Hope it can help you.

BRs,

Celeste

--------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the "ACCEPT AS SOLUTION" button. Thank you!
--------------------------------------------------------------------------------------------------------------------

[vediyappan_villali]

@nxp Please support on this issue.

[hasim__khan]

i am also facing same issue with newly purchased boards.
Nxp team please provide the solution.

[vediyappan_villali]

Attaching the screenshot.