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.

Initialization procedure for bare metal application on TMS320C6678

Other Parts Discussed in Thread: TMS320C6678

Hi everybody, I have a simple question:

If I would like to run a bare metal application running in a TMS320C6678 dev board (without using SYS/BIOS), what is the standard initialization procedure that I have to implement in software, from the POR to the execution of the application code?

I mean: I've to do PLL init, DDR controller init, ...and what else? If I set the PLL in hardware with PLL Boot configuration BOOTMODE pin, is really necessary to set the PLL in software?

thank you in advance for the answer

Carmine

PS: I am really new to this kind of platform

  • Are you planning on bootloading the code, or running from CCS?  If bootloading, what peripheral are you bootloading from?

    For CCS loading of code, you can have the GEL file configure the PLL and DDR for you.  There's really nothing else you need to configure to get going out of the box.  Actually, you don't need to configure DDR unless you're using the DDR memory space.

    For bootloading, it depends on the bootmode if you need to configure the PLL or not.  The I2C and SPI bootmodes require the PLL to be programmed (usually with the bootcode), the other bootmodes will sample three of the boot pins, which need to be driven to a specific value for the various input clocks (see the Data Manual) and then using the DEVSPEED of the device it will program the PLL for you.

    Best Regards,
    Chad 

  • I have to do a bootloading from a nor flash, so the bootmode pins will be emif16, 1250Mhz device with 100 Mhz external osc. So, in this configuration, if I dont want to change the frequency from 1250mhz do I have to set the PLL in software?

    thank you,

    Carmine 

  • For EMIF boot bootmode[12:10] pins are used for configuring the PLL.  Please see the Data Manual for details in Chapter 2.

    Best Regards,

    Chad