Using ST-Link V2 to flash KV31F Board

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

Using ST-Link V2 to flash KV31F Board

Jump to solution
5,754 Views
SANGEERTH-P
Contributor II

Hi all

I am currently using a KV31F512VLL12 Microcontroller. I tried to flash this board using ST-Link V2 Adapter. The jumper pins of ST Link was not matching the JTAG Jumper pins on the Evaluation Board. So I soldered few jumpers on the board. Then I connected KV31F Board JTAG pins to ST-Link Utility and then through the USB Port of ST-Link Utility I connected to my PC. I was able to see that my board was getting powered and it was executing the last dumped code. When i tried to debug the board with a new code, MCUXpresso-IDE was not showing any of the Debug port availability even when the ST-Link was connected to the PC. I changed the Debugger options too.

SANGEERTHP_0-1624869125843.png

Even then I see this following error.

SANGEERTHP_1-1624869288442.png

I am not sure of what is the cause for this error. I need your suggestions here.

Is the MCU KV31F incompatible with ST-LINK V2? If yes, what are the other ways to flash the code than this OPENSDA.

0 Kudos
1 Solution
5,746 Views
EdwinHz
NXP TechSupport
NXP TechSupport

Hello @SANGEERTH-P 

The ST-Link V2 is not a product that I’m are too familiar with, considering its primarily developed for ST products. I don’t see why it wouldn’t be compatible if it supports JTAG/SWD communication. Unfortunately I don’t have a way of testing this for you, so I’ll leave you with some links that might prove useful for your inquiry:

https://electronics.stackexchange.com/questions/250664/can-i-use-st-link-programmer-for-non-st-chips

https://community.particle.io/t/tutorial-using-eclipse-st-link-v2-openocd-to-debug/10042

I also noticed that the ST-Link V2 comes with the standard 20 pin connector. Perhaps a 20 pin to 10 pin JTAG adapter would be a better alternative than soldering the lines to make sure the connections are right.

It goes without saying that we recommend using a different debug probe, like the MCU-Link, since this one is specifically developed for NXP devices. Here’s a link so you can check it out:

https://mcuoneclipse.com/2020/11/29/new-mcu-link-debug-probe-from-nxp/

 

Regards,

Edwin.

View solution in original post

1 Reply
5,747 Views
EdwinHz
NXP TechSupport
NXP TechSupport

Hello @SANGEERTH-P 

The ST-Link V2 is not a product that I’m are too familiar with, considering its primarily developed for ST products. I don’t see why it wouldn’t be compatible if it supports JTAG/SWD communication. Unfortunately I don’t have a way of testing this for you, so I’ll leave you with some links that might prove useful for your inquiry:

https://electronics.stackexchange.com/questions/250664/can-i-use-st-link-programmer-for-non-st-chips

https://community.particle.io/t/tutorial-using-eclipse-st-link-v2-openocd-to-debug/10042

I also noticed that the ST-Link V2 comes with the standard 20 pin connector. Perhaps a 20 pin to 10 pin JTAG adapter would be a better alternative than soldering the lines to make sure the connections are right.

It goes without saying that we recommend using a different debug probe, like the MCU-Link, since this one is specifically developed for NXP devices. Here’s a link so you can check it out:

https://mcuoneclipse.com/2020/11/29/new-mcu-link-debug-probe-from-nxp/

 

Regards,

Edwin.