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.

RTOS/66AK2H12: Moving from the GEL file on the EVM, to SoC initialization on production chip

Part Number: 66AK2H12

Tool/software: TI-RTOS

Hi there,

We are working on transitioning from demo software on the EVMK2H evaluation module to a production 66AK2H12 chip. So far we have been putting software on our DSP chips on the EVMK2H by first loading the correct GEL file onto the selected DSP core via Code Composer Studio, and then loading a .out file onto that DSP core. We are running SYS/BIOS on all DSP cores.

We need to transition away from Code Composer Studio so that when we finally manufacture a prototype board with the 66AK2H12 chip we are ready to go. Currently, we want to start by switching to having the system pull the .out image for each DSP core from an SD card and then loading it onto each DSP core. This leads to some questions:

  • How do pull the .out image from an SD card properly, and load it onto a DSP core? Do we use the secondary bootloader? If so, how do we do this and how do we prepare the SD card.

  • How do we initialize the DSP core (PLL, clocks, DDR3, etc) without a GEL file? I see that the GEL file is written in syntax that looks like C, is there a place that we can find "initialization" code that we can run on startup that mimics the functionality of the GEL files?

  • How can we see what hardware changes to expect when we transition from the EVMK2H to the 66AK2H12 chip? Obviously our memory regions will change, is there a document that details any other changes and what the transition process looks like?

Thanks!

Andre

  • Andre,

    The functionality provided by GEL file in the debug environment of enabling clocks, and modules and setting up the external DDR memory is provided by the secondary bootloader software that we provide in the Processor SDK RTOS. The secondary bootloader is part of a two step boot process where the ROM bootloader on the device loads the secondary bootloader code to MSMC memory from flash or supported boot media and then the secondary bootloader (user defined) sets up the clocks, PSC and DDR memory and copies the application from an offset in flash to device memory.

    The secondary bootloader software and documentation is provided in PRocessor SDK RTOS and documented in the software developers guide:

    http://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_Foundational_Components.html#k2h-k2e-k2l

    K2H device doesn`t support SDMMC interface or booting from it. We provide flash programming utilities that allow programming of flash over JTAG as you can see from the description. 

    The .out that you are using in CCS needs to be converted to a app binary file using the utilities out2rprc.exe and MutlicoreImageGen.exe as described in the software developers guide.

    As far as porting K2H EVM to your custom design is concerned, you need to follow the process that is described here:

    http://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_board.html#custom-board-addition

    Regards,

    Rahul

  • Thank you very much! This has been super useful.