Hi Team,
We have identified the MKE13Z512VLL9 microcontroller as the suitable for one of our application. Before developing the hardware prototype, we would like to verify the interfaces on the development board.
We have seen in your website that FRDM-KE17Z development board can support MKE13Z512VLL9 microcontroller. Link: https://www.nxp.com/design/design-center/development-boards-and-designs/general-purpose-mcus/freedom...
Could you please confirm the below?
Hi NXP Team, Could you please suggest us the solution for the problem - FRD-MKE17Z512VLL9 development board is not getting detected in the Ozone J-Link debugger?
Hi,
Thank you so much for your interest in our products and for using our community.
For the MKE13Z512VLL9 part we do not have an specific development board.
However, FRDM-KE17Z512 can help you to do a proof of concept for your application. FRDM-KE17Z512 contains a MKE17Z512VLL9, which only has one TSI module more than MKE13Z512VLL9.
On the other hand, you cannot use the same binary file for both devices, because memory map change. However config and SW will be equal or similar. So, to use the MKE13Z512VLL9 you need to develop your own custom board and create a new project with its respective SDK.
Finally, you need to take into account that SDK for development boards have examples, and SDK for part do not have examples.
Hope it helps you.
Have a nice day!
@_Leo_ Thank you for the details.
Now, 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?