element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
Ultra96 Hardware Design ultra96-V2 wifi connection
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 9 replies
  • Subscribers 332 subscribers
  • Views 2450 views
  • Users 0 members are here
  • ultra96v2
  • ultra96-v2
  • wifi
  • ultra96
  • connect via websever to ultra96
  • ultra -96
  • SD card
  • boot from sd
Related

ultra96-V2 wifi connection

luciaom_02
luciaom_02 over 2 years ago

Hello.

I'm using a ultra96-v2 and I'm trying to set up the wifi connection, following the guide and I'm running into some problems.
I'm reading chapter 8, "Connect to Webserver", but I can't set up the network called Ultra96-V2_<MAC_ADDRESS>.
I boot the image which is called ultra96v2_oob_2020_1_210303_8GB. But when I connect the display port, nothing comes out.

I'm also getting this error on the terminal:

ERROR:gcm_channel_status_request.cc(145)] GCM channel request failed.

Additionally, when I run the ls command it shows:

bt.sh, pmic-prog, usb_gadget_ethernet.sh, wifi.sh, wpa_supplicant.conf

But wifi.sh also runs into an error. When I run ifup wlan0 it says:

power up request for already powered up source Wifi

(full output in comment).

Can I get some help either connecting via the webserver or by setting up the wlan0 connection.

