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.

LP-AM263: Error connecting to target (Error -1170 @ 0x0). JTAG connection test passes.

Part Number: LP-AM263
Other Parts Discussed in Thread: TUSB320

I have built the "hello_world" example for the AM263x successfully.  However, when I start the debug session I get the error in the title line.  I have tested the JTAG connection and it passes.  I have also experimented with different TCLK frequencies (down to 1.25 MHz) to no avail.

Here is the console messages:

Cortex_R5_0: GEL Output: Loading Gel Files on R5F0
Cortex_R5_0: GEL Output: Gel files loading on R5F0 Complete
Cortex_R5_0: GEL Output: ***OnTargetConnect() Launched***

Cortex_R5_0: GEL Output: AM263x Initialization Scripts Launched.
Please Wait...


Cortex_R5_0: GEL Output: AM263x_Cryst_Clock_Loss_Status() Launched
Cortex_R5_0: GEL Output: Crystal Clock present
Cortex_R5_0: GEL Output: AM263x_SOP_Mode() Launched
Cortex_R5_0: GEL Output: SOP MODE = 0x00000000    
Cortex_R5_0: GEL Output:
 QSPI - 4S Functional boot mode
Cortex_R5_0: GEL Output: AM263x_Read_Device_Type() Launched
Cortex_R5_0: GEL Output: EFuse Device Type Value = 0x000000AA    
Cortex_R5_0: GEL Output: AM263x_Check_supported_mode() Launched
Cortex_R5_0: GEL Output:
 efuse1=0x01000000  
Cortex_R5_0: GEL Output:
 The Device supports both LockStep & Dual Core mode
Cortex_R5_0: GEL Output:
 mode = 0
Cortex_R5_0: GEL Output: MSS_CTRL Control Registers Unlocked
Cortex_R5_0: GEL Output: MSS_TOP_RCM Control Registers Unlocked
Cortex_R5_0: GEL Output: MSS_RCM Control Registers Unlocked
Cortex_R5_0: GEL Output: MSS_IOMUX Control Registers Unlocked
Cortex_R5_0: GEL Output: TOP_CTRL Control Registers Unlocked
Cortex_R5_0: GEL Output:

***R5FSS0 Reset for Lockstep ***
Cortex_R5_0: GEL Output:

*** R5FSS1 Reset for Lockstep ***
Cortex_R5_0: GEL Output: R5F ROM Eclipse
Cortex_R5_0: GEL Output: R5FSS0_0 Released
Cortex_R5_0: GEL Output: R5FSS0_1 Released
Cortex_R5_0: GEL Output: R5FSS1_0 Released
Cortex_R5_0: GEL Output: R5FSS1_1 Released
Cortex_R5_0: GEL Output:

 All R5F Cores Released for program load
Cortex_R5_0: GEL Output: L2 Mem Init Complete
Cortex_R5_0: GEL Output: MailBox Mem Init Complete
Cortex_R5_0: GEL Output: *********** R5FSS0/1 Lockstep mode Configured********
Cortex_R5_0: GEL Output: SYS_CLK DIVBY2
Cortex_R5_0: GEL Output: DPLL_CORE_HSDIV0_CLKOUT0 selected as CLK source for R5FSS & SYS CLKs
Cortex_R5_0: GEL Output:
 CLK Programmed R5F=400MHz and SYS_CLK=200MHz
Cortex_R5_0: GEL Output:

 *** Enabling Peripheral Clocks ***
Cortex_R5_0: GEL Output: Enabling RTI[0:3] Clocks
Cortex_R5_0: GEL Output: Enabling RTI_WDT[0:3] Clocks
Cortex_R5_0: GEL Output: Enabling UART[0:5]/LIN[0:5] Clocks
Cortex_R5_0: GEL Output: Enabling QSPI Clocks
Cortex_R5_0: GEL Output: Enabling I2C Clocks
Cortex_R5_0: GEL Output: Enabling TRACE Clocks
Cortex_R5_0: GEL Output: Enabling MCAN[0:3] Clocks
Cortex_R5_0: GEL Output: Enabling GPMC Clocks
Cortex_R5_0: GEL Output: Enabling ELM Clocks
Cortex_R5_0: GEL Output: Enabling MMCSD Clocks
Cortex_R5_0: GEL Output: Enabling MCSPI[0:4] Clocks
Cortex_R5_0: GEL Output: Enabling CONTROLSS Clocks
Cortex_R5_0: GEL Output: Enabling CPTS Clocks
Cortex_R5_0: GEL Output: Enabling RGMI[5,50,250] Clocks
Cortex_R5_0: GEL Output: Enabling XTAL_TEMPSENSE_32K Clocks
Cortex_R5_0: GEL Output: Enabling XTAL_MMC_32K Clocks
Cortex_R5_0: GEL Output:

 ***All IP Clocks are Enabled***

