Re: Problems on sleep/resume in XScale and PB 4.2

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: lur (lur444_at_hotmail.com)
Date: 06/11/04 

Date: 11 Jun 2004 04:48:00 -0700

Hi,

Thanks for your answer Cliff. I have looked up the PWR_EN signal and
it is working correctly: when I select the "Start->Suspend" option or
I use the power button driver, which uses the S17 switch, the system
enters in suspend sequency and when the code of the OEMPowerOff()
function is executed and the PXA255 enters in sleep mode, the PWR_EN
signal goes low and when a edge is detected in the GPIO1, the PWR_EN
signal goes high.

And what is more, the RESET_OUT signal is also selected and deselected
in this process, so is supposed that the reset is happening correctly
and that the reset handler should be entered and its code should be
executed, but it isn't happening. I am going to try to put a scope in
the rest of the signals that reach to the Flash and I am going to try
to find what is happenning.

By the way: is there any difference between the way that is followed
on suspend/resume when you select the "Start->Suspend" or when you use
the power button??

And I have another question: I'm not sure if I should define the
B_STEP_PXA2X0 flag for the PXA255 or not. In some cases I think that
this code is necessary for this microprocessor, but in other cases,
like in the first lines of the reset handler in the fwxsc1.s file, I'm
not completely sure.

Thanks in advance for your help,

Lur

Cliff Brake <cbrake_n*sp*M@bec-systems_n*sp*m.com> wrote in message news:<eUGOTWvTEHA.3528@TK2MSFTNGP12.phx.gbl>...
> Have you looked at the hardware to make sure it is getting into suspend and
> trying to resume? I would put a scope on the PXA255::PWR_EN signal. It
> should go low at the end of the suspend process and go high at the
> beginning of the resume process. This will tell you if you are making it
> into suspend properly and if it is trying to resume.
>
> Cliff Brake
> BEC Systems
>
>
> lur wrote:
>
> > Hi all,
> >
> > I'm working on the sleep/resume of an Intel's DBPXA255 based platform
> > using PB
> > 4.2.
> >
> > When I select "Start->Suspend" the execution goes to the OEMPowerOff()
> > function and it makes the PXA255 sleep correctly. I have configured
> > the GPIO1
> > like wake up source in the OEMPowerOff() function but when I use this
> > GPIO for
> > waking up from sleep, the system doesn´t wake up correctly.
> >
> > I have proved to enable the TEST_NOT_REALLY_SLEEPING flag in the
> > pmgrxsc1.s
> > file. In this way the system returns correctly but if the sleep
> > occurs, then
> > the system seems to be hanged somewhere and it doesn´t resume.
> >
> > When the wake up event happens the execution is supposed to go to the
> > reset
> > handler so I have tried to show some codes through the displays while
> > the code
> > of the reset handler is executed but that codes doesn't appear in the
> > displays
> > when I am waking up from sleep so I don't know if the reset handler is
> > entered
> > or not.
> >
> > Has anyone any idea about what would be the problem?? Any similar
> > problem?? Any help would be esteemed.
> >
> > Thanks in advance,
> >
> > Lur

Relevant Pages

  • Re: deadlocks with intr NFS mounts and ^Z (or: PCATCH and sleepable locks)
    ... When the mount is set intr, this is an interruptible sleep, so ... that interrupting signals can abort the sleep. ... In the mean time we suspend as well. ...
    (freebsd-arch)
  • Re: Problems on sleep/resume in XScale and PB 4.2
    ... should go low at the end of the suspend process and go high at the ... > waking up from sleep, the system doesn´t wake up correctly. ... > handler so I have tried to show some codes through the displays while ... > when I am waking up from sleep so I don't know if the reset handler is ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Premature wakeup of time.sleep()
    ... >> The actual suspension time may be less than that requested because ... What signals would that be? ... KeyboardInterrupt exception - and which does interrupt the sleep() ... which is a granularity of 10ms. ...
    (comp.lang.python)
  • Re: Abolishing sleeps in issignal()
    ... mutex complicates sleep queues by forcing them to drop the spinlock to ... check for signals and then check for races. ... So SIGSTOP combined with a stopeventactually breaks because ... debugging events and SIGSTOP not aborting non-restartable syscalls as they ...
    (freebsd-arch)
  • Re: [suspend/resume] Re: userspace notification from module
    ... Actually I think this is what signals are there for and bringing this ... I'm not quite sure how this is implemented within the kernel, ... have lots of processes doing their suspend routines, ...
    (Linux-Kernel)