Windows 7 SP1
CCS Version: 5.4.0.00091
I am using loadti to download and run our application on an MSP430F5438A target using the following
invocation of loadti:
loadti -v -c MSP430F5438A.ccxml MyApp.out
I have verified that the application is running on the target yet printf output does not appear in the Windows
command shell.
This web page:
http://processors.wiki.ti.com/index.php/Loadti
suggests that C I\O can be sent to the console window, but does not explain how.
None of the command line options for loadti seems appropriate for sending C I\O to the windows shell
(I suspect it goes there by default?).
I tried the following option:
-s, --stdout-file=FILE Save C I/O to specified file
After the run, the file was empty.
Note: if i download and run my app from CCS then printf output can be seen in the CCS console OK.
Here is the output of loadti:
C:\CCS\ccsv5\ccs_base\scripting\examples\loadti>loadti -v -c MSP430F5438A.ccxml InsightFW_Standalone_MRAM.o
***** DSS Generic Loader *****
START: 11:25:47 GMT-0000 (GMT)
Configuring Debug Server for specified target...
getServer: ENTRY sServerName: DebugServer.1
getServer: Getting definition for: DebugServer.1
getServer: Constructing server
getServer: RETURN com.ti.debug.engine.scripting.DebugServer@1a33d48
setConfig: ENTRY sConfigurationFile: MSP430F5438A.ccxml
setConfig: RETURN
Done
debuggerOpen: ENTRY sBoardName: * sCPUName: *
start: ENTRY
start: Firing: onServerStarting()
start: Connecting to XPCOM DebugServer
start: Initializing DebugServer using specified configuration: "C:\CCS\ccsv5\ccs_base\scripting\examples\lo
waitUntil: ENTRY com.ti.ccstudio.scripting.environment.ScriptingEnvironment@1a5f739 timeout: infinite
<init>: CPU Name: MSP430
<init>: PartNum: MSP430F5438A
<init>: Family: 430
<init>: SubFamily/MajorISA: 0
<init>: Revision/MinorISA: 0
<init>: Platform: EMULATOR
<init>: Processor ID: 1803550720
waitUntil: RETURN com.ti.ccstudio.scripting.environment.ScriptingEnvironment@1a5f739
start: Firing: onServerStarted()
start: Searching for devices
listDevices: ENTRY
listDevices: Found debuggable device: TI MSP430 USB1/MSP430
listDevices: RETURN
start: RETURN
open: Initializing RTDX: "RTDXServer.1"
getServer: ENTRY sServerName: RTDXServer.1
getServer: Getting definition for: RTDXServer.1
getServer: Constructing server
getServer: RETURN com.ti.debug.engine.scripting.RTDXServer@118fa47
openSession: ENTRY sDebugSession: TI MSP430 USB1/MSP430
getServer: ENTRY sServerName: DebugServer.1
getServer: Getting cached server: DebugServer.1
getServer: RETURN com.ti.debug.engine.scripting.DebugServer@1a33d48
openSession: ENTRY session: com.ti.debug.engine.scripting.DebugSession@d16fc1
openSession: RETURN com.ti.debug.engine.scripting.RTDXSession@1eb0
openSession: RETURN
debuggerOpen: RETURN TI MSP430 USB1/MSP430
setString: ENTRY ID: FileIODefaultDirectory Value: undefined
setString: RETURN
TARGET: TI MSP430 USB1
Connecting to target...
connect: ENTRY
connect: Requesting target connect
waitUntil: ENTRY timeout: infinite
log: Target is now connected
waitUntil: RETURN
connect: RETURN
testEnv.outFiles: InsightFW_Standalone_MRAM.out
Loading InsightFW_Standalone_MRAM.out
loadProgram: ENTRY sFileName: InsightFW_Standalone_MRAM.out
load: Requesting program load
waitUntil: ENTRY timeout: infinite
MSP430: Loading complete. Code Size - Text: 31886 bytes Data: 17762 bytes.
setupBeforeRun: ENTRY emuPin: 0
getConfigMode: ENTRY
getConfigMode: RETURN Failure
waitUntil: RETURN
load: Program load successful
getBoolean: ENTRY ID: AutoRunToLabelOnRestart
getBoolean: RETURN true
waitForHaltIfPropertySet: Waiting for halt
waitUntil: ENTRY timeout: infinite
log: Target has halted at 0x00014BC6
waitUntil: RETURN
loadProgram: RETURN
Done
Target running...
setScriptTimeout: ENTRY nTimeout: -1
setScriptTimeout: Timeout is infinite
setScriptTimeout: RETURN
exists: ENTRY sSymbol: C$$EXIT
exists: Getting symbol package
exists: Looking-up symbol
exists: Symbol "C$$EXIT" exists
exists: RETURN true
evaluate: ENTRY sExpression: PC == C$$EXIT
eval: Requesting evaluation of expression: "PC == C$$EXIT"
waitUntil: ENTRY timeout: infinite
onEvent: Evaluated expression: PC == C$$EXIT
waitUntil: RETURN
evaluate: RETURN 0x0
exists: ENTRY sSymbol: C$$EXITE
exists: Getting symbol package
exists: Looking-up symbol
exists: RETURN false
exists: ENTRY sSymbol: abort
exists: Getting symbol package
exists: Looking-up symbol
exists: Symbol "abort" exists
exists: RETURN true
evaluate: ENTRY sExpression: PC == abort
eval: Requesting evaluation of expression: "PC == abort"
waitUntil: ENTRY timeout: infinite
onEvent: Evaluated expression: PC == abort
waitUntil: RETURN
evaluate: RETURN 0x0
Interrupt to abort . . .
runBenchmark: ENTRY
runBenchmark: ENTRY nEventID: 0
runBenchmark: Setting Profile Clock count event
setCurrentEvent: ENTRY nEventID: 0
setCurrentEvent: Profile Clock is already configured to profile: CPU Cycles
setCurrentEvent: RETURN
runBenchmark: Enabling Profile Clock event counting
enable: ENTRY
enable: RETURN
runBenchmark: Resetting the profile clock register
reset: ENTRY
reset: RETURN
runBenchmark: Running target
run: ENTRY
go: Requesting target execution
waitUntil: ENTRY timeout: infinite