Actions
Forum Thread Details
  • Replies 12 replies
  • Subscribers 349 subscribers
  • Views 3186 views
  • Users 0 members are here
Related

Can't connect via wifi to Ultra96. Nor ethernet.

miner_tom

I have recently downloaded the current sdcard image for the ultra96v2. Not only that, I have created an image via a petalinux build. Both behave the same way.

 

when connected via serial port on the jtag pod, after "./wifi.sh" I am getting endless streams of "Sending discover...".

 

In another post I have seen setup instructions as follows: I have done all of the below but with the same result.

Also, I have a Click Board Ethernet pod, which I am plugged into, but I can not make ethernet connection to the ultra96. I would like to communicate with my ultra96 via some kind of networking.

 

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

 

Thank You

Tom

  • in reply to clem57

    Clem, thank you for your reply.

     

    To the Ultra96 board I am using the 12V, 4A power supply, to the power jack, which was recommended for the Ultra96 board.

     

    Tom

  • Hi Tom,

     

    We just finished completing the 2018.3 BSP targeting Ulta96-V2. This BSP has the working WIFI support built in among other things.

    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.

  • Tom,

    I built 2018.3 yesterday and I was able to get wifi working.  Initially, I tried to start the network via the webpage but that didn't work.  I then tried the script and saw the same thing you are seeing with dhcp.  I just killed wpa_supplicant and restarted it manually and then I was able to get a ip address when I ran dhcp.

     

    jeff

  • in reply to jhane

    Jeff,

     

    I was able to connect just now. I think that there was some interference between the "click board" ethernet add-on board that I had attached. I removed it and then deleted wlan0.  After that, it ran. I put the click board back but now the wifi runs ok. Still no wired ethernet. Is that going to be the case for a while? Only wifi?

     

    I managed to get to the web app at 192.168.2.1. I also logged in via SSH at 192.168.2.1 port 22. Not sure how to get items downloaded directly into the Ultra96 (other than trying SCP) since I don't see in the /bin directory "apt-get"or other onboard program. I could do a little research there.

     

    I have two other questions:

     

    1) The HDMI port does not seem to be providing any output. I remember on the boot up that there was a message that the GPU was not initialized, etc. Is this going to be fixed in another build? Is there a demo project that uses the HDMI port?

     

    2) I am an "old school" FPGA programmer, around from the days when there was no "hard silicon" embedded in the device. One just loaded whatever was compiled from verilog, vhdl or other (yes, there were others). I have a Pynq development board but did not do a whole lot with it because of the DDR limitations. I am working with object detection and a few things and needed more "horsepower". I know that on the Pynq development board there are "overlays" that can be written so that the programmable portion of the zynq can be written to without disturbing the software portion of the board. I have all of the xilinx viviado tools and I was looking for ultra96 programming examples. Xilinx does not have much at this time, dealing with the Ultra96. They are, more or less, pushing their own fairly expensive development systems (although I did notice that the price is coming down on one of them). To make a long story shorter, do vhdl or verilog programming, I suppose through the jtag port, interfere with the petalinux programming? Should I have posted this question separately in a new post?

     

    Thank You for your help.

    Tom

  • I just built a new set of images without X and the web support so was trying this again.  The system does boot up with networking enable and wpa_supplicant is already running.  I did stop everything and run the script but I still couldn't connect.  So I undid everything and just ran the lines from the script individually, except after doing ifconfig wlan0 up , I ran a scan to see what networks were visible: 'iwlist wlan0 scan'.   After confirming my network was being seen I started wpa_supplicant and dhcp and I was able to get an ip address.

    Also, make sure you are using a network with passwd protection only.  Our internal wifi only has some multi-level authentication that I could never connect to by editing wpa_supplicant.conf.

     

    One other option is to setup the usb ethernet gadget, this would give you RNDIS over USB.  I did this a few years ago and think the ultra96 could be setup to connect this way via the usb3 device port.

     

    jeff

  • in reply to jhane

    One other thing, on reboot the wifi will fail to reconnect again.  This is because the wrong wpa driver is being used.   If you are using SD card and you want a short term workaround, edit /etc/network/interfaces and change:

    wpa-driver wext

    to

    wpa-driver nl80211

     

    If you update the SD card this will be lost so you need to create a recipe in yocto make it persistant.

     

     

    jeff

  • in reply to miner_tom

    Tom,

     

    What is the click-board you are trying?  I'm not familiar with it. 

     

    Before I disable X, I got a desktop on a monitor connected the the DP port and even with X I get a terminal login on the monitor.

     

    You know there is a PYNQ image for the ultra96?   Also, Avnet has a TRD that builds hardware accelerators for the openCV functions in python.

    I have done any debugging yet on the US, I'm still trying to get my builds working, but the JTAG can connect to a processor or the PL.  On the 7000 I could connect to the PL without interfering with Linux.

     

    jeff

  • in reply to jhane

    Ah, the 2018.3 BSP has a modification to init-ifupdown and the interfaces file can be modified there so it will always have nl80211 as the driver.     should update this in the BSP so once the wpa conf is update everything works on bootup.

     

    jeff

  • in reply to jhane

    Jeff,

     

    The ethernet "click" board that I used for an rj45 connector to the ultra96 is attached through an mezzanine connector as shown here https://www.avnet.com/wps/portal/us/products/new-product-introductions/npi/96boards-click-mezzanine/  and here https://www.mikroe.com/eth-click  .    So far, I have not been able to achieve connectivity through the wired ethernet port.

     

    I am looking now at the reference designs (TRDs) from xilinx that you suggested. Very good information. One of the projects that you mentioned, the accelerator for openCV functions (binary neural networks BNN) is targeted for the Ultra 96 V1 as well as the ZC702 evaluation board by xilinx.

     

    One question that I have, which you might be able to answer, is, how different is the hardware on the ultra96 v1 as compared to the ultra96 v2? I expect that the zynq IC used, is the same. I know that the BSP, used in petalinux builds is different (just released for the v2). If I "re-built" the source files for the ultra96 v1 TRD in vivado and then used the v2 BSP when compiling petalinux, do you think that would be a valid way to proceed?

     

    Thank You

    Tom