• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 122 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.

DRA829J: AVS-Class0 - VDD_CC

Antonio Pinto
Prodigy 130 points
Part Number: DRA829J
Other Parts Discussed in Thread: DRA829

Tool/software:

Dear TI-Team,

According DRA829 TRM (SPRUIL1D), only VDD_CC is supported for AVS-Class0.

When checking PDK implementation to configure PMIC (SBL_SetupPmicCfg), we realized that logic reads all voltage domains and checks which is supported.

However, we want to read and configure VDD_CC only (avoiding multiple readings).

Can you please confirm which is the corresponding index for VDD_CC?
According to the read values it corresponds to index 2 (WKUP_VTM_VD_OPPVID_j where j = 2) but we didn't find any evidence in the documentation that confirms the value.

Additionally, is this index fixed or may change in the future?

Thank you in advance.
António

  • 0
    TI__Guru**** 163630 points

    Hi António,

    Apologies for the delayed response.

    This is the code which finally sets voltage.

    if (vtmDevInfo & CSL_VTM_CFG1_DEVINFO_AVS0_SUP_MASK)
    {
    vtmOppVid = (vtmOppVid & vtmOppVidMask) >> opp;
    pmicCfg->millivolts = sblMapOtpVidToMilliVolts[vtmOppVid];
    SBL_log(SBL_LOG_MAX, "Efuse xlated: VD %d to %d mV (OppVid: 0x%x, Slave:0x%x, Res:0x%x)\r\n", vd, pmicCfg->millivolts, vtmOppVid, pmicCfg->slaveAddr, pmicCfg->powerResource);
    }

    Antonio Pinto said:

    Additionally, is this index fixed or may change in the future?

    For a particular SoC. This should be fixed. You should be able to avoid the loop.

    I am looping in HW expert to get double confirmation.

    - Keerthy

  • 0 in reply to Keerthy J
    TI__Guru 54512 points

    Keerthy,

    The index is fixed for a particular SoC + domain + OPP.

    Regards,

    Kyle

  • 0 in reply to Keerthy J
    Prodigy 130 points

    Hi Keerthy

    Thanks for your answer.

    Can you please confirm which is the index to read "vtmDevInfo" and "vtmOppVid" for VDD_CC?

    I mean, the "j" value to be used in the MMR registers "WKUP_VTM_VD_DEVINFO_j" and WKUP_VTM_VD_OPPVID_j.

    Thank you.
    António