Open leandrolanzieri opened 3 years ago
I still have this problem while running the demo apps in the example folder.
Error message like this:
Info : Using CMSIS-DAPv2 interface with VID:PID=0x0d28:0x0204, serial=02400b0131754e45003a0018948500316461000097969900
Info : CMSIS-DAP: SWD Supported
Info : CMSIS-DAP: FW Version = 0254
Info : CMSIS-DAP: Serial# = 02400b0131754e45003a0018948500316461000097969900
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 0 SWDIO/TMS = 1 TDI = 0 TDO = 0 nTRST = 0 nRESET = 1
Info : Connecting under reset
Info : CMSIS-DAP: Interface ready
Info : clock speed 1000 kHz
Info : SWD DPIDR 0x2ba01477
Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : kx.cpu: external reset detected
Info : MDM: Chip is unsecured. Continuing.
Info : starting gdb server for kx.cpu on 0
Info : Listening on port 37369 for gdb connections
TargetName Type Endian TapName State
-- ------------------ ---------- ------ ------------------ ------------
0* kx.cpu cortex_m little kx.cpu reset
Info : MDM: Chip is unsecured. Continuing.
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000a28 msp: 0x1fff0200
Info : Kinetis MK64FN1M0xxx12 detected: 2 flash blocks
Info : 2 PFlash banks: 1024k total
auto erase enabled
wrote 126976 bytes from file /home/newton/Desktop/RIOT/examples/micropython/bin/frdm-k64f/micropython.elf in 12.361661s (10.031 KiB/s)
Info : kx.cpu: external reset detected
Error: timed out while waiting for target halted
target halted due to debug-request, current mode: Handler PendSV
xPSR: 0x6100000e pc: 0x00001122 msp: 0x1fff01a0
Error: error executing cortex_m crc algorithm
verified 126152 bytes in 21.310106s (5.781 KiB/s)
Info : MDM: Chip is unsecured. Continuing.
shutdown command invoked
Done flashing
Description
When trying to flash any application on the
frdm-k64f
board, I am getting which seems to be an error on the CRC check of the binary. If left alone until timeout the output is:If this check is aborted by me pressing
Ctrl+C
, I get a bunch of errors. Afterwards the application seems to be flash in the MCU all the same.For most of the flashing processes I had to follow the "Solution 1" in the board documentation, by pressing the reset button.
Expected results
Flashing succeeds
Actual results
Flashing fails with:
Versions