I am a newbie and have a lot of doubts, and I would very much like to get the help of your seniors.
I am using the MK20DX128VFM5 chip, and when I connect the computer directly through USB, the computer does not recognize any device, and when I press the reset button to enter, there is no phenomenon.
So I started measuring the REST-B pin of the chip, and I had applied it high, but the chip would force the signal low. When I change a chip that someone else has used, press and hold the reset button to enter, a high level signal appears on the REST-B pin, and the computer can recognize the device and display 'BOOTLOADER'.But when I drag the firmware, the device still doesn't respond.
What do I need to do to make my computer recognize the correct device and be able to refresh the program? I'm not sure if I overlooked some important steps during the operation.
Anyone who can provide answers or documentation would be appreciated.
已解决! 转到解答。
Hi @zhaofan123 ,
your device does not have a USB bootloader on it in the ROM. You need to program it first with an application running the USB stack.
I hope this helps,
Erich
Hi @zhaofan123 ,
your device does not have a USB bootloader on it in the ROM. You need to program it first with an application running the USB stack.
I hope this helps,
Erich
sure!
here you go:
https://github.com/ErichStyger/mcuoneclipse/tree/master/Examples/KDS/tinyK20
https://github.com/ErichStyger/mcuoneclipse/tree/master/Examples/KDS/FRDM-K20D50M
The tinyK20 board is basically a stripped down circuit from the FRDM boards, see
https://mcuoneclipse.com/2015/05/17/tinyk20-open-source-arm-debuguniversal-board-first-prototypes/
You need initially a debug probe with SWD.
See for example https://mcuoneclipse.com/2018/03/03/flash-resident-usb-hid-bootloader-with-the-nxp-kinetis-k22-micro...
For example the MCU-Link:
https://mcuoneclipse.com/2020/11/29/new-mcu-link-debug-probe-from-nxp/
Or the Pro version:
https://mcuoneclipse.com/2021/10/17/new-mcu-link-pro-debug-probe-with-energy-measurement/
You find them on Mouser/etc or directly from NXP.com
You can use the MCUXpresso IDE, see https://mcuoneclipse.com/2017/05/06/using-eclipse-to-program-binary-files-to-an-embedded-target/
Or you can use the LinkServer command line utility, see https://mcuoneclipse.com/2023/05/14/linkserver-for-microcontrollers/
I read your blog, then added K20 and was able to query it successfully.
But as I read this,
I have some doubts:
I don't know what 'implicit wildcards' is.My device is MK20DX128VFM5 and my board is Analog Devices' EVAL-ADICUP3029, so how exactly should I enter instructions when entering?
What matters in this case is the device, not the board.
The board would be only relevant if you have external RAM or FLASH, as that would be board specific.
Implicit wildcards means that you did not specify the full device/board tuple.
I just installed the LinkServer command line utility and tried to follow your blog to use it. But when I enter the command shown in the figure below, the computer shows the supported devices as I thought, and I can't query any information about the K20.
See https://mcuoneclipse.com/2023/07/30/using-legacy-devices-with-linkserver/
And what file types you can load depends not on the IDE, but on the debug probe. See https://mcuoneclipse.com/2017/05/06/using-eclipse-to-program-binary-files-to-an-embedded-target/