Having troubles downloading code to MC9S12C128

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Having troubles downloading code to MC9S12C128

Jump to solution
1,255 Views
smahlt
Contributor I

In an introductory Electrical Engineering class, I used this microcontroller on the robot I assembled. Now, I've learned how to program the same microcontroller using CodeWarrior.

 

Now, the problem. When attempting to download my code to it, first I get a Non Fatal Error, and then I get a Non Volatile Memory Control error that says "Error while loading diagnostics algorithm to target system. The chip may be secured, or the derivative selected may be wrong." I suspect this may have something to do with the program I was given during the class, but I do not have a copy of it to show.

 

I'm still a beginner at this stuff, but I was hoping to mess around with my microcontroller a bit and see if I could make the robot do some cool stuff. Thanks for any help.

Labels (1)
Tags (1)
0 Kudos
1 Solution
545 Views
kef
Specialist I

I've never used TBDML. As https://community.freescale.com/message/55293#55293 thread suggests, you could try clicking in debugger TBDML HCS12->Unsecure.  Also try using search to find more information about TBDML. There's TBDML dedicated forum.

View solution in original post

0 Kudos
3 Replies
545 Views
smahlt
Contributor I

Ah, sorry. I was using TBDML.

0 Kudos
546 Views
kef
Specialist I

I've never used TBDML. As https://community.freescale.com/message/55293#55293 thread suggests, you could try clicking in debugger TBDML HCS12->Unsecure.  Also try using search to find more information about TBDML. There's TBDML dedicated forum.

0 Kudos
545 Views
kef
Specialist I

Try unsecuring chip. You didn't say what BDM tool are you using. If it's P&E USB Multilink, then try downloading Unsecure12 utility from www.pemicro.com.

Error while downloading diag. algorithm is generated when debugger writes some flash burning codes to RAM location, but verify fails. It may fail because of wrong chip selected, which doesn't have RAM at addresses, debugger is trying to write burning code to. 

0 Kudos