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 & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • 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
Technical Library
  • Products
  • Dev Tools
  • Technical Library
  • More
  • Cancel
Technical Library
Files BBONE-GATEWAY-CAPE_README_11292016_v0 1.pdf
  • Documents
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Technical Library to participate - click to join for free!
Actions
  • Next
  • Previous
  • Share
  • More
  • Cancel
Related
Recommended

BBONE-GATEWAY-CAPE_README_11292016_v0 1.pdf

An important README on firmware compatibility, configuration and use of the Wireless Connectivity Cape for BeagleBone Black.

  • wireless connectivity cape
  • Reference Manual
  • BeagleBone Black
jcasiello
jcasiello
  • 29 Nov 2016
  • 15 Downloads
  • Share
  • More
  • Cancel
  • Sign in to reply

Top Comments

  • chicagobob
    chicagobob over 6 years ago +3
    And I have the Element14 WIFI cape working with the latest Debian. It took a lot of poking around. But God smiled upon the struggle and I found BB-GATEWAY-WL1837-00A0.dtbo in the /lib/firmware directory…
  • bbbuser777
    bbbuser777 over 7 years ago +2
    Has anyone gotten this thing to work on a BBB Rev C? I suggest, that they update their documentation and/or show verifiable examples of getting this device to work or stop selling it. I will return this…
  • jack.dempsy47
    jack.dempsy47 over 8 years ago +1
    From other posts I've found that this wireless cape uses same pins as emmc, so you HAVE to boot from SD card.. the fun part is, in order to do this, you have to push a button inbetween the cape and BB…
  • mvduin
    mvduin over 5 years ago in reply to mohitkhakharia@gmail.com

    This cape is not compatible with eMMC due to pin conflict.  If you have an older beaglebone black with Micron eMMC then it may be possible to get it to work by booting from SD card and keeping eMMC disabled.  If you have a newer beaglebone black with Kingston eMMC (which cannot be held in reset) then it may be impossible to get this cape to work at all.  See this thread for more discussion: https://github.com/beagleboard/Latest-Images/issues/18

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • mvduin
    mvduin over 5 years ago in reply to chicagobob

    chicagobob  wrote:

    Add this line.

    cape_enable=bone_capemgr.enable_partno=BB-BONE-WL183

    This line is nonsense since

    1. it applies only to ancient systems (prior to u-boot overlays) while your remaining instructions only apply to recent systems (with u-boot overlays)
    2. there's no overlay named "BB-BONE-WL183"
    3. if it did load another WL183x overlay (it doesn't), it would conflict with the BB-GATEWAY-WL1837-00A0 overlay and probably break your system.
    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • pedotech
    pedotech over 5 years ago

    Thanks Robert

    Working, at last.

    Stay healthy

     

    Pedro

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • chicagobob
    chicagobob over 6 years ago

    And I have the Element14 WIFI cape working with the latest Debian.

    It took a lot of poking around.

    But God smiled upon the struggle and I found BB-GATEWAY-WL1837-00A0.dtbo in the /lib/firmware directory.

     

    Edit the /boot/uEnv.txt  with these modifications.

    ###Additional custom capes

    uboot_overlay_addr4=/lib/firmware/BB-GATEWAY-WL1837-00A0.dtbo

     

    Then modify this sectoin

    ###Disable auto loading of virtual capes (emmc/video/wireless/adc)

    disable_uboot_overlay_emmc=1

    disable_uboot_overlay_video=1

    disable_uboot_overlay_audio=1

    #disable_uboot_overlay_wireless=1

    disable_uboot_overlay_adc=1

     

    Comment out

    # enable_uboot_cape_universal=1

     

    Add this line.

    cape_enable=bone_capemgr.enable_partno=BB-BONE-WL183

     

    power down

    PLUG your wifi module in

    and and power up.

    start connmanctl and do what the readme says to do.

    enable your wifi, scan your wifi etc..

     

    You should be running and not tearing your hair out.

    Have a great day

    • Cancel
    • Vote Up +3 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • chicagobob
    chicagobob over 6 years ago in reply to chicagobob

    Following the directions you have in your readme

    this is whats output from the Debug cable. YOUR DIRECTIONS DO NOT WORK !!

     

    ....... TIMEOUT !

    using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in

    MAC fc:69:47:99:82:17

    HOST MAC de:ad:be:af:00:00

    RNDIS ready

    The remote end did not respond in time.Retrieving file: pxelinux.cfg/C0A80102

    cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT !

    using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in

    MAC fc:69:47:99:82:17

    HOST MAC de:ad:be:af:00:00

    RNDIS ready

    The remote end did not respond in time.Retrieving file: pxelinux.cfg/C0A8010

    cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT !

    using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in

    MAC fc:69:47:99:82:17

    HOST MAC de:ad:be:af:00:00

    RNDIS ready

    The remote end did not respond in time.Retrieving file: pxelinux.cfg/C0A801

    cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT !

    using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in

    MAC fc:69:47:99:82:17

    HOST MAC de:ad:be:af:00:00

    RNDIS ready

    The remote end did not respond in time.Retrieving file: pxelinux.cfg/C0A80

    cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT !

    using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in

    MAC fc:69:47:99:82:17

    HOST MAC de:ad:be:af:00:00

    RNDIS ready

    The remote end did not respond in time.Retrieving file: pxelinux.cfg/C0A8

    cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT !

    using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in

    MAC fc:69:47:99:82:17

    HOST MAC de:ad:be:af:00:00

    RNDIS ready

    The remote end did not respond in time.Retrieving file: pxelinux.cfg/C0A

    cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT !

    using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in

    MAC fc:69:47:99:82:17

    HOST MAC de:ad:be:af:00:00

    RNDIS ready

    The remote end did not respond in time.Retrieving file: pxelinux.cfg/C0

    cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT !

    using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in

    MAC fc:69:47:99:82:17

    HOST MAC de:ad:be:af:00:00

    RNDIS ready

    The remote end did not respond in time.Retrieving file: pxelinux.cfg/C

    cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT !

    using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in

    MAC fc:69:47:99:82:17

    HOST MAC de:ad:be:af:00:00

    RNDIS ready

    The remote end did not respond in time.Retrieving file: pxelinux.cfg/default-arm

    -am33xx

    cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT !

    using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in

    MAC fc:69:47:99:82:17

    HOST MAC de:ad:be:af:00:00

    RNDIS ready

    The remote end did not respond in time.Retrieving file: pxelinux.cfg/default-arm

     

     

    cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT !

    using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in

    MAC fc:69:47:99:82:17

    HOST MAC de:ad:be:af:00:00

    RNDIS ready

    The remote end did not respond in time.Retrieving file: pxelinux.cfg/default

    cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT !

    using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in

    MAC fc:69:47:99:82:17

    HOST MAC de:ad:be:af:00:00

    RNDIS ready

    The remote end did not respond in time.Config file not found

    starting USB...

    USB0:   Port not available.

    cpsw Waiting for PHY auto negotiation to complete......... TIMEOUT !

    using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in

    MAC fc:69:47:99:82:17

    HOST MAC de:ad:be:af:00:00

    RNDIS ready

    The remote end did not respond in time.cpsw Waiting for PHY auto negotiation to

    complete......... TIMEOUT !

    using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in

    MAC fc:69:47:99:82:17

    HOST MAC de:ad:be:af:00:00

    RNDIS ready

    The remote end did not respond in time.=>

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • 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