Ultra96-V2 No Wifi or Bluetooth

Hello everyone,

I have recently bought an Ultra96 V2. I managed to flash the SD card with the latest OOB image available from Avnet but the Ultra96 doesn't bring up the Access Point and it doesn't work either when I try with the ./wifi.sh script.
I also tried with the latest Pynq image and I also built with petalinux the latest U96V2 SBC BSP (2022.2) but nothing changes.

Here is the error I have at boot time:

[   13.881500] wilc_sdio mmc1:0001:1 p2p0: Failed to get RSSI value
[   13.894769] power up request for already powered up source Wifi
[   13.900811] wilc_sdio mmc1:0001:1 p2p0: Failed to set driver handler
[   13.907269] wilc_sdio mmc1:0001:1 p2p0: Failed to get mac address
[FAILED] Failed to start Access point for Ultra96.

When trying with wifi.sh:

root@u96v2-sbc-base-2022-2:~# ./wifi.sh
Stopping Connection Manager
ifdown: interface wlan0 not configured
Successfully initialized wpa_supplicant
nl80211: kernel reports: Authentication algorithm number required[ 442.409487] power up request for already powered up source Wifi
[ 443.164679] wilc_sdio mmc1:0001:1 wlan0: WLAN initialization FAILED
Could not set interface wlan0 flags (UP): Timer expired
nl80211:[ 443.171509] wilc_sdio mmc1:0001:1 wlan0: Failed to frame register
Could not set interface 'wlan0' UP
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
wlan0: Failed to initialize driver interface
[ 443.201258] power up request for already powered up source Wifi
[ 443.207246] wilc_sdio mmc1:0001:1 wlan0: Failed to set driver handler
[ 443.213759] wilc_sdio mmc1:0001:1 wlan0: Failed to get mac address
RTNETLINK answers: Invalid argument
udhcpc: started, v1.34.1
[ 444.653053] power up request for already powered up source Wifi
[ 445.404683] wilc_sdio mmc1:0001:1 wlan0: WLAN initialization FAILED
RTNETLINK answers: Timer expired
udhcpc: broadcasting discover
udhcpc: sendto: Network is down
udhcpc: read error: Network is down, reopening socket

And finally the errors I've got when trying to bring up the Bluetooth interface:

root@u96v2-sbc-base-2022-2:~# ./bt.sh
[ 470.128734] wilc_sdio mmc1:0001:1 wlan0: Failed to set driver handler
[ 470.156962] wilc_sdio mmc1:0001:1 p2p0: Failed to set driver handler
[ 472.365450] wilc_sdio mmc1:0001:1 wlan0: Failed to get RSSI value
Device setup complete
[ 475.644614] Bluetooth: hci0: command 0x1003 tx timeout
[ 477.660590] Bluetooth: hci0: command 0x1001 tx timeout
[ 479.676581] Bluetooth: hci0: command 0x1009 tx timeout
[ 479.681822] wilc_sdio mmc1:0001:1 wlan0: WLAN initialization FAILED

I could access another Ultra96 V2 and with the same OOB, the Wifi was brought up so I thought it was an hardware issue with my board. But when I got my new Ultra96 V2 board (100% sure that it's NOT the same as the 1st one), I've got the same issue.

Is there anything special to do or change to use the Wifi/BT module?

Thank you very much.

Top Replies

redmed over 1 year ago in reply to embeddedguy +1

No, indeed, it doesn't appear in the output of ifconfig: root@u96v2-sbc-base-2022-2:~# ip a s 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback…

0 embeddedguy over 1 year ago

Hi,

It could be hard to find out the right issue with Bluetooth and WiFi and why it's not working but therre are some standard Linux commands which could help.

From above logs, it seems that wifi interface is not up.

ifdown: interface wlan0 not configured

You can try something like

$sudo ifconfig interfacename up

then for bluetooth

$sudo bluetoothctl
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

0 redmed over 1 year ago in reply to embeddedguy

Thank you for your reply.

Unfortunately, it gives me an error too:

root@u96v2-sbc-base-2022-2:~# ifconfig wlan0 up
[   73.930335] power up request for already powered up source Wifi
[   74.688702] wilc_sdio mmc1:0001:1 wlan0: WLAN initialization FAILED
ifconfig: SIOCSIFFLAGS: Timer expired

0 embeddedguy over 1 year ago in reply to redmed
That looks scary to me. I checked on internet and this error can be if network interface is damaged. What is the output of ifconfig? do you see wifi device?

Or try similar command which lists system hardware.

To avoid breaking the devices, do double-check that the interface is down whenever you want to change the connection. A broken NIC port will result in the ‘ifconfig: SIOCSIFFLAGS: Timer expired’ error when initiating the interface.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

0 redmed over 1 year ago in reply to embeddedguy

No, indeed, it doesn't appear in the output of ifconfig:

root@u96v2-sbc-base-2022-2:~# ip a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/sit 0.0.0.0 brd 0.0.0.0
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
4: p2p0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
root@u96v2-sbc-base-2022-2:~# ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:152 errors:0 dropped:0 overruns:0 frame:0
          TX packets:152 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:12280 (11.9 KiB)  TX bytes:12280 (11.9 KiB)

As you can see, it's state is "DOWN" in the ip command output...

So it seems that I was unlucky and got 2 bad boards in a row.

0 redmed over 1 year ago in reply to embeddedguy

I was looking at the board and I am not sure but some pins don't seem to be well soldered (right above the blue buttons)? I will take a look at the board I know works correctly and will compare just to be sure...

From the datasheet, they are not the Not Connected pins: ww1.microchip.com/.../70005327A.pdf
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 embeddedguy over 1 year ago in reply to redmed

Perhaps check with multimeter for continuty and the pins which are supposed to be connected are connected well..And check this onto the board which is working correctly. compare the results.

If you can not exchange the board(I assume that boards from Avnet do not come with garranty/warranty etc), then try to solder the pins yourself.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 misaz over 1 year ago in reply to embeddedguy

Continuity test can be dangerous in this situation: https://electronics.stackexchange.com/questions/56066/continuity-tests-risks
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 lightcollector over 1 year ago

Hi, Circumstantially it does seem like a hardware issue, may be a bad batch (purely speculation at this point). If it helps any, the PYNQ image for V2 has a Jupyter Notebook that can be used to connect to a wifi AP. If the interface isn't present the NB will probably fail with some cryptic messages, there are some startup scripts that invoke the driver and setup the user space access. The PYNQ wifi module scripts can be found here: https://github.com/Avnet/Ultra96-PYNQ/tree/master/Ultra96/packages/wilc3000
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 glee263 over 1 year ago in reply to redmed

I have the same issue. Did you solve the issue?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel