Project didn't start under debuger, kds3 ksdk120 MQX full

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

Project didn't start under debuger, kds3 ksdk120 MQX full

Jump to solution
1,190 Views
dafodil
Contributor III

Hi,

 

I made a new project from scratch with KDS3, KSDK12, stand alone, processor Expert, with a K64F (frdm). I add MQX full with the new default task main_task that should blink a led.

There is some IRQ on 3 gpio not used.

Clock came from external osc PTA18

All compile good.

 

When I run debuger, the project didn't start and stay at boot.s 0x410. see below screenshoot:

I have a bigger project with the same problem.

 

Maybe some one can give me a soultion?

 

Bernard

 

 

 

 

32686_32686.pngpastedImage_0.png

Labels (1)
Tags (1)
0 Kudos
Reply
1 Solution
1,042 Views
DavidS
NXP Employee
NXP Employee

Hi Bernard,

Please disable WDOG by setting value to "yes".

ScreenHunter_146 May. 29 12.46.gif

Regards,

David

View solution in original post

0 Kudos
Reply
5 Replies
1,042 Views
DavidS
NXP Employee
NXP Employee

Hi Bernard,

Please post your project to get additional help.

Regards,

David

0 Kudos
Reply
1,042 Views
dafodil
Contributor III

Hi,

I attached the "test" project to this message.

Note: linker file generator is desactivated after seeing the heap size to 0000.

regards

Bernard

0 Kudos
Reply
1,043 Views
DavidS
NXP Employee
NXP Employee

Hi Bernard,

Please disable WDOG by setting value to "yes".

ScreenHunter_146 May. 29 12.46.gif

Regards,

David

0 Kudos
Reply
1,042 Views
dafodil
Contributor III

Hi David,

It works. Thank a lot.

I understand my mistake.

To make this test project, I used a processor defined inside other project (drag and drop) where I plan to use WatchDog and where I add a component watchdog.

What is the target of this option 'watchdog disable'?

Regards

Bernard

0 Kudos
Reply
1,042 Views
DavidS
NXP Employee
NXP Employee

Hi Bernard,

Glad you are up and running.

The disable feature to disable the watchdog from running is mainly to allow debugging of code where you might hit breakpoints or halt for time frame longer than the watchdog timeout so as not to have a reset occur.

I typically see customer disable during bedug and development of application and turn on lastly for testing and production code.

Regards,

David

0 Kudos
Reply