Run in debug mode, but fail after burn into Flash

 Run in debug mode, but fail after burn into Flash

I'm using ARM MDK to develop TMS470 applications.

Everything works in debug mode with ULINK2.
I burn the image into internal flash. But it just can't work.

Anyone has exp on such case?

 Anyone has exp on such case?

No,

I just type in the code and let other people test it.

Minkey.

 RE: Run in debug mode, but fail after burn into Flash

I burn the image into internal flash. But it just can't work.

How do you know that?

 RE: Run in debug mode, but fail after burn into Flash

I have leds turned on to show the function present

 RE: Run in debug mode, but fail after burn into Flash

this issue fixed.

the problem is from startup code.

To make it run standalone, we have to init the RW, ZI with the right memory map. Usually, it is done by the runtime lib __main. But our project have to be done by ourselves.

I guess in debug run. The host/debugger init the RW, ZI regions even without the keil runtime init __main. That's why we can run without right startup.

 RE: Run in debug mode, but fail after burn into Flash

But our project have to be done by ourselves.

Huh? What kind of argument is that supposed to be? What does you doing your own project have to do with letting the compiler do its job?