Try
kinetis mdm halt
for the case if reset is not properly connected on the board.
And if it fails, proceed as suggested in the message:
**** If MCU cannot be halted, it is likely secured and running ****
**** in RESET/WDOG loop. Issue 'kinetis mdm mass_erase' ****
There is no point in sending more detailed logs.
On 04.12.2017 17:16, [email protected] wrote:
The log is normal for a blank kinetis device.
You've configured reset correctly. Just continue.
So either issue 'reset init' command to see target halted
or start programming by 'program your_shiny_fw.elf'
When I try 'reset init' I get this (I've appended the -d3 log as well)
--------------------------------------------------------------------------------
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Open On-Chip Debugger
>reset init
**** Your Kinetis MCU is probably locked-up in RESET/WDOG loop. ****
**** Common reason is a blank flash (at least a reset vector). ****
**** Issue 'kinetis mdm halt' command or if SRST is connected ****
**** and configured, use 'reset halt' ****
**** If MCU cannot be halted, it is likely secured and running ****
**** in RESET/WDOG loop. Issue 'kinetis mdm mass_erase' ****
SWD DPIDR 0x5ba02477
SWD DPIDR 0x5ba02477
AP write error, reset will not halt
SWD DPIDR 0x5ba02477
TARGET: kx.cpu - Not halted
in procedure 'reset'
in procedure 'ocd_bouncer'
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
