Hello,
I want to run my application on c64x+ simulator using command prompt .
Can anyone please tell me the procedure for this. How to pass .ccxml file as argument to simulator?
Regards,
Mike
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hello,
I want to run my application on c64x+ simulator using command prompt .
Can anyone please tell me the procedure for this. How to pass .ccxml file as argument to simulator?
Regards,
Mike
Mike,
I would suggest checking out loadti. This is an example debug server script that acts as a command line loader.
This example is included with CCS.
http://processors.wiki.ti.com/index.php/Loadti
Regards,
John
I just downloaded a "fresh" ccs5 (CCS5.2.0.00069_linux.tar.gz)
followed instructions on the link you provided, and get this error:
Mandatory arguments to long options are mandatory for short options too.
did it get broken?
I've tried a bunch...
I have my own wrapper script:
P=ccsv5/ccs_base/scripting/examples
C=ccsv5/ccs_base/common/targetdb/configurations
PATH=$CCSV5BASE/$P/loadti:$PATH
app=test_prog.out
# same error out of all of these:
loadti.sh -q --cfg-file=$CCSV5BASE/$C/tisim_c64xple.xml $app
loadti.sh -q -c=$CCSV5BASE/$C/tisim_c64xple.xml $app
loadti.sh -q -c $CCSV5BASE/$C/tisim_c64xple.xml $app
loadti.sh -q -c $CCSV5BASE/$P/TestServer/c64xp_le_sim.ccxml $app
I munged through the several layers of shell scripts and came up with this single script... (it got me further but still fails)
$ cat sim
#!/bin/ksh
export CCSV5BASE=/opt/TI
export B=ccsv5/ccs_base
export R=$B/scripting
export C=$B/common/targetdb/configurations
export P=$R/examples
DEBUGSERVER_ROOT=$CCSV5BASE/$B/DebugServer
export DEBUGSERVER_ROOT
CLASSPATH=$DEBUGSERVER_ROOT/packages/ti/dss/java/js.jar:$CLASSPATH
CLASSPATH=$DEBUGSERVER_ROOT/packages/ti/dss/java/dss.jar:$CLASSPATH
CLASSPATH=$CCSV5BASE/$B/dvt/scripting/dvt_scripting.jar:$CLASSPATH
export CLASSPATH
export JAVA_HOME=$CCSV5BASE/ccsv5/eclipse/jre
PATH=$JAVA_HOME/bin:$PATH
export LOADTI_PATH=$CCSV5BASE/$P/loadti
java -DXPCOM.RUNTIME=$DEBUGSERVER_ROOT/linux org.mozilla.javascript.tools.shell.Main $CCSV5BASE/$P/loadti/main.js -c $CCSV5BASE/$P/TestServer/c64xp_le_sim.ccxml test_layout
$ ./sim
***** DSS Generic Loader *****
START: 15:46:39 GMT-0700 (MST)
Configuring Debug Server for specified target...
Done
flxInitLoad: client has not been protected.
flxInitLoad: client has not been protected.
TARGET: C64x+ CPU Cycle Accurate Simulator, Little Endian_0
Connecting to target...
testEnv.outFiles: test_layout
Loading test_layout
#
# An unexpected error has been detected by Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x0026f666, pid=24376, tid=1811778416
#
# Java VM: Java HotSpot(TM) Server VM (11.3-b02 mixed mode linux-x86)
# Problematic frame:
# C [libc.so.6+0x7e666]
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid24376.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Abort
I can send the .log file if you'd like it
dkerns said:I can send the .log file if you'd like it
log and dmp files would be great. If you can also provide the test_layout executable, that;d be great too.
http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv5#CCS_Diagnostic_Logs
Thanks
ki
for both versions (CCS5.1.1.00033 and CCS5.2.0.00069) I never did the admin driver step... could that be causing my errors? (I've never attempted to start CCS5 gui, only tried running the simulator from the command line) ... Do I need to start a new thread for this issue? (since this one is marked solved)
dkerns said:for both versions (CCS5.1.1.00033 and CCS5.2.0.00069) I never did the admin driver step... could that be causing my errors?
oh.. did you install as root? If not, then there would be an issue. If you did install as root, you don't need to do the extra step of running the script for the emulation drivers.
dkerns said:Do I need to start a new thread for this issue? (since this one is marked solved)
I'll split this thread to a new thread
ki