• State
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 214 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

PROCESSOR-SDK-AM64X: ddr clock enable takes 700 ms.

Jun Tu
Expert 1680 points

Part Number: PROCESSOR-SDK-AM64X
Other Parts Discussed in Thread: TMDS64EVM

Tool/software:

Hi, 

I am running TMDS64EVM board. I am in SBL stage, there is no OS. 

I am initializing ddr.

I found during the whole boot process, "ddr enable clock" takes 700ms. 

question. is this timing reasonable, is there a way to bypass? 

SOC_moduleClockEnable(TISCI_DEV_DDR16SS0, 1)  takes 670ms
SOC_moduleClockEnable(TISCI_DEV_FSS0,1) takes 3 ms. 

Why it takes that long to enable ddr clock. I mean the whole boot process, maybe < 1 second?  Enable that ddr clock takes 60% of time. 
 

Thanks
  • 0
    TI__Guru* 91155 points

    Hi Jun, 

    I'm not sure, but the clock enable for DDR may be accounting for the PLL locking time, which is probably taking up a majority of that time.   I agree that it seems long. 

    Do you have the full boot log?

    Regards,

    James

  • 0 in reply to JJD
    Expert 1680 points

    Hi,

    Here is the boot log. 

    uint32_t gSocModules[] = {
        TISCI_DEV_FSS0,
        TISCI_DEV_FSS0_FSAS_0,
        TISCI_DEV_FSS0_OSPI_0,

        TISCI_DEV_EMIF_DATA_0_VD,
        TISCI_DEV_DDR16SS0,

        TISCI_DEV_UART1,
        TISCI_DEV_UART0,

        SOC_MODULES_END,
    };
    Thanks.
    It  takes around 700ms to enable TISCI_DEV_DDR16SS0 clock

     


  • 0 in reply to Jun Tu
    TI__Guru* 91155 points

    Can you give more context on what this log is?  Is this a log from the trace port in CCS? 

    Is the 687ms referring to the 4th function (EMIF_DATA_0_VD) or the 5th function (DDR16SS0).  I'm wondering this because further down in the trace is a time of  1.36s, which seems to refer to the pinmux_init function in the line before.  Also, the first function trace doesn't have a time associated with it.

    Regards,

    James

  • 0 in reply to JJD
    Expert 1680 points

    for sure, it is a trace from lauterbach. it is not trace for CCS. 

    687ms refer to 5th function of DDR16ss0.  (Pinmux init is not a issue.can be ignored, I put a break point inside. )

    Thanks, I will try to use ccs provide a log as well.  

  • 0 in reply to Jun Tu
    TI__Guru* 91155 points

    I don't have a reason for the long time.  Please verify with CCS and let me know

    Regards,

    James