Daplink firmware compatibility with K64 device family

[Asad_Khan]

Hi,

I have designed a custom board using NXP MK64FX512 MCU and included the OpenSDA circuit from the FRDM-K64F board.
For OpenSDA, I have flashed the latest FRDM-K64F DAPlink bootloader and target firmware interface files, as mentioned on the daplink.io website.

After flashing the bootloader file, I am able to copy and paste the firmware interface file on Mk20 MCU, but while debugging on MCUXpresso it is giving me the error:>
" Unable to connect wire for probe index 1" Error: Wire Ack Fault - target connected?

I also checked the hardware, everything looks ok and there is no issue with the hardware.

So, I just want to confirm whether the FRDM-K64F Daplink bootloader and firmware interface files will work with target MCU MK64FX512xx or not! The bootloader and firmware interface files are device specific? Because the FRDM-K64F board has a different target device MK64FN1Mxx.

Thanks,
Mohammad Asad Khan

[ErichStyger]

The 'copy and paste' part depends on the target MCU, so is specific, because it needs to know about the memory map and flash algos.

The debugging part itself does not (or should not) depend on the OpenSDA firmware, as this knowledge is on the host/debugger side.

Were you able to debug initially? I think with your drag&drop you screwed up the target, so it constantly resets, and the OpenSDA K20 is not able to take over control.

Do you still have a debug header? If so, you could try this: https://mcuoneclipse.com/2021/05/20/recovering-cortex-m-microcontroller-with-a-power-glitch/

I hope this helps,

Erich

[Asad_Khan]

Hi Erich,
I have downloaded the firmware files from this link.

https://www.nxp.com/design/software/development-software/sensor-toolbox-sensor-development-ecosystem...

Thanks,
Mohammad Asad Khan

[ErichStyger]

What firmware are you using?

Keep in mind that the P&E and SEGGER firmware do not allow you to use it with your custom hardware. You would have to use the ARM DAPLink one: https://github.com/ARMmbed/DAPLink

[Asad_Khan]

Yes, I am using the DAPlink firmware only. But it is not mentioned anywhere whether it will support K64 family devices or it is a single device-specific firmware.

[ErichStyger]

So here is how I can use the DAPLink bootloader and firmware with my K22FX:

- using v0257 from https://github.com/ARMmbed/DAPLink/releases

- programmed 0257_k20dx__0x0000.bin at address 0x0

- programmed 0257_k20dx_frdmk20dx_0x8000.bin at address 0x8000

- debugging my application using MCUXpresso IDE 11.6.0, the DAPLink gets recognized as LinkServer connection

Note:

- I'm not using the MSD Drag&Drop programming, so I don't care that the firmware is for K20

- I'm not actively using the DAPLink because it is so slow. But if you have nothing else available, it is better than nothing

I hope this helps,

Erich

[Asad_Khan]

Hi Erich,

Thanks for the reply.
So, it means the FRDM-K64F OpenSDA firmware interface will work only with its target device (MK64FN1Mxx) and for all K64F family devices.

If I connect the external debugger with the target MCU then I can able to debug. In my case, the external debugger is Multilink universal from PEmicro.
Thanks,
Mohammad Asad Khan

[ErichStyger]

it all depends what you use as 'firmware' on top of the MSD bootloader: if that firmware is device specific, then it only works for that given device.