• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 84 subscribers
  • Views 743 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320F28075: Error connecting to the target: (Error -1015 @ 0x0)

Carlo
Expert 7715 points
Part Number: TMS320F28075
Other Parts Discussed in Thread: LAUNCHXL-F280049C

Hi E2E,

Our customer is using the Launchxl-f28049c launchpad to program a standalone MCU TMS320F28075. They're using the launchpad's onboard emulator XDS110 to program externally the TMS320F28075. They can verify the test connections successfully on Code composer studio, but when they debug the F2807x example code it gives the following error.

C28xx_CPU1: Error connecting to the target: (Error -1015 @ 0x0) Device is not responding to the request.  Device may be locked, or the debug probe connection may be unreliable. Unlock the device if possible (e.g. use wait in reset mode, and power-cycle the board). If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.4.0.00129)  

Your assistance to solve the error is appreciated.

Regards,
Carlo

  • 0
    Guru 55913 points

    Hi Carlo,

    I was having similar error codes trying to connect to x49c after adding SCI interrupts. The trick was to hold the target MCU in reset then click on retry quickly release target MCU reset. Then Debug posted message rude connect target ? clicking yes the target PLL would finally start. After a few failed attempts debug to connect target it would then erase necessary pages and load the firmware via CCS v9.3. 

  • 0 in reply to Genatco
    TI__Guru* 80520 points

    Carlo,

    The TMS320F28075 device requires IEEE 1149.1 JTAG type connection(standard 5 pin including TSRTn), where the XDS110 connection to the F28004x on the LAUNCHXL-F280049C uses IEEE 1149.7 cJTAG 2 pin advanced mode.

    Unfortunately, even though the J102 header includes the necessary signals for 4 pin cJTAG, the XDS_RESET_OUT is not equivalent to TRSTn signal needed by the F28075 device.

    You could set the JTAG mode for the XDS110 to IEEE1149.1 in the advanced tab of the CCXML, and attempt to manually toggle the TRSTn pin from low to high before connecting with CCS to see if this will work.

    Best,

    Matthew

  • 0 in reply to MatthewPate
    TI__Genius 16655 points

    Hello Matthew,

    Thanks for looking into this. Below are the response from the customer.

    "I Have tested it as per your guidance but i getting following error.

    The value is '-233' (0xffffff17).
    The title is 'SC_ERR_PATH_BROKEN'.

    The explanation is:
    The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
    An attempt to scan the JTAG scan-path has failed.
    The target's JTAG scan-path appears to be broken
    with a stuck-at-ones or stuck-at-zero fault.

    [End: Texas Instruments XDS110 USB Debug Probe_0]"

    Let us know what your thoughts are.

    Thanks and regards,

    Art

  • 0 in reply to Art Mecina
    TI__Guru* 80520 points

    Art,

    I'd like to clarify a bit and suggest one more step:

    1)I shouldn't have used the word "toggle" in my response.  For your connection you just need to transition TRSTn from low to high and keep it driven high then launch/connect the debugger.  TRSTn needs to stay high during the debug session.

    2)I would also like to make sure the the F28075 device is in Wait_Boot Mode(I've included an image below to show which and how the pins need to be driven at power up(once this is latched by the Boot ROM you are free to change the pins including TRSTn per the above).  This device has a feature of its Code Security Module that will disconnect the debugger if we are executing code in a secure region.  Wait Boot will guarantee this is not possible.

    So, power up with the boot pins outlined above, manually pullup TRSTn to VDDIO, launch the debugger.

    Best,

    Matthew