Actions
Forum Thread Details
  • Replies 4 replies
  • Subscribers 332 subscribers
  • Views 816 views
  • Users 0 members are here
Related

Ultra slow wifi in Ultra96v2 (and other probs.)

miner_tom

I have an Ultra96V2 and I am having similar problems to the ones experienced by

https://www.element14.com/community/thread/73694/l/fail-to-enable-ultra96v2-wifi

 

PROBLEM #1

Yes, when I am getting access to the ultra96v2 with the USB to JTAG/UART pod, I run the ./wifi_sh and I see the same

sending discover.....

sending discover.... etc.

 

Yes, I did edit the wpa_supplicant.conf file to include

 

The name of the my Wifi Router

The password to the router.

I checked to see that the security that the ultra96 is using is the same as that of my router, which is WPA-PSK.

My router is running on channel 11 (2.462 GHz)

 

To no effect. That is even after I deleted the /var/run/wpa_supplicant/wlan0, as directed.

 

PROBLEM #2

If I access the ultra96V2 by USB keyboard, USB mouse and special active DP to HDMI cable, I see on the monitor that the unit is booting up and gives me access to a web page.

From there I can to into the wifi settings page and connect to my router. It displays "Connected to (myrouter).

However, internet access is extremely slow. Painfully slow.

I can't download various pages. I did much, much better with other microcomputers.

 

I have used the latest SD card factory image that I could find. ultra96v2_oob_2018_3_190917_8GB.img
I also did a Petalinux build with the latest board support package xilinx-ultra96-reva-v2018.2-final.bsp
The build completed and after I loaded it into the SD card and ran it I got the same results.

 

The one thing that I did not try was loading a PYNQ image.

 

PROBLEM 3

It would be nice if I could use wired internet but there is no physical RJ45 on the board. However, I did attached the mezzanine board with a Wired Ethernet board attached to it and

the results were that I got no attachment light on the RJ45 when the ethernet cable was attached. Nothing to show that there was communication.

 

Somehow, some setting is not correct on the board or in the setup instructions.

 

How to proceed?

Thank You

Tom

  • Were you able to solve this issue. I am having similar problems with my ultra96-v2?

  • in reply to zorjak

    I see the OP is dated back in October, 2019, and the PetaLinux OS image that was created then uses a different mechanism to configure and bring up the WiFi interface than the current PetaLinux OS.  In PetaLinux 2019.1 and prior the WiFi was configured via a /etc/wpa_supplicant.conf file.  Starting in PetaLinux 2019.2 Xilinx made the change to configure and bring up with WiFi using connmanctl.  You can see this process described in the webserver.py Python script:

    https://github.com/Xilinx/ultra96-startup-pages/blob/ultra96v2/webapp/webserver.py

     

    That script uses the webserver wifi_setup.html webpage to collect the SSID and passphrase information from the user for the WLAN. This is a small snippet of what that script does to bring up the WiFi:

    image

    Rather than a /etc/wpa_supplicant.conf file, connmanctl uses a /var/lib/ultra96.config file to store the WLAN connection settings.

     

    You can either use a DP monitor, mouse and keyboard to navigate to this web page locally, or use a PC or smartphone to connect to the Ultra96-V2 WiFi AP SSID “Ultra96-V2_<MAC ID>” and navigate to http://192.168.2.1/wifi_setup.html and enter your WLAN SSID and passphrase.  Note - you will probably need to reboot once you enter your WLAN info via the webpage and press “Connect”.

     

    I hope this helps.

     

    --Tom

  • in reply to narrucmot

    Thanks for the explanation Tom.

    It solved my doubts.

     

    best,

    Zoran

  • in reply to narrucmot

    Tom,

     

    I followed your advice, and the webpage claims that I connected successfully, but when I try to click the 'Check Connection' button it breaks the entire p2p0 network.

     

    Running ifconfig in the UART command line of the board also shows that the board was never assigned a local IP address by the specified network.