Thanks

  • Sign in to reply
  • Cancel
  • bidrohini
    bidrohini over 2 years ago

    This appeared when I googled the message: misoji-engineer.com/.../vitis-ai-2-0.html

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • balajivan1995
    balajivan1995 over 2 years ago

    Have you tried running the .sh files?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • luciaom_02
    luciaom_02 over 2 years ago

    I think I'm making some progress, but still having some issues.

    When running ifdown I get the following output:

    ifdown: interface wlan0 not configured

    I have tried using ip link set wlan0 down instead. That seems to work and doesn't report any error.

    However when running either ifup wlan0 or ip link set wlan0 up, I get the following error

    [ 883.500230] power up request for already powered up source Wifi
    [ 883.506161] Device already up. request source is Wifi
    [ 883.511239] wilc_sdio mmc1:0001:1 wlan0: Failed to get mac address
    [ 883.517421] wilc_sdio mmc1:0001:1: wilc_sdio_disable_interrupt
    RTNETLINK answers: Invalid argument

    Any idea of what could be the problem?

    The other thing I have tried is to use the output of the display port. This is the option that the official guide suggests and uses a web server interface.
    However, I seem to run into the following error:

    ERROR:gcm_channel_status_request.cc(145)] GCM channel request failed.

    It appears to be related to Chromium (or maybe Selenium) but I cannot find a fix.

    Has anyone encountered the same issue and knows how to get around it?

    Thanks again

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • luciaom_02
    luciaom_02 over 2 years ago in reply to balajivan1995

    Yes, when trying to connect via wifi (using wifi.sh) I run into a problem with the configuration of the LAN. ifup wlan0 throws an error as if the device was already up (even if I set down that connection right before).

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • redmed
    redmed over 1 year ago

    I have the exact same issues with 2 different boards ordered recently. And I could test with the same SD card on a 3rd Ultra96-V2 which could get the Wifi connection up and running.

    Neither the bluetooth or the wifi are working.

    Have you found a solution to this issue?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • cardalexx
    cardalexx over 1 year ago in reply to redmed

    This is frustrating: I received yesterday my Ultra96-V2 and WiFi is not working as expected from getting started guide ... I was speculating a systematic issue, hence a possible SW one, but your statement goes unfortunately in the HW direction ...

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • lenv
    lenv over 1 year ago in reply to cardalexx

    Hello sir, I also have the same issues. When the ultra96V2 is started from the sdcard that having been flashed with  ultra96v2_oob_2020_1_210303_8GB by etcher. the terminal is always reporting ERROR:gcm_channel_status_request.cc(145)] GCM channel request failed, and i cannot see the network called Ultra96-V2_<MAC_ADDRESS> in windows10 of my pc.

    I also tried using the wifi.sh, I get the problem as follow:

    root@ultra96v2-2020-1:~# ./wifi.sh
    Stopping Connection Manager
    ifdown: interface wlan0 not configured
    Successfully initialized wpa_supplicant
    [  452.862578] power up request for already powered up source Wifi
    [  452.868507] Device already up. request source is Wifi
    [  452.873584] wilc_sdio mmc1:0001:1 wlan0: Failed to get mac address
    [  452.879769] wilc_sdio mmc1:0001:1: wilc_sdio_disable_interrupt
    Could not set interface wlan0 flags (UP): Invalid argument
    nl80211: Could not set interface 'wlan0' UP
    nl80211: deinit ifname=wlan0 disabled_11b_rates=0
    wlan0: Failed to initialize driver inte[  452.901227] power up request for already powered up source Wifi
    rface
    [  452.910258] Device already up. request source is Wifi
    [  452.918127] wilc_wlan_firmware_downloadDownloading firmware size = 136788
    [  453.141540] wilc_wlan_firmware_download Offset = 119860
    [  453.149016] wilc_wlan_firmware_download Offset = 136788
    [  453.685160] wilc_sdio mmc1:0001:1: wilc_sdio_disable_interrupt
    RTNETLINK answers: Input/output error
    udhcpc: started, v1.31.0
    [  454.724941] power up request for already powered up source Wifi
    [  454.730897] Device already up. request source is Wifi
    [  454.735992] wilc_sdio mmc1:0001:1 wlan0: Failed to get mac address
    [  454.742177] wilc_sdio mmc1:0001:1: wilc_sdio_disable_interrupt
    RTNETLINK answers: Invalid argument
    udhcpc: sending discover
    udhcpc: sendto: Network is down
    udhcpc: read error: Network is down, reopening socket
    udhcpc: sending discover
    udhcpc: sendto: Network is down
    udhcpc: read error: Network is down, reopening socket
    udhcpc: sending discover
    udhcpc: sendto: Network is down
    udhcpc: read error: Network is down, reopening socket
    udhcpc: read error: Network is down, reopening socket
    udhcpc: read error: Network is down, reopening socket
    udhcpc: read error: Network is down, reopening socket
    udhcpc: read error: Network is down, reopening socket
    udhcpc: read error: Network is down, reopening socket

    So i tried ip link set wlan0 down and ip link set wlan0 up, then i got erros as follow

    root@ultra96v2-2020-1:~# ip link set wlan0 down
    root@ultra96v2-2020-1:~# ip link set wlan0 up
    [  792.877742] power up request for already powered up source Wifi
    [  792.883680] Device already up. request source is Wifi
    [  792.891445] wilc_wlan_firmware_downloadDownloading firmware size = 136788
    [  793.113877] wilc_wlan_firmware_download Offset = 119860
    [  793.121413] wilc_wlan_firmware_download Offset = 136788
    [  793.653169] wilc_sdio mmc1:0001:1: wilc_sdio_disable_interrupt
    RTNETLINK answers: Input/output error

    Besides, I also get a img called ultra96v2_sbc-v2022.2-2023-05-10.img from Ultra96V2 GSC. After flashing this img, the GCM channel error is disappered. But the wifi is still not working, after excuting ./wifi.sh, errors are as follow:

    root@u96v2-sbc-2022-2:~# ls
    Vitis-AI                       bt.sh            usb_gadget_ethernet.sh
    asl_classification_vitis_ai    dpu_sw_optimize  wifi.sh
    avnet_dualcam_python_examples  pmic-prog        wpa_supplicant.conf
    root@u96v2-sbc-2022-2:~# ./wifi.sh
    Stopping Connection Manager
    ifdown: interface wlan0 not configured
    Successfully initialized wpa_supplicant
    nl80211: kernel reports: Authentication algorithm number required[   79.334456]                       power up request for already powered up source Wifi
    
    [   80.095288] wilc_sdio mmc1:0001:1 wlan0: WLAN initialization FAILED
    Could not set interface wlan0 flags (UP): Timer expired
    nl80211:[   80.102467] 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
    [   80.176570] power up request for already powered up source Wifi
    [   80.182567] wilc_sdio mmc1:0001:1 wlan0: Failed to set driver handler
    [   80.189050] wilc_sdio mmc1:0001:1 wlan0: Failed to get mac address
    RTNETLINK answers: Invalid argument
    udhcpc: started, v1.34.1
    [   82.194842] power up request for already powered up source Wifi
    [   82.943261] 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
    udhcpc: read error: Network is down, reopening socket
    udhcpc: read error: Network is down, reopening socket

    And errors of ip link set wlan0 up/down are as follow:

    root@u96v2-sbc-2022-2:~# ip link set wlan0 down
    root@u96v2-sbc-2022-2:~# ifconfig -a
    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:1073 errors:0 dropped:0 overruns:0 frame:0
              TX packets:1073 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:82876 (80.9 KiB)  TX bytes:82876 (80.9 KiB)
    
    p2p0      Link encap:Ethernet  HWaddr 00:00:00:00:00:00
              BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
    
    sit0      Link encap:IPv6-in-IPv4
              NOARP  MTU:1480  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
    
    wlan0     Link encap:Ethernet  HWaddr 00:00:00:00:00:00
              BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
    
    root@u96v2-sbc-2022-2:~# ip link set wlan0 up
    [  295.100081] power up request for already powered up source Wifi
    [  295.839213] wilc_sdio mmc1:0001:1 wlan0: WLAN initialization FAILED
    RTNETLINK answers: Timer expired
    root@u96v2-sbc-2022-2:~#

    Sir, Have you fixed that problem? Is there any chance that we can talk about this problem by X or other contact way. Thank you very much.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • glee263
    glee263 over 1 year ago in reply to lenv

    I have the same issue here. Did you figure out?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • magnus
    magnus over 1 year ago

    I have the same issue, have you checked this errata?  Looks like the wrong component was mounted on Y1 on some boards.

    image
    www.avnet.com/.../Errata 24001 U96 WiFi.pdf

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube