MC56F84763 works with debugger connected but not on own

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

MC56F84763 works with debugger connected but not on own

922 Views
leepenn
Contributor III


Hi,

 

Currently have a project with a MC56F84763 that when I run my project through the debugger after I download it using CW 10.6 and a multilink universal the code runs fine. If I remove the debugger and hope that the code would start and run on it's own it does not seem to run and I am looking for my outputs and none are changing. Is there a setting in the project that I am not seeing? I have made changes to my kinetis release projects to make them work and wondering if there are similar tweaks that I do not see in DSC projects.

 

Thanks,

 

Lee

Labels (1)
0 Kudos
Reply
3 Replies

712 Views
TICS_Fiona
NXP Employee
NXP Employee

If it starts up correctly in debug mode, but not in stand-alone mode, the possible reason may be:

1) Watchdog reset. Is the watchdog being serviced? Please first disable the watchdog in your application and test whether it makes any difference.


2)  Incorrect interrupt vector. In debug mode, the program starts from Entry Point which is set in the Target setting. While in stand-alone mode, it starts from vector table.

Please check whether the vector table is placed at the correct address in program flash. And the reset vector is correctly calling the start up routine.

3) Lost data in RAM. Please check the linker command file and MAP file,  whether there’s code  or initialized  data are placed in RAM, please place them in flash.

4) Initialized global variable, whether they are initialized correctly. This is another difference between running in debug mode and stand-alone mode.   When program before debugging, CodeWarrior will erase the memory before writing, but in stand-alone mode.




Fiona Kuang

Technical Information & Commercial Support

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

712 Views
leepenn
Contributor III

Thank you, you got me looking and I noticed code that Processor expert creates a interrupt that is for unhandled interrupts that places the code in debug halt.

0 Kudos
Reply

712 Views
johnlwinters
NXP Employee
NXP Employee

Is the board electrically dependent on the JTAG connection to the computer?

What kind if board is it running on?

Is the watchdog being serviced?

Best Regards,

John L. Winters

Senior Applications Engineer

AMR/EU MCU & MPU AE Group

Freescale Inc.

2100 Elliot Road

This email and any associated attachments have been classified as:

Freescale Confidential and Proprietary

0 Kudos
Reply