<Linking> "### Created: ./EnergyManagement.out" "### Invoking postbuild tool "Hex Converter" on "EnergyManagement.out"..." C:/PROGRA~3/MATLAB/SUPPOR~1/R2018b/3P778C~1.INS/TIC200~1.INS/TI-CGT~1.LTS/bin/hex2000 -i "EnergyManagement.out" -o "../../EnergyManagement.hex" -order MS -romwidth 16 -q "### Done Invoking postbuild tool "Hex Converter" ..." "### Successfully generated all binary outputs." C:\dcmg\EnergyManagement_ert_rtw\pil>exit /B 0 ### Starting application: 'EnergyManagement_ert_rtw\pil\EnergyManagement.out' Starting PIL simulation *** User inputs: Target Configuration: C:\PROGRA~3\MATLAB\SUPPOR~1\R2018b\toolbox\target\SUPPOR~1\tic2000/CCS_CO~1/F28335~2.CCX Program Name: C:\dcmg\ENERGY~1\pil\ENERGY~1.OUT Board Name: unspecified (connect to first board) CPU Name: unspecified (connect to first CPU) *** Starting debug session... *** Debug Session Name: Texas Instruments XDS100v1 USB Emulator_0/C28xx *** Board Name: Texas Instruments XDS100v1 USB Emulator_0 *** CPU Name: C28xx *** Connecting to target... 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 one or more of: invalid emulator serial number, blank emulator EEPROM, missing FTDI drivers, faulty USB cable. Use the xds100serial command-line utility in the 'common/uscif' folder to verify the emulator can be located. (Emulation package 5.1.507.0) 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.environment.ScriptingException: Error reseting target: Cannot perform operation, target is not connected. (C:\PROGRA~3\MATLAB\SUPPOR~1\R2018b\toolbox\target\SUPPOR~1\tic2000/CCS_CO~1/RUNPRO~1.JS#93) at org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1693) at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:160) at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:204) at org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:119) at org.mozilla.javascript.gen.c1._c0(C:\PROGRA~3\MATLAB\SUPPOR~1\R2018b\toolbox\target\SUPPOR~1\tic2000/CCS_CO~1/RUNPRO~1.JS:93) at org.mozilla.javascript.gen.c1.call(C:\PROGRA~3\MATLAB\SUPPOR~1\R2018b\toolbox\target\SUPPOR~1\tic2000/CCS_CO~1/RUNPRO~1.JS) at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:340) at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2758) at org.mozilla.javascript.gen.c1.call(C:\PROGRA~3\MATLAB\SUPPOR~1\R2018b\toolbox\target\SUPPOR~1\tic2000/CCS_CO~1/RUNPRO~1.JS) at org.mozilla.javascript.gen.c1.exec(C:\PROGRA~3\MATLAB\SUPPOR~1\R2018b\toolbox\target\SUPPOR~1\tic2000/CCS_CO~1/RUNPRO~1.JS) at org.mozilla.javascript.tools.shell.Main.evaluateScript(Main.java:503) at org.mozilla.javascript.tools.shell.Main.processFileSecure(Main.java:425) 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.java:88) Caused by: com.ti.ccstudio.scripting.environment.ScriptingException: Error reseting 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
The timeout of 10 seconds for receiving data from the rtiostream interface has been exceeded. There might be multiple reasons for this failure. You should: (a) Check that the target hardware configuration is correct, for example, check that the byte ordering is correct. (b) Confirm that the target is running. (c) Consider the possibility of application run-time failures (e.g. divide by zero exceptions, incorrect custom code integration, etc.). Note (c): To identify possible reasons for the run-time failure, consider using SIL, which supports signal handlers and debugging. If you cannot find a solution, consider using the method setTimeoutRecvSecs of rtw.connectivity.RtIOStreamHostCommunicator to increase the timeout value.
