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.

CCS/C55XCODECS: C5517 Target configuration is not connected

Part Number: C55XCODECS

Tool/software: Code Composer Studio

Hi Champs:

  I got a issue while using CCS to download the image onto C5517EVM.

  No matter I use the "C5517EVM_Onboard_Emulator.ccxml" file inside the CSL3.07 or I create another new one.

  The connection test will show me this.

  Please guide me how to solve it.

Thanks.

BR Rio

[Start: Texas Instruments XDS100v2 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\a0219345\AppData\Local\TEXASI~1\
CCS\TI\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 'jioserdesusb.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 XDS100v2 USB Debug Probe_0]

  • Hi Rio,

    I've forwarded this to the c55x experts. Their feedback should be posted here.

    BR
    Tsvetolin Shulev
  • Hi .
    I can load the program right now.
    But , the issue comes, please see the below log msg.
    Please send me the correct "CCXML file" + correct "GEL" file to make the Audio Beanforming demo.

    There are bunch of ccxml / gel in the CSL 3.0.7, but, I have tried some how.
    Still not working properly.

    THanks,
    BR Rio




    Audio Pre-processing Demo for C5517 EVM with CMB
    This Demo Will Continuously Get Audio Input from CMB, Process the Audio Using BF+ASNR+MSS, then
    Send the Processed Audio to the Left Channel of the On-Board Codec (AIC3204-2)
    Bypass Audio Input from Mic2 of CMB to the Right Channel of the On-Board Codec

    Please Connect the Headphone to the Audio Output (Headphone) Jack (P9)

    I2S2 Module Instance opened successfully
    I2S2 Module Configured successfully
    I2S3 Module Instance opened successfully
    I2S3 Module Configured successfully
    I2S0 Module Instance opened successfully
    I2S0 Module Configured successfully
    bf required buffers:
    Buffer Size(twords) Alignment Volatile address
    0 82 1 no 0x0
    1 138 0 no 0x0
    2 144 0 no 0x0
    3 184 1 yes 0x0
    4 320 1 yes 0x0
    Buffers allocated by SIU for bf:
    Buffer Size(twords) Alignment Volatile address
    0 82 1 no 0x1
    1 138 0 no 0x1
    2 144 0 no 0x1
    3 184 1 yes 0x1
    4 320 1 yes 0x1
    bf required buffers:
    Buffer Size(twords) Alignment Volatile address
    0 82 1 no 0x0
    1 138 0 no 0x0
    2 144 0 no 0x0
    3 184 1 yes 0x0
    4 320 1 yes 0x0
    Buffers allocated by SIU for bf:
    Buffer Size(twords) Alignment Volatile address
    0 82 1 no 0x1
    1 138 0 no 0x1
    2 144 0 no 0x1
    3 184 1 yes 0x1
    4 320 1 yes 0x1
    bf required buffers:
    Buffer Size(twords) Alignment Volatile address
    0 82 1 no 0x0
    1 138 0 no 0x0
    2 144 0 no 0x0
    3 184 1 yes 0x0
    4 320 1 yes 0x0
    Buffers allocated by SIU for bf:
    Buffer Size(twords) Alignment Volatile address
    0 82 1 no 0x1
    1 138 0 no 0x1
    2 144 0 no 0x1
    3 184 1 yes 0x1
    4 320 1 yes 0x1
    bf required buffers:
    Buffer Size(twords) Alignment Volatile address
    0 82 1 no 0x0
    1 138 0 no 0x0
    2 144 0 no 0x0
    3 184 1 yes 0x0
    4 320 1 yes 0x0
    Buffers allocated by SIU for bf:
    Buffer Size(twords) Alignment Volatile address
    0 82 1 no 0x1
    1 138 0 no 0x1
    2 144 0 no 0x1
    3 184 1 yes 0x1
    4 320 1 yes 0x1
    bf required buffers:
    Buffer Size(twords) Alignment Volatile address
    0 82 1 no 0x0
    1 138 0 no 0x0
    2 144 0 no 0x0
    3 184 1 yes 0x0
    4 320 1 yes 0x0
    Buffers allocated by SIU for bf:
    Buffer Size(twords) Alignment Volatile address
    0 82 1 no 0x1
    1 138 0 no 0x1
    2 144 0 no 0x1
    3 184 1 yes 0x1
    4 320 1 yes 0x1
    bf required buffers:
    Buffer Size(twords) Alignment Volatile address
    0 82 1 no 0x0
    1 138 0 no 0x0
    2 144 0 no 0x0
    3 184 1 yes 0x0
    4 320 1 yes 0x0
    Buffers allocated by SIU for bf:
    Buffer Size(twords) Alignment Volatile address
    0 82 1 no 0x1
    1 138 0 no 0x1
    2 144 0 no 0x1
    3 184 1 yes 0x1
    4 320 1 yes 0x1
    Buffers requested by NR:
    Buffer Size(twords) Alignment Volatile
    0 44 1 no
    1 774 1 yes
    2 516 1 yes
    3 387 1 yes
    4 192 1 no
    5 516 1 no
    6 14 1 no
    Buffers allocated for NR:
    Buffer Size(twords) Alignment Volatile address
    0 88 3 no 0x1
    1 1552 3 yes 0x1
    2 1032 3 yes 0x1
    3 776 3 yes 0x1
    4 384 2 no 0x1
    5 1032 2 no 0x1
    6 32 3 no 0x1
    Buffers requested by NR:
    Buffer Size(twords) Alignment Volatile
    0 44 1 no
    1 774 1 yes
    2 516 1 yes
    3 387 1 yes
    4 192 1 no
    5 516 1 no
    6 14 1 no
    Buffers allocated for NR:
    Buffer Size(twords) Alignment Volatile address
    0 88 3 no 0x1
    1 1552 3 yes 0x1
    2 1032 3 yes 0x1
    3 776 3 yes 0x1
    4 384 2 no 0x1
    5 1032 2 no 0x1
    6 32 3 no 0x1
    Buffers requested by NR:
    Buffer Size(twords) Alignment Volatile
    0 44 1 no
    1 774 1 yes
    2 516 1 yes
    3 387 1 yes
    4 192 1 no
    5 516 1 no
    6 14 1 no
    Buffers allocated for NR:
    Buffer Size(twords) Alignment Volatile address
    0 88 3 no 0x1
    1 1552 3 yes 0x1
    2 1032 3 yes 0x1
    3 776 3 yes 0x1
    4 384 2 no 0x1
    5 1032 2 no 0x1
    6 32 3 no 0x1
    Buffers requested by NR:
    Buffer Size(twords) Alignment Volatile
    0 44 1 no
    1 774 1 yes
    2 516 1 yes
    3 387 1 yes
    4 192 1 no
    5 516 1 no
    6 14 1 no
    Buffers allocated for NR:
    Buffer Size(twords) Alignment Volatile address
    0 88 3 no 0x1
    1 1552 3 yes 0x1
    2 1032 3 yes 0x1
    3 776 3 yes 0x1
    4 384 2 no 0x1
    5 1032 2 no 0x1
    6 32 3 no 0x1
    Buffers requested by NR:
    Buffer Size(twords) Alignment Volatile
    0 44 1 no
    1 774 1 yes
    2 516 1 yes
    3 387 1 yes
    4 192 1 no
    5 516 1 no
    6 14 1 no
    Buffers allocated for NR:
    Buffer Size(twords) Alignment Volatile address
    0 88 3 no 0x1
    1 1552 3 yes 0x1
    2 1032 3 yes 0x1
    3 776 3 yes 0x1
    4 384 2 no 0x1
    5 1032 2 no 0x1
    6 32 3 no 0x1
    Buffers requested by NR:
    Buffer Size(twords) Alignment Volatile
    0 44 1 no
    1 774 1 yes
    2 516 1 yes
    3 387 1 yes
    4 192 1 no
    5 516 1 no
    6 14 1 no
    Buffers allocated for NR:
    Buffer Size(twords) Alignment Volatile address
    0 88 3 no 0x1
    1 1552 3 yes 0x1
    2 1032 3 yes 0x1
    3 776 3 yes 0x1
    4 384 2 no 0x1
    5 1032 2 no 0x1
    6 32 3 no 0x1
    MSS required buffers:
    Buffer Size(twords) Alignment Volatile address
    0 122 1 no 0x0
    Buffers allocated by SIU for MSS:
    Buffer Size(twords) Alignment Volatile address
    0 220 1 no 0x1
    ...Initializing DRC
    Not enough heap, exiting
    BR Rio
  • Hi all:
    Set as the 4 mics in the codec_pcm_186x.h will solve this issue.
    Because the 6 mics will cause the heap not enough.

    BR Rio
  • Hi all:

    I made this SOP for C5517 DSP bring up demo "beam forming".

    Enjoy.

    BR Rio

    TI C5517_EVM_SOP_By_TI_Rio.pdf

  • Hi Rio
    Thank you for sharing your step guide with helper steps and videos, it should benefit other users.

    I will ask to review this to see if any of this needs to be added to our wikis or ti.com collateral.

    Please let us know if you have additional feedback on collateral updates /enhancements needed to make this a better out of box experience.

    Regards
    Mukul