topic Re: FRDM-KL26Z DOA in Kinetis Microcontrollers

FRDM-KL26Z DOA

Frotz — Sat, 20 Mar 2021 16:18:47 GMT

Hi,

Got a FRDM-KL26Z from Digikey and it's dead on arrival. Connecting the device to power via USB reveals no activity. Documentation indicates that there's a demo onboard. No evidence of any such thing with this board. Connecting it to a Mac and running USB Prober reveals that there's no device connected to the Mac. No activity on the board when powered in any way. No MSD. No change when holding down reset.

Digikey was very kind to send a replacement. It's just as useless.

What's the deal?

Thanks,

Andre.

Re: FRDM-KL26Z DOA

mjbcswitzerland — Sat, 20 Mar 2021 16:52:50 GMT

The FRDM-KL26Z is quite an old board and often stocks are also old and still programmed with a version of debugger that gets killed when connecting to MAC or Win 10 (due to a change that the OS manufacturers made on connection of external hard drives).

Updating the debugger firmware should solve it but this needs to be done with an older PC like Win 7.

Take a look at Erich Styger's blogs since he have a number of entries about recovering boards:https://mcuoneclipse.com/

The debugger firmware is available via this link, which also contains some instructions: https://www.nxp.com/design/microcontrollers-developer-resources/ides-for-kinetis-mcus/opensda-serial-and-debug-adapter:OPENSDA?tid=vanOpenSDA

Regards

Mark
[uTasker project developer for Kinetis and i.MX RT]
Contact me by personal message or on the uTasker web site to discuss professional training, solutions to problems or rapid product development requirements

For professionals searching for faster, problem-free Kinetis and i.MX RT 10xx developments the uTasker project holds the key: https://www.utasker.com/kinetis/FRDM-KL26Z.html

Re: FRDM-KL26Z DOA

Frotz — Sat, 20 Mar 2021 22:31:54 GMT

Hi Mark,

I was very careful with the second board to first plug it into power via USB (observing ESD precautions) with no computer in sight using a Petzl headlamp charger and appropriate cable. No demo. No blinking green LED beside the OpenSDA chip indicating some error or even lighting for a moment. No bootloader needed to follow the procedure at: https://www.nxp.com/design/microcontrollers-developer-resources/ides-for-kinetis-mcus/opensda-serial-and-debug-adapter... or Erich's procedure at: https://mcuoneclipse.com/2018/04/10/recovering-opensda-boards-with-windows-10/ Nothing. At the very least applying power to the board should cause the demo to run. I'd say there's no firmware anywhere.

I've had a look at the other threads regarding this board and their experiences do not match mine. All of them had some response from the board initially—a green LED, MSD mounting etc. These two boards never showed the slightest response to power or power+data.

Poking around with an old HP LogicDart shows the OpenSDA SWD port is triggering a reset pulse at 72kHz, there's nothing from the 8MHz oscillator to the KL25, but there is power.

What's the problem?!

Thanks very much,

Andre.

Re: FRDM-KL26Z DOA

mjbcswitzerland — Sun, 21 Mar 2021 07:19:29 GMT

Andre

I have had a FRDM-KL26Z board die on me (too) and ordered a new one but I never tried repairing the failed one.
My suspicion is that the USB power supply failed so you can check the voltage there to see whether there is a problem with the the series diode, for example (couldl be a problem restricted to the OpenSDA part and not the KL26).

I also have freedom boards where the OpenOSD part failed and I keep backups of the 0.5" headers that I can solder in when needed to move to an external debugger.

In your case it would be very unlucky to have two fail (in my case I have probably about all of the approx. 50 different Freedom (and similar style) boards and had around 5 fail in 9 years).

If you don't find a solution it may be worth going for a different board since the KL26 is stone age now and there are more interesting newer parts - also look at a cheap i.MX RT 1010 board which will give you 500MHz for about the same price.

Regards

Mark

P.S It is normal to have a saw tooth signal on the reset line when the KL26 is not programmed. This is its internal watchdog triggering over and over again (each several hundred clock cycles) and driving the reset as output. It is not the OpenSDA debugger doing this.

Re: FRDM-KL26Z DOA

ErichStyger — Sun, 21 Mar 2021 07:40:28 GMT

Hi Andre,

as Mark said: I would connect a 10 pin SWD header on J7 if you happen to have an external debugger (e.g. J-Link: that way you can program/debug the KL26Z, but not sure if this is worth the effort.

You actually don't need to solder the header: just pressing it against the pads should give you a good enough connection to try it out.

I suspect that maybe the K20 is not programmed (not sure why). In that case you can use the same approach and programm/flash the firmware image to it, because then it would not be protected by the bootloader and you can use it as you want.

In any case: I'm wondering what kind of testing they do at the factory?

As Mark said: there are more interesting parts, so you just might need to move on.

I hope this helps,

Erich

Re: FRDM-KL26Z DOA

Frotz — Sun, 21 Mar 2021 19:55:24 GMT

Thanks Mark & Erich,

Turns out the KL26 can be programmed using an external DAP (I used my cheapest in case it blew-up: the MAXDAP from Maxim) and just pressing the SWD header against the pads (super helpful cheap-n-cheerful tip, Erich!) on BOTH boards. Clearly they were not programmed or they "lost" their programming somehow.

There are indeed more interesting parts, but the KL26 is the right size (QFN 32) right peripherals (Self-Cap TSI, SAI & the usual suspects) and right memory/performance (128/16@48MHz) for the application. Mark, if you know of something ARM based with similar specs, I'd love to hear about it!

So how do I now program the KL20? In reading posts of others with damaged FRDM-KL26Z boards I seem to remember that the KL20 can't be reprogrammed via SWD because mass erase is disabled in the chip. At any rate, I've no access to a windows machine!

Thank you both very kindly,

Andre.

Re: FRDM-KL26Z DOA

ErichStyger — Mon, 22 Mar 2021 07:20:49 GMT

Hi Andre,

the K20 can be programmed using the J12 header (see https://mcuoneclipse.files.wordpress.com/2013/12/frdm-kl26z-board-components.png?w=584&h=381 or https://mcuoneclipse.com/2013/12/29/review-new-frdm-kl26z-board/ .

It might be that your K20 is not programmed at all, so you could give it a try, because then the chip is just empty and you can program it.

You can load the same V2.x bootloader do the K20 as the one on the other FRDM boards, see https://mcuoneclipse.com/2016/06/26/how-to-recover-the-opensda-v2-x-bootloader/

Or you can load it with the patched bootloader I have on GitHub, see https://mcuoneclipse.com/2017/10/29/adding-a-delay-to-the-arm-daplink-bootloader/

I hope this helps,

Erich

Re: FRDM-KL26Z DOA

Frotz — Mon, 22 Mar 2021 16:18:43 GMT

Hi Erich,

I had a look at those links yesterday and can't get anything to work.

As far as I can tell the Segger stuff requires a J-Link device, but I don't have one.

Creating a project using the K20DX128xxx5 isn't possible because that chip isn't available. I made a stub project using the MK20DX128xxx10 instead. I used the flash tool in MCUXpresso with the k20dx_frdmkl26z_if_crc.bin from OpenSDAv2.2_DAPLink_frdmkl26z_rev0242.zip downloaded from https://www.nxp.com/design/microcontrollers-developer-resources/ides-for-kinetis-mcus/opensda-serial-and-debug-adapter:OPENSDA?tid=vanOpenSDA#FRDM-KL26Z It seems to have flashed the K20 using the J12 header, but it doesn't seem to change anything. Mac sees no USB device, no MSD etc. I tried to re-flash it and got lots of errors. Both logs are below.

What can be done now?

Thank you very much,

Andre.

Executing flash operation 'Program' (Program file into flash: k20dx_frdmkl26z_if_crc.bin) - Mon Mar 22 12:00:08 EDT 2021

Checking MCU info...

Scanning for targets...

Executing flash action...

MCUXpresso IDE RedlinkMulti Driver v11.3 (Jan 11 2021 15:42:37 - crt_emu_cm_redlink build 9)

( 0) Reading remote configuration

Wc(03). No cache support.

Found chip XML file in /Users/high/Documents/MCUXpressoIDE_11.3.0/workspace/MK20D10_Project/MK20DX128xxx10.xml

( 5) Remote configuration complete

Reconnected to existing LinkServer process.

============= SCRIPT: kinetisconnect.scp =============

Kinetis Connect Script

Connecting to Probe Index = 1

This probe = 1

This TAP = 0

This core = 0

DpID = 2BA01477

Assert NRESET

Reset pin state: 00

Power up Debug

MDM-AP APID: 0x001C0000

MDM-AP System Reset/Hold Reset/Debug Request

MDM-AP Control: 0x0000001C

MDM-AP Status (Flash Ready) : 0x00000032

Part is not secured

MDM-AP Control: 0x00000014

Release NRESET

Reset pin state: 00

MDM-AP Control (Debug Request): 0x00000004

MDM-AP Status: 0x0001003A

MDM-AP Core Halted

============= END SCRIPT =============================

Probe Firmware: DAPLink CMSIS-DAP (ARM)

Serial Number: 040900009c13c22800000000000000000000000097969906

VID:PID: 0D28:0204

USB Path: USB_0d28_0204_fd132120_ff00

Using memory from core 0 after searching for a good core

( 30) Emulator Connected

( 40) Debug Halt

( 50) CPU ID

debug interface type = CoreSight DP (DAP DP ID 2BA01477) over SWD TAP 0

processor type = Cortex-M4 (CPU ID 00000C24) on DAP AP 0

number of h/w breakpoints = 6

number of flash patches = 2

number of h/w watchpoints = 4

Probe(0): Connected&Reset. DpID: 2BA01477. CpuID: 00000C24. Info: <None>

Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.

Content of CoreSight Debug ROM(s):

RBASE E00FF000: CID B105100D PID 04000BB4C4 ROM (type 0x1)

ROM 1 E000E000: CID B105E00D PID 04000BB000 Gen SCS (type 0x0)

ROM 1 E0001000: CID B105E00D PID 04003BB002 Gen DWT (type 0x0)

ROM 1 E0002000: CID B105E00D PID 04002BB003 Gen FPB (type 0x0)

ROM 1 E0000000: CID B105E00D PID 04003BB001 Gen ITM (type 0x0)

ROM 1 E0040000: CID B105900D PID 04000BB9A1 CSt TPIU type 0x11 Trace Sink - TPIU

NXP: MK20DX128xxx10

DAP stride is 4096 bytes (1024 words)

XML Error - no license-type XML file 'crt_common.xme' on path.

note - part information contained no product license-type data

Inspected v.2 On chip Kinetis Flash memory module FTFL_2K.cfx

Image 'Kinetis SemiGeneric Dec 17 2020 10:03:38'

Opening flash driver FTFL_2K.cfx

Sending VECTRESET to run flash driver

Flash variant 'K 24 FTFL Generic 2K' detected (128KB = 64*2K at 0x0)

Closing flash driver FTFL_2K.cfx

( 65) Chip Setup Complete

Connected: was_reset=true. was_stopped=true

( 70) License Check Complete

Loading 'k20dx_frdmkl26z_if_crc.bin' Binary 0x00000000 len 0x17C00

Opening flash driver FTFL_2K.cfx (already resident)

Sending VECTRESET to run flash driver

Flash variant 'K 24 FTFL Generic 2K' detected (128KB = 64*2K at 0x0)

Writing 97280 bytes to address 0x00000000 in Flash

1 of 1 ( 0) Writing sectors 0-47 at 0x00000000 with 97280 bytes

( 0) at 00000000: 0 bytes - 0/97280

( 2) at 00000000: 2048 bytes - 2048/97280

( 4) at 00000800: 2048 bytes - 4096/97280

( 6) at 00001000: 2048 bytes - 6144/97280

( at 00001800: 2048 bytes - 8192/97280

( 10) at 00002000: 2048 bytes - 10240/97280

( 12) at 00002800: 2048 bytes - 12288/97280

( 14) at 00003000: 2048 bytes - 14336/97280

( 16) at 00003800: 2048 bytes - 16384/97280

( 18) at 00004000: 2048 bytes - 18432/97280

( 21) at 00004800: 2048 bytes - 20480/97280

( 23) at 00005000: 2048 bytes - 22528/97280

( 25) at 00005800: 2048 bytes - 24576/97280

( 27) at 00006000: 2048 bytes - 26624/97280

( 29) at 00006800: 2048 bytes - 28672/97280

( 31) at 00007000: 2048 bytes - 30720/97280

( 33) at 00007800: 2048 bytes - 32768/97280

( 35) at 00008000: 2048 bytes - 34816/97280

( 37) at 00008800: 2048 bytes - 36864/97280

( 40) at 00009000: 2048 bytes - 38912/97280

( 42) at 00009800: 2048 bytes - 40960/97280

( 44) at 0000A000: 2048 bytes - 43008/97280

( 46) at 0000A800: 2048 bytes - 45056/97280

( 98) at 0000B000: 51200 bytes - 96256/97280

(100) at 00017800: 2048 bytes - 98304/97280

Sectors written: 23, unchanged: 25, total: 48

Erased/Wrote sector 0-47 with 97280 bytes in 3009msec

Closing flash driver FTFL_2K.cfx

(100) Finished writing Flash successfully.

Flash Write Done

Loaded 0x17C00 bytes in 3236ms (about 30kB/s)

Reset target (system)

Starting execution using system reset

state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access

error closing down debug session - Nn(05). Wire ACK Fault in DAP access

Executing flash operation 'Program' (Program file into flash: k20dx_frdmkl26z_if_crc.bin) - Mon Mar 22 12:04:03 EDT 2021

Checking MCU info...

Scanning for targets...

Executing flash action...

MCUXpresso IDE RedlinkMulti Driver v11.3 (Jan 11 2021 15:42:37 - crt_emu_cm_redlink build 9)

( 0) Reading remote configuration

Wc(03). No cache support.

Found chip XML file in /Users/high/Documents/MCUXpressoIDE_11.3.0/workspace/MK20D10_Project/MK20DX128xxx10.xml

( 5) Remote configuration complete

Reconnected to existing LinkServer process.

============= SCRIPT: kinetisconnect.scp =============

Kinetis Connect Script

Connecting to Probe Index = 1

This probe = 1

This TAP = 0

This core = 0

DpID = 2BA01477

Assert NRESET

Reset pin state: 00

Power up Debug

MDM-AP APID: 0x001C0000

MDM-AP System Reset/Hold Reset/Debug Request

MDM-AP Control: 0x0000001C

MDM-AP Status (Flash Ready) : 0x00000032

Part is not secured

MDM-AP Control: 0x00000014

Release NRESET

Reset pin state: 00

MDM-AP Control (Debug Request): 0x00000004

MDM-AP Status: 0x00000032

MDM-AP Core Halt Failed

MDM-AP Control (Debug Request): 0x00000004

MDM-AP Status: 0x00000032

MDM-AP Core Halt Failed

MDM-AP Control (Debug Request): 0x00000004

MDM-AP Status: 0x00000032

MDM-AP Core Halt Failed

============= END SCRIPT =============================

Probe Firmware: DAPLink CMSIS-DAP (ARM)

Serial Number: 040900009c13c22800000000000000000000000097969906

VID:PID: 0D28:0204

USB Path: USB_0d28_0204_fd132120_ff00

Using memory from core 0 after searching for a good core

On debug connection - reset using system reset

Warning - processor did not halt - gave up waiting

( 30) Emulator Connected

Cannot halt processor

Request debug reset of DAP

( 40) Debug Halt

( 50) CPU ID

debug interface type = CoreSight DP (DAP DP ID 2BA01477) over SWD TAP 0

processor type = Cortex-M4 (CPU ID 00000C24) on DAP AP 0

number of h/w breakpoints = 6

number of flash patches = 0

number of h/w watchpoints = 0

Probe(0): Connected&Reset. DpID: 2BA01477. CpuID: 00000C24. Info: <None>

Debug protocol: SWD. RTCK: Disabled. Vector catch: Enabled.

Content of CoreSight Debug ROM(s):

RBASE E00FF000: CID B105100D PID 04000BB4C4 ROM (type 0x1)

ROM 1 E000E000: CID B105E00D PID 04000BB000 Gen SCS (type 0x0)

ROM 1 E0001000: CID B105E00D PID 04003BB002 Gen DWT (type 0x0)

ROM 1 E0002000: CID B105E00D PID 04002BB003 Gen FPB (type 0x0)

ROM 1 E0000000: CID B105E00D PID 04003BB001 Gen ITM (type 0x0)

ROM 1 E0040000: CID B105900D PID 04000BB9A1 CSt TPIU type 0x11 Trace Sink - TPIU

NXP: MK20DX128xxx10

DAP stride is 4096 bytes (1024 words)

XML Error - no license-type XML file 'crt_common.xme' on path.

note - part information contained no product license-type data

Inspected v.2 On chip Kinetis Flash memory module FTFL_2K.cfx

Image 'Kinetis SemiGeneric Dec 17 2020 10:03:38'

Opening flash driver FTFL_2K.cfx

Sending VECTRESET to run flash driver

Warning - processor did not halt - gave up waiting

target failed to halt after flash driver reset - (null)

flash start - disabling IRQs failed - rc Ep(08). Cannot access core regs when target running.

chip initialization failed - Ep(08). Cannot access core regs when target running.

failed to initialize flash driver FTFL_2K.cfx

( 65) Chip Setup Complete

(100) Target Connection Failed

Unable to perform operation!

Command failed with exit code 1

Re: FRDM-KL26Z DOA

Frotz — Mon, 22 Mar 2021 16:22:26 GMT

One more thing:

Should have mentioned that first flash was with USB connected to KL26's USB port and second flash was with USB connected to K20's USB port.

Re: FRDM-KL26Z DOA

ErichStyger — Mon, 22 Mar 2021 18:19:06 GMT

imho you have to set the device to the K20DX128: the 100 MHz version is different.

Not sure what else you can do. But in any case I recommend that you get a J-Link (the EDU mini is just $20 and allows you to work with virtually any ARM Cortex on this planet, so can save you from other difficult situations too.

The other option really could be that you get access to a windows machine: It really could be that somehow your machine does not recognize the board. With a Window machine you can at least check if the OpenSDA on the board would be still present.

Re: FRDM-KL26Z DOA

mjbcswitzerland — Mon, 22 Mar 2021 18:34:17 GMT

Hi Erich

>>..really could be that you get access to a windows machine

To a MAC user this may be like you asking them to make a pact with the devil. And don't mention William Gates since to a MAC users that IS the devil...

Regards

Mark

Re: FRDM-KL26Z DOA

ErichStyger — Mon, 22 Mar 2021 19:02:07 GMT

Hi Mark,

No pact with the devil at all, just having a friend somewhere who allows you to plug in that board. I would offer my machine at least.

The reality with these things is imho: the more diversity you have (machine types, debug probes, ...), the better.

Erich

Re: FRDM-KL26Z DOA

Frotz — Mon, 22 Mar 2021 21:05:55 GMT

Hi Erich & Mark,

Visiting a friend with a windows PC is impossible due to restrictions here & the personal safety of myself and my friends with PC's. I've been working on this for over a week now—most of the time spent quarantining stuff from DigiKey and it's REALLY frustrating and disappointing.

That file I downloaded "OpenSDAv2.2_DAPLink_frdmkl26z_rev0242", is it the latest version of the K20 OpenSDA program? If not, perhaps I could try again with something more current.

Is there any way to get the right chip in MCUXpresso. I can d/l older versions from NXP...

Are you able to test a FRDM-KL26Z loaded with the same OpenSDA code on a Mac?

Is there some other way to get the .bin into the K20 w/o spending massive amounts of time on this?

Thank you very much,

Andre.

Re: FRDM-KL26Z DOA

mjbcswitzerland — Mon, 22 Mar 2021 23:18:01 GMT

I have two FRDM-KL26Zs in my draw. One died on me so doesn't do anything (no LEDs but 5V arrives on the USB)
The other works (still) and this is the information I get from the OpenSDA version installed on it:

Board Name is: FRDM-KL26Z
MicroBoot Kernel Version is: 1.05
Bootloader Version is: 1.09
Installed Application: PEMicro FRDM-KL26Z Mass Storage/Debug App
Application Version is: 1.18
DUID is: E9F33938-8F7881E0-3762E817-B779E678
EUID is: F171A239-1DD2876E-18620A0C-958268D6
TUID is: 74823938-47328207-3755980C-B990E678
TOA is: 86B6E505-FA9781CB-1D79DB3C-C6787CF0
TOA2 is: 86B6E505-871683E8-8B5E2BB1-6ABE6B74
SUID is: 86B6E505-6D47969C-37239804-8003EC65

Is has what looks like a boot loader and then an application (the OpenSDA used by the actual board, which can normally be exchanged when the USB is connected with the reset button held down, to starts its boot loader). Doing this is what will cause the the main problem if done on MAC or post Win 8.1 but once the OpenSDA application can been installed (using Win 7 for example) it is OK (as long as the reset is not held when powering again).

I thought that if I just uploaded an image from the K20 and sent it to you you could just load it and have all but it looks like this is not possible because they have (permanently) secured the chip (presumably to protect the boot loader code) and so it is not possible to connect or read out the content (possibly a mass erase would work but it would then lose the program before it could be copied out).
If you can in fact connect to the K20 it means that it was never programmed.
If you can connect to the KL26 on the other JTAG/SWD connector you don't need the OpenSDA and can just use that instead (you just lose the OpenSDA's VCOM for the UART).

Can you connect and then use your available programmer/debugger to start working with your board (without the onboard debugger)?

Regards

Mark

(using WIn 7

Re: FRDM-KL26Z DOA

ErichStyger — Tue, 23 Mar 2021 06:13:49 GMT

Hi Mark,

I thought that if I just uploaded an image from the K20 and sent it to you you could just load it and have all but it looks like this is not possible because they have (permanently) secured the chip (presumably to protect the boot loader code) and so it is not possible to connect or read out the content (possibly a mass erase would work but it would then lose the program before it could be copied out).

The OpenSDA V1.x (which is on that FRDM-KL26Z) has read-out protection enabled and mass erase disabled, so you won't be able to read-out the chip or erase it to regain access. This is different for OpenSDA V2.x as there the bootloader is open.

Erich

Re: FRDM-KL26Z DOA

mjbcswitzerland — Tue, 23 Mar 2021 07:16:05 GMT

Erich

In fact the debugger states that it was permanently protected and mass erase disabled but asked "would I like to try anyway".
In any case there is a not a lot to do because not even erasing and installing OpenSDA V2 is possible (without replacing the K20).

Regards

Mark

Off-topic: is it correct that your TinyK22 can be provided by PCBway and that you receive royalties? Private message me maybe.

Re: FRDM-KL26Z DOA

Frotz — Tue, 23 Mar 2021 16:00:04 GMT

Update:

The K20 can't be erased with MCUXpresso now so there's no point sending me anything. (Except a fully functional board, hint, hint NXP.)

Any ideas about my questions in the post above from yesterday?

Thank you,

Andre.

Re: FRDM-KL26Z DOA

Frotz — Tue, 23 Mar 2021 16:01:04 GMT

Here's the log when trying a mass erase:

Executing flash operation 'Erase' (Erase flash) - Tue Mar 23 11:46:59 EDT 2021

Checking MCU info...

Scanning for targets...

Executing flash action...

MCUXpresso IDE RedlinkMulti Driver v11.3 (Jan 11 2021 15:42:37 - crt_emu_cm_redlink build 9)

( 0) Reading remote configuration

Wc(03). No cache support.

Found chip XML file in /Users/high/Documents/MCUXpressoIDE_11.3.0/workspace/MK20D10_Project/MK20DX128xxx10.xml

( 5) Remote configuration complete

Reconnected to existing LinkServer process.

============= SCRIPT: kinetisconnect.scp =============

Kinetis Connect Script

Connecting to Probe Index = 1

This probe = 1

This TAP = 0

This core = 0

DpID = 2BA01477

Assert NRESET

Reset pin state: 00

Power up Debug

MDM-AP APID: 0x001C0000

MDM-AP System Reset/Hold Reset/Debug Request

MDM-AP Control: 0x0000001C

MDM-AP Status (Flash Ready) : 0x00000032

Part is not secured

MDM-AP Control: 0x00000014

Release NRESET

Reset pin state: 00

MDM-AP Control (Debug Request): 0x00000004

MDM-AP Status: 0x00000032

MDM-AP Core Halt Failed

MDM-AP Control (Debug Request): 0x00000004

MDM-AP Status: 0x00000032

MDM-AP Core Halt Failed

MDM-AP Control (Debug Request): 0x00000004

MDM-AP Status: 0x00000032

MDM-AP Core Halt Failed

============= END SCRIPT =============================

Probe Firmware: DAPLink CMSIS-DAP (ARM)

Serial Number: 040900009c13c22800000000000000000000000097969906

VID:PID: 0D28:0204

USB Path: USB_0d28_0204_fd132120_ff00

Using memory from core 0 after searching for a good core

( 30) Emulator Connected

Cannot halt processor

Request debug reset of DAP

( 40) Debug Halt

( 50) CPU ID

debug interface type = CoreSight DP (DAP DP ID 2BA01477) over SWD TAP 0

processor type = Cortex-M4 (CPU ID 00000C24) on DAP AP 0

number of h/w breakpoints = 6

number of flash patches = 0

number of h/w watchpoints = 0

Probe(0): Connected&Reset. DpID: 2BA01477. CpuID: 00000C24. Info: <None>

Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.

Content of CoreSight Debug ROM(s):

RBASE E00FF000: CID B105100D PID 04000BB4C4 ROM (type 0x1)

ROM 1 E000E000: CID B105E00D PID 04000BB000 Gen SCS (type 0x0)

ROM 1 E0001000: CID B105E00D PID 04003BB002 Gen DWT (type 0x0)

ROM 1 E0002000: CID B105E00D PID 04002BB003 Gen FPB (type 0x0)

ROM 1 E0000000: CID B105E00D PID 04003BB001 Gen ITM (type 0x0)

ROM 1 E0040000: CID B105900D PID 04000BB9A1 CSt TPIU type 0x11 Trace Sink - TPIU

NXP: MK20DX128xxx10

DAP stride is 4096 bytes (1024 words)

XML Error - no license-type XML file 'crt_common.xme' on path.

note - part information contained no product license-type data

Inspected v.2 On chip Kinetis Flash memory module FTFL_2K.cfx

Image 'Kinetis SemiGeneric Dec 17 2020 10:03:38'

Opening flash driver FTFL_2K.cfx

Sending VECTRESET to run flash driver

Warning - processor did not halt - gave up waiting

target failed to halt after flash driver reset - (null)

flash start - disabling IRQs failed - rc Ep(08). Cannot access core regs when target running.

chip initialization failed - Ep(08). Cannot access core regs when target running.

failed to initialize flash driver FTFL_2K.cfx

( 65) Chip Setup Complete

(100) Target Connection Failed

Unable to perform operation!

Command failed with exit code 1

Re: FRDM-KL26Z DOA

Frotz — Tue, 06 Apr 2021 00:25:16 GMT

Hello Erich,

I bought a Segger J-Link and tried it with the board and got nowhere useful. A log follows. Any ideas?

Thanks,

Andre.

- Connecting via USB to probe/ programmer device 0

- Probe/ Programmer firmware: J-Link EDU Mini V1 compiled Nov 12 2020 13:31:42

- Device "MK20DX128XXX5" selected.

- Target interface speed: 4000 kHz (Fixed)

- VTarget = 3.121V

- InitTarget()

- Timeout while halting CPU.

- Found SW-DP with ID 0x2BA01477

- DPIDR: 0x2BA01477

- 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: 0x24770011)

- AP[1]: JTAG-AP (IDR: 0x001C0000)

- Iterating through AP map to find AHB-AP to use

- AP[0]: Core found

- AP[0]: AHB-AP ROM base: 0xE00FF000

- CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)

- Found Cortex-M4 r0p1, Little endian.

- FPUnit: 6 code (BP) slots and 2 literal slots

- CoreSight components:

- ROMTbl[0] @ E00FF000

- ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB000 SCS

- ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT

- ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB

- ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM

- ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU

- Executing init sequence ...

- ERROR: Failed to connect.

Could not perform custom init sequence.

Re: FRDM-KL26Z DOA

Frotz — Tue, 13 Apr 2021 15:56:43 GMT

Hi,

I've been trying all sorts of things to get this board to work (and its replacement) and have found the DAP to be "flakey." I was able to get the J-Link to halt the K20, erase the flash and re-program it using Segger's FRDM-KL26Z OpenSDA firmware—which locked the chip, but still the onboard DAP does not present itself as useable anywhere and the green LED does not work. I only got this far on one of the two boards, the other is not at all cooperative. And I was only able to get the one board to cooperate for a few minutes and since has been just as useless as the other.

It would seem that the KL26 on each board was not programmed b/c the onboard K20 DAP is unreliable at best.

Can someone at NXP comment on this and have a look at the picture below showing lot#, S/N etc let me know how I can get a FRDM-KL26Z that is in proper condition?

Thank you,

Andre.