topic Re: The BDM has been re-enabled in CodeWarrior for MCU

The BDM has been re-enabled

goelectrons — Thu, 22 Apr 2010 08:22:33 GMT

I have been developing for 9S12DT256 for several years using CodeWarrior Pro and a P&E Micro USB-ML-12 BDM module version C. All of the drivers for the BDM are up to date as well as the firmware. I don't have the version of CodeWarrior available right now but I can provide it.

As soon as the PLL is enabled (first time I have ever used it) the debugger streams the error "The BDM has been re-enabled" several times and communication is lost.

My simple test program I am using to work this problem out just toggles a bit in a while loop. There is only a problem with the HiWave debugger. I tried the P&E debugger and it steps through the program fine and I have verified that the operating frequency has changed as it is supposed to, ie I can change the frequency of the output as desired by changing the PLL settings.

Any ideas?

Re: The BDM has been re-enabled

CrasyCat — Thu, 22 Apr 2010 19:39:01 GMT

Hello

According to my understanding you are changing the value of the PLL within the application.

If you are doing so you need to configure your connection to tell the debugger PLL might change in the application.

In order to do that:

- Select Multilink/Cycllone Pro -> Connection or Communication

- In the P&E ICD12, Cable12, Multilink, Cyclone Pro Connection dialog activate the Special Setup tab.

- Check Set CLKSW bit in BDM control register.

- Click on OK to close the dialog.

From now on the debugger should be able to resynchronize after a change of PLL

CrasyCat

Re: The BDM has been re-enabled

goelectrons — Thu, 22 Apr 2010 20:17:50 GMT

Previously I was setting the PLL in the CPU bean but of course I would lose communication before I even got to the default breakpoint @ main() so I removed it from the bean and did it myself.

The checkbox you speak of is already checked, I probably should have mentioned that.

-g

Re: The BDM has been re-enabled

goelectrons — Thu, 22 Apr 2010 21:10:22 GMT

I downloaded the newest version of CodeWarrior for HCS12(X) v5.0 and all my problems went away.

Happy, happy, happy.

-cheers

Re: The BDM has been re-enabled

goelectrons — Fri, 23 Apr 2010 20:31:22 GMT

Ok, the last message was a bit premature I guess.

I am used to hitting the debug icon in CW and having it erase and program the device and break at the beginning of main(). Now when I do this I get a connection manager dialog. I cannot seem to figure out what is necessary to get it to reliably find the communication speed and re-program the device. The connection manager does not remember my setting for "Autodetect communications speed".

Error while loading diagnostics algorithm.... over and over and over.

Re: The BDM has been re-enabled

kef — Sat, 24 Apr 2010 00:15:52 GMT

When S12(X) MCU is secured, P&E debug connection has problems with communication speed etc. Did you try to unsecure MCU with P&E Unsecure_12 utility?

BTW I wonder why P&E has problems with BDM communication speed, since BDM SYNC "command" works even in secured mode and allows to determine BDM speed quite precisely. SYNC isn't supported by old HC12 MCUs, but these old HC12 don't have chip security. Why then we are having problems? Or why debugger doesn't tell clearly MCU is secured.

Re: The BDM has been re-enabled

goelectrons — Sat, 24 Apr 2010 00:34:24 GMT

The unsecure utility reports that the chip is not secured.

Re: The BDM has been re-enabled

cfu — Tue, 27 Apr 2010 14:08:31 GMT

Hello, I'm having a similar problem with CW4.5 and the P&E USB Multilink: I suddenly started getting a failure message "Error while loding diagnostics algorithm to taget system,the chip may be secured,or the derivative selected may be wrong." when I try to burn the application on the target, The chip is definitely not secured.

Most weird is that, even though the failure message always appears, HI-WAVE sometimes DOES manage to program the device, sometimes not.

Does anyone know what the problem can be?

Thanx a lot!