internal flash memory or debugger issue

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

internal flash memory or debugger issue

Jump to solution
1,049 Views
mikibart
Contributor II

Hello,

 

Can somebody help me with this. Before I powered down the system I downloaded the elf file and after I powered up the system again the system doesn't respond at all.

Basically, it looks like the elf file is not saved in internal flash memory.

This thing started recently.

 

I am using CodeWarrior Development Studio 5.9.0 and MPC5646C microcontroller

 

I woyld appriciate any help !

 

Thanks,

 

 

 

Labels (1)
0 Kudos
1 Solution
698 Views
mikibart
Contributor II

Hello Jun,

The problem is solved.

The second core vector table was not right.

Thanks,

View solution in original post

0 Kudos
4 Replies
698 Views
ZhangJennie
NXP TechSupport
NXP TechSupport

i wonder if the code was successful downlaod to the right flash address in the first time. after you download the code, don't lose connection, check flash memory address. can you see the code in the expeted flash memory range?

0 Kudos
698 Views
mikibart
Contributor II

Hello Jun,

Yes the code was downloaded successfully. When the code (elf file) is downloaded the
program runs normally. I checked the flash memory addresses and everything is
there as it should be. The only problem is when the system is turned off and on
again the program is not running. I tested it when the elf file is downloaded
by outputting some characters on UART, and turning a diode on. However, when
the system is powered down on powered up again the program outputs nothing and
the diode is off.

I am wondering if there is some issue with debugger that comes with
CodeWarrior software. Should I reinstall the CodeWarrior?

Here is one more detail. The previous program that was developed with the
same software for the same target runs normally when the system is powered down
and powered up again. There is no significant difference between those two projects.

Do you have idea what might be the issue here?

Thanks,

0 Kudos
699 Views
mikibart
Contributor II

Hello Jun,

The problem is solved.

The second core vector table was not right.

Thanks,

0 Kudos
698 Views
ZhangJennie
NXP TechSupport
NXP TechSupport

you are welcome!

0 Kudos