Coldfire V1 (MCF51MM128) & Reset

[Eric_t]

Hi,

I have started my very first project with Coldfire V1 (MCF51MM128) and Codewarrior v10.2.

My project works OK when the debugger is connected (Pemicro Multilink Universal). 

When I disconnect the debugger, the controller does not start. 

Here is my steps:

          1. I am connecting the debugger. 

          2. I am building the project.

          3. I am pressing the debug button.

          4. I am pressing the RUN to line button.

          5. The program runs (the led is blinking).

          6. I am disconnecting the power supply.

          7. I am disconnecting the debugger.

          8. I am connecting the power supply.

          9. The program does not run (the led is off). 

Had anyone faced the same problem?

Thanks

Nikos

[kef]

Nikos,

It is simple to verify if vectors are programmed. When code is flashed inspect memory at address 0. It it's not all 0xFF, then vectors should be OK.

Isn't it your own untested board? I so, then I would verify that there's a high level at BKGD/MS pin at power on. Is there any pull up resistor? MS is mode select and should rise quite quickly to "1" at power on, else MCU will boot in background mode and keep waiting for BDM commands.

[Eric_t]

Problem solved

In "RUN configuration" window -> Debug Tab, the option "Stop on start up: user specified: main" was selected.
 
I have deselected it, and now “MCF51MM128" works after reset.

Thanks for your help
Nikos

[kef]

Sounds like vectors table is not defined.

[Eric_t]

Thanks Kef for your answer

I have used an example fom CW v10.2 for MCF51MM128, so I suppose that vectors table is OK.

I have only modify the main soutine, so a led is blinking.

Nikos

[TomE]

Your problem is in getting a CodeWarrior project to be burned into the chip so it will run standalone.

So this isn't a problem specific to the ColdFire chips.

I suggest you search through the CodeWarrior forums for anyone who has had similar problems.

Development environments like Visual Studio have a "Debug versus Release" option that generates builds for debugging versus builds for a production release. CodeWarrior probably has something equivalent that you need to set to make a build that can be burned into the chip's FLASH to run standalone rather than one that is loaded from, and run under the debugger.

Tom