Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed the week of November 23.

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.

Compiler/EVMK2H: Porting Code From C6678EVM to K2HEVM

Part Number: EVMK2H

Tool/software: TI C/C++ Compiler

Hi,

I have a code that runs perfectly on the c6678, and was trying to port it to the K2H and I got few problems.

1. PCIe: one of the cores is running PCIe, the EVM is connected to a custom board, it shows Link up but when i try to read the Vendor Id i always get garbage (mostly 0xFFFFFF) are there any differences in the PCIE memory space or anything else that i am not aware of? both EVMs seem to have the same PCIe user guide ?

2. we created bootloader  .eth file for the C6678  Ethernet boot, which is working. i tried to do the same but as i see from the behavior of the K2HEVM it simply rejects the file i am sending and keeps sending boot request, the file is 12 mb in size if that makes any difference. As i understood, both EVMs have the same dsp cores but is there something different that i need to be aware of when i try bootloading through Ethernet ? different file format ? initialize arm cores ( which i do not use)?

Would be thankful for any help 

Jameel. 

  • Hi Jameel,

    1. The two SoCs do have some differences in their memory map. Consult the Memory Map section in the datasheet of both devices.

    2. Again check the memory maps. Also the following guide might be of use:
      

    There is a subsection for K2H/K2L/K2E  and C66x devices in the Platforms section.

    Best Regards,
    Yordan

  • Hi Yordan,

    Thanks for the reply. I did see the differences in the memory map of both EVMs and did the changes required. the code runs but not the PCIe module, link is up but i am reading wrong data.

    As for the bootloader I used RBL in C6678 and I can set the K2h to boot from Ethernet as well (DSP RBL ENET) however i am not getting any boot requests from the K2h. 

  • Have you checked the PCIe configuration from Processor SDK RTOS PCIe examples for K2H? Compare the register settings.

    Regarding ETH boot, can you check this wiki:
      

    Best Regards,
    Yordan

  • Hi Yordan,

    The wiki you just linked here is an example where ARM is the boot master, I am trying to bypass everything ARM related I need DSP boot Only, we are working on a project for a client and we simply need to make the K2H work the same way the c6678 works with minimal changes. changing all the boot process right now is not an option. as I understand there is a way for this but i cant find a solution to the problem that I can get no boot requests from the K2H on with DSP.

    best regards,

    Jameel

  • Hi Yordan,

    regarding the PCI, I managed to find the problem, it was a wrong definition of one of the addresses which was not defined with the rest of the address definitions. The entire system now works although it is working slower than the C6678. one of the cores runs an Ethernet connection with the pc and it is much slower and i will have to debug that. 

    Regarding the Ethernet boot, I am not able to make the DSP the boot master, although I followed the guides and it should be sending me boot request packet but I don't get any. Do you have any idea why is that ? I saw some other posts about DSP boot but no clear answer is given and always the answer is to use ARM first then wake up the DSP Cores, but that will change everything we have and we really don't have any time, we simply need the same boot sequence that worked on keystone 1 to work on keystone 2 without the ARM Cores.

    best regards,

    Jameel

  • Jameel,

     For K2H devices, we currently provide examples only for ARM boot master as you can see from the 

    Keystone II boot Examples Application notes

    The device does have ROM boot support for Ethernet boot similar to C6678 but this is not widely used. Can you please indicate what is your DEVSTAT settings.Can you check the IP address or provide wireshark logs. Is the ethernet port working independent of boot ?  Have you tried to see if your image is booting on K2H EVM ? This might be good first step to get this working on known good HW.

    Regards,

    Rahul