I've verified that CS5 is working, by reading from address 0x1400
in my bootloader (always seems to return 0, but the scope says that
the CS is getting activated). I'm suspicious that the board should
have PXA255 A0<->isp1161 A0, and that's why the driver can't seem to
do a software
On Mon, 20 Jun 2005, Michael wrote:
>
> --- Bill Gatliff <[EMAIL PROTECTED]> wrote:
>
> > Guys:
> >
> >
> >
> > I'm trying to use an isp1161 on a PXA255-based board. The
> > isp1161 is tied to CS5, with A1 tied to the isp1161's A0 pin
> > and A2 tied to the isp1161's A1 pin. I'm using ND
Michael:
Are you using the latest version of the isp116x driver?
These differences might be the diffs btw/ isp116x & isp1362,
but I thought it would be helpful.
I used ndelay, with the same address lines as well. My HW_SUSP is
tied high, but these chips could be different in this respect.
At
--- Bill Gatliff <[EMAIL PROTECTED]> wrote:
> Guys:
>
>
>
> I'm trying to use an isp1161 on a PXA255-based board. The
> isp1161 is tied to CS5, with A1 tied to the isp1161's A0 pin
> and A2 tied to the isp1161's A1 pin. I'm using NDELAY.
>
> My resources look like this:
>
> static struct
Ian:
Ian Campbell wrote:
Did you do this? In my experience this error is most often due to the
H_WAKEUP pin being pulled the wrong way (or not at all).
I didn't do the board, but I just caught that statement on p. 9 of the
datasheet... I'll break out the soldering iron, then get back to
On Wed, 2005-06-15 at 23:27 -0500, Bill Gatliff wrote:
> 116x: Clock not ready after 20ms
> 116x: The driver does not support hardware wakeup.
> 116x: Please make sure that the H_WAKEUP pin is pulled low!
Did you do this? In my experience this error is most often due to the
H_WAKEUP pin being pull
Guys:
I'm trying to use an isp1161 on a PXA255-based board. The isp1161 is
tied to CS5, with A1 tied to the isp1161's A0 pin and A2 tied to the
isp1161's A1 pin. I'm using NDELAY.
My resources look like this:
static struct resource isp116x_resources[] = {
[0] = {
.start = PXA255_CS5
