topic Re: Freedom K64F: starting without debugger? in Kinetis Microcontrollers

Freedom K64F: starting without debugger?

davenadler — Thu, 22 Dec 2016 14:36:37 GMT

I have an application running on Freedom K64F (using Segger JLink, SDK2.1).
Application is stored in flash and runs absolutely fine under debugger.

I'd like the board to run the application when powered up without the debugger - but nothing happens.
I disabled EZport per Erich's blog https://mcuoneclipse.com/

Traces are cut to onboard debugger as detailed here: https://developer.mbed.org/questions/4658/FRDM-K64F-alternative-JTAG-Debugger/

So what am I missing?
Thanks!
Best Regards, Dave

Re: Freedom K64F: starting without debugger?

BlackNight — Thu, 22 Dec 2016 19:50:23 GMT

I would have a look at the RESET and NMI lines (is NMI disabled?).

The Reset line should have a pull-up (say 10k) with a capacitor (say 1uF).

I hope this helps,

Erich

Re: Freedom K64F: starting without debugger?

davenadler — Thu, 22 Dec 2016 21:04:02 GMT

I disabled NMI in FOPT as well, same behavior (hope I did this right):

Not sure I understand about the RESET line - I'm using the K64F Freedom board; shouldn't this be already set up?

Thanks Erich, Best Regards, Dave

Re: Freedom K64F: starting without debugger?

BlackNight — Fri, 23 Dec 2016 06:56:17 GMT

Yes, on the FRDM-K64F the rest line has this already. That comment was a general one in case a custom board is used.

Re: Freedom K64F: starting without debugger?

davenadler — Tue, 27 Dec 2016 13:35:05 GMT

The problem was caused by semi-hosting. This project used -specs=rdimon.specs to linker to support SWO output debug connection. The library support for SWO is too lame to notice no debugger attached, and hangs in the startup code awaiting a debugger connection prior entering main. Oddly, IIRC I used semi-hosting for a couple products I developed using NXP LPC11C14 and LPC Xpresso, and I don't recall seeing this problem before. Anyway, just adjust the linker options:
- Remove: -specs=rdimon.specs
- Add: -specs=nosys.specs

Hope that helps someone else,
Best Regards, Dave