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.

EVMK2H Get Started

Other Parts Discussed in Thread: TCI6636K2H

I use Win7 64 bit on my host. I have installed CCS 6.0.1, mcsdk 3.01.0.104 and a lot more packages. I want to get started programing the evm board.I have nothing more than what cones with the EVM board.

I create a new project in CCS and try to connet to the board clicking "verify" in the window but it fails:

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]


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

C:\Users\laku\AppData\Local\TEXASI~1\CCS\
    ti\0\0\BrdDat\testBoard.dat

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

This utility has selected a 560/2xx-class product.
This utility will load the program 'xds2xxu.out'.
E_RPCENV_IO_ERROR(-6) No connection: DTC_IO_Open::dtc_io
Failed to open i/o connection (xds2xxu:0)

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 '-250' (0xffffff06).
The title is 'SC_ERR_ECOM_EMUNAME'.

The explanation is:
An attempt to access the debug probe via USCIF ECOM has failed.

[End]

1) How do the dip switched need to be set?

2) which probe do i need to selct: XDS2xx USB Debug Probe or XDS2xx Onboard USB Debug Probe?

3) which target do i have to select: Cartox A or C66xx?

Thanks for your help

Lars

  • Hi Lars,

    Ans1: Refer below wiki link for select the JTAG DSP Little Endian Boot mode based on your EVM revision.

    http://processors.wiki.ti.com/index.php/EVMK2H_Hardware_Setup#No_Boot.2FJTAG_DSP_Little_Endian_Boot_mode

    Ans2: EVM K2H have XDS200mezzanine card, you need to select "Texas Intruments XDS2xx USB Onboard Emulator". For more information refer EVM Technical ReferenceDocument

    http://www.advantech.com/Support/TI-EVM/EVMK2HX_sd3.aspx

    Ans3: C66xx

    Thanks,

  • Hi Lars,

    the A15 cores 1-3 or in powerdown after startup. You can enable them and setup PLL easily using the GEL file you can find in:

    CCS_INSTALL_DIR\ccs_base\emulation\boards\xtcievmk2x\gel

    When you're using the GEL-File (details on usage http://processors.wiki.ti.com/index.php/GEL) use the function

    TETRIS_POWERUP_AND_PLL_INIT

    Kind regards,

    one and zero

  • Hi Ganapathi,

    i used 0010 as dip setting, i have REV40 on a sticker and A104-1 on my board.

    The option "Texas Intruments XDS2xx USB Onboard Emulator" doe snot exist, i guess you meant "Texas Intruments XDS2xx USB Onboard Debug Probe"

    Still it does not connect:

    [Start]

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

    [Result]


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

    C:\Users\laku\AppData\Local\TEXASI~1\CCS\
        ti\0\0\BrdDat\testBoard.dat

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

    This utility has selected a 560/2xx-class product.
    This utility will load the program 'xds2xxu.out'.
    E_RPCENV_IO_ERROR(-6) No connection: DTC_IO_Open::dtc_io
    Failed to open i/o connection (xds2xxu:0)

    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 '-250' (0xffffff06).
    The title is 'SC_ERR_ECOM_EMUNAME'.

    The explanation is:
    An attempt to access the debug probe via USCIF ECOM has failed.

    [End]
    I tried both USBs, mezanine and mainboard, no connection.

    tested several usb-cabled, several usb-ports, with and without hub in between.

    I can see the two comports.

    What's next?

     

  • Hi,

    Please tyr to using true USB 2.0 ports instead of USB 3 ports on the host. I have attached the K2H target configuration screen shot for your reference.

    Thanks,

  • Hi,

    i used USB 2.0 all the time. Out of a sudden it works now, i do not know what i have changed. At least i can connect now.

    Regards

    Lars

  • HI. I am trying to get started with EVMK2H. I ran into similar problems.

    Problem 1:

    The XDS2XX usb onboard Emulator option is missing from the dropdown menu. I am sure im using usb2. I have the free licensed version of CCS 6.0.1.  I wonder if I need the regular licensed verision to be able use the onboard emulator?

    Problem 2:

    error occurs when i tried to compile and debug a simple helloworld project using XDS2XX usb onboard Debug Probe

    arm_A15_0: File Loader: Data verification failed at address 0x00010134 Please verify target memory and memory map.
    arm_A15_0: Unable to terminate memory download: NULL buffer pointer at 0x3aa4
    arm_A15_0: GEL: File: /home/eric/workspace/Test2/Debug/Test2.out: a data verification error occurred, file load failed.

    A

  • I was trying to compile a helloworld project for the ARMs
  • Hi,

    The XDS2XX usb onboard Emulator option is missing from the dropdown menu. I am sure im using usb2. I have the free licensed version of CCS 6.0.1.  I wonder if I need the regular licensed verision to be able use the onboard emulator?

    Have you installed the latest MCSDK package? If no, Please download the latest MCSDK 3.x for Keystone II devices(K2H, K2K, K2L & K2E) and the follow user guide from here.

    Have you installed the Keystone2 emulation pack (ti_emupack_keystone2_setup_1.1.1.0?

    Thanks,

  • Better to use latest CCS version Code Composer Studio 6.1.0
  • I  tried and installed CCS 6.1.0. It recognized the MCSDK and the emulation pack. I aslo verified the versions are correct. And the "xds 2x USB Onboard Emulator" is  still missing. Again, I am not using the official licensed CCS. Do I need to get my CCS licensed before I can use the onboard emulator? 

  • Hi,

    CCS license is not required for onboard emulator selection. You are not able to see the "Texas Instruments XDS2xx USB Onboard Debug Probe" emulator on your target configuration file. Please see my below image:

    Thanks,

  • I am able to see "XDS2xx USB onboard Debug Probe" , but I wasn't able to "XDS2xx USB onboard Debug emulator". Sorry, I am new to developing for TI products. I am not sure what is the difference between those two.
    When trying to debug a simple helloworld project using "XDS2xx USB onboard Debug Probe", I ran into some problems. I posted the error message on previous replies if that helps clarify things a little bit more.
  • Better to use MCSDK package target configuration file for your testing:
    MCSDK Path: \ti\mcsdk_bios_3_01_03_06\tools\program_evm\configs\evmk2e\
  • I am getting the error No source available for "0x20b02cd0"
    Connected to No boot mode, connected usb to mezzanine board via USB2.0, set device as TCI6636K2H ,and connection to XDS2xx Onboard Emulator. And I am not able to connect to the target
    C66xx_0: GEL Output:
    Connecting Target...
    C66xx_0: GEL Output: TCI6638K2K GEL file Ver is 1.3
    C66xx_0: GEL Output: Detected PLL bypass disabled: SECCTL[BYPASS] = 0x00000000
    C66xx_0: GEL Output: (3a) PLLCTL = 0x00000040
    C66xx_0: GEL Output: (3b) PLLCTL = 0x00000040
    C66xx_0: GEL Output: (3c) Delay...
    C66xx_0: GEL Output: (4)PLLM[PLLM] = 0x0000000F
    C66xx_0: GEL Output: MAINPLLCTL0 = 0x07000000
    C66xx_0: GEL Output: (5) MAINPLLCTL0 = 0x07000000
    C66xx_0: GEL Output: (5) MAINPLLCTL1 = 0x00000040
    C66xx_0: GEL Output: (6) MAINPLLCTL0 = 0x07000000
    C66xx_0: GEL Output: (7) SECCTL = 0x00090000
    C66xx_0: GEL Output: (8a) Delay...
    C66xx_0: GEL Output: PLL1_DIV3 = 0x00008002
    C66xx_0: GEL Output: PLL1_DIV4 = 0x00008004
    C66xx_0: GEL Output: PLL1_DIV7 = 0x00000000
    C66xx_0: GEL Output: (8d/e) Delay...
    C66xx_0: GEL Output: (10) Delay...
    C66xx_0: GEL Output: (12) Delay...
    C66xx_0: GEL Output: (13) SECCTL = 0x00090000
    C66xx_0: GEL Output: (Delay...
    C66xx_0: GEL Output: (Delay...
    C66xx_0: GEL Output: (14) PLLCTL = 0x00000041
    C66xx_0: GEL Output: PLL has been configured (CLKIN * PLLM / PLLD / PLLOD = PLLOUT):
    C66xx_0: GEL Output: PLL has been configured (122.88 MHz * 16 / 1 / 2 = 983.04 MHz)
    C66xx_0: GEL Output: Power on all PSC modules and DSP domains...
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=2, md=9!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=17, md=25!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=17, md=26!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=18, md=27!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=19, md=28!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=19, md=29!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=20, md=30!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=20, md=31!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=20, md=32!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=20, md=33!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=21, md=34!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=22, md=35!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=22, md=36!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=23, md=37!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=23, md=38!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=24, md=39!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=24, md=40!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=24, md=41!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=24, md=42!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=25, md=43!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=25, md=44!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=25, md=45!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=25, md=46!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=26, md=47!
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=27, md=48!
    C66xx_0: GEL Output: Power on all PSC modules and DSP domains... Done.
    C66xx_0: GEL Output: WARNING: SYSCLK is the input to the PA PLL.
    C66xx_0: GEL Output: Completed PA PLL Setup
    C66xx_0: GEL Output: PAPLLCTL0 - before: 0x0x07080400 after: 0x0x07080400
    C66xx_0: GEL Output: PAPLLCTL1 - before: 0x0x00002040 after: 0x0x00002040
    C66xx_0: GEL Output: DDR begin
    C66xx_0: GEL Output: XMC setup complete.
    C66xx_0: GEL Output: DDR3 PLL (PLL2) Setup ...
    C66xx_0: GEL Output: DDR3 PLL Setup complete, DDR3A clock now running at 666 MHz.
    C66xx_0: GEL Output: DDR3A initialization complete
    C66xx_0: GEL Output: DDR3 PLL Setup ...
    C66xx_0: GEL Output: DDR3 PLL Setup complete, DDR3B clock now running at 800MHz.
    C66xx_0: GEL Output: DDR3B initialization complete
    C66xx_0: GEL Output: DDR done

    Regrads
    Deepak Sen
  • Hi Deepak,
    We strongly recommend you to create new e2e thread for your queries instead of following up on an old/closed e2e thread, new threads gets more attention than old threads and can provide link of old threads or information on the new post for clarity and faster response.

    Thank you.