• State Resolved
  • Locked Locked
  • Replies 22 replies
  • Subscribers 30 subscribers
  • Views 554 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.

Original question:

AM2634: Not able to load .out file to AM263x

AM2631: AM263x_cc board

Quanying Peng
Prodigy 30 points
Part Number: AM2631

I got simular issue, I imported the empty example project from the SDK and tried to load it onto AM263x_cc emulator board.

I was loading the program from Debug as ->CCS project session.

  • 0
    TI__Genius 10574 points

    Quanying,

    Can you confirm the bootmode settings of the AM263x-CC board?  The bootmode switches should be set as shown in the image below:

    Regards,

    Brennan

  • 0 in reply to Brennan Hartigan
    Prodigy 30 points

    I tried this mood. I got exact same error.

  • 0 in reply to Quanying Peng
    TI__Genius 10574 points

    Can you try loading the hello world example?

    C:\ti\mcu_plus_sdk_am263x_08_06_00_34\examples\hello_world\am263x-cc\r5fss0-0_nortos

  • 0 in reply to Brennan Hartigan
    Prodigy 30 points

    Sure, let me import the hello world example step by step:
    1. which import wizard? Code composer Studio or Run/Debug?

  • 0 in reply to Brennan Hartigan
    Prodigy 30 points

    Just want to confirm, it is r5fss0-0_nortos NOT r5fss0-0_freertos

  • 0 in reply to Quanying Peng
    TI__Genius 10574 points

    You may use either.

  • 0 in reply to Brennan Hartigan
    Prodigy 30 points

    I did follow the above instruction to setup the develop environment. This is the second around that I re-install everything. still the same issue.

  • 0 in reply to Quanying Peng
    TI__Genius 10574 points

    Please double check, your screenshot shows you are on MCU SDK 8.5.xx.  You need to be on the latest version of the SDK: 09.01.00.41

  • 0 in reply to Brennan Hartigan
    Prodigy 30 points

    Our team start with version 8.5.xxx, we haven't roll into the latest yet. I could upgrade to the latest alone.

  • 0 in reply to Quanying Peng
    TI__Genius 10574 points

    I would also suggest using the latest version of CCS.  Please update to the latest versions of both SW and try again.

  • 0 in reply to Brennan Hartigan
    Prodigy 30 points

    OK, I fixed the load build issue by changing the TLS search path to exact where I installed the CCS, the load build issue is gone. But I still got the same error when try to load the program

  • 0 in reply to Quanying Peng
    Prodigy 30 points

    I run test my target file, got log as below, is it normal?

    -----[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).

  • 0 in reply to Quanying Peng
    TI__Genius 10574 points

    The full log for testing target configuration connection should read:

    [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\a0488740\AppData\Local\TEXASI~1\
    CCS\ccs1240\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 'Sep 6 2023'.
    The library build time was '09:57:39'.
    The library package version is '9.13.0.00201'.
    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).

    -----[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.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG IR Integrity scan-test has succeeded.

    -----[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.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG DR Integrity scan-test has succeeded.

    [End: Texas Instruments XDS110 USB Debug Probe_0]

  • 0 in reply to Brennan Hartigan
    TI__Genius 10574 points

    Is SW5 on the EVM in the 'ON' position? XDS110 JTAG Selected

  • 0 in reply to Brennan Hartigan
    Prodigy 30 points

    Yes, the SW5 is set properly. Here is my target connection test log. It looks match with the log you posted above:

    [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\USQUPEN\AppData\Local\TEXASI~1\
    CCS\ccs1240\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 'Jun 2 2023'.
    The library build time was '12:47:07'.
    The library package version is '9.12.0.00150'.
    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).

    -----[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.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG IR Integrity scan-test has succeeded.

    -----[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.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG DR Integrity scan-test has succeeded.

    [End: Texas Instruments XDS110 USB Debug Probe_0]

  • 0 in reply to Quanying Peng
    Prodigy 30 points

    Is this message normal?
    "Selected device does not currently provide project initialization details for the TICLANG toolchain. The project may require further manual set up."

  • 0 in reply to Quanying Peng
    TI__Genius 10574 points

    What device do you have selected in the Target Configuration?  It should be AM263x_CC

  • 0 in reply to Brennan Hartigan
    Prodigy 30 points

    Yes, it is AM263x_CC, I even set the JTAG TCLK to 1MHz:

  • +1 in reply to Quanying Peng
    TI__Genius 10574 points

    Please follow this more detailed guide to ensure you have not missed any steps: https://dev.ti.com/tirex/explore/node?node=A__AD2nw6Uu4txAz2eqZdShBg__com.ti.MCU_PLUS_SDK_AM263X__aBmeCqF__LATEST

    Please also check the EVM Setup page to ensure all connections and switches are configured correctly:

    Regards,

    Brennan