Cortex_R5_0: GEL Output: CPU reset (soft reset) has been issued through GEL.
Cortex_M4_0: 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.10.0.00080)

  • Hello James,

    It appears that you are trying to connect to the M4 core of the AM263x. The M4F core is used as a part of the Hardware Security Module (HSM) and that is why you are not able to connect to the core. Please try connecting to one of the R5_<n> cores to load the hello world program. 

    Regards,

    Erik

  • I tried to restart the debug session and now it fails even earlier.  In fact, the JTAG connection test fails.  The only thing that has changed is that the board has been powered for a few hours.  I reduced the TCLK to 1.25 MHz and re-tested but it still fails:
    Connection test log:
    [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)]------------------------------------

    C:\Users\jkurnik\AppData\Local\TEXASI~1\
        CCS\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 'jioxds110.dll'.
    The library build date was 'Nov 28 2022'.
    The library build time was '16:30:46'.
    The library package version is '9.10.0.00080'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '5' (0x00000005).
    The controller has an insertion length of '0' (0x00000000).
    This utility will attempt to reset the controller.
    This utility has successfully reset the controller.

    -----[Print the reset-command hardware log-file]-----------------------------

    The scan-path will be reset by toggling the JTAG TRST signal.
    The controller is the XDS110 with USB interface.
    The link from controller to target is direct (without cable).
    The software is configured for XDS110 features.
    The controller cannot monitor the value on the EMU[0] pin.
    The controller cannot monitor the value on the EMU[1] pin.
    The controller cannot control the timing on output pins.
    The controller cannot control the timing on input pins.
    The scan-path link-delay has been set to exactly '0' (0x0000).

    -----[An error has occurred and this utility has aborted]--------------------

    This error is generated by TI's USCIF driver or utilities.

    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]

    Any suggestions so I can get back to where I was earlier?

  • Hello James,

    • Which version of CCS are you using?
    • Did you setup the target configuration to be for XDS110 USB Debug Probe and AM263x LAUNCHPAD?

    I would suggest creating a new target configuration to get the default settings and ensuring that you have the correct settings for general setup. Once you have done that, try power cycling the board and testing the connection again. 

    Regards,

    Erik

  • I'm using CCS 12.2.  The target configuration was already set for the XDS110 USB Debug and the AM263x Launchpad.  Just to be sure, I created a new debug configuration and created a new target configuration.  When I test the connection I get the same -233 error that I showed above.

    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <configurations XML_version="1.2" id="configurations_0">
        
        <configuration XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
            <instance XML_version="1.2" desc="Texas Instruments XDS110 USB Debug Probe_0" href="connections/TIXDS110_Connection.xml" id="Texas Instruments XDS110 USB Debug Probe_0" xml="TIXDS110_Connection.xml" xmlpath="connections"/>
            <connection XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
                <instance XML_version="1.2" href="drivers/tixds510debugssm.xml" id="drivers" xml="tixds510debugssm.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds510cs_dap.xml" id="drivers" xml="tixds510cs_dap.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds510cortexR.xml" id="drivers" xml="tixds510cortexR.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds510cortexM.xml" id="drivers" xml="tixds510cortexM.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds510pru.xml" id="drivers" xml="tixds510pru.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds510csstm.xml" id="drivers" xml="tixds510csstm.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds510etbcs.xml" id="drivers" xml="tixds510etbcs.xml" xmlpath="drivers"/>
                <platform XML_version="1.2" id="platform_0">
                    <instance XML_version="1.2" desc="AM263x_LAUNCHPAD_0" href="boards/AM263x_LaunchPad.xml" id="AM263x_LAUNCHPAD_0" xml="AM263x_LaunchPad.xml" xmlpath="boards"/>
                </platform>
            </connection>
        </configuration>
    </configurations>

  • Hello James,

    • Could you try swapping out the micro USB cable?
    • What are you using to supply power to the USB-C connector? Are you connected directly to a host PC or to a wall adapter? Ensure that the power supply is capable of 5V/3A. 

    Regards,

    Erik

  • I switched the micro USB to a known good one, but that did not change the symptoms.

    For power, I'm using a USB 3.2 Gen 2 Type-C Thunderbolt 3 port from my laptop, so I believe it should have enough capacity.

  • Hello James,

    Just to confirm, when both cables are plugged in, there are 5 green LEDs glowing?

    If so, go to the Device Manager on your PC and confirm that you can see the two XDS110 COM ports under Ports. 

    After confirming both COM ports are visible, follow the instructions for a manual update of the XDS110 firmware: https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html#troubleshooting)

    • Open command prompt
    • cd to ccs1220\ccs\ccs_base\common\uscif\xds110
    • >xdsdfu -e
    • >xdsdfu -m
    • >xdsdfu -f firmware_<firmware number>.bin -r
    • retry testing the connection on CCS

    Regards,

    Erik

  • I used to have 5 green LEDs glowing, but now I am down to 2 (D6 and D3).  I've tried pulling power and debug and reconnecting to reset the board but am still unable to get all 5 lights back on.

    I confirmed the ports shown are in my device manager.  I also did the manual firmware update already. 

  • Hello James, 

    Only having D6 LED glowing indicates that the TUSB320 Type-C CC Logic Controller is not recognizing the type-C connection as one that is capable of 5V/3A. You can confirm this by probing U21.4 as Low. This is a power supply issue rather than an XDS110 issue for the test connection failure. The AM263x is not getting powered because of the TUSB320 Logic Controller not enabling the power tree. Try changing the type-C connection to something else but a thunderbolt connection should be sufficient and I am able to confirm that a thunderbolt type-C to type-C is capable of powering the board (all LEDs glowing) using an HP Elitebook. For more information refer to: https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1183354/faq-sitara-mcu-evm-and-launchpad-power-supply-requirements

    Once you have the SoC powered, try to test the connection again and if it passes then you should be able to connect to an R5F core to load the hello world program. 

    Regards,

    Erik

  • Hello James, 

    Could you confirm if it was a thunderbolt type-C connection that was providing insufficient current to the board? Was the host PC in a low power mode?

    Regards,

    Erik

  • Initially I had the board plugged into a Dell Precision laptop with a thunderbolt port that is supposed to be able to source 3A.  I had all 5 LEDs on, but when I tried to enter a debug session I would get one of several different errors.  In hindsight, I think the power was marginal so the debug initialization would exceed the threshold and fail.  At some point the laptop stopped supplying enough current to get the 5 LEDs on (I was down to 2).  The USB-C 20W brick that I purchased solved the issues and I can now enter into a debug session.

  • Hello James, 

    If you don't mind, could you please share the exact model number of the Dell Precision laptop so that we can track down why the thunderbolt connection is not providing enough current?

    Regards,

    Erik