WiFi not installed on SAM9263

Hi,

My journey to intergate a SDIO Wifi card to the AT91SAM9263 has reached some
stage. Following are the steps:
1. kernel 2.6.27 + AT91 patches are compiled and downloaded to the data
flash using U-boot
2. libertas source code is compiled. Both libertas.ko and
libertas_sdio.koare inserted.
3. i have copied sd8686.bin and helper_sd.bin (renamed to sd8686_helper.bin)
in /lib/firmware/ directory of the kernel on target board. Note: I am using
azurewave SDIO-wifi board with Marvell's 8686 chip.

problem: when libertas objects are installed (using insmod), i don't see any
message showing the downloading of the firmware. Can any one give the reason
for this problem?
when i insert the wifi card, I get the following message on the debug
console:
mmc0: new SDIO card at address 0001

I am no able to run "iwconfig" command and not able to configure an ip
address to ETH1 node. Following error I get:

# iwconfig eth1 essid "mynw"
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device eth1 ; No such device.

# ifconfig eth1 192.168.1.10
ifconfig: SIOCSIFADDR: No such device
# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.

appreciate any inputs to debug the above issue

thanks,
susa,. Start a New Thread

On Mon, 23 Nov 2009 20:32:07 +0530
suse auto wrote:
> problem: when libertas objects are installed (using insmod), i don't
> see any message showing the downloading of the firmware.

If you've got a syslog running, what is dmesg showing you? Can you use
modprobe instead of insmod and put a "-v" in there and see if that
gives you some diagnostic information?

Dan
Start a New Thread

Hi,

> Note: I am using azurewave SDIO-wifi board with Marvell's 8686 chip.

I think it's possible that the SDIO Vendor/Device ID for your azurewave
card doesn't match the existing ones in the Libertas interface.
Specifically, check for matching IDs in the if_sdio.c file where the
device LUT is (line 66) :

static const struct sdio_device_id if_sdio_ids[] = {
{ SDIO_DEVICE(SDIO_VENDOR_ID_MARVELL,
SDIO_DEVICE_ID_MARVELL_LIBERTAS) },
{ SDIO_DEVICE(SDIO_VENDOR_ID_MARVELL,
SDIO_DEVICE_ID_MARVELL_8688WLAN) },
{ /* end: all zeroes */ },
};

If your card doesn't match the above IDs, the Libertas code will ignore
your card completely. If so, add yours and recompile.
This is just a thought, but probably a good chance that this is the
problem (or at least, that's where I'd start looking first).

HTH
B Rgds
Kris

On Mon, 2009-11-23 at 20:32 +0530, suse auto wrote:
> Hi,
>
> My journey to intergate a SDIO Wifi card to the AT91SAM9263 has
> reached some stage. Following are the steps:
> 1. kernel 2.6.27 + AT91 patches are compiled and downloaded to the
> data flash using U-boot
> 2. libertas source code is compiled. Both libertas.ko and
> libertas_sdio.ko are inserted.
> 3. i have copied sd8686.bin and helper_sd.bin (renamed to
> sd8686_helper.bin) in /lib/firmware/ directory of the kernel on target
> board. Note: I am using azurewave SDIO-wifi board with Marvell's 8686
> chip.
>
> problem: when libertas objects are installed (using insmod), i don't
> see any message showing the downloading of the firmware. Can any one
> give the reason for this problem?
> when i insert the wifi card, I get the following message on the debug
> console:
> mmc0: new SDIO card at address 0001
>
> I am no able to run "iwconfig" command and not able to configure an ip
> address to ETH1 node. Following error I get:
>
> # iwconfig eth1 essid "mynw"
> Error for wireless request "Set ESSID" (8B1A) :
> SET failed on device eth1 ; No such device.
>
> # ifconfig eth1 192.168.1.10
> ifconfig: SIOCSIFADDR: No such device
> # iwconfig
> lo no wireless extensions.
> eth0 no wireless extensions.
>
> appreciate any inputs to debug the above issue
>
> thanks,
> susa,.
>

Start a New Thread

Hi,

In the kernel; configuration menu and in the Network device support
submenu,go to the wireless submenu ahnd enable wireless extensions.

Regards
TVRPrasad
On 11/23/09, suse auto wrote:
>
> Hi,
>
> My journey to intergate a SDIO Wifi card to the AT91SAM9263 has reached
> some stage. Following are the steps:
> 1. kernel 2.6.27 + AT91 patches are compiled and downloaded to the data
> flash using U-boot
> 2. libertas source code is compiled. Both libertas.ko and libertas_sdio.koare inserted.
> 3. i have copied sd8686.bin and helper_sd.bin (renamed to
> sd8686_helper.bin) in /lib/firmware/ directory of the kernel on target
> board. Note: I am using azurewave SDIO-wifi board with Marvell's 8686 chip.
>
> problem: when libertas objects are installed (using insmod), i don't see
> any message showing the downloading of the firmware. Can any one give the
> reason for this problem?
> when i insert the wifi card, I get the following message on the debug
> console:
> mmc0: new SDIO card at address 0001
>
> I am no able to run "iwconfig" command and not able to configure an ip
> address to ETH1 node. Following error I get:
>
> # iwconfig eth1 essid "mynw"
> Error for wireless request "Set ESSID" (8B1A) :
> SET failed on device eth1 ; No such device.
>
> # ifconfig eth1 192.168.1.10
> ifconfig: SIOCSIFADDR: No such device
> # iwconfig
> lo no wireless extensions.
> eth0 no wireless extensions.
>
> appreciate any inputs to debug the above issue
>
> thanks,
> susa,.
> Start a New Thread

hi,
I am still not able to install the wifi card on AT91SAM9263. I came across
in some mailing list that the firmware files at /lib/firmware/ will be
fetched by kernel only if an udev daemon is running. although i don't know
anything about this perhaps i feel this could be the reason for the issue.
can somebody brief me what is this udev?
i am confused as to whether '/udev' :

1. a module to be integrated with kernel while compiling?
2. a requires enabling of configuration parameter in kernel's
configuration file (i have enabled CONFIG_SYSFS=y, CONFIG_HOTPLUG=y).

non of the mailing list so far that i have referred explains /udev in simple
words. any light on this is appreciated.
please let me know if you require any info from the running kernel, i can
immediately post it for your ref.

thanks
-susan.

On Tue, Nov 24, 2009 at 8:21 PM, vishnu Tadepalli <
v...@gmail.com> wrote:

> Hi,
>
> In the kernel; configuration menu and in the Network device support
> submenu,go to the wireless submenu ahnd enable wireless extensions.
>
> Regards
> TVRPrasad
> On 11/23/09, suse auto wrote:
>>
>> Hi,
>>
>> My journey to intergate a SDIO Wifi card to the AT91SAM9263 has reached
>> some stage. Following are the steps:
>> 1. kernel 2.6.27 + AT91 patches are compiled and downloaded to the data
>> flash using U-boot
>> 2. libertas source code is compiled. Both libertas.ko and
>> libertas_sdio.ko are inserted.
>> 3. i have copied sd8686.bin and helper_sd.bin (renamed to
>> sd8686_helper.bin) in /lib/firmware/ directory of the kernel on target
>> board. Note: I am using azurewave SDIO-wifi board with Marvell's 8686 chip.
>>
>> problem: when libertas objects are installed (using insmod), i don't see
>> any message showing the downloading of the firmware. Can any one give the
>> reason for this problem?
>> when i insert the wifi card, I get the following message on the debug
>> console:
>> mmc0: new SDIO card at address 0001
>>
>> I am no able to run "iwconfig" command and not able to configure an ip
>> address to ETH1 node. Following error I get:
>>
>> # iwconfig eth1 essid "mynw"
>> Error for wireless request "Set ESSID" (8B1A) :
>> SET failed on device eth1 ; No such device.
>>
>> # ifconfig eth1 192.168.1.10
>> ifconfig: SIOCSIFADDR: No such device
>> # iwconfig
>> lo no wireless extensions.
>> eth0 no wireless extensions.
>>
>> appreciate any inputs to debug the above issue
>>
>> thanks,
>> susa,.
>
> Start a New Thread

On Fri, 27 Nov 2009 18:41:38 +0530
suse auto wrote:
> reason for the issue. can somebody brief me what is this udev?

udev is a user-space daemon that manages devices. Among other things,
when the kernel detects device changes it runs (by default, this can be
changed) /sbin/hotplug. If you're running udev on your
system, /sbin/hotplug is a part of udev that does the user space
manipulations to create the new devices in /dev and do other
system-specific stuff (on a desktop machine, it might also try to mount
that device and pop up a folder on the resulting filesystem, for
instance).

(Just for completeness, you can often manually run "mdev -s" to create
devices that the kernel knows about, but that aren't created in the /dev
filesystem yet. Recently I wanted to mount USB drives and do things with
the resulting filesystem but thought udev added unneeded complexity, so
my app just watched the syslog output, spawned mdev to create the
device, did the mount itself, and then accessed the resulting data.)

A full running Linux system can require a lot more than just a kernel.
How are you compiling your system utilities to go along with your
kernel? One of the scripts like "buildroot" that creates the uCLibC
environment? udev is probably an option in that environment somewhere.

Dan
Start a New Thread

Hello,

I am still not able to install the SDIO wifi card on AT91SAM9263.
I have placed sd8686.bin and sd8686_helper.bin files in /lib/firmware/

When I insert the SDIO wifi card to the MMC interface; the board detects by
printing the following msg:
firmware: requesting sd8686_helper.bin
libertas: can't load helper firmware
libertas: failed to load helper firmware
libertas_sdio: probe of mmc0:0001:1 failed with error -2
When I *dmesg* it, i get the following message:
-----------/ start of dmesg messsage /-------------------
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
mmc0: starting CMD52 arg 80022000 flags 00000195
Sending command 52 as 00001074, arg = 80022000, blocks = 0, length = 0 (MR 00001B01)
MCI irq: status = 0000C0E5, C07F0001, 00000001
Command ready
Completed command
Status = 00000001/0000c0e5 [00001000 00000000 00000000 00000000]
mmc0: req done (CMD52): 0: 00001000 00000000 00000000 00000000
mmc0: starting CMD52 arg 80022201 flags 00000195
Sending command 52 as 00001074, arg = 80022201, blocks = 0, length = 0 (MR 00001B01)
MCI irq: status = 0000C0E5, C07F0001, 00000001
Command ready
Completed command
Status = 00000001/0000c0e5 [00001001 00000000 00000000 00000000]
mmc0: req done (CMD52): 0: 00001001 00000000 00000000 00000000
SDIO: Enabling device mmc0:0001:1...
mmc0: starting CMD52 arg 00000400 flags 00000195
Sending command 52 as 00001074, arg = 00000400, blocks = 0, length = 0 (MR 00001B01)
MCI irq: status = 0000C0E5, C07F0001, 00000001
Command ready
Completed command
Status = 00000001/0000c0e5 [00001000 00000000 00000000 00000000]
mmc0: req done (CMD52): 0: 00001000 00000000 00000000 00000000
mmc0: starting CMD52 arg 80000402 flags 00000195
Sending command 52 as 00001074, arg = 80000402, blocks = 0, length = 0 (MR 00001B01)
MCI irq: status = 0000C0E5, C07F0001, 00000001
Command ready
Completed command
Status = 00000001/0000c0e5 [00001002 00000000 00000000 00000000]
mmc0: req done (CMD52): 0: 00001002 00000000 00000000 00000000
mmc0: starting CMD52 arg 00000600 flags 00000195
Sending command 52 as 00001074, arg = 00000600, blocks = 0, length = 0 (MR 00001B01)
MCI irq: status = 0000C0E5, C07F0001, 00000001
Command ready
Completed command
Status = 00000001/0000c0e5 [00001002 00000000 00000000 00000000]
mmc0: req done (CMD52): 0: 00001002 00000000 00000000 00000000
SDIO: Enabled device mmc0:0001:1
SDIO: Enabling IRQ for mmc0:0001:1...
mmc0: starting CMD52 arg 00000800 flags 00000195
Sending command 52 as 00001074, arg = 00000800, blocks = 0, length = 0 (MR 00001B01)
MCI irq: status = 0000C0E5, C07F0001, 00000001
Command ready
Completed command
Status = 00000001/0000c0e5 [00001000 00000000 00000000 00000000]
mmc0: req done (CMD52): 0: 00001000 00000000 00000000 00000000
mmc0: starting CMD52 arg 80000803 flags 00000195
Sending command 52 as 00001074, arg = 80000803, blocks = 0, length = 0 (MR 00001B01)
MCI irq: status = 0000C0E5, C07F0001, 00000001
Command ready
Completed command
Status = 00000001/0000c0e5 [00001003 00000000 00000000 00000000]
mmc0: req done (CMD52): 0: 00001003 00000000 00000000 00000000
mmc0: starting CMD52 arg 10000000 flags 00000195
Sending command 52 as 00001074, arg = 10000000, blocks = 0, length = 0 (MR 00001B01)
MCI irq: status = 0000C0E5, C07F0001, 00000001
Command ready
Completed command
Status = 00000001/0000c0e5 [00001000 00000000 00000000 00000000]
mmc0: req done (CMD52): 0: 00001000 00000000 00000000 00000000
mmc0: starting CMD52 arg 10000200 flags 00000195
Sending command 52 as 00001074, arg = 10000200, blocks = 0, length = 0 (MR 00001B01)
MCI irq: status = 0000C0E5, C07F0001, 00000001
Command ready
Completed command
Status = 00000001/0000c0e5 [00001000 00000000 00000000 00000000]
mmc0: req done (CMD52): 0: 00001000 00000000 00000000 00000000
mmc0: starting CMD52 arg 10000400 flags 00000195
Sending command 52 as 00001074, arg = 10000400, blocks = 0, length = 0 (MR 00001B01)
MCI irq: status = 0000C0E5, C07F0001, 00000001
Command ready
Completed command
Status = 00000001/0000c0e5 [00001001 00000000 00000000 00000000]
mmc0: req done (CMD52): 0: 00001001 00000000 00000000 00000000
mmc0: IRQ thread started (poll period = 2147483647 jiffies)
mmc0: starting CMD52 arg 10006800 flags 00000195
Sending command 52 as 00001074, arg = 10006800, blocks = 0, length = 0 (MR 00001B01)
MCI irq: status = 0000C0E5, C07F0001, 00000001
Command ready
Completed command
Status = 00000001/0000c0e5 [00001000 00000000 00000000 00000000]
mmc0: req done (CMD52): 0: 00001000 00000000 00000000 00000000
mmc0: starting CMD52 arg 10006a00 flags 00000195
Sending command 52 as 00001074, arg = 10006A00, blocks = 0, length = 0 (MR 00001B01)
MCI irq: status = 0000C0E5, C07F0001, 00000001
Command ready
Completed command
Status = 00000001/0000c0e5 [00001000 00000000 00000000 00000000]
mmc0: req done (CMD52): 0: 00001000 00000000 00000000 00000000
firmware: requesting sd8686_helper.bin
mmc0: starting CMD52 arg 00000a00 flags 00000195
Sending command 52 as 00001074, arg = 00000A00, blocks = 0, length = 0 (MR 00001B01)
MCI irq: status = 0000C0E5, C07F0001, 00000001
Command ready
Completed command
Status = 00000001/0000c0e5 [00001000 00000000 00000000 00000000]
mmc0: req done (CMD52): 0: 00001000 00000000 00000000 00000000
mmc0: sdio_irq A : enable
libertas: can't load helper firmware
libertas: failed to load helper firmware
SDIO: Disabling IRQ for mmc0:0001:1...
mmc0: sdio_irq A : disable
mmc0: IRQ thread exiting with code 0
mmc0: starting CMD52 arg 00000800 flags 00000195
Sending command 52 as 00001074, arg = 00000800, blocks = 0, length = 0 (MR 00001B01)
MCI irq: status = 0000C0E5, C07F0001, 00000001
Command ready
Completed command
Status = 00000001/0000c0e5 [00001003 00000000 00000000 00000000]
mmc0: req done (CMD52): 0: 00001003 00000000 00000000 00000000
mmc0: starting CMD52 arg 80000800 flags 00000195
Sending command 52 as 00001074, arg = 80000800, blocks = 0, length = 0 (MR 00001B01)
MCI irq: status = 0000C0E5, C07F0001, 00000001
Command ready
Completed command
Status = 00000001/0000c0e5 [00001000 00000000 00000000 00000000]
mmc0: req done (CMD52): 0: 00001000 00000000 00000000 00000000
SDIO: Disabling device mmc0:0001:1...
mmc0: starting CMD52 arg 00000400 flags 00000195
Sending command 52 as 00001074, arg = 00000400, blocks = 0, length = 0 (MR 00001B01)
MCI irq: status = 0000C0E5, C07F0001, 00000001
Command ready
Completed command
Status = 00000001/0000c0e5 [00001002 00000000 00000000 00000000]
mmc0: req done (CMD52): 0: 00001002 00000000 00000000 00000000
mmc0: starting CMD52 arg 80000400 flags 00000195
Sending command 52 as 00001074, arg = 80000400, blocks = 0, length = 0 (MR 00001B01)
MCI irq: status = 0000C0E5, C07F0001, 00000001
Command ready
Completed command
Status = 00000001/0000c0e5 [00001000 00000000 00000000 00000000]
mmc0: req done (CMD52): 0: 00001000 00000000 00000000 00000000
SDIO: Disabled device mmc0:0001:1
libertas_sdio: probe of mmc0:0001:1 failed with error -2
---------- / End of dmesg message /--------------------
Below are the processes running on the board. the command *ps -ef* listed
the below processes:
# ps -ef
PID USER COMMAND
1 root init
2 root [kthreadd]
3 root [ksoftirqd/0]
4 root [events/0]
5 root [khelper]
66 root [kblockd/0]
69 root [cqueue]
77 root [ksuspend_usbd]
82 root [khubd]
86 root [kmmcd]
113 root [pdflush]
114 root [pdflush]
115 root [kswapd0]
116 root [aio/0]
117 root [nfsiod]
284 root [mtdblockd]
349 root [rpciod/0]
353 root [jffs2_gcd_mtd1]
376 root /sbin/udevd -d
716 daemon portmap
735 root /usr/sbin/ntpd
739 root /usr/sbin/dropbear
745 root /sbin/getty 38400 tty1
748 root /sbin/getty 38400 tty2
754 root -sh
755 root /sbin/syslogd -n -m 0
759 root /sbin/klogd -n
762 root /usr/bin/tail -f /var/log/messages
804 root [ksdiorqd]
812 root ps -ef
#
Can any one give me a hint for debugging? what could be the real cause for
this problem? thanks!
Regards,
Susa,.

On Fri, Nov 27, 2009 at 11:48 PM, Dan Lyke wrote:

> On Fri, 27 Nov 2009 18:41:38 +0530
>
> suse auto > wrote:
> > reason for the issue. can somebody brief me what is this udev?
>
> udev is a user-space daemon that manages devices. Among other things,
> when the kernel detects device changes it runs (by default, this can be
> changed) /sbin/hotplug. If you're running udev on your
> system, /sbin/hotplug is a part of udev that does the user space
> manipulations to create the new devices in /dev and do other
> system-specific stuff (on a desktop machine, it might also try to mount
> that device and pop up a folder on the resulting filesystem, for
> instance).
>
> (Just for completeness, you can often manually run "mdev -s" to create
> devices that the kernel knows about, but that aren't created in the /dev
> filesystem yet. Recently I wanted to mount USB drives and do things with
> the resulting filesystem but thought udev added unneeded complexity, so
> my app just watched the syslog output, spawned mdev to create the
> device, did the mount itself, and then accessed the resulting data.)
>
> A full running Linux system can require a lot more than just a kernel.
> How are you compiling your system utilities to go along with your
> kernel? One of the scripts like "buildroot" that creates the uCLibC
> environment? udev is probably an option in that environment somewhere.
>
> Dan
> Start a New Thread

Hi!
I am also getting somewhat similar problem while integrating a azurewave SDIO wifi card with Marvell's 8686 chip to the AT91SAM9263 board. For this I am using Linux 2.6.27 kernel with 2.6.27-at91.patch and 2.6.27-at91-exp patches as given on http://www.at91.com/linux4sam/bin/view/Linux4SAM/LinuxKernel.
While inserting the wifi card.. message displays-
"root@at91sam:~$ mmc0: new SDIO card at address 0001"

Now when I inserted the 'libertas.ko' and 'libertas_sdio.ko', I got the following messages:

libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
firmware: requesting helper_sd.bin
firmware: requesting sd8686.bin
libertas: 00:22:43:77:77:22, fw 11.47.18p0, cap 0x00000301
libertas: PREP_CMD: command 0x001d failed: 2
libertas: PREP_CMD: command 0x00a3 failed: 2
libertas: PREP_CMD: command 0x00a3 failed: 2
libertas: eth1: Marvell WLAN 802.11 adapter

which I think similar to as shown on http://www.at91.com/linux4sam/bin/view/Linux4SAM/WifiSolutions.

After this I tried to set the SSID..using
root@at91sam:~$ iwconfig eth1 essid "shraddha" (even without "" also) and got the following messages:
libertas: PREP_CMD: command 0x0006 failed: 2
libertas: SCAN_CMD failed

After iwconfig.. displays:
root@at91sam:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11b/g ESSID:""
Mode:Managed Frequency:2.417 GHz Access Point: Not-Associated
Bit Rate:0 kb/s
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Also tried for scan -
root@at91sam:~$ iwlist eth1 scan
libertas: PREP_CMD: command 0x0006 failed: 2
libertas: SCAN_CMD failed
eth1 No scan results

It would be very helpful if someone can help me out.
Thanks in advance.

Regards,
A.Surana

Start a New Thread