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.

power down and up of the omap(3530) using the TSP65950

Other Parts Discussed in Thread: TPS65950, OMAP3530

I'm setting the DEVOFF bit in the P1_SW_EVENTS register to power off the OMAP.  So when I hit the power key it shuts down my unit but it will not power back up no matter what I do with the power button.

We have our power button connected to the PWRON pin, so when the power button is pressed the PWRON pin is tied low.

We have the chip setup as Master.

From reading the documentation I would think that if a signal is seen on the PWRON pin it should power up the OMAP with no software configuration, is this correct?

if I also set the STOPON_PWRON bit in the P1_SW_EVENTS register allong with the DEVOFF bit, then if I hold the power button down for 8 seconds it powers up the OMAP.

I am attempting to get the unit to power up, not having to wait the eight seconds

Should the unit power up with no software configuration if the PWRON is held low?

What other methods are there for powering down and/or up?

 

 

 

 

 

  • Hi,

    What you are attempting is correct. First TPS65950 should power ON and then it will provide power to the core supplies on OMAP.

    Is the other end of your power-on switch tied to VBAT? With a negative pulse on PWRON the device should power on, you need not have to use STOPON_PWRON.

    Main battery insertion and charger insertion are some of the other power-on options you can try.

     

    Regards,

    Gandhar.

     

     

  • Hi Guys,

    This thread comes with impeccable timing as I'm just looking into sorting out our power button functionality! Power-up on our board is fine, but I can't seem to figure out how to get the PWRON signal to trigger a power off... In the TRM 5.3.2.1it states "Pressing PWRON for 8 seconds without removing the battery also switches off the device (even if the
    backup registers are not reset).
    " Most if not all related TPS65950 regs should be in their reset default states, and trying this appears to have no effect.

    Really there are two things we'd like to achieve :

    1. To start with, just have a TPS65950 controlled 'hard' power off initiated by PWRON
    2. Use PWRON to trigger a software initiated power off.

    (2) we can do already as we can catch the PWRON interrupt from in the kernel. However if for some reason the kernel is hung, or we are prior to the kernel executing we need to be able to initiate the power off in hardware... I've scoured the TRM but am having difficulty in seeing how we can do this...?!

    Cheers,

    ~Pev

     

     

  • I'm setting the DEVOFF bit in the P1_SW_EVENTS register to power off.

    Is this an exceptable way to power off?

    Does there need to be any sw configuration to have the PWRON low signal,  trigger a powerup?

    Is there anything that could be preventing the PWRON low signal from triggering a power up?

     

  • Hi Pev,

    Please refer table 5-12, the device will restart under the conditions you mention (and not power-off). Section 5.3.2.1 is a typo and I will correct it.

     

    Hi Sean,

    Setting DEVOFF is the correct way to power off the device.

    There is no special need in software configuration, STARTON_PWON is default set to '1'. I am assuming you do not change any of these settings in software.

     

    Regards,

    Gandhar.

     

  • STARTON_PWON is an indication when a keypad button is pressed.  we are not using the keypad controller.  We have our power button directly connected to the PWRON signal going to the TPS65950.

    When the documentation refers to keypad button, is it refering to the keypad controller section of the TPS65950?

  • Hi,

    STARTON_PWON refers to PWRON only. I need to fix the typo in the description.

     

    Regards,

    Gandhar.

     

  • Can you point me to or provide the best reference material (most informative and descriptive) for the power management code used in Android, 2.6.27 kernal?

     

     

     

  • When I set the STARTON_PWON bit and I removed the power managment stuff from our BSP, I was able to power up by pressing the power button. So it seems the power management software(used in android kernal 2.6.27) is handling the warmrestart coming back from the omap and not ignoring it. So if you could identify that code it would help greatly.

  • If I don't have the power management sw I can power down and then hit the power button and it powers back up completely.  When I add in the power management SW I can power down, but then when I attempt to power up it will power the OMAP up when I hit the button, but that is it.  the display and other functionality does not come up.  Do you know any part of the power managment that could be preventing the rest of the system from coming up?

     

  • Hi Gandhar,

    I have a similar issue.

    The power button on TI's Omapzoom II (omap34xx-based) doesn't work at all with Android, 2.6.27 kernal.     Could you provide some clue ?

     

    Thanks,

    Charles

  • Hi Charles,

    Can you try to use version 2.6.29?

    This is the version that is supported by TI. I dont know the exact issues in the older version. Looks to me that some fixes went in the newer versions. Sean was able to take some changes from the newer version and he got it working on his board.

    Sean - if it is easy to share the fixes then please post on the forum. That would be a great help to the community.

    Thank you

     

    Regards,

    Gandhar.

     

  • Hi Gandhar,

    I have the same issue when use 65920/OMAP3530.

    I have a board which can run WINCE6 and Android. The power key connected to the 65920.PWRON pin, so when the power key is pressed the PWRON pin is tied low. I set the DEVOFF bit in the P1_SW_EVENTS register to make 65920 starts an ACTIVE-to-OFF mode.

    In WINCE, when I set DEVOFF to power off OMAP3530 then hit power key, the OMAP3530 can not power on. But in Android, when I do the same operation, the OMAP3530 can be power off and power on.

    Should I set any other registers before set P1_SW_EVENTS.DEVOFF in WINCE?

     

    Regards,

    Ben