CW10.5 debug problem > Cannot enter background mode. Check connections.

[cavebiker]

I just installed 10.5 and when I try to debug, everything looks good until the end when I get these messages, and then it pukes:

INF: Cannot enter background mode. Check connections. 

ERR: Error Erasing flash of device

ERR: Error occured during Flash programming.

Everything works with CW10.3 with the same setup.

Has anyone else had this issue? If so, how did you solve it?

Thank you in advance,

Tom

[tektronix]

Something weird happened with me. I tried burning to flash the code was burnt sucessfully but now when i try to again connect to the board it says cannot enter in background mode. Can you please help me with that?

I read your blod too but that did not help

Figure is attacjed

[trytohelp]

Hi,

Do you reproduce the problem with a sample project created with the project wizard for your hardware config (Board+interface) ?

The example project will include all default settings.

With this example you should be able to load and flash the application using the debug, Flash File to Target, etc ...

If this example is running fine, this means you've a problem with your project else it could be a hardware problem.

Regards

Pascal

[tektronix]

Hello Pascal

It is hardware problem I erased Sensorship information that was the cause of this behaviour.

[panpwr · Accepted solution]

Something that worked for me:

Debug configurations->in "Target settings" choose your connection and "Edit"->in "target Communication Speed" check the "Delay after reset..."  checkbox, and add some delay (I've added 50mSec).

It allows the chip enough time to reset and enter background mode.

I hope it'll help you as well.

Lior.

[cavebiker]

Hey panpwr,

I went back to the project I originally had this problem with and it was still a problem. I added this delay you speak about and that fixed that problem. SUPER!

Thanks again

Tom

[Jorge_Gonzalez]

Hello Tom:

What target MCU are you trying to program?

What debugging probe are you using, Multilink, Universal Multilink, FX, OSBDM?

If the same setup works with CW10.3, then it sounds to me like the problem might be the drivers.

Please check the next link, especially the post marked as "Correct answer" from tom_thompson:

BDM multilink does not communicate with target board

Next blog could also be useful for you from MCU on Eclipse blog by Erich Styger:

http://mcuoneclipse.com/2012/10/12/fixing-the-usb-drivers/

Hope this helps. If not please provide more details.

Regards!

Jorge González

[cavebiker]

Thanks a ton Jorge for the rapid response.

My target MCU is a Kinetics K20DX

I am using a PE Micro MultiLink universal

I tried downloading new P&E Multilink drivers as the link you provided suggests, I followed all the procedures in the link. It still acts the same and does not work

Thanks again :smileyplain:

Tom

[trytohelp]

Hi Tom,

I've the TWR-K20D72M with a PK20DX256.

I've installed the MCU v10.3 and MCU V10.5.

I've created for each version an example with the wizard for this board/device.

I've a P&E Multilink Universal rev B interface.

I'm able to launch the debugger on MCU v10.3 and MCU V10.5.

Attached you will find the project example I'm using.

Below the driver version used:

hope this will help you.

Pascal

[Rick_Li]

hi Tom,

can you please try to update your driver by following the below steps:

1) connect your P&E Multilink to PC and then right click "My Computer" icon from desktop to launch System Properties, then -> Device Manager

2) Expand item 'Jungo', right click USB Multilink 2.0 (should be this name) to Uninstall it.

3) re-connect your P&E Multilink and let the PC install the software automatically.

4) follow the instruction and select USB Multilink 2.0 11.1.0.0...oem116.inf to install.

if the above does not help, then, I would also recommend updating the firmware of Multilink.

the updater can be get from below link:

P&E Microcomputer Systems

please select "Kinetis" for  "3. select Architecture to support" to upate.

hope it helps!

[cavebiker]

That did it, I'm In!

I guess what I didn't do was un-install the USB Multilink 2.0, I just disabled it.

Thanks a ton Yong Li :smileyhappy: And thanks to all the rest for helping out also.

Freescale Community Rocks

Cheers, Tom