Re: [Gumstix-users] fatls returns "Unable to use ide"

[Birger Brunswiek <birger.b@gm...>]

Digging in the list's archives I found a discussion on the topic "Wifistix-CF
Boot Problems" which essentially says that you can't use the wifistix-cf's cf in
uboot... and that is exactly what I was trying to do :-|

In one post Craig said that he was going to look into this. From the discussion
I was unable to determine whether a solution was ever found.

Regards,
Birger

[Gumstix-users] fatls returns "Unable to use ide"

[Birger Brunswiek <birger.b@gm...>]

Hello List,
I am having difficulties to access my Compact Flash card from uboot on a
Wifistix which is connected to a Connex 400 xm and a Console-st. The
instructions as described on http://docwiki.gumstix.org/U-Boot#The_CF_car=
d don't
seem to work for me. "fatls ide 0" always returns "** Unable to use ide 0=
:1 for
fatls **". Believing that I may have provided the wrong partition number,=
 I also
tried to do "fatls ide 1" but that doesn't seem to make a difference.

The CF card I use has 1 GB of space, a single partition which is fat form=
atted,
and there is one file in the file system's root dir. If I boot the Connex=

normally I can access the file without any problems.

Here are the gory details:
U-Boot 1.1.4 (Nov  6 2006 - 11:20:03) - 400 MHz - 1161

*** Welcome to Gumstix ***

U-Boot code: A3F00000 -> A3F25DE4  BSS: -> A3F5AF00
RAM Configuration:
Bank #0: a0000000 64 MB
Flash: 16 MB
Using default environment

SMC91C1111-0
Net:   SMC91C1111-0
Hit any key to stop autoboot:  0
GUM> pinit on
Marvell 802.11 CF ID: 04
            Network Adapter Card
GUM> fatls ide 0

** Unable to use ide 0:1 for fatls **

Well, then I boot the thing ... and we see that the card and its data can=
 be
accessed:
# ls /mnt/cf
# mount /mnt/cf
# ls /mnt/cf
HelloWorld.txt
# cat /mnt/cf/HelloWorld.txt
Hello World!

And yes, there really is a fat file system on the one partition of the CF=
 card:
# fdisk -l /dev/hda

Disk /dev/hda: 1014 MB, 1014644736 bytes
255 heads, 63 sectors/track, 123 cylinders
Units =3D cylinders of 16065 * 512 =3D 8225280 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1               1         123      987966    6  FAT16
# cat /proc/mounts
[...]
/dev/hda1 /mnt/cf vfat
rw,sync,fmask=3D0022,dmask=3D0022,codepage=3Dcp437,iocharset=3Diso8859-1 =
0 0

Does anybody know what prevents me from accessing the CF card from uboot?=


Regards,
Birger

Re: [Gumstix-users] fatls returns "Unable to use ide"

[Birger Brunswiek <birger.b@gm...>]

Digging in the list's archives I found a discussion on the topic "Wifistix-CF
Boot Problems" which essentially says that you can't use the wifistix-cf's cf in
uboot... and that is exactly what I was trying to do :-|

In one post Craig said that he was going to look into this. From the discussion
I was unable to determine whether a solution was ever found.

Regards,
Birger

Re: [Gumstix-users] fatls returns "Unable to use ide"

[Craig Hughes <craig@gu...>]

On Sep 1, 2007, at 3:19 PM, Birger Brunswiek wrote:

> Digging in the list's archives I found a discussion on the topic  
> "Wifistix-CF
> Boot Problems" which essentially says that you can't use the  
> wifistix-cf's cf in
> uboot... and that is exactly what I was trying to do :-|
>
> In one post Craig said that he was going to look into this. From  
> the discussion
> I was unable to determine whether a solution was ever found.

I'm afraid it's still on my todo list; the u-boot code is looking at  
the "first" CF slot, which on the wifi-cf is where the wifi module  
is, rather than the CF card slot.  I really need to add the u-boot  
the code which makes the CPLD on the wifi-cf do the slot-switching  
that needs to be done to allow comms with the card slot too.

C

Re: [Gumstix-users] fatls returns "Unable to use ide"

[Birger Brunswiek <birger.b@gm...>]

Craig Hughes wrote:
>> Digging in the list's archives I found a discussion on the topic =20
>> "Wifistix-CF
>> Boot Problems" which essentially says that you can't use the =20
>> wifistix-cf's cf in
>> uboot... and that is exactly what I was trying to do :-|
>>
>> In one post Craig said that he was going to look into this. From =20
>> the discussion
>> I was unable to determine whether a solution was ever found.
>=20
> I'm afraid it's still on my todo list; the u-boot code is looking at =20
> the "first" CF slot, which on the wifi-cf is where the wifi module =20
> is, rather than the CF card slot.  I really need to add the u-boot =20
> the code which makes the CPLD on the wifi-cf do the slot-switching =20
> that needs to be done to allow comms with the card slot too.

If you could provide me some pointers I might be able to fix this myself.=


Birger

Re: [Gumstix-users] fatls returns "Unable to use ide"

[Craig Hughes <craig@gu...>]

On Sep 4, 2007, at 12:18 PM, Birger Brunswiek wrote:

> Craig Hughes wrote:
>>> Digging in the list's archives I found a discussion on the topic
>>> "Wifistix-CF
>>> Boot Problems" which essentially says that you can't use the
>>> wifistix-cf's cf in
>>> uboot... and that is exactly what I was trying to do :-|
>>>
>>> In one post Craig said that he was going to look into this. From
>>> the discussion
>>> I was unable to determine whether a solution was ever found.
>>
>> I'm afraid it's still on my todo list; the u-boot code is looking at
>> the "first" CF slot, which on the wifi-cf is where the wifi module
>> is, rather than the CF card slot.  I really need to add the u-boot
>> the code which makes the CPLD on the wifi-cf do the slot-switching
>> that needs to be done to allow comms with the card slot too.
>
> If you could provide me some pointers I might be able to fix this  
> myself.

If you look at

<http://websvn.gumstix.com/filedetails.php?repname=Buildroot&path=% 
2Ftrunk%2Ftarget%2Fdevice%2FGumstix%2Fkernel-patches%2Fcompact- 
flash.patch>

You'll see the function gumstix_count_cards() defined.  The comments  
above the function explain it a bit.  Basically on the wifi-CF and cf- 
cf cards, there is a CPLD which does the switching between the 2  
cards.  In order to differentiate between those boards which have the  
CPLD (and thus 2 CF "slots) vs those which don't, we also programmed  
the CPLD to return the contents of a shift register when the CF reset  
line is held in reset.  To read from the CPLD shift register, while  
RESET is asserted, you have to tick a "clock" on the nPOE line, and  
the data can be read one bit at a time on the nCD0 line.  The CPLDs  
are programmed to return 0xC2.  If there's no CPLD there (just a CF  
card held in reset or no CF card), then this sequence of events will  
just read back 0xFF since the nCD0 line is pulled high.

So you'll basically need to reproduce that CF detection sequence into  
u-boot.  IIRC, the detection sequence works fine multiple times --  
each time the CF reset line is exercised, the CPLD resets the shift  
register, so no changes to linux ought to be needed.

C