• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 359 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.

OPP and OPM status messages

DavidVescovi
Genius 5470 points

I am using an OMAP35XX and the 2.30 BSP

I noticed the OPP messages like:

OPM3
SetOpp to 2
Vdd1=0x30
VDD1 1.2000V

But these values do not match the table shown in:

http://processors.wiki.ti.com/index.php/WinCE-TIBSP_Power_Management

 

If as in the example above with Opp=2 VDD1 should be 1.000V and not 1.2000V as shown.

The 1.2000V should be for Opp=3.

All the status messages seem to be off by one from what the table shows.

Is this a bug? Is it just the status Opp indication label is wrong or something more?

 

 

  • 0
    Mastermind 9310 points

    SetOpp to 2

    comes from OALMSG(1, (L"SetOpp to %d \r\n", opp)); where opp is actually the index used in the function to access the following table:

    bsp_opp_map.h:

    static VddOppSetting_t  *_rgVdd1OppMap[VDD1_OPP_COUNT_35xx] = {    

    &vdd1Opp1Info,      // kOpp1    

     &vdd1Opp2Info,      // kOpp2    

    &vdd1Opp3Info,      // kOpp3    

     &vdd1Opp4Info,      // kOpp4    

     &vdd1Opp5Info,      // kOpp5    

    &vdd1Opp6Info       // kOpp6 };

    This variable actually points to OPP3 which is correct according to the wiki (OPP3: VDD1 = 1.200 V, MPU = 500 MHz, IVA = 360 MHz).

    Therefor, the trace is misleading and should actually be :

    OALMSG(1, (L"SetOpp to OPP%d \r\n", opp+1));

  • 0 in reply to Adeneo Embedded support team
    Genius 5470 points

    Thank you..that is exactly what I thought...and also how I fixed it too.

    Thanks for the confirmation.