How can i get the app for openSDA about MK20DX128VFM5

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

How can i get the app for openSDA about MK20DX128VFM5

Jump to solution
2,048 Views
hesander
Contributor II

I want to use a part of DEVKIT-MPC5744P. I have finished downloading the bootload in MK20DX128VFM5,Now need the app for openSDA about MK20DX12 8VFM5,but i Can not found the right one.Can you provide this?

This one is I found in JLink web.

pastedImage_1.png

This one is in DEVKIT-MPC5744P.

pastedImage_2.png

Waiting for your reply,

Thanks.He

Tags (2)
0 Kudos
1 Solution
1,748 Views
mariuslucianand
NXP Employee
NXP Employee

Hello hesander‌,

You can download from PEmicro's link http://www.pemicro.com/downloads/download_file.cfm?download_id=378  all the .SDA files they provides and you can try flashing the MSD-DEBUG-FRDM-K20D50M_Pemicro_v118.SDA file on the OpenSDA.

Hope this helps, 

Marius

View solution in original post

0 Kudos
6 Replies
1,749 Views
mariuslucianand
NXP Employee
NXP Employee

Hello hesander‌,

You can download from PEmicro's link http://www.pemicro.com/downloads/download_file.cfm?download_id=378  all the .SDA files they provides and you can try flashing the MSD-DEBUG-FRDM-K20D50M_Pemicro_v118.SDA file on the OpenSDA.

Hope this helps, 

Marius

0 Kudos
1,748 Views
hesander
Contributor II

Hello Marius Lucian Andrei,

I can only download *.bin files and cannot download *.SDA files. When I execute DEBUG_OpenSDA_for_MBED_Bootloader_by_Pemicro_v108_v2.1.bin, the board does not work properly and restarts frequently. This is the details on the board:

# DAPLink Firmware - see https://mbed.com/daplink
Unique ID: 0000000028884e450056700f6bf0002e8021000097969900
HIC ID: 97969900
Daplink Mode: Bootloader
Bootloader Version: 0244
Git SHA: 39c605031b1e82c34976bc5eeb892bf29f010d6c
Local Mods: 0
Bootloader CRC: 0x5f9747b1

how Can i do it.

Waiting for your reply,

Thanks.He

0 Kudos
1,748 Views
mariuslucianand
NXP Employee
NXP Employee

Hello hesander‌,

So let's summarize a bit your scenario: You want to use the OpenSDA from a MPC5744P to program a MK20 on another board, connected through JTAG connector? In this case the .SDA file must be written in the OpenSDA. For this, you need to keep the RESET button while you plug in the usb cable on the MPC5744DEVKIT, and copy paste the .SDA on the newly mounted disk.

Hope this helps,

Marius 

0 Kudos
1,748 Views
hesander
Contributor II

Hello Marius Lucian Andrei,

I reset openSDA on my development board, and now it shows bootload.I put msd-debug-frdm-k20d50m_pemicro_v118.sda into the bootload, and then it went from bootload to frdm-k20d50m. I think it was installed successfully.But I used it to flash on the S32, and what it showed was :The OpenSDA circuit is using an older Debug APP firmware.Please update the Debug APP to a minumum of release 1.00.

Waiting for your reply,

Thanks.He

0 Kudos
1,748 Views
mariuslucianand
NXP Employee
NXP Employee

Hello hesander‌,

So let's summarize a bit your scenario: You want to use the OpenSDA from a MPC5744P to program a MK20 on another board, connected through JTAG connector?

Btw, is my assumption right? Because in this case you need to be sure that on the MPC5744PEVB the mcu is not powered up to avoid the situation when you have two controllers linked to the same OpenSDA. I think (BUT NOT 100% SURE) that a more suitable approach would be using a S32KEVB an a scenario like here https://community.nxp.com/message/1151643 beacuse the K20 is a Cortex M4 architecture while the MPC5744P is Power Architecture. Obviously is the same OpenSDA but the ARM communicate over SWD and here is JTAG.

Please have a look on this document https://www.nxp.com/docs/en/user-guide/OPENSDAUG.pdf that explains in more detail how to use OpenSDA with the K20. Your problem seems to be related with the OpenSDA's firmware but try what the guide explains.

Hope this helps,

Marius

0 Kudos
1,748 Views
hesander
Contributor II

Hello Marius Lucian Andrei,

I have tried to use the method in that document, but it just indicated that the APP version was wrong. I used the development board for debugging, which could eliminate hardware problems.Do you have any other solutions?

Waiting for your reply,

Thanks.He

0 Kudos