• State TI Thinks Resolved
  • Locked Locked
  • Replies 21 replies
  • Answers 1 answer
  • Subscribers 83 subscribers
  • Views 1827 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:

The problem of establishing serial communication between launchxl-28069m & my host computer

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

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

Hello
I'm woking with launchxl-f28069m.  I've been programming  on targe till today, but today I faced the following error with no certain reason:  

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\test1_mcu_28069.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 6.0.576.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\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: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(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

in fact, programming on target can't be done. moreover, I use MATLAB2018a & CCSv7.

please help me with this problem.   

   Regards                                                                                                                            

  • 0
    Intellectual 325 points

    Part Number: LAUNCHXL-F28069M

    Hello
    I'm woking with launchxl-f28069m.  I've been programming  on targe till today, but today I faced the following error with no certain reason:  

    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\test1_mcu_28069.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 6.0.576.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\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: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(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

    in fact, programming on target can't be done. moreover, I use MATLAB2018a & CCSv7.

    please help me with this problem.   

       Regards

  • 0
    Mastermind 9005 points

    Can you connect to board with CCS only? 

    • If no, this is probably a CCS or board issue.
    • If yes, then this is an error on the MathWorks side, and to get help please contact MathWorks Tech Support

    Cheers,

    -Brian

  • 0
    TI__Mastermind 30255 points
    Hello

    Are you able to program using just CCS and not matlab?
    Some debug tips: processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems

    Best regards
    Chris
  • 0 in reply to Christopher Chiarella
    Intellectual 325 points

    Hi Chris
    Unfortunately, I can't communicate with 28069 through ccs. I promoted ccs to version 8 and while connecting, this error occured:

    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]

    I dont really know the reason, It's been working in recent days with no problem... In addition, I have observed
    processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems But it wasn't a solution for my problem.
    Does it mean the board is out of order? How should I know?

  • 0 in reply to Brian McKay
    Intellectual 325 points
    Hi Brian
    Unfortunately, I can't communicate with 28069 through ccs. I promoted ccs to version 8 and while connecting, this error occured:

    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]

    I dont really know the reason, It's been working in recent days with no problem... In addition, I have observed
    processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems But it wasn't a solution for my problem.
    Does it mean the board is out of order? How should I know?
  • 0 in reply to Mohammad Farahani
    Mastermind 9005 points

    I'd say it looks like a bad board or communications cable. Hopefully someone from TI will respond with additional debugging suggestions.

    -b

  • 0 in reply to Brian McKay
    Intellectual 325 points

    Thanks for your giudance Mr.Mckay
    But I checked connection cable and changed with other cables. There is nothing wrong with cable. Moreover, I tested launchpad with other pc's and recieved the same error.

  • 0 in reply to Mohammad Farahani
    TI__Mastermind 30255 points
    Hello

    Have you tried a different USB cable? Additionally, make sure your switches are correct, see this post: e2e.ti.com/.../489498

    Best regards
    Chris
  • 0 in reply to Christopher Chiarella
    Intellectual 325 points

    I changed the cable and switches are in (high) up status. Besides, when I want to debug the programm with ccs8, this error occurs:

    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 Christopher Chiarella
    Intellectual 325 points

    I noticed that my previous program is running on 28069m.But running another program is impossible, why?
    I want TI technical team to help me.

    Does it mean the emulator is out of order?

  • 0 in reply to Brian McKay
    Intellectual 325 points

    I noticed that my previous program is running on 28069m.But running another program is impossible, why?
    I want TI technical team to help me.

    Does it mean the emulator is out of order?

  • 0 in reply to Mohammad Farahani
    Mastermind 9005 points
    Can you try and stop the running program. Maybe it is blocking the download of a new program.

    If not, maybe someone from TI can assist.

    Cheers,
    -Brian
  • 0 in reply to Brian McKay
    TI__Guru* 77720 points

    Mimi,

    Since we've confirmed that the problem still exists with CCS connection, I would like to start with the steps for debugging this outlined in this application note:

    http://www.ti.com/lit/an/spracf0/spracf0.pdf 

    I've tried to capture as many scenarios as possible to either root cause the problem, or provide a known checklist for you to reply back to the E2E so we can make get to the bottom of the problem as quickly as possible.

    Best,
    Matthew

  • 0 in reply to MatthewPate
    TI__Guru 62975 points
    Mimi,

    You can also try to use boot switch settings 123 = LHH. This should put your device in either WAIT or emulation boot depending on the TRSTn status.

    -Tommy
  • 0 in reply to tlee
    Intellectual 325 points

    Hi Tommy,

    thanks for your guidance.

    I left Dip switch situation in LHH=123 mode. Number 9(D9) LED turbed on but the same error occured for programming. I'm tired and confused and don't know the reason for sure. I Know some other people having the same problem. Is there any problem with board structure. Is dsp locked? Is there any solution for it at all?

    ''### Build procedure for model: 'test1_mcu_28069' 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:\28335\dsp_simul\test1_mcu_28069.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''

    Regards
    MIMI

  • 0 in reply to tlee
    Intellectual 325 points
    NO, I'm still in trouble and solutions didn't work
  • 0 in reply to MatthewPate
    Intellectual 325 points

    Hi Matthew
    Thanks for your help, but I'm still in trouble somehow.

    Regards
    MIMI

  • 0 in reply to Mohammad Farahani
    TI__Guru 62975 points
    MIMI,

    Have you tried to connect through CCS again with the boot switches set to LHH? Do you have another board available for comparison?

    How far did you get in the flowchart from the JTAG debug application note that Matthew posted?

    -Tommy
  • 0 in reply to tlee
    TI__Guru 62975 points
    MIMI,

    Are you still having trouble?

    -Tommy
  • 0 in reply to tlee
    TI__Guru 62975 points
    MIMI,

    It has been a while since your last update. I assume that you were able to resolve your issue. If this isn’t the case, please reject this resolution and reply to this thread. If this thread is locked, please make a new thread describing the current status of your issue.

    -Tommy