eZdsp TMS320F28335 : What might cause the following error?

The following error occurred during deployment to your hardware board: Debug Server Scripting (DSS) error: *** User inputs: Target Configuration: C:\PROGRA~3\MATLAB\SUPPOR~1\R2021b\toolbox\target\SUPPOR~1\tic2000/CCS_CO~1/F28335~1.CCX Program Name: C:\Users\resadmin\DOCUME~1\MATLAB\TI_DSP\DSPX1.out Board Name: * 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 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.3.0.00032) 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\R2021b\toolbox\shared\SUPPOR~1\tic2000/CCS_CO~1/RUNPRO~2.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\R2021b\toolbox\shared\SUPPOR~1\tic2000/CCS_CO~1/RUNPRO~2.JS:93) at org.mozilla.javascript.gen.c1.call(C:\PROGRA~3\MATLAB\SUPPOR~1\R2021b\toolbox\shared\SUPPOR~1\tic2000/CCS_CO~1/RUNPRO~2.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\R2021b\toolbox\shared\SUPPOR~1\tic2000/CCS_CO~1/RUNPRO~2.JS) at org.mozilla.javascript.gen.c1.exec(C:\PROGRA~3\MATLAB\SUPPOR~1\R2021b\toolbox\shared\SUPPOR~1\tic2000/CCS_CO~1/RUNPRO~2.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:89) 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:641) 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 .

Answer 1

[Prannoy]

The error message you provided indicates that there is an issue connecting to the target hardware board for debugging. The error message suggests several possible causes for the issue, including:

• No XDS100 emulator is plugged in.
• Invalid XDS100 serial number.
• Blank XDS100 EEPROM.
• Missing FTDI drivers.
• Faulty USB cable.

To troubleshoot this issue, you can try the following steps:

1. Verify that the XDS100 emulator is properly connected to your computer and the hardware board.
2. Check if the XDS100 serial number is correct and matches the emulator you are using.
3. Ensure that the XDS100 EEPROM is not blank. You can use the xds100serial command-line utility in the 'common/uscif' folder to verify the XDS100 can be located.
4. Make sure that the FTDI drivers are installed correctly. You may need to reinstall or update the drivers.
5. Try using a different USB cable to rule out any issues with the cable itself.