Debug & GDB server don't launch MKV4x

[HGRR]

Hello,

I try to send the hellowolrd example in the SDK (twrkv46f150m_hello_world), but when i build the project, everysing is done with no warning, and when i lunch the debug i have this window :

i try to find the correct BDM speed but i didn't successed, so i try all of them. No success.

So i search more information and i find this error: 

Error in services launch sequence

PEmicro GDB Launch Failure : The GDB Server was not able to establish a connection to the target processor. Please check your connections and power. Verify that the launch settings in the Debug Configuration are accurate.

But I don't know how to set up the server, this is the actual config:

So since I don't know anything about GDB servers, I was interested in the flashing error. And I have this error report:

Executing flash operation 'Program' (Program file into flash: twrkv46f150m_hello_world.axf) - Fri Sep 29 09:45:16 CEST 2023
Checking MCU info...
Scanning for targets...
Executing flash action...
P&E GDB Server for Arm(R) devices, Version 9.30.00.00
Copyright 2018, P&E Microcomputer Systems Inc, All rights reserved
Loading library D:\Nxp\MCUXpressoIDE_11.8.0_1165\ide\plugins\com.pemicro.debug.gdbjtag.pne_5.7.1.202309212104\win32\gdi\unit_ngs_arm_internal.dll ... Done.
Command line arguments: -interface=OPENSDA -port=USB1 -speed=5000 -flashobjectfile=D:\MCUXpressiIDE_11.0.8\twrkv46f150m_hello_world\Debug\twrkv46f150m_hello_world.axf -device=NXP_KVx_KV46F256M16 -programmingtype=0 -runafterprogramming -startserver -singlesession -quitafterprogramming
Device selected is NXP_KVx_KV46F256M16
User Specified Hardware Selection : Interface=OPENSDA and Port=USB1
Connecting to target.
Unable to load libusb0.dll
OpenSDA detected - Flash Version 1.08
Can not enter background mode.
Unable to initialize PEDebug.
PEmicro GDB Launch Failure : The GDB Server was not able to establish a connection to the target processor. Please check your connections and power. Verify that the launch settings in the Debug Configuration are accurate.
Target Disconnected.
Flash command failed!
Unable to perform operation.

 And maybe the problem is not a GDB server error but maybe the Libusb0. i try to reinstall the software, add the lib in soft & win directories.

it's doesn't work. I have no idea why, help me please.

I work on the TWR-KV46F150M devboard with a MKV46F256VLL16 MCU.

Software version :
Win10 22H2
MCUXpresso IDE 11.8.0
PEMicro OpenSDA Debug driver 12.4.0.0
OpenSDA - CDC Serial Port 1.1.2600.1
Tera term 4.106

[ajayyadav1996]

Hello,

I was facing same issue and going through comments on software forum, As I am looking into older comments on forum in future someone like me may reach this thread and he might get benefitted from my comment so adding it to this thread.

I found that issue was present with my PE micro hardware (It was faulty), I was able to find root cause with Kinetis Recovery utility tool. 

To download it, Follow below link,
Solved: Can't use PEmicro debugger with S32K118EVB2-Q048 - NXP Community

Or there is one more possibility that your watchdog is not disabled.

Best Regards,

Ajay Yadav

[HGRR]

Hello @EduardoZamora,

Thanks for your help,

There is the bridge config : 

I use the tower pack with the TWR-SER module.

The power is provided by the tower boards.

I try to delete the .launch file and reload/build the project.

I can still see the detection of the SDA probe, but I still have the PEmicro assistant coming after it. (and all possible config doesn't work).

I try also without the tower boards with the MCU board only and it's the same result.

The problem come from the drivers i think but i try to Un/install them 3 times...

The probe avalable for me :

And I click "OK", I'm stuck at this step : 

With this window :

[EduardoZamora]

Hi,

Could you please try shorting J518-1 to J517-2? Also, connect the USB cable to J511:

Regards,
Eduardo.

[HGRR]

Hi,
I shorted J518-1 to J517-2, connect the USB and retry the procedure of your message below.
But it's the same probleme I don't know why

Regards,

[EduardoZamora]

Hi,

Please, take a look at this website: Resurrecting ‘bricked’ NXP Kinetis Devices. Here you should find some recommendations on how to recover your device if it is bricked.

Regards,
Eduardo.

[HGRR]

Hi @EduardoZamora,

I follows all the instructions on this site and there dependancies.

I have the same problem, i can detect the board with the probe discovery, I can send SREC files but i can debug the board.

I have no idea why

Thx for your help

[EduardoZamora]

Hi,

Could you please confirm if you can access/debug your KV4x by using an external debugger? Example of this external debugger is the MCU Link JTAG/SWD Debug Probe or MCU-Link Pro Debug Probe; just to verify that KV4x chipset is still working.

Regards,
Eduardo.

[HGRR]

Hi @EduardoZamora,

i try to use the external debugger, using P&E probe, nothing works.
I have contacted the support team to change the board and maybe the new one will not being bricked.

I follows instruction in Resurrecting ‘bricked’ NXP Kinetis Devices.
I full chip erase or the power glitching doesn"t work.

The board is still bricked : 

Thanks for your help

[EduardoZamora]

Hello @HGRR

Could you please help us providing the jumper configuration of your dev-board? A picture of the top side of your board would be very helpful.

Please, try deleting the existent *.launch file from your project.
 

After this, click on debug with the active build configuration.

This should start the probe discovery. The available probes should be listed here, select the probe corresponding to your board and try debugging again.
 

Regards,
Eduardo.