OpenSDA on custom board based on FRDM-K64 reference design

[Asad_Khan]

Hi,

I have designed a custom board using references from the FRDM-64 development board. I copied the complete circuit for the OpenSDA section on my board. Going ahead to work with OpenSDA, I am able to program K20DX128VFM5 MCU for DAP LINK bootloader firmware. Now the issue is, that MCU is not able to detect on Host PC as an MSD after flashing the bootloader firmware. Need your help to resolve the issue. Please suggest if I am doing something wrong.

Regards,

Mohammad Asad Khan

[ErichStyger]

I would verify if the MCU itself plus the USB circuit is working.

I do have a few USB applications (Kinetis Design Studio) available on GitHub, maybe you could try them if they run properly. The advantage is that you can debug them too, so you could find out what could be wrong with your circuit:

https://github.com/ErichStyger/mcuoneclipse/tree/master/Examples/KDS/FRDM-K20D50M

I hope this helps,

Erich

[Asad_Khan]

Hi,

After a few trials, the bootloader file is successfully loaded on OpenSDA MCU and I am able to copy and paste firmware interface files to the OpenSDA MCU. In my custom hardware, the target processor I have used is MK64FX512xx. For OpenSDA, I am using FRDM-K64F bootloader and firmware interface files downloaded from Daplink.io.

Now coming to the debugging using the OpenSDA interface, MCUXpresso 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.

Now, 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