• State TI Thinks Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 2 answers
  • Subscribers 32 subscribers
  • Views 514 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.

TMDSCNCD263: Unable to get Code Composer Studio to recognize TMDSCNCD263 / CCS does not show AM263X-CC as a target in drop down menu

bak chong
Prodigy 20 points
Part Number: TMDSCNCD263

Hi:

I have received the evaluation board and attempted to configure the target to work with the Code Composer Studio app that I installed on my MAC.
I do not see AM263X-CC as a target selection. Also, CCS app is unable to detect the target automatically. I have the USB connected and the power on.
The board configuration is as it was when I received it. 
My question is what are the tools that are currently being supported for this target; 
Let me know what I need to do to get this support or to make it working.
Regards
Bak

  • 0
    TI__Mastermind 29338 points

    Hi,

    Which SDK do you intend to use? Note the MCU+SDK only supports Windows and Linux PC hosts. Please see: https://software-dl.ti.com/mcu-plus-sdk/esd/AM263X/08_02_00_28/exports/docs/api_guide_am263x/SDK_DOWNLOAD_PAGE.html#autotoc_md10

    Regards,
    Frank

  • 0 in reply to Frank Livingston
    TI__Guru**** 463681 points
    Frank Livingston said:
    Note the MCU+SDK only supports Windows and Linux PC hosts

    In addition to the SDK, CCS on macOS does NOT support AM263. Sorry.

    ki

  • 0 in reply to Ki
    Prodigy 20 points

    Hi Frank:

    Will it work if I run ubuntu on top of VMWare Fusiojn on my MAC PC ?

    Regards

    Bak

  • 0 in reply to bak chong
    TI__Guru**** 463681 points
    bak chong said:
    Will it work if I run ubuntu on top of VMWare Fusiojn on my MAC PC ?

    This may work. Other customers have run virtualization software liek VMWare or Parallels from their MAC as a workaround. This will work for most people. But please note that this is not an officially supported environment so if you run into issues, we will not be able to provide much support.

  • 0 in reply to Ki
    Prodigy 20 points

    Fullscreen testuart.txt Download 
    [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\bakho\AppData\Local\TEXASI~1\CCS\
    ccs1110\0\0\BrdDat\testBoard.dat

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

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Dec  8 2021'.
The library build time was '11:16:32'.
The library package version is '9.6.0.00172'.
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]

[Start: UARTConnection_0]

Execute the command:

The Diagnostic Command is not defined in the connection properties.

[Start: Texas Instruments XDS100v3 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\bakho\AppData\Local\TEXASI~1\CCS\
    ccs1110\0\0\BrdDat\testBoard.dat

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

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusbv3.dll'.

An error occurred while soft opening the controller.

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

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

The value is '-151' (0xffffff69).
The title is 'SC_ERR_FTDI_OPEN'.

The explanation is:
One of the FTDI driver functions used during the connect
returned bad status or an error. The cause may be one or
more of: no XDS100 is plugged in, invalid XDS100 serial number,
blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
Use the xds100serial command-line utility in the 'common/uscif'
folder to verify the XDS100 can be located.

[End: Texas Instruments XDS100v3 USB Debug Probe_0]
    Hi Ki:   Do I need to have the 5V DC input USB 3.0 type c cable connected to power ? Is the connection to the UART/JTAG USB Type B all I need. I tried get the UART to respond to my terminal thru' serial connection. I am trying out  CCS on MS windows 10. Unfortunately, I got no output from the UART.  Also, I have attached a log output when I ran the test connection in CCS. Could you give some suggestion on how to get the terminal app to show some output from the UART.

  • 0 in reply to bak chong
    TI__Guru**** 463681 points

    Based on the error message, you configured the debugger for an XDS100 connection type. Note that it appears that the TMDSCNCD263 has an XDS110 on-board debug probe. If you are using the onboard XDS110, you need to change the connection type in the ccxml file.

    And yes it appears you need 5V 3A power. 

    Please see the below user's guide for more information. All the above information I mentioned is in the user's guide:

    https://www.ti.com/lit/ug/spruj09/spruj09.pdf

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 20 points

    I guess drawing the power from the computer port is not enough.  Which LED should be on for me to know it is getting enough power. Spec says an LED should flash if there is not enough power but I don't see going on.

  • 0 in reply to bak chong
    Prodigy 20 points

    Hi Ki: If the LD16 does not glow, does that mean my power is ok ? Also, only LD6 is on. The rest of the LED are off. I have the Type USB Type C connector to my MAC charger or adaptor. 

  • 0 in reply to bak chong
    TI__Guru**** 463681 points
    bak chong said:
    I guess drawing the power from the computer port is not enough

    Unless your computer port is speced for USB PD power, it is likely not enough.

    I do not have this target so I cannot comment any further. I will defer to Frank for any further questions.

  • 0 in reply to Ki
    Prodigy 20 points

    Hi Ki: I also connect it to my MAC adaptor charger which is capable of up to 80W of output. The only LED that is on is LD6.  I am wondering whether this is the right behaviour.

  • 0 in reply to bak chong
    TI__Mastermind 22685 points

    Hi Bak,

    LD6 is an XDS110 status LED, which in this case is indicating that the XDS110 is successfully connected to the host PC.

    For power, you need to connect a USB-C power source capable of negotiating and delivering 15W (5V@3A) to J12, the USB-C connector, separately from the XDS110 USB.  I suspect your MAC adapter charge should be able to meet this requirement, so please ensure it is correctly connected.  Please note that section 3 of the TMDSCNCD263 User's Guide describes the power requirements for the TMDSCNCD263.

    Thanks,
    Mike