• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 598 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

LAUNCHXL-F28069M: The problem in programming on launchxl-f28069m

LAUNCHXL-F28069M: The problem in programming on launchxl-f28069m

Mohammad Farahani
Intellectual 325 points
Part Number: LAUNCHXL-F28069M
Other Parts Discussed in Thread: CCSTUDIO

Hi

I set the status of the boot switches to 123 = LHH, but it still delivers the following error when programming.

Build procedure for model: 'test_1' aborted due to an 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\R2018a\toolbox\target\SUPPOR~1\tic2000/CCS_CO~1/F28069~1.CCX
Program Name: E:\28069\dsp_simul\test_1.out
Board Name: *
CPU Name: unspecified (connect to first CPU)

*** Starting debug session...
*** Debug Session Name: Texas Instruments XDS100v2 USB Debug Probe/C28xx
*** Board Name: Texas Instruments XDS100v2 USB Debug Probe
*** CPU Name: C28xx

*** Connecting to target...
SEVERE: C28xx: Error connecting to the target: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.0.27.9)

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\R2018a\toolbox\target\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\R2018a\toolbox\target\SUPPOR~1\tic2000/CCS_CO~1/RUNPRO~2.JS:93)
at org.mozilla.javascript.gen.c1.call(C:\PROGRA~3\MATLAB\SUPPOR~1\R2018a\toolbox\target\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\R2018a\toolbox\target\SUPPOR~1\tic2000/CCS_CO~1/RUNPRO~2.JS)
at org.mozilla.javascript.gen.c1.exec(C:\PROGRA~3\MATLAB\SUPPOR~1\R2018a\toolbox\target\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:622)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:145)
... 18 more
.

  • 0
    TI__Guru 55700 points
    Mimi,

    This is not a flash programming problem. You are having problem with establish emulator connection itself.

    Has this device been previously programmed? Is the device password protected?

    Regards,
    Manoj
  • 0
    TI__Guru 62975 points
    MIMI,

    Can you try to connect to the device using CCS?

    -Tommy
  • 0 in reply to Manoj Santha Mohan
    Intellectual 325 points
    Hi Manoj,
    I've worked with dsp for two months. Currently, I can run only my last programming on it which includes epwm blocks.But it doesn't accept any new program for no certain reason.By the way, I didn't defined any password for it.
  • 0 in reply to tlee
    Intellectual 325 points
    Hi Tommy,
    Unfortunately, I can't connect via CCS.
  • 0 in reply to Mohammad Farahani
    TI__Guru 62975 points

    MIMI,

    Can you share the CCS error message?  Were you able to work through the debug flowchart from this JTAG Connectivity Appnote?

    We are not able to offer a solution for your setup issue because we do not have sufficient information.

    -Tommy

  • 0 in reply to tlee
    Intellectual 325 points
    Tommy,
    massage of test connection:

    -----[Perform the standard path-length test on the JTAG IR and DR]-----------

    This path-length test uses blocks of 64 32-bit words.

    The test for the JTAG IR instruction path-length failed.
    The JTAG IR instruction scan-path is stuck-at-ones.

    The test for the JTAG DR bypass path-length failed.
    The JTAG DR bypass scan-path is stuck-at-ones.

    -----[Perform the Integrity scan-test on the JTAG IR]------------------------

    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.
    Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    The details of the first 8 errors have been provided.
    The utility will now report only the count of failed tests.
    Scan tests: 2, skipped: 0, failed: 1
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 2
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 3
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 4
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 5
    Some of the values were corrupted - 83.3 percent.

    The JTAG IR Integrity scan-test has failed.

    -----[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.
    Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    Test 2 Word 7: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
    The details of the first 8 errors have been provided.
    The utility will now report only the count of failed tests.
    Scan tests: 2, skipped: 0, failed: 1
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 2
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 3
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 4
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 5
    Some of the values were corrupted - 83.3 percent.

    The JTAG DR Integrity scan-test has failed.

    [End: Texas Instruments XDS100v2 USB Debug Probe]
  • 0 in reply to tlee
    Intellectual 325 points

    Tommy,
    when i want debug the program in ccs, The following error is occured:
    C28xx: Error connecting to the target: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 8.0.27.9)

  • 0 in reply to Mohammad Farahani
    TI__Guru* 77700 points

    Mimi,

    From the error logs it looks like the emualtor is not being recognized by CCS.  Tommy had mentioned this app note in a prior post:

    http://www.ti.com/lit/pdf/spracf0  Have you been able to look through it?  This will help diagnose where the problem is as well as give us a clearer picture of the system if you can't solve the issue with the app note alone.

    Given that this is a LaunchPad, it may be that the FTDI needs to be reprogrammed if you are getting this error. The above app note has directions for that as well.

    Best,

    Matthew