gumstix

Hi Mic,

> I am not a programmer but it looks to me like there is a bug in pxaregs.
> The RTAR_RTMV should be a static value but I have found it to increment at a
> rate of once per second.  When I look at various source listings for
> pxaregs.c, that register is shown at a physical address of 0x40900010 but by
> the Intel documentation it should be at 0x40900004.  The same document shows
> the physical address of 0x40900010 really occupied by the RTC Day Counter
> Register (RDCR) in which the low bits do reflect the seconds part of the
> current time.
>
> >From various listings of pxaregs.c
> { "RTAR", 0x40900010, 0, 0xffffffff, 'x', "RTC Alarm Register (4-30)" },
> { "RTAR_RTMV", 0x40900010, 0, 0xffffffff, 'x', "RTC Target Match Value" },

So one thing to keep in mind is that pxaregs was written for the
pxa255. Having said that, the RTC definitions for the PXA255 and
PXA270 both appear to be the same.
And, yes, I agree that the RTAR and RTAR_RTMV should both have
physical addresses of 0x4090004 and the RDCR register should have a
physical address of 0x40900010.

So the definition of the RTAR stuff in pxaregs appears to be incorrect.

-- 
Dave Hylands
Shuswap, BC, Canada
http://www.DaveHylands.com/

Hi Dave,

Thanks for taking a look at my question.  I thought it looked like pxaregs
might work for the PXA270.

So is there another utility with similar functionality that I can use from
the command line or shell script to read and write to the registers I need
to wake from standby?  I think it is only three registers.

Barring that, I assume that I can get the source, make the changes I have
identified, and rebuild pxaregs?  That's the sequence I don't have a clue on
where to start.

Thanks again,

Mic

-----Original Message-----

Date: Wed, 26 Nov 2008 19:57:37 -0800
From: "Dave Hylands" <dhylands@...>
Subject: Re: [Gumstix-users] RTC registers and alarms; PXA270
To: "General mailing list for gumstix users."
	<gumstix-users@...>
Message-ID:
	<c32efac40811261957p3776e7f9n7a879d76bb1859ef@...>
Content-Type: text/plain; charset=ISO-8859-1

Hi Mic,

> I am not a programmer but it looks to me like there is a bug in pxaregs.
> The RTAR_RTMV should be a static value but I have found it to increment at
a
> rate of once per second.  When I look at various source listings for
> pxaregs.c, that register is shown at a physical address of 0x40900010 but
by
> the Intel documentation it should be at 0x40900004.  The same document
shows
> the physical address of 0x40900010 really occupied by the RTC Day Counter
> Register (RDCR) in which the low bits do reflect the seconds part of the
> current time.
>
> >From various listings of pxaregs.c
> { "RTAR", 0x40900010, 0, 0xffffffff, 'x', "RTC Alarm Register (4-30)" },
> { "RTAR_RTMV", 0x40900010, 0, 0xffffffff, 'x', "RTC Target Match Value" },

So one thing to keep in mind is that pxaregs was written for the
pxa255. Having said that, the RTC definitions for the PXA255 and
PXA270 both appear to be the same.
And, yes, I agree that the RTAR and RTAR_RTMV should both have
physical addresses of 0x4090004 and the RDCR register should have a
physical address of 0x40900010.

So the definition of the RTAR stuff in pxaregs appears to be incorrect.

-- 
Dave Hylands
Shuswap, BC, Canada
http://www.DaveHylands.com/

Hi Mic,

> Thanks for taking a look at my question.  I thought it looked like pxaregs
> might work for the PXA270.

Yeah - for the most part the PXA270 registers overlap with the PXA255
registers. I was just pointing out that whenever you do find a problem
you should look at the PXA255 datasheet to see if things are right for
the PXA255 or not.

In this case, for the RTC registers, it appears to be wrong for both
processor, i.e. it's a bug in pxaregs.

> So is there another utility with similar functionality that I can use from
> the command line or shell script to read and write to the registers I need
> to wake from standby?  I think it is only three registers.
>
> Barring that, I assume that I can get the source, make the changes I have
> identified, and rebuild pxaregs?  That's the sequence I don't have a clue on
> where to start.

I know what to do for buildroot but not for OE, so I can't offer much help here.

You could just create your utility program and manually compile/link
it using the OE toolchain. You don't actually need to integrate it
into OE.

--
Dave Hylands
Shuswap, BC, Canada
http://www.DaveHylands.com/