Respected Sir/Mam,
I tried to program tms320f28027 for a simple gpio toggle application, but when i tried to build the simulink embedded coder the below are the errors I have encountered ( I have already connected the target )
Texas Instruments XDS100v2 USB Debug Probe_0/C28xx (Suspended)
0x3FF7BF (no symbols are defined for 0x3FF7BF)
below are the errors generated when build has completed to matlab simulink
"C:/ti/ccsv6/tools/compiler/ti-cgt-c2000_6.4.6/bin/cl2000.exe" -z -I"C:/ti/ccsv6
/tools/compiler/ti-cgt-c2000_6.4.6/lib" -l"rts2800_ml.lib" -c -x -m"untitled.map
" -stack0x200 -o ./CustomMW/untitled.out ./derived/DSP2802x_CodeStartBranch.obj
./derived/DSP2802x_CpuTimers.obj ./derived/DSP2802x_DefaultIsr.obj ./derived/DSP
2802x_MemCopy.obj ./derived/DSP2802x_PieCtrl.obj ./derived/DSP2802x_PieVect.obj
./derived/DSP2802x_SysCtrl.obj ./derived/DSP2802x_usDelay.obj ./derived/DSP2802x
_GlobalVariableDefs.obj ./derived/MW_c28xx_board.obj ./derived/MW_c28xx_csl.obj
./derived/untitled.obj ./derived/untitled_data.obj ./derived/untitled_main.obj .
./../SAMPLE~1/UNTITL~1/untitled.cmd C:/PROGRA~1/MATLAB/R2013a/toolbox/idelink/EX
TENS~1/ticcs/rtlib/IQmath.lib
<Linking>
"Evaluating build target..."
"Evaluating execute target..."
"C:/ti/ccsv6/ccs_base/scripting/bin/dss.bat" "D:\MATLAB\ticcsexecute\ccsdemos\ru
nProgram.js" "D:\MATLAB\targetconfigurations\NewTargetConfiguration.ccxml" "./Cu
stomMW/untitled.out"
*** User inputs:
Target Configuration: D:\MATLAB\targetconfigurations\NewTargetConfiguration.
ccxml
Program Name: ./CustomMW/untitled.out
Board Name: unspecified (connect to first board)
CPU Name: unspecified (connect to first CPU)
*** Starting debug session...
*** Debug Session Name: Texas Instruments XDS100v2 USB Debug Probe_0/C28xx
*** Board Name: Texas Instruments XDS100v2 USB Debug Probe_0
*** CPU Name: C28xx
*** Connecting to target...
SEVERE: C28xx: Error connecting to the target: (Error -151 @ 0x0) One of the FTD
I driver functions used during the connect returned bad status or an error. The
cause may be one or more of: invalid XDS100 serial number, blank XDS100 EEPROM,
missing FTDI drivers, faulty USB cable. Use the xds100serial command-line utilit
y in the 'common/uscif' folder to verify the XDS100 can be located. (Emulation p
ackage 6.0.14.5)
SEVERE: emulation failure occurred
SEVERE: Error connecting to the target: emulation failure occurred
SEVERE: Cannot perform operation, target is not connected.
SEVERE: Error reseting target: Cannot perform operation, target is not connected
.
org.mozilla.javascript.WrappedException: Wrapped com.ti.ccstudio.scripting.envir
onment.ScriptingException: Error reseting target: Cannot perform operation, targ
et is not connected. (D:\MATLAB\ticcsexecute\ccsdemos\runProgram.js#93)
at org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:16
93)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:160)
at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:20
4)
at org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java
:119)
at org.mozilla.javascript.gen.c1._c0(D:\MATLAB\ticcsexecute\ccsdemos\run
Program.js:93)
at org.mozilla.javascript.gen.c1.call(D:\MATLAB\ticcsexecute\ccsdemos\ru
nProgram.js)
at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:3
40)
at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:275
8)
at org.mozilla.javascript.gen.c1.call(D:\MATLAB\ticcsexecute\ccsdemos\ru
nProgram.js)
at org.mozilla.javascript.gen.c1.exec(D:\MATLAB\ticcsexecute\ccsdemos\ru
nProgram.js)
at org.mozilla.javascript.tools.shell.Main.evaluateScript(Main.java:503)
at org.mozilla.javascript.tools.shell.Main.processFileSecure(Main.java:4
25)
at org.mozilla.javascript.tools.shell.Main.processFile(Main.java:391)
at org.mozilla.javascript.tools.shell.Main.processSource(Main.java:382)
at org.mozilla.javascript.tools.shell.Main.processFiles(Main.java:179)
at org.mozilla.javascript.tools.shell.Main$IProxy.run(Main.java:100)
at org.mozilla.javascript.Context.call(Context.java:528)
at org.mozilla.javascript.ContextFactory.call(ContextFactory.java:450)
at org.mozilla.javascript.tools.shell.Main.exec(Main.java:162)
at com.ti.ccstudio.apps.internal.scripting.RunScript$1.run(RunScript.jav
a:88)
Caused by: com.ti.ccstudio.scripting.environment.ScriptingException: Error reset
ing target: Cannot perform operation, target is not connected.
at com.ti.debug.engine.scripting.Target.reset(Target.java:622)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:145)
... 18 more
D:\MATLAB\project\Sample 1\untitled_ticcs>
So as the above error says the target is not connected but intially i have connected the target
and after this i see the
target disconneccted ( suspeneded ) error in ccsv6 window
so i tried to check the test connection option in target configuration
[Start: Texas Instruments XDS100v2 USB Debug Probe_0]
Execute the command:
%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity
[Result]
-----[Print the board config pathname(s)]------------------------------------
C:\Users\WISDOM~1\AppData\Local\TEXASI~1\
CCS\ti\0\0\BrdDat\testBoard.dat
-----[Print the reset-command software log-file]-----------------------------
This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusb.dll'.
An error occurred while soft opening the controller.
-----[An error has occurred and this utility has aborted]--------------------
This error is generated by TI's USCIF driver or utilities.
The value is '-151' (0xffffff69).
The title is 'SC_ERR_FTDI_OPEN'.
The explanation is:
One of the FTDI driver functions used during
the connect returned bad status or an error.
The cause may be one or more of: invalid XDS100 serial number,
blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
Use the xds100serial command-line utility in the 'common/uscif'
folder to verify the XDS100 can be located.
[End: Texas Instruments XDS100v2 USB Debug Probe_0]
after this i tired to reset the controller board ( by making it power off and on ) then again i tried to check the test connection in target configuration.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.
The JTAG IR Integrity scan-test has succeeded.
-----[Perform the Integrity scan-test on the JTAG DR]------------------------
This test will use blocks of 64 32-bit words.
This test will be applied just once.
Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.
The JTAG DR Integrity scan-test has succeeded.
[End: Texas Instruments XDS100v2 USB Debug Probe_0]
So can any body help me out and correct my mistakes
Regards,
Anuroop