v2 board SD boots but no WiFi access

Sorry for the delay. I am working on that document. Also, at the time we released that May 30th image, the Access Point wasn't working yet. Therefore, you have to configure it manually to work. See the instructions below. I hope to have a new image by next week with the Access Point working.

Before bringing up the WiFi interface you must first edit the /home/root/wpa_supplicant.conf file with the correct SSID and security password for your WiFi access point.  Once that is done you can run the supplied /home/root/wifi.sh script to copy the wpa_supplicant.conf file to /etc, load the kernel modules for the driver, and bring up the WiFi interface:

#Copy the supplied wpa_supplicant.conf file to /etc

#!!!NEED TO EDIT WITH SSID & PASSWORD FIRST!!!

cp -f /home/root/wpa_supplicant.conf /etc

# Load ATWILC3000 driver

modprobe wilc-sdio

# bring up interface

ifconfig wlan0 up

#Run wpa_supplicant for secure networking:

wpa_supplicant -Dnl80211 -iwlan0 -c/etc/wpa_supplicant.conf -B

#To add DHCP:

            udhcpc -i wlan0

Were you successful with these instructions? I have also included these in the Getting Started Guide posted here:

Ultra96-V2 Development Board | Zedboard

The next version will have the Ultra96-V2 acting as an Access Point, so it will be a bit simpler.

Bryan

Hello,

I'm facing the same issue. I have followed the instructions of the "Getting started" and here what I get :

root@ultra96v2-oob-2018-3:~# ./wifi.sh

[ 2576.363612] power up request for already powered up source Wifi

[ 2576.369550] Device already up. request source is Wifi

Successfully initialized wpa_supplicant

udhcpc (v1.24.1) started

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Do you have any idea ?

Regards,

Emilie

Hi Emillie,

Did you enter your SSID and password into the wap_supplicant file?

-Josh

Hi Joshua,

Thank you for you quick reply!

Yes I did, at least, I entered the following:

ctrl_interface=/var/run/wpa_supplicant

ctrl_interface_group=0

update_config=1

network={

      key_mgmt=WPA-PSK

     ssid="RCK_MY_WRLD"

     psk="AABBCCDDEEFF00112233445566"

}

Do I have to use my own password and SSID? If yes, where can I find it ?

Regards,

Emilie

Hi Joshua,

Thank you for you quick reply!

Yes I did, at least, I entered the following:

ctrl_interface=/var/run/wpa_supplicant

ctrl_interface_group=0

update_config=1

network={

      key_mgmt=WPA-PSK

     ssid="RCK_MY_WRLD"

     psk="AABBCCDDEEFF00112233445566"

}

Do I have to use my own password and SSID? If yes, where can I find it ?

Regards,

Emilie

Hi Emile,

That's your problem, you need to use your own internet SSID and Password for your local network.

In case your not familiar with the terms.

SSID is the name of your wifi network.

psk is the password for that wifi network.

Does that make sense?

-Josh

Ok I understand now.

I thought it was like the Ultra 96 V1, I mean, the Ultra 96 v1 provides a wifi network. Is the Ultra 96 v2 able to do that?  or can we just connect the u96 v2 to a network ?

Regards,

Emilie

Hi Emile,

We are currently working on getting the wireless access point working with the Ultra96-V2. Please stay tune for the latest BSP!

-Josh

One last question !

Does it mean that I cannot create my own Petalinux project ?  I mean, if I use settings like :

DTG Settings → (zcu100-revc) MACHINE_NAME

u-boot Configurations → (xilinx_zynqmp_zcu100_revC_defconfig) u-boot config target

Yocto Settings → (ultra96-zynqmp) YOCTO_MACHINE_NAME

Will it works ?

Regards,

Emilie

Better to wait than jumping in head first unless you are ready to drink from a fire hose.

  Well, at least you have the "secret" codenames to build the image correctly.  I didn't figure this out until I already tried setting up and building the petelinux image.  As you may have already discovered, this will get you an image that will boot but no wifi.  There is a 2018.2 BSP floating around but when I looked at the contents it doesn't have wifi support either.   After reading the V2 getting started, I mounted the oob image on my linux machine to look at the script that are used to start  the wifi and that gave the hint about the needed kernel driver.   Apparently, the PYNQ V2 does have the wifi support so I'm not building that so I can look at the yocto recipes that add the wireless driver.  Anyway, if you haven't got it figure out yet, you can go look at the PYNQ build to figure out how to at WIFI support.

Personally, I'm finding this whole process rather lame and frustrating.  What's the point of having an OOB image but no way to build the images from scratch with the same capabilities???

jeff

Hi Jeff and all,

We just finished completing the 2018.3 BSP targeting Ulta96-V2. This BSP has the working WIFI support built in your requesting.

To avoid any additional time lag please use this link to access it. http://avnet.me/Ultra96-V2-2018.3-BSP

This link will be active for 30 days, which upon that time the BSP will only be available for download here.

Ultra96-V2

We are trying to get this BSP posted formally in the Zedboard community by the end of the week.

Thanks,

Josh

Thanks, exactly what I was looking!  Unfortunately, now there seems to be a problem with the Xilinx repo that has the Mali userspace code so I can't finish the build...

jeff

Hi Jeff,

Can you share the build log (<petalinux project folder>/build/build.log) and petalinuxbsp.conf (<petalinux project folder>/project-spec/meta-user/conf/petalinuxbsp.conf) files from your PetaLinux build?

Thanks!

Tom

Hi Tom,

My petalinuxbsp.conf is the one the is in the 2018.3 BSP, no modifications.   I worked around the problem so don't have a log of a broken build.

My short-term fix this was to find the mali tarbal and put it in the files directory for the recipe in petalinux release.  I had to modify the petalinux recipe to find it there since for some reason I couldn't get yocto to find it in other directories.

There is something strange with the 2018.3 build besides the mali issue.  My 2018.2 builds fine and I can build the whole thing in about 16 minutes and my 2018.2 image is close to the 2018.3 except for the wifi kernel driver.  The 2018.3 build, sometimes crashes my gui(some java thing with a xilinx tool), take forever to build chromium, webkitgtk and create the rootfs.  So now my build it taking like an hour????  But it did boot!

jeff