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.

TCIEVMK2X: TCIEVMK2X Development tools

Part Number: TCIEVMK2X

Hi Team,

We have a couple of questions concerning TCIEVMK2X.

1. Our customer was recently using XTCIEVMK2X, which was already tagged obsolete. We would like to know its particular difference(s) with regards to TCIEVMK2X.

2. We need its relevant technical documents so we would also like to confirm the exact processor inside the board. We are looking at TCI6638K2K as discussed on the post below.

https://e2e.ti.com/support/processors/f/791/p/841824/3127620#pi320966=2

3. Aside from CCS, is there any other development tool or a processor SDK which supports this board? MCSDK apparently is no longer reliable for development.

Appreciate your help on this.

Kind Regards,

Jejomar

  • Jejomar,

    TCIEVMK2X is mounted with TCI6638K2K which is super set of tci6634k2k, tci6636k2h, 66ak2h14, 66ak2h12 and 66ak2h06.

    XTCIEVMK2X is mounted with XTCI6638K2K.

    The difference between XTCI6638K2K and TCI6638K2K is:

    X: Experimental device that is not necessarily representative of the final device's electrical

    specifications

    [Blank]: Fully qualified production device

    So this means the TCIEVMK2X is the full production EVM.

     

    For TCI6638K2K, technical document can be found here:

    http://www.ti.com/product/TCI6638K2K/technicaldocuments

    For EVM, take a look at this link, especially: XTCIEVMK2X_Technical_Reference_Manual_Rev1_0.pdf.

    www2.advantech.com/.../EVMK2HX_sd4.aspx

    For SDK, yes, the MCSDK has not been maintained any more but you can always use very last version.

    http://software-dl.ti.com/sdoemb/sdoemb_public_sw/mcsdk/latest/index_FDS.html

     

    best regards,

    David Zhou

  • Hi Jejomar and David,

    Thank you for your help.

    I have these two different boards from TI evaluation modules that I would like to develop software for:

    Board 1 from XTCIEVMK2X EVM: Top stickers: "XTCIEVMK2X Rev 20" and "9792830502E DSPM-8305E", PCB bottom silkscreen: "DSPM-8305E AMC REV: A103-1"
    Board 2 I think from EVMK2H EVM: Top stickers: "EVMK2H Rev 3.0" and "9792830533E DSPM-8305E", PCB bottom silkscreen: "DSPM-8305E AMC REV: A104-1"

    I would like to locate the hardware documentation for each board, identify the specific processor on each board,
    and locate the appropriate development software. I am new to TI multicore processors. After a few days on the TI and Advantech websites,
    I think I am close to my goal. Here is my understanding so far. Can you please correct and guide if I am wrong?

    Hardware documentation for the A103 and A104 boards are at www2.advantech.com/.../EVMK2HX_sd2.aspx
    and www2.advantech.com/.../EVMK2HX_sd3.aspx, respectively.

    I tried inspecting the processor part number physically on the boards, but even with screws removed, the processor heat sinks
    are stuck on so strongly that they will not come off reasonably easily.

    The A103 PCB has an experimental XTCI6638K2K processor (with SA enabled) mounted (judging from David's reply and the what I think is the BOM,
    wfcache.advantech.com/.../XEVMK2HX_BOM_Rev2_0.xlsx)

    The A104 PCB has a TCI6638K2K processor mounted (judging from what I think is the BOM,
    wfcache.advantech.com/.../XEVMK2HX_BOM_Rev3_0.xlsx)

    The latest version of the MCSDK, software-dl.ti.com/.../index_FDS.html,
    is not maintained, but can be used for both boards.

    The PROCESSOR-SDK-K2H, www.ti.com/.../PROCESSOR-SDK-K2H, supports both boards
    PROCESSOR-SDK-LINUX-K2HK 06_00_00_07, software-dl.ti.com/.../index_FDS.html
    PROCESSOR-SDK-LINUX-RT-K2HK 06_00_00_07, software-dl.ti.com/.../index_FDS.html
    PROCESSOR-SDK-RTOS-K2HK 06_00_00_07, software-dl.ti.com/.../index_FDS.html

    What is the difference between the PROCESSOR-SDK-K2H and MCSDK?

    I am still trying to get the OOB demo to work, and platform_test example in pdk_k2hk_4_0_14 to compile successfully under CCS 8.3 and 6.1...

    Best regards,
    Walt Rogers

  • Hello Walt,

    Yes, the Advantech site has different version of board listed. I think you are right in making the correlations of version and document.

    Okay, let me ask you one question: which device do you intend to use? K2H or K2K?

    If it is K2H, you can use either board, whichever will be fine although EVMK2H is sufficient.

    If it is K2K, use the TCIEVMK2X or XTCIEVMK2X board.

    MCSDK is old software which was replaced by Processor SDK. Imagine Windows 7 replaced by Windows 10.

    If you are just starting your development work, you can start with the latest software:

    http://software-dl.ti.com/processor-sdk-rtos/esd/K2HK/latest/index_FDS.html

    Please note a new version 6.1 will be coming out soon.

    In the release download page, it has the CCS version listed, my suggestion is to use that version instead.

    best regards,

    David Zhou

  • Hi David,

    >>>>> Okay, let me ask you one question: which device do you intend to use? K2H or K2K?

    I know it is a bit backwards, but I want to use whatever devices are on my boards.

    I feel pretty comfortable that Board 1, marked "XTCIEVMK2X ", has a 6638K2K, since all information sources correlate. However I am not so sure about the other board, marked "EVMK2H". For example, judging from the TI EVMK2H product page and e2e.ti.com/.../355783, one might be inclined to think that it has a 66AK2H14, 66AK2H12 or 66AKH06 on it.

    I must admit that I am confused about the part numbering. I cannot find a 6636K2H datasheet on the TI website; does the part exist? If so, does it have a datasheet?

    Can I electrically confirm the installed part via the onboard XDS200 JTAG or some way other than removing the heat sink?

    At this point, I just want to flash the user LEDs.

    So far I have been unsuccessful creating an SDK LED blink example for either EVM. I have tried CCS6.1.1, CCS8.3.1, MCSDK 3.1.4.7, and the two most recent versions of the PROCESSOR-SDK-RTOS-K2HK. I have been getting errors trying to create CCS projects from the PDK by running pdkProjectCreate.bat. I guess I have a lot more to learn.

    >>>>> In the release download page, it has the CCS version listed, my suggestion is to use that version instead.

    My host platform is 32-bit Windows, so that apparently limits me to CCS 8.3.1, and that rules out the latest PROCESSOR-SDK-RTOS-K2HK, 06_00_00_07, which specifies 64-bit CCS 9. So, backing down to the next earlier PROCESSOR-SDK-RTOS-K2HK, 05_03_00_07, I should use the specified CCS 8.3.0 instead of CCS 8.3.1, correct?

    Best regards,
    Walt Rogers

  • Walt,

    Yes, XTCIEVMK2X is mounted with XTCI6638K2K.

    EVMK2H should have 66AK2H14 on board. 66ak2H14 is a superset of K2H devices. The purpose to have a superset of K2H device on EVMK2H is so we only need to provide one EVM, not multiple EVMs, one per device. The only exception is earlier/prototype version of EVMK2H may have 66AK2H12 mounted as 66AK2H12 silicon comes out first before 66AK2H14 device but EVM needs to be ready to use. But you EVMK2H version is 3.0 so it should be Okay.

    There is no 6636k2h, that was a type error. We have corrected it on the TCI6638K2K EVM ordering website.

    Difference between 66AK2H14 and 66AKEH12 is the former supports 10 GbE, so if you check 66AK2H14, in memory map section of datasheet, there is memory sections for 10 GbE. E.g.:  00 02F00000 to 00 02FFFFFF,  1M bytes, 10GbE Config for 66AK2H14 only. You can view/change this memory for K2H14 but it should be reserved for K2H12. But you need to write code to power on 10 GbE domain first.

    Another option if you want to be 100% sure: you can certainly use screw driver to remove the heat sink and heat sink compound and take a look. Be sure to apply new heat sink compound and then screw it back. However, I would not recommend it if you are not comfortable doing it yourself. I just happen to have the same version of XTCIEVMK2X EVM board that you have so I did it and confirmed it. I don't have the exact version of EVMK2H you have so I can't do it on my end.

    If possible, I would recommend you use the latest Processor SDK and CCS so you have all the latest fixes already.

    If you have to use old version (given limitation of your PC system), you can certainly go back to old SDK but you lose all the fixes/feature in between. You can refer to release notes to find out what you are missing.

    Either CCS 8.3.1 or CCS 8.3.0 should be Okay, there is only minor difference between them. My suggestion again is to use the CCS version that was specified in the Processor SDK download website to avoid unnecessary issue as that is the version being validated. A newer CCS version may or may be compatible with Processor SDK as they have different release cycles. But minor difference between CCS 8.3.1 and CCS 8.3.0 should be Okay in general unless there is fundamental change between them in terms of compiler and other tools' versions.

    From your response it seems you are using RTOS, not Linux?

    You can take a look at the user guide here:

    software-dl.ti.com/.../index_overview.html

    Search for "PDK example and test project creation". There are a lot of examples available once you create them so  you can just import it into CCS and use it as is.

    Best regards,

    David Zhou

  • Hi David,

    Thank you for the wealth of useful information.

    I visually identified the installed processors as XTCI6638K2K on the Rev2, A103 board, and X66AK2H12 on the Rev3, A104 board. (The Rev3 BOM wfcache.advantech.com/.../XEVMK2HX_BOM_Rev3_0.xlsx erroneously specifies the same processor and PCB revision as the Rev2 board.)

    I am using RTOS. I successfully created and ran the PDK GPIO_LedBlink_K2K_EVM_c66xTestProject and UART_BasicExample_K2K_c66xExampleProject projects on both boards using CCS 8.3.1 and ti-processor-sdk-rtos-k2hk-evm-05.03.00.07.

    After installing the SDK and "discovering" it in CCS, I encountered an issue during PDK CCS project creation. The pdkProjectCreate script stopped with the error that the TI C6000 compiler 8.3.2 was not installed. CCS RTSC did not discover the compiler, which was installed with the SDK. Perhaps I did something wrong. I fixed it by adding it to the compiler tools discovery path, although it never did appear in the Installation Details list. I still have a lot to learn about the development tools.

    Best regards,
    Walt Rogers

  • Walt,

    Glad to see your progress. Yes, you did the right thing to help CCS find the installed components. One trick is after you install a new component, say a new compiler, you would need to close CCS and then open it again. From my experience, CCS 9.x, if you are going to use it later on does a much better job in finding all the components.

    I think you are now on a solid ground now. Please continue with your project development.

    I would like to close this E2E. If you have new issues, please feel free to open a new thread. Thank you and good luck with your project.

    best regards,

    David Zhou