topic How do I resolve 'Can not enter background mode'? in Kinetis Design Studio

How do I resolve 'Can not enter background mode'?

SAS_Andrew — Sun, 01 Feb 2015 04:16:42 GMT

I have a K20DN512VLQ10 on a custom board and I'm attempting to debug the default Kinetis Design Studio project via a P&E Multilink Universal on Windows 8.1.

When I create a default project for the chip and immediately debug it, the target resets, and this is the output I get in the console:

P&E GDB Server, Version 5.13.02.00

Loading library C:\Freescale\KDS_2.0.0\eclipse\plugins\com.pemicro.debug.gdbjtag.pne_1.1.7.201410171532\win32\gdi\unit_ngs_arm_internal.dll ... Done.

Command line arguments: -device=K20DN512 -startserver -singlesession -serverport=7224 -interface=USBMULTILINK -speed=5000 -usejtag -port=USB1 -USE_CYCLONEPRO_RELAYS=0 -FORCE_MASS_ERASE=0

Device selected is k20dn512

User Specified Hardware Selection : Interface=USBMULTILINK and Port=USB1

Connecting to target.

P&E Interface detected - Flash Version 6.10

Can not enter background mode .

Unable to initialize PEDebug.

PE-ERROR: Failed to Initialize Target

Server running on 127.0.0.1:7224

Connection from "127.0.0.1" via 127.0.0.1

PE-ERROR: Target is not connected

Disconnected from "127.0.0.1" via 127.0.0.1

Target Disconnected.

I have made two changes to the debug configuration:

Unchecked 'Use SWD reduced pin protocol for communications' as the board has a 20-pin JTAG port.
Changed device name from 'K20DN512M10' to 'K20DN512' as the package identifier for the chip is 'LQ', not 'Mx'.

Trying different combinations of these settings (using SWD, not using SWD, using different K20 device names) has had no effect. Interestingly, after the 'Can not enter background mode' message, two unprintable characters are echoed to the console (both 0x07).

I've searched this forum for solutions without success. Attached is an image of my debug configuration. Is there a specific configuration setting I'm missing?

Thanks.

Re: How do I resolve 'Can not enter background mode'?

Carlos_Mendoza — Wed, 04 Feb 2015 02:49:42 GMT

Hi Andrew Perkins,

Take a look to the following post created by our colleague Erich Styger, it mentions a check list and provides some hints that might help you resolve the issue:

Debugging Failure: Check List and Hints | MCU on Eclipse

Please also review the below document where you can find information about the 20-pin header debug interface Implementation (section 2.1.5.3 Debug interface) and make sure your connections are correct:

http://cache.freescale.com/files/32bit/doc/quick_ref_guide/KQRUG.pdf

Hope it helps!

Best Regards,

Carlos Mendoza

Technical Support Engineer

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

Re: How do I resolve 'Can not enter background mode'?

tharonhall — Thu, 05 Feb 2015 14:57:03 GMT

Erich just plain rocks. I have shared the link to his debugging page to LinkedIn, including several groups. It's as good a "how to get debugging working" list as I have ever seen.

Re: How do I resolve 'Can not enter background mode'?

tharonhall — Thu, 05 Feb 2015 15:03:29 GMT

I hate to ask this, but it is good to check assumptions. Since it is your own target board (correct?), are you confidence your hardware is good?

We recently brought up our own K22F board. I could program the code and start execution, but when we tried to setup the watchdog the system reset. It turned out that while we didn't need Vbat for the RTC just yet, we hadn't installed the Schottky diode array that switched the chips Vbat between the battery and Vcc. When we did, everything worked fine. I could understand accessing the RTC causing a problem, but not so much the Watchdog.

Just goes to show that one of the challenges of embedded is there are lots and lots and lots of things that have to be "just right" or "she no worky".

Best of luck regardless. Getting a new target board up is always a challenge. I am a huge fan of bringing a new system up in stages, but sooner or later you have to cross your fingers, flip the switch, and hope the micro feels like talking to you. :smileywink: