element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • 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 Ultra96v2 Modprobe wilc3000 failed
  • 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 4 replies
  • Subscribers 319 subscribers
  • Views 647 views
  • Users 0 members are here
  • ultra96v2
  • wilc3000
  • ultra96
Related

Ultra96v2 Modprobe wilc3000 failed

thomas-schulik
thomas-schulik over 5 years ago

Hello,

 

I have built a new Petalinux 2018.3 image with the usage of the BSP from https://github.com/Avnet/Ultra96-PYNQ  from image_2.4_v2 and added my own hardware design from Vivado 2018.3.

 

petalinux-config --get-hw-description /path-to-sdk-folder

 

When I have booted Petalinux successfully, I would like to connect to the WiFi and I initially executed following command:

 

modprobe wilc-sdio

 

After this I get the response:

 

[   62.466155] wifi_pm : 0

[   62.468637] wifi_pm : 1

[   62.471309] wilc_sdio mmc1:0001:1: Driver Initializing success

root@sensors96b:~# [   62.693564] WILC POWER UP

[   62.696202] wilc_sdio mmc1:0001:1: SDIO speed: 50000000

[   62.701659] wilc_sdio mmc1:0001:1: chipid 003000d0

[   62.708144] wilc_sdio mmc1:0001:1: Direct firmware load for mchp/wilc3000_wifi_firmware.bin failed with error -2

[   62.718326] wilc_sdio mmc1:0001:1: wilc_sdio_disable_interrupt

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

[   62.747999] Device already up. request source is Wifi

[   62.754776] wilc_sdio mmc1:0001:1: Direct firmware load for mchp/wilc3000_wifi_firmware.bin failed with error -2

[   62.764959] wilc_sdio mmc1:0001:1: wilc_sdio_disable_interrupt

 

What is wrong with my wilc3000 firmware or the connection to the wilc3000 module?

Why the firmware can't be loaded successfully?

 

In the attachment you can find a complete UART Trace from the startup sequence.

 

Regards

Attachments:
UART_Trace_Ultra96_StartUp.txt.zip
  • Sign in to reply
  • Cancel
  • ralphjy
    ralphjy over 5 years ago

    I guess this is an obvious question, but have you tried using the the ultra96-pynq-image-v2.4_v2 before doing your hardware design mods?  I haven't used that particular image, but the I've used the ultra96v2-pynq-image-v2.5 and the wifi works in that image.  If the released image works, that would verify that your board is okay and that you should look at your design changes.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • clem57
    clem57 over 5 years ago

    Refer porting guide and then install the wifi firmware.bin to /lib/firmware.

     

    If you are using petalinux then create a recipe to copy the firmware to rootfs.

     

    DESCRIPTION = "Firmware binaries for use with Microchip ATWILC1003" SECTION = "libs" LICENSE = "MIT" LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"  SRC_URI = " \ file://wilc3000_wifi_firmware.bin \ "  S = "${WORKDIR}"  PROVIDES += "wilc3000-firmware" RPROVIDES_${PN} += "wilc3000-firmware"  do_install() { install -d ${D}${base_libdir}/firmware cp -a --no-preserve=ownership ${S}/wilc3000_wifi_firmware.bin ${D}${base_libdir}/firmware/ }  FILES_${PN} = "${base_libdir}/firmware/*"  # Inhibit warnings about files being stripped INSANE_SKIP_${PN} = "ldflags" INHIBIT_PACKAGE_DEBUG_SPLIT = "1" INHIBIT_PACKAGE_STRIP = "1"  # These libraries shouldn't get installed in world builds unless something # explicitly depends upon them. EXCLUDE_FROM_WORLD = "1"

    This is similar to what you need thomas-schulik

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • thomas-schulik
    thomas-schulik over 5 years ago in reply to clem57

    Hey guys,

     

    I solved the problem in the meanwhile by copying the firmware to the /lib/firmware folder. image

    I was able to set up the SSH scripts and the g_ether connection also, so WiFi and the RNDIS connection is working now.

     

    Thanks for your support.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • clem57
    clem57 over 5 years ago in reply to thomas-schulik
    I solved the problem in the meanwhile by copying the firmware to the /lib/firmware folder

    Glad it was this simple thomas-schulik

    Clem

    • 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