I'm trying to figure out why my target program continues running when I terminate a debug session from within CCS, but not when I use loadti and use the -a option.
(I can tell that my target program was executed, ran for a bit because it is always inside an LED blinky loop when I connect to debug the issue, and the blinky loop count got pretty far before it stopped...)
I made a copy of the loadti example to hack into it, and I can confirm that the launch of the program is one via the
debugSession.target.runAsynch();
command.
I added a statement before this to print the debug options:
debugSession.options.printOptions(".+");
and I get a list that roughly matches the options I see in CCS.
But, I tried changing an option in CCS for example under "On-Chip Flash" I changed erase options to 'Necessary Sectors Only (for Program Load).
I hit the 'Remember My Settings" button and confirmed that when I exit CCS and restart it again the setting has been remembered.
However, when DSS script runs it prints the following for the option:
Radio Button Option:
id: FlashEraseSelection
name: TMS470RDX.TMS570LS3137 Flash Settings.Erase Options.
value: Entire Flash
choices:
Entire Flash
Necessary Sectors Only (for Program Load)
Selected Sectors Only
So, it seems to be tapping into a different 'store' of option settings.
I am using the exact same CCXML file for launching the session in CCS and DSS so I'm guessing the options aren't stored in there...
Question 1: Where do the default options come from when a debug server scripting session is started?
Question 2: Does it make sense that this is different than the settings when CCS is started?
Question 3: I'm trying to figure out if one of the options controls whether the target is halted before disconnecting... not finding something specific to
'disconnect' although a lot of options are there for 'connect'... any suggestions on this?
CCS version is the 5.3 beta.
Thanks and Best Regards,
Anthony
