• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 55 subscribers
  • Views 967 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:

Compiler: error code " The value is '-233' (0xffffff17)" for F28069 chip via Jtag

xds110 debug error "The value is '-233' (0xffffff17). The title is 'SC_ERR_PATH_BROKEN'."

Rohit6230
Intellectual 745 points
Other Parts Discussed in Thread: MSP432E401Y, TMDSEMU110-U

Dear Team,

I am trying to program MSP432e401y launchpad using XDS110 Debug probe using 20 PIn to 10 PIn cable convertor which is provided by TI. CCS show me "The value is '-233' (0xffffff17). The title is 'SC_ERR_PATH_BROKEN'." Please find attachment to detail understand

Could you suggest me how to program it using debugger.

  • +1
    Guru 92251 points

    Your Target Configuration file shows Debug Probe Selection as "Select by serial number" with a Serial number of "ME401023". I think that serial number could be for the onboard XDS110 on the launchpad, which is disconnected from the target, rather than for the TMDSEMU110-U.

    I tried the same configuration, with the launchpad USB connection powered from the same PC as the TMDSEMU110-U. Plugging one in at a time caused xdsdfu  -e to show:

    • The launchpad XDS110 serial number was ME401023
    • The TMDSEMU110-U serial number was 00000000

    If I use "Select by serial number" with a Serial number of "ME401023" (the launchpad) then a test connection fails with 'SC_ERR_PATH_BROKEN'.

    Whereas if use "Select by serial number" with a Serial number of "00000000" (the TMDSEMU110-U) then the test connection passes:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    [Start: Texas Instruments XDS110 USB Debug Probe_0]
    Execute the command:
    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity
    [Result]
    -----[Print the board config pathname(s)]------------------------------------
    /home/mr_halfword/.ti/ccs1210/0/0/BrdDat/
    testBoard.dat
    -----[Print the reset-command software log-file]-----------------------------
    This utility has selected a 100/110/510 class product.
    This utility will load the adapter 'libjioxds110.so'.
    The library build date was 'Sep 20 2022'.
    The library build time was '12:24:54'.
    The library package version is '9.9.0.00040'.
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Chester Gillon
    Intellectual 745 points

    Thank you Chester, This is solved my problem.

    Same thing I have done with my new design pcb and  write a program to toggling GPIO pin and I have done programming successfully 1st time in new pcb but after that I am trying to do programming it shows me below message. Its happened with 3 Nos of new pcb. I am using 32MHz crystal

    Error connecting to the target:
    (Error -1170 @ 0x0)
    Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 9.8.0.00235)

  • 0 in reply to Rohit6230
    Guru 92251 points
    Rohit6230 said:
    Same thing I have done with my new design pcb and  write a program to toggling GPIO pin and I have done programming successfully 1st time in new pcb but after that I am trying to do programming it shows me below message.

    Section 6.2 JTAG Not Working After Software Was Loaded in Using SimpleLink MSP432E4 microcontrollers over the JTAG interface has some possible causes for that.

    Section 5.3 Executing Unlock Sequence in that referenced document explains how you can perform the unlock sequence to reset the MSP432E4 microcontrollers to the factory state, which should make the device accessible over JTAG again.

    Suspect there is a problem with the program downloaded which set an incorrect clock for the device.

    If you can't identify the problem, suggest create a new thread in the Arm-based microcontrollers forum.