topic Re: Fail to connect MKM34Z256 in Kinetis Microcontrollers

Fail to connect MKM34Z256

rahul_4 — Tue, 25 Jul 2023 10:07:35 GMT

Hi,

During programming, I am getting below error -

Connecting ...
- Connecting via USB to probe/ programmer device 0
- Probe/ Programmer firmware: J-Link WiFi-V1 compiled Mar 15 2023 11:22:42
- Device "MKM34Z256XXX7" selected.
- Target interface speed: 4000 kHz (Fixed)
- VTarget = 3.290V
- InitTarget()
- Readout protection is set and mass erase is disabled. J-Link cannot unprotect the device.
- Found SW-DP with ID 0x0BC11477
- DPIDR: 0x0BC11477
- CoreSight SoC-400 or earlier
- Scanning AP map to find all available APs
- AP[2]: Stopped AP scan as end of AP map has been reached
- AP[0]: AHB-AP (IDR: 0x04770031)
- AP[1]: JTAG-AP (IDR: 0x001C0020)
- Iterating through AP map to find AHB-AP to use
- AP[0]: Skipped. Could not read CPUID register
- AP[1]: Skipped. Not an AHB-AP
- Attach to CPU failed. Executing connect under reset.
- DPIDR: 0x0BC11477
- CoreSight SoC-400 or earlier
- Scanning AP map to find all available APs
- AP[2]: Stopped AP scan as end of AP map has been reached
- AP[0]: AHB-AP (IDR: 0x04770031)
- AP[1]: JTAG-AP (IDR: 0x001C0020)
- Iterating through AP map to find AHB-AP to use
- AP[0]: Skipped. Could not read CPUID register
- AP[1]: Skipped. Not an AHB-AP
- Could not find core in Coresight setup
- InitTarget()
- Readout protection is set and mass erase is disabled. J-Link cannot unprotect the device.
- Found SW-DP with ID 0x0BC11477
- DPIDR: 0x0BC11477
- CoreSight SoC-400 or earlier
- Scanning AP map to find all available APs
- AP[2]: Stopped AP scan as end of AP map has been reached
- AP[0]: AHB-AP (IDR: 0x04770031)
- AP[1]: JTAG-AP (IDR: 0x001C0020)
- Iterating through AP map to find AHB-AP to use
- AP[0]: Skipped. Could not read CPUID register
- AP[1]: Skipped. Not an AHB-AP
- Attach to CPU failed. Executing connect under reset.
- DPIDR: 0x0BC11477
- CoreSight SoC-400 or earlier
- Scanning AP map to find all available APs
- AP[2]: Stopped AP scan as end of AP map has been reached
- AP[0]: AHB-AP (IDR: 0x04770031)
- AP[1]: JTAG-AP (IDR: 0x001C0020)
- Iterating through AP map to find AHB-AP to use
- AP[0]: Skipped. Could not read CPUID register
- AP[1]: Skipped. Not an AHB-AP
- Could not find core in Coresight setup
- ERROR: Failed to connect.
Could not establish a connection to target.

Can you please guide me how to solve this issue?

Thanks,

Rahul

Re: Fail to connect MKM34Z256

Pavel_Hernandez — Tue, 25 Jul 2023 19:10:02 GMT

Hello, my name is Pavel, and I will be supporting your case, I reviewed your information, but could you tell me if you have an EVK board or if this is a custom?

If your board is custom trying to do a mass erase. In case you have an EVK try to follow the steps on the next page.

Resurrecting ‘bricked’ NXP Kinetis Devices | MCU on Eclipse

Best regards,
Pavel

Re: Fail to connect MKM34Z256

rahul_4 — Wed, 26 Jul 2023 07:56:06 GMT

Hi Pavel,

I am using custom board.

Thanks,
Rahul

Re: Fail to connect MKM34Z256

rahul_4 — Wed, 26 Jul 2023 11:29:59 GMT

Hi Pavel,

I am getting below error in MCUXpresso IDE -

Executing flash operation 'Resurrect locked Kinetis device' (Resurrect locked Kinetis device) - Wed Jul 26 16:57:28 IST 2023
Checking MCU info...
Scanning for targets...
Executing flash action...
SEGGER J-Link Commander V7.86 (Compiled Feb 15 2023 17:16:22)
DLL version V7.86, compiled Feb 15 2023 17:14:56
J-Link Command File read successfully.
Processing script file...
J-Link>ExitOnError 1
J-Link Commander will now exit on Error
J-Link>unlock kinetis
J-Link connection not established yet but required for command.
Connecting to J-Link via USB...O.K.
Firmware: J-Link WiFi-V1 compiled Mar 15 2023 11:22:42
Hardware version: V1.00
J-Link uptime (since boot): 0d 00h 06m 31s
S/N: 941000092
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
USB speed mode: High speed (480 MBit/s)
IP-Addr: DHCP (no addr. received yet)
VTref=3.277V
Found SWD-DP with ID 0x0BC11477
Unlocking device...Unlock via debug port is disabled. Unlock failed.
Timeout while unlocking device.
Script processing completed.
Unable to perform operation!
Command failed with exit code 1

Thanks,
Rahul

Re: Fail to connect MKM34Z256

Pavel_Hernandez — Wed, 26 Jul 2023 23:27:01 GMT

Hello, have you ever this available to program the MCU in the past? It seems like the MCU is blocking.

Could you read the FSEC? and share the result.

Production Flash programming best practices for Kinetis K and L MCUs (nxp.com)

This app note shows different methods to do a mass erase.

Best regards,
Pavel