Other Parts Discussed in Thread: UNIFLASH, TMS320F28023, CCSTUDIO, TMS320F28335
Dear Team,
Is it necessary to use XDS200's .ccxml file when using Program Piccolo SW (JTAG/UniFlash)?
Do I need to use Program Piccolo SW (JTAG/UniFlash) to program the bootloader into the MCU before using Program Piccolo SW (Cheetah SPI)? Or are Program Piccolo SW (JTAG/UniFlash) and Program Piccolo SW (Cheetah SPI) actually programming the same thing?
Is using Program Piccolo SW (JTAG/UniFlash) to program the .out file into the MCU the same as using the 'Piccolo SPI Bootloader SW' project in CCS to program it?
The following error message occurs when I use the Cheetah SPI:
"Application configuration structure should be in the beginning or end of the data being programmed"
When using JTAG/UniFlash (XDS200), the following error message occurs:
***** Texas Instruments Universal Flash Programmer *****
<START: 09:10:38 GMT+0800 (CST)>
> Configuring the Flash Programmer with the given configuration ...
> Flash Manager is configured for the following part: TMS320F28023
> Setting up the user Flash Options ...
> Connecting to the target for Flash operations ...
SEVERE: C28xx: Error connecting to the target: (Error -151 @ 0x0) One of the FTDI driver functions used during the connect returned bad status or an error. The cause may be one or more of: no XDS100 is plugged in, 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. (Emulation package 9.10.0.00080)
SEVERE: emulation failure occurred
SEVERE: Error connecting to the target: emulation failure occurred
> Error connecting to target.
<END: 09:10:44 GMT+0800 (CST)>
<Total Time: 5.829s>
<< If using XDS510, the following message will be displayed.>>
***** Texas Instruments Universal Flash Programmer *****
<START: 09:09:36 GMT+0800 (CST)>
> Configuring the Flash Programmer with the given configuration ...
SEVERE: Cannot read System Setup data from XML file D:\Texas Instruments-DLP\dlpc120\Bootloader eliza 20210511\HUD_Piccolo_Bootloader_SW_Release_V0.1(6)\Target Config Files\XDS510LC_F28023.ccxml
Error parsing file:
Fatal Error at (0, 0): An exception occurred! Type:RuntimeException, Message:The primary document entity could not be opened. Id=C:\ti\ccs1200\ccs\ccs_base\common\targetdb\connections\SD2000USB_Connection.xml while parsing file: C:\ti\ccs1200\ccs\ccs_base\common\targetdb\connections\SD2000USB_Connection.xml
SEVERE: Could not start server: DebugServer.1: Cannot read System Setup data from XML file D:\Texas Instruments-DLP\dlpc120\Bootloader eliza 20210511\HUD_Piccolo_Bootloader_SW_Release_V0.1(6)\Target Config Files\XDS510LC_F28023.ccxml
Error parsing file:
Fatal Error at (0, 0): An exception occurred! Type:RuntimeException, Message:The primary document entity could not be opened. Id=C:\ti\ccs1200\ccs\ccs_base\common\targetdb\connections\SD2000USB_Connection.xml while parsing file: C:\ti\ccs1200\ccs\ccs_base\common\targetdb\connections\SD2000USB_Connection.xml
org.mozilla.javascript.WrappedException: Wrapped com.ti.ccstudio.scripting.environment.ScriptingException: Could not start server: DebugServer.1: Cannot read System Setup data from XML file D:\Texas Instruments-DLP\dlpc120\Bootloader eliza 20210511\HUD_Piccolo_Bootloader_SW_Release_V0.1(6)\Target Config Files\XDS510LC_F28023.ccxml
Error parsing file:
Fatal Error at (0, 0): An exception occurred! Type:RuntimeException, Message:The primary document entity could not be opened. Id=C:\ti\ccs1200\ccs\ccs_base\common\targetdb\connections\SD2000USB_Connection.xml while parsing file: C:\ti\ccs1200\ccs\ccs_base\common\targetdb\connections\SD2000USB_Connection.xml (C:\ti\ccs1200\ccs\ccs_base\scripting\examples\uniflash\cmdLine\uniFlash_core.js#49)
at org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1705)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:157)
at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:201)
at org.mozilla.javascript.optimizer.OptRuntime.call2(OptRuntime.java:74)
at org.mozilla.javascript.gen.c4._c1(C:\ti\ccs1200\ccs\ccs_base\scripting\examples\uniflash\cmdLine\uniFlash_core.js:49)
at org.mozilla.javascript.gen.c4.call(C:\ti\ccs1200\ccs\ccs_base\scripting\examples\uniflash\cmdLine\uniFlash_core.js)
at org.mozilla.javascript.optimizer.OptRuntime.callName0(OptRuntime.java:106)
at org.mozilla.javascript.gen.c1._c6(C:\ti\ccs1200\ccs\ccs_base\scripting\examples\uniflash\cmdLine\uniFlash_main.js:241)
at org.mozilla.javascript.gen.c1.call(C:\ti\ccs1200\ccs\ccs_base\scripting\examples\uniflash\cmdLine\uniFlash_main.js)
at org.mozilla.javascript.optimizer.OptRuntime.callName0(OptRuntime.java:106)
at org.mozilla.javascript.gen.c1._c0(C:\ti\ccs1200\ccs\ccs_base\scripting\examples\uniflash\cmdLine\uniFlash_main.js:21)
at org.mozilla.javascript.gen.c1.call(C:\ti\ccs1200\ccs\ccs_base\scripting\examples\uniflash\cmdLine\uniFlash_main.js)
at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:337)
at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2755)
at org.mozilla.javascript.gen.c1.call(C:\ti\ccs1200\ccs\ccs_base\scripting\examples\uniflash\cmdLine\uniFlash_main.js)
at org.mozilla.javascript.gen.c1.exec(C:\ti\ccs1200\ccs\ccs_base\scripting\examples\uniflash\cmdLine\uniFlash_main.js)
at org.mozilla.javascript.tools.shell.Main.evaluateScript(Main.java:500)
at org.mozilla.javascript.tools.shell.Main.processFileSecure(Main.java:422)
at org.mozilla.javascript.tools.shell.Main.processFile(Main.java:388)
at org.mozilla.javascript.tools.shell.Main.processSource(Main.java:379)
at org.mozilla.javascript.tools.shell.Main.processFiles(Main.java:176)
at org.mozilla.javascript.tools.shell.Main$IProxy.run(Main.java:97)
at org.mozilla.javascript.Context.call(Context.java:540)
at org.mozilla.javascript.ContextFactory.call(ContextFactory.java:447)
at org.mozilla.javascript.tools.shell.Main.exec(Main.java:159)
at org.mozilla.javascript.tools.shell.Main.main(Main.java:137)
Caused by: com.ti.ccstudio.scripting.environment.ScriptingException: Could not start server: DebugServer.1: Cannot read System Setup data from XML file D:\Texas Instruments-DLP\dlpc120\Bootloader eliza 20210511\HUD_Piccolo_Bootloader_SW_Release_V0.1(6)\Target Config Files\XDS510LC_F28023.ccxml
Error parsing file:
Fatal Error at (0, 0): An exception occurred! Type:RuntimeException, Message:The primary document entity could not be opened. Id=C:\ti\ccs1200\ccs\ccs_base\common\targetdb\connections\SD2000USB_Connection.xml while parsing file: C:\ti\ccs1200\ccs\ccs_base\common\targetdb\connections\SD2000USB_Connection.xml
at com.ti.debug.engine.scripting.DebugServer$SessionFactory.<init>(DebugServer.java:158)
at com.ti.debug.engine.scripting.DebugServer.openSession(DebugServer.java:1257)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:142)
... 24 more