AnsweredAssumed Answered

What exactly does the debugger do to execute your program?

Question asked by dave408 on Oct 14, 2015
Latest reply on Oct 20, 2015 by dave408

I have a problem where a particular PCB with a K64F will run via the debugger in KDS, but when I power cycle it, the program does not execute.  I have already tried the approach suggested in one of my previous posts: How do you program and run from flash?

 

However, 1/3 of my boards (same revision PCB) does boot on startup.  I'm trying to understand why this is the case.

 

Since all of the boards work when debugging under KDS, I'm interested in knowing exactly what happens.  My simplified guess would be:

 

  • flash program
  • verify program
  • reset processor
  • send go command

 

I have used the J-Link Commander to flash my hex image, then I reset the processor and sent the go command.  My program does not run.  I must be missing some important steps here!  While it is necessary for me to eventually get the program to run on powerup, for the time being, it will be good enough if I can "kick start" the execution of the program via J-Link Commander commands.


Can anyone provide me with some more information about what's happening under the hood when the KDS debugger runs?  Thank you!

 

p.s. any suggestions about what I should look at with the scope to determine why the program isn't running on powerup would be much appreciated as well!

Outcomes