https://elinux.org/api.php?action=feedcontributions&user=Ever4ever&feedformat=atomeLinux.org - User contributions [en]2024-03-29T11:25:47ZUser contributionsMediaWiki 1.31.0https://elinux.org/index.php?title=BeagleBone_Usb_Networking&diff=258836BeagleBone Usb Networking2013-05-29T18:55:46Z<p>Ever4ever: </p>
<hr />
<div>'''Troubleshooting:'''<br />
<br />
'''USB networking not available (192.168.7.2 not accessible):'''<br />
<br />
In some linux systems a few kernel modules might be needed to support the BeagleBone usb network.<br />
<br />
If your usb network is unreachable and you cannot find the following line (or similar) in your dmesg log:<br />
<br />
"rndis_host 1-4.3:1.0: eth2: register 'rndis_host' at usb-0000:00:1a.7-4.3, RNDIS device, c8:a0:30:ad:27:19"<br />
<br />
Follow the next steps:<br />
<br />
1) Find your kernel sources and edit them. (usually at /usr/src/linux)<br />
make menuconfig<br />
<br />
2) Add the following options as Modules:<br />
<br />
Device Drivers ---> <br />
[*] Network device support ---><br />
USB Network Adapters ---><br />
<M> Multi-purpose USB Networking Framework <br />
<M> CDC Ethernet support (smart devices such as cable modems) <br />
<M> Host for RNDIS and ActiveSync devices (EXPERIMENTAL)<br />
<M> Simple USB Network Links (CDC Ethernet subset)<br />
<br />
Device Drivers ---> <br />
[*] USB support ---> <br />
<M> USB Gadget Support ---><br />
<M> Ethernet Gadget (with CDC Ethernet support)<br />
<M> CDC Composite Device (Ethernet and ACM)<br />
<M> Multifunction Composite Gadget (EXPERIMENTAL<br />
[*] RNDIS + CDC Serial + Storage configuration<br />
<br />
3) Recompile the kernel and install the modules<br />
make && make modules_install<br />
<br />
4) If everything went as expected a new network interface will be created the next time you connect your beaglebone.<br />
ip addr<br />
<br />
5) assign an IP address to the freshly created network interface and enjoy!</div>Ever4everhttps://elinux.org/index.php?title=BeagleBone_Community&diff=258686BeagleBone Community2013-05-29T14:30:56Z<p>Ever4ever: /* Subpages */</p>
<hr />
<div>[[Category: Linux]]<br />
[[Category: OMAP]]<br />
[[Category:Development Boards]]<br />
[[Category: BeagleBoard]]<br />
[[Category: BeagleBone]]<br />
<br />
[[File:BeagleBone_256x249.jpg|320px|thumb|right|BeagleBone]]<br />
[[File:BeagleBone-Black-A5_product_detail_black_sm.jpg|320px|thumb|right|BeagleBone Black]]<br />
<br />
This page collects information about [http://beagleboard.org BeagleBoard.org]'s range of [http://beagleboard.org/bone BeagleBone] boards based on the [http://www.ti.com/am335x TI Sitara AM335x], an application processor SoC containing an [http://en.wikipedia.org/wiki/ARM_Cortex-A8 ARM Cortex-A8] core. The range currently consists of the original '''BeagleBone''' and the upgraded but lower cost '''BeagleBone Black'''.<br />
<br />
Most features are common to the two models. The differences between them are described in each section under a '''BeagleBone Black''' subheading.<br />
<br />
<br><br />
= Events =<br />
* ongoing 2009: [[BeagleBoard/contest|Beagle Sponsored Project Program]] - add a cool project and get a free BeagleBoard to realize it!<br />
<br />
= Description =<br />
The two models of BeagleBone share most features in common through employing only slightly different versions of the same TI Sitara SoC. In addition they both adhere to the same standard for expansion and interfacing through "cape" daughterboards. <br />
<br />
== BeagleBone (original) ==<br />
The '''BeagleBone''' is a low-cost, high-expansion board from the [http://beagleboard.org/ BeagleBoard] product line. It uses the [http://www.ti.com/am335x TI AM3358/9] SoC based on an [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344d/DDI0344D_cortex_a8_r2p1_trm.pdf ARM Cortex-A8] processor core using the [http://infocenter.arm.com/help/topic/com.arm.doc.subset.architecture.reference/index.html#v7AR ARMv7-A] architecture. It is similar in purpose to earlier BeagleBoards, and can be used either standalone or as a USB or Ethernet-connected expansion for a BeagleBoard or any other system. The BeagleBone is small even by BeagleBoard standards yet still provides much of the performance and capabilities of the larger BeagleBoards.<br />
<br />
BeagleBone ships with a 4GB micro-SD card preloaded with the [http://www.angstrom-distribution.org/ Angstrom] ARM Linux distribution.<br />
<br />
The board uses a [http://www.ti.com/product/tps65217b TI TPS65217B PMIC] to generate stable supply voltages regardless of input power variation. +5V DC power can be supplied to the BeagleBone through a barrel connector or from the mini-USB, both of which are located near the large RJ45 Ethernet connector.<br />
<br />
The mini-USB type-A OTG/device '''client-mode''' socket is multi-functional. In addition to providing an alternative source of power, it gives access to an on-board front-end two-port USB client-side hub. (This is not related to the separate '''host-mode''' USB socket described later). One port of the hub goes directly to the '''USB0''' port of the TI AM3358/9 SoC, while the other port connects to a dual-port [http://www.ftdichip.com/Products/ICs/FT2232H.htm FTDI FT2232H] USB-to-serial converter to provide board-to-external-host serial communications and/or JTAG debugging. The BeagleBone's Linux serial console is available through this USB serial connection.<br />
<br />
The SoC's '''USB0''' connection to the front-end hub works in one of two modes, and you can toggle between them at any time: it either presents the SD card as a mountable USB storage device to the host, or it provides an [http://www.linux-usb.org/usbnet/ Ethernet-over-USB] networking interface which yields a simple method of quick-start. The Ethernet-over-USB facility is additional to the BeagleBone's normal 10/100 Ethernet interface, which is directly implemented in the SoC rather than hanging off USB as in some other designs. Full IPv4 and IPv6 networking is provided by the supplied Linux system out of the box.<br />
<br />
In addition to the USB OTG Device or '''client-mode''' facilities already described, BeagleBone also provides one '''host-mode''' USB type-A socket on the other end of the board. This is driven from the '''USB1''' connection on the AM3358/9 SoC, and provides access to USB host peripherals such as mice, keyboards, storage, and wifi or Bluetooth dongles, or a USB hub for further expansion.<br />
<br />
== BeagleBone Black ==<br />
On 23rd April 2013, Beagleboard officially announced '''[http://beagleboard.org/Products/BeagleBone%20Black BeagleBone Black]''' at a price approximately half that of the original BeagleBone.<br />
<br />
The new board's most important new features include a AM3359 SoC upgraded to 1GHz, doubling of memory to 512MB, use of faster DDR3 memory in contrast to the DDR2 of the original BeagleBone, and a new HDMI audio/visual output. (The original BeagleBone required an additional cape daughterboard for graphic output).<br />
<br />
= Specifications =<br />
The two boards are very similar in those features provided directly by the SoC. Despite the original BeagleBone being specified as using "AM3358/9", in practice most boards are believed to have shipped with the AM3359 generic part. BeagleBone Black has therefore upgraded only the specific device selected from the AM3359 range, and hence the differences are few. In contrast, the boards have significantly different designs but a high degree of compatibility.<br />
== BeagleBone ==<br />
* Up to 720 MHz superscalar ARM Cortex-A8 AM3358/9<br />
* 256 MB DDR2 RAM<br />
* 10/100 Ethernet RJ45 socket, IPv4 and IPv6 networking<br />
* MicroSD slot and 4GB microSD card supplied<br />
* Preloaded with Angstrom ARM Linux Distribution<br />
* Single USB 2.0 type A host port<br />
* Dual USB hub on USB 2.0 type mini-A OTG device port<br />
* On-board USB-to-serial/JTAG over one shared USB device port<br />
* Storage-over-USB or Ethernet-over-USB on other USB device port<br />
* Extensive I/O: 2 I2C, 5 UART, SPI, CAN, 66 GPIO, 8 PWM, 8 ADC<br />
* +5V DC power from barrel connector or USB device port<br />
* Power consumption of 300-500mA at 5V<br />
* Two 46-pin 3.3-V peripheral headers with multiplexed LCD signals<br />
* Board size: 3.4" × 2.1" (86.4mm x 53.3mm) -- fits in an Altoid tin<br />
<br />
== BeagleBone Black (differences) ==<br />
* 1 GHz superscalar ARM Cortex-A8 AM3359<br />
* 512 MB DDR3 RAM<br />
* On-board 2 GB eMMC flash, preloaded with Angstrom ARM Linux Distribution<br />
* MicroSD slot for additional user data or operating systems (no card supplied)<br />
* USB 2.0 type A host port<br />
* Dedicated single mini-USB 2.0 client port (no additional 2-port hub)<br />
* New micro-HDMI audio/visual output<br />
* USB-to-serial and USB-to-JTAG interfaces removed (available on expansion headers)<br />
* Power expansion header for backlight removed, battery charging moved onto pads<br />
* Lower power consumption of 210-460 mA at 5V<br />
<br />
= Expansion Connectors =<br />
The BeagleBone provides two 46-pin dual-row expansion connectors "'''P9'''" and "'''P8'''" which are also known as "'''Expansion A'''" and "'''Expansion B'''", respectively. The location and pinout of these connectors is illustrated below (click tables to enlarge). All signals on expansion headers are 3.3V except where indicated otherwise.<br />
<br />
=== P9 and P8 - Each 2x23 pins ===<br />
[[File:BeagleBone_P9_256x256.jpg|256px|left|top|border|P9 Header|link=File:BeagleBone_p9_pinout.jpg]]<br />
[[File:BeagleBone_P9_P8_256x256.jpg|256px|top|border|BeagleBone P9 + P8|link=File:BeagleBone_P9_P8_512x512.jpg]]<br />
[[File:BeagleBone_P8_256x256.jpg|256px|top|border|P8 Header|link=File:BeagleBone_p8_pinout.jpg]]<br />
<p><br><br />
In addition to the two large headers above, a small 10-pin dual-row connector provides "'''P6'''" provides a "'''PMIC Expansion'''" that brings out some additional signals from the TPS65217B Power Management IC, using the following pinout:<br />
<br />
=== P6 - 2x5 pins''' ===<br />
[[File:BeagleBone_P6_464x222.jpg|464px|left|middle|border|P6 MPIC Expansion Header]]<br />
<br />
'''NB. P6 is not available on BeagleBone Black'''<br />
<br />
'''IMPORTANT'''<br />
<br />
This diagram of P6 provides an '''UNDERSIDE PINOUT''' view.<br />
<br />
It is therefore ''' ''laterally inverted'' ''' relative to the photograph.<br />
<br />
To obtain the top-side pinout that corresponds to the physical orientation shown in the photograph, swap the two rows of pins so that odd-numbered pins are on the left of even-numbered pins.<br style="clear: both" /><br />
<br />
= Expansion Boards and Accessories =<br />
<br />
== Capes ==<br />
A '''BeagleBone Cape''' is an expansion board which can be plugged into the BeagleBone's two 46-pin dual-row '''Expansion Headers''' and which in turns provides similar headers onto which further capes can be stacked. Up to four capes at a time can be stacked on top of a BeagleBone. An expansion board which can be fitted only at the top of a stack of capes (usually for physical reasons) is a special case of "cape", but this usage is common for display expansion boards such as LCDs (see next section).<br />
<br />
Capes are required to provide a 32Kbyte I2C-addressed EEPROM which holds board information such as board name, serial number and revision, although this is typically omitted on simple prototyping capes. Capes are also expected to provide a 2-position DIP switch to select their address in the stack, although this too is often omitted in prototyping capes.<br />
<br />
The [https://docs.google.com/spreadsheet/ccc?key=0AtD7XdBlve3HdDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc&hl=en_US#gid=0 Capes Registry] seeks to index all existing capes and cape concepts, including private projects. A [https://docs.google.com/spreadsheet/viewform?formkey=dDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc6MQ registration page] is available to help add capes to the list.<br />
<br />
This section lists only those capes which are available commercially or which are close to a production release, as well as open hardware designs.<br />
<br />
* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_DVID CircuitCo BeagleBone DVI-D cape]<br />
* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_Breadboard CircuitCo BeagleBone Breadboard cape]<br />
* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_Breakout CircuitCo BeagleBone Breakout cape]<br />
* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_CANBus CircuitCo BeagleBone CANBus cape]<br />
* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_RS232 CircuitCo BeagleBone RS232 cape]<br />
* [http://beagleboardtoys.com/wiki/index.php?title=BeagleBone_Battery CircuitCo BeagleBone Battery cape]<br />
* [http://www.adafruit.com/products/572 Adafruit Proto Cape kit for BeagleBone]<br />
* [http://www.towertech.it/en/products/hardware/tt3201-can-cape/ TowerTech TT3201 Multi-Channel CAN Cape]<br />
* [https://specialcomp.com/beaglebone/BeagleBone_FPGA.html Special Computing Spartan-3A FPGA cape for BeagleBone] -- in development<br />
* [http://syntheticlifeforms.net/?p=43 Thinking Machines LCD-IO Expansion Cape] -- in development<br />
* [https://github.com/piranha32/FlyingBone Open Source BeagleBone Prototyping Board] -- piranha32 GitHub repository<br />
* [http://www.armkits.com/product/beaglebone-hdmicape.asp Embest BeagleBone HDMI cape]<br />
* [[BeagleBone 6502 RemoteProc cape]] -- in development<br />
<br />
== LCD Displays and Other Expansions ==<br />
LCD displays for the BeagleBone are typically implemented as capes which plug in as the ''' ''top board'' ''' in a stack of capes, for reasons of visibility. Such displays are often larger than the BeagleBone itself, so the normal physical relationship in which a daughterboard is smaller than its host board is inverted. In this arrangement it is the expansion board that provides the physical support for the BeagleBone.<br />
<br />
* [[File:Beaglebone.jpg|320px|thumb|BeadaFrame]][http://www.nxelec.com/products/hmi/beadaframe-beaglebone NAXING Electronics BeadaFrame] with BeagleBone companion board<br />
:Expanded Hardware Features:<br />
:* 7" 800x480 TFT LCD screen<br />
:* PWM Backlight control<br />
:* Resistive touch panel<br />
:* Plastic frame<br />
:* 256MB Nand flash(K9F2G08)<br />
:* RS232 serial ports(UART1 w/ CTS&RTS)<br />
:* Stereo audio out<br />
:* Micro-phone in<br />
:* 6 x USER buttons<br />
:* PWM Beeper<br />
:* RTC with Battery(DS1302)<br />
<br />
* [http://beagleboardtoys.info/index.php?title=BeagleBone_LCD3 CircuitCo BeagleBone LCD3 cape and LCD display]<br />
: 3.5" TFT LCD screen, resolution 320x240, 4-wire resistive touchscreen, seven buttons at finger-friendly positions. <br />
* [http://beagleboardtoys.info/index.php?title=BeagleBone_LCD4 CircuitCo BeagleBone LCD4 cape and LCD display]<br />
: 4" TFT LCD screen, resolution 480x272, 4-wire resistive touchscreen, seven buttons at finger-friendly positions. <br />
* [http://beagleboardtoys.info/index.php?title=BeagleBone_LCD7 CircuitCo BeagleBone LCD7 cape and LCD display]<br />
: 7" TFT LCD screen, resolution 800x480, 4-wire resistive touchscreen, rear mount for BeagleBone and capes.<br />
* A very low cost LCD implementation for the BeagleBone Black using the PRU-ICSS is [http://www.element14.com/community/community/knode/single-board_computers/next-gen_beaglebone/blog/2013/05/28/bbb--connecting-up-an-lcd here]. It requires a graphics library to be written; currently it just displays a couple of lines on the screen.<br />
<br />
== Cases ==<br />
* [http://www.adafruit.com/products/699 Adafruit Bone Box - Enclosure for Beagle Bone]<br />
* [http://www.skpang.co.uk/catalog/acrylic-cover-for-beaglebone-p-1076.html SK Pang Acrylic Cover for BeagleBone]<br />
* [http://specialcomp.com/beagleboard/BB-Bone-assy2_l.jpg Special Computing Bone Acrylic Case]<br />
* [http://www.thingiverse.com/thing:19153 canadaduane's 3D-printable BeagleBone Case design]<br />
* [http://www.thingiverse.com/thing:16195 NinjaBlock's 3D-printable Beaglebone front panel design]<br />
* [http://www.thingiverse.com/thing:20122 builttospec's laser-cut design for BeagleBone Enclosure with DVI Cape]<br />
* [http://www.built-to-spec.com/blog/2012/03/01/beaglebone-case-update-and-new-kits-page/ Built to Spec BeagleBone Case Update], and [http://builttospecstore.storenvy.com/products/225603-beaglebone-enclosure final product]<br />
<br />
= BeagleBone Operating Systems =<br />
BeagleBone's default operating system is [http://www.angstrom-distribution.org/ Angstrom], which ships with the board. This section provides basic information on Angstrom and other operating systems commonly used on BeagleBone. This information may help in making a preliminary choice, but full details should be obtained from the home sites.<br />
<br />
The latest images of the official Angstrom images for BeagleBoard.org products can be found at [http://beagleboard.org/latest-images the beagleboard.org latest images web page]<br />
<br />
=== Angstrom ===<br />
* Home site: http://www.angstrom-distribution.org/<br />
* Mailing lists: [http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel angstrom-distro-devel] and [http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users angstrom-distro-users]<br />
* IRC channel: irc://irc.freenode.net/#angstrom<br />
Ångström was started by a small group of people who worked on the OpenEmbedded, OpenZaurus and OpenSimpad projects to unify their effort to make a stable and user-friendly distribution for embedded devices like handhelds, set top boxes and network-attached storage devices.<br />
Ångström can scale down to devices with only 4MB of flash storage.<br />
<br />
The Angstrom community does not provide a forum, [http://www.angstrom-distribution.org/contact intentionally].<br />
<br />
Angstrom uses [http://www.busybox.net/ Busybox] for many key utilities, which has both pros and cons. Advantages include requiring less storage space and a smaller memory footprint for many common utilities, which also improves system startup time and performance. The main disadvantages stem from those utilities not mirroring exactly their full-size counterparts. These differences can be annoying if one is used to standard behavior, and may also break shell scripts that rely on portable functionality.<br />
<br />
Angstrom uses [http://connman.net/ connman] for network connection management, but no documentation is available for this currently. Also, man(1) and man pages are not provided by default, nor debugging utilities like strace(1) and tcpdump(1). Getting started may therefore present difficulties, depending on experience.<br />
<br />
=== Debian ===<br />
* See [[BeagleBoardDebian]]<br />
* Home site: [http://wiki.debian.org/ArmEabiPort http://wiki.debian.org/ArmEabiPort]<br />
* Mailing list: http://lists.debian.org/debian-arm/<br />
* IRC channel: irc://irc.debian.org/debian-arm<br />
The ARM EABI port is the default port of the standard Debian distribution of Linux for the ARM architecture ("armel").<br />
EABI ("Embedded ABI") is actually a family of ABIs, and one of the "subABIs" is the GNU EABI for Linux which is used for this port.<br />
Starting with Debian 7.0 (Wheezy) there is a port targeted at newer (armv7 with fpu) hardware with another ABI ("armhf").<br />
<br />
The [http://www.debian.org/intro/about Debian Project] is strongly committed to software freedom, and has a long pedigree and a good reputation.<br />
<br />
=== Ubuntu ===<br />
* See [[BeagleBoardUbuntu]]<br />
* Home site: https://wiki.ubuntu.com/ARM<br />
* IRC channel: irc://irc.freenode.net/#ubuntu-arm<br />
The vision for Ubuntu is part social and part economic: free software, available free of charge to everybody on the same terms, and funded through a portfolio of services provided by Canonical.<br />
<br />
The first version of Ubuntu was based on the GNOME desktop, but has since added a KDE edition, Kubuntu, and a server edition. All of the editions of Ubuntu share common infrastructure and software. In recent years, special emphasis has been placed on netbooks for lightweight, connected, mobile computing, and on the cloud as a new architecture for data centres.<br />
<br />
=== Fedora ===<br />
* See [[BeagleBoardFedora]].<br />
* Home site: http://fedoraproject.org/wiki/Architectures/ARM<br />
* Mailing list: http://lists.fedoraproject.org/pipermail/arm/<br />
* IRC channel: irc://irc.freenode.net/#fedora-arm<br />
The Fedora Project is sponsored by Red Hat, which invests in its infrastructure and resources to encourage collaboration and incubate innovative new technologies. Some of these technologies may later be integrated into Red Hat products. They are developed in Fedora and produced under a free and open source license from inception, so other free software communities and projects are free to study, adopt, and modify them.<br />
<br />
Red Hat has been a major player since the earliest days of Linux distributions, and has earned a good reputation for solidity which continues in Fedora. The Fedora ARM initiative is very active (see mailing list).<br />
<br />
=== ArchLinux ===<br />
* Home site: http://archlinuxarm.org/platforms/armv7/beaglebone<br />
* Source repository: https://github.com/archlinuxarm/PKGBUILDs<br />
* IRC channel: irc://irc.freenode.net/#archlinux-arm<br />
Arch Linux for BeagleBone is a version of the Arch Linux ARM distribution. This carries forward the Arch Linux philosophy of simplicity and user-centrism, targeting and accommodating ''competent'' Linux users by giving them complete control and responsibility over the system. Instructions are provided to assist in navigating the nuances of installation on the varied ARM platforms; however, the system itself will offer little assistance to the user.<br />
<br />
The entire distribution is on a rolling-release cycle that can be updated daily through small packages instead of huge updates on a defined release schedule. Most packages are unmodified from what the upstream developer originally released.<br />
<br />
=== Gentoo ===<br />
* Home site: http://dev.gentoo.org/~armin76/arm/beaglebone/install.xml<br />
* IRC channel: irc://irc.freenode.net/#gentoo-embedded<br />
Gentoo is a source-based '' '''meta'''-distribution'' of Linux. Instead of distributing a standard system image built with predefined options, Gentoo gives each user the means to create their own customized system that doesn't contain unused bloat and with minimum dependencies. Upgrades are incremental and under user control, so a Gentoo system is normally always up-to-date and wholesale upgrades are avoided.<br />
<br />
Being a source-based system, the downside of Gentoo for low-power ARM systems is very long install times for large applications. Cross-compilation on x86 machines and [http://www.gentoo.org/doc/en/distcc.xml distcc] can overcome this problem, but they add complexity.<br />
<br />
=== Sabayon ===<br />
* Home site: [http://wiki.sabayon.org/index.php?title=Hitchhikers_Guide_to_the_BeagleBone_%28and_ARMv7a%29 wiki.sabayon.org/Hitchhikers Guide to the BeagleBone]<br />
* IRC channel: irc://irc.freenode.net/#sabayon<br />
Sabayon Linux uses the mechanisms of Gentoo to create a pre-configured Linux distribution that can be installed as rapidly as a normal binary distribution, but still retains the benefits of Gentoo's source-based package management. Sabayon on Intel/AMD also provides the Entropy binary package management system, which could in principle greatly ease installation of packages on resource-constrained embedded Linux devices, but this is not yet available for ARM.<br />
<br />
Although it is still early days for Sabayon on ARM (and hence on BeagleBone), there is regular progress reported on [http://lxnay.wordpress.com/2012/ lxnay's blog], and contributions from the community would probably accelerate the work.<br />
<br />
=== Buildroot ===<br />
* Home site: http://www.zoobab.com/beaglebone<br />
* Buildroot project site: http://buildroot.uclibc.org/<br />
Buildroot is a set of Makefiles and patches that makes it easy to generate a complete embedded Linux system. Buildroot can generate any or all of a cross-compilation toolchain, a root filesystem, a kernel image and a bootloader image. Buildroot is useful mainly for people working with small or embedded systems, using various CPU architectures (x86, ARM, MIPS, PowerPC, etc.) : it automates the building process of your embedded system and eases the cross-compilation process.<br />
<br />
The resulting root filesystem is mounted read-only, but other filesystems can be mounted read/write for persistence. Although user accounts can be created, in practice almost everything is done as root. Buildroot uses no package manager. Instead, package selection is managed through '''make menuconfig'''.<br />
<br />
=== Nerves Erlang/OTP ===<br />
* Home site: http://nerves-project.org/<br />
* Source repository: https://github.com/nerves-project/bbone-erlang-buildroot<br />
* Erlang project site: http://www.erlang.org/<br />
Erlang is a programming language used to build massively scalable soft realtime systems with high availability requirements (5-9’s). Some of its uses are in telecoms, banking, e-commerce, computer telephony and instant messaging. Erlang’s runtime system has built-in support for concurrency, distribution and fault tolerance.<br />
<br />
OTP is a set of Erlang libraries and design principles providing middle-ware to develop these systems. It includes its own distributed database, applications to interface towards other languages, debugging and release handling tools.<br />
<br />
The Nerves project provides an embedded Linux-based environment for running Erlang and an easy-to-use API to access common I/O interfaces, based on '''Buildroot''' (see above). If you are interested in running an Erlang node on a low power ARM-based board such as BeagleBone, this project can get you started.<br />
<br />
= Board recovery =<br />
* See [http://elinux.org/BeagleBoardRecovery#USB_recovery BeagleBoardRecovery] ''--- (*) Check applicability''<br />
<br />
= Software Development =<br />
Software development on the BeagleBone is normally no different to any other Linux platform, and typically varies with language and with the IDE used, if any. This section deals only with development issues that are specific to BeagleBone, or mostly so.<br />
<br />
=== Cloud9 IDE and Bonescript ===<br />
''..... description here .....''<br />
* Source repository: https://github.com/jadonk/bonescript<br />
* Language documentation: http://nodejs.org/<br />
<br />
=== BeagleBone JTAG Debugging ===<br />
''..... description here .....''<br />
<br />
===Using Netbeans to remotely compile and debug C/C++===<br />
<br />
When developing c/c++ on a linux desktop, a toolchain is available for cross-compiling the code for arm. However no such toolchain is readily available for windows. Netbeans can be used to write the code on your desktop, save it in a location accessible to the beagle, and then automatically compile it on the beagle itself using ssh and the built in compiler on the beaglebone's OS.<br />
<br />
Netbeans can also use GDB for remote debugging over ssh.<br />
<br />
Requirements:<br />
<br />
* Set up a samba / smb network share through which code can be shared between both desktop and beagle<br />
* Give netbeans the SSh login details of the beagle<br />
* Give netbeans the path mapping so it can translate between the desktop code folder and beagle code folder<br />
* Setup only takes a few minutes.<br />
<br />
====More info====<br />
<br />
* Download Netbeans (Windows/Linux/OS-X/Solaris): http://www.netbeans.org/<br />
* Example tutorial on setting this up: http://mechomaniac.com/BeagleboardDevelopmentWithNetbeans<br />
<br />
<br />
= Kernel =<br />
<br />
=== Getting the Right Kernel ===<br />
The modern BeagleBone kernels are Maintained by Koen Kooi and are available on the 3.8 branch at https://github.com/beagleboard/kernel/tree/3.8 . This repo contains a set of patches and a script which downloads a mainline kernel and then patches it appropriately. Exact steps for building it are in the README.<br />
<br />
=== Device Tree ===<br />
The 3.5 and newer BeagleBone kernels make use of [[Device_Trees|Device Trees]]. A Device Tree is a text file which describes the layout of a machine, commonly the combination of a system-on-chip (SoC) and a board, so that the kernel can know at what addresses and on which buses hardware is located. The BeagleBone kernels make use of an extension called [[Capemgr|Capemgr]] which allows dynamic loading and unloading of device tree fragments both at compile time and from userspace post-boot.<br />
Learning about the Device Tree is very essential, if you wish to be able to manipulate pins and be able to use them as inputs/outputs. There is a [http://www.element14.com/community/community/knode/single-board_computers/next-gen_beaglebone/blog/2013/05/22/bbb--working-with-the-pru-icssprussv2 short guide to it here] (part-way down the page). In a nutshell, the device tree can be manipulated by creating a text 'fragment' file that can be converted into a .dtbo file using a program called dtc which is already installed on the BeagleBone Black. The .dtbo file can then be installed and uninstalled as desired. The procedures to install and uninstall are at that link:<br />
<br />
<tt>echo cape-bone-name > $SLOTS</tt> to install, and<br />
<br />
<br />
<tt>echo -<slotnum> > $SLOTS</tt> to uninstall,<br />
but read through the web page and comments section first to see what $SLOT is set to).<br />
<br />
<br />
<br />
= FAQ =<br />
<br />
For BeagleBoard frequently asked questions (FAQ) see [[BeagleBoardFAQ|community FAQ]] and "official" [http://beagleboard.org/support/faq BeagleBoard.org FAQ].<br />
<br />
= Links =<br />
== Home site and Community ==<br />
* [http://beagleboard.org/ beagleboard.org] -- home for BeagleBoard and BeagleBone products<br />
* [http://beagleboard.org/Products/BeagleBone%20Black BeagleBone Black] -- manufacturer's page for the second BeagleBone board<br />
* irc://irc.freenode.net/#beagle -- official combined IRC channel<br />
* [http://beagleboard.org/discuss Google Groups forums/mailing list] -- [https://groups.google.com/forum/?fromgroups#!forum/beagleboard English], [http://groups.google.com/group/pandabeagle-jp Japan], [http://groups.google.com/group/beagleboard-brasil Brasil], [https://groups.google.com/group/beagle-board-turkiye Turkey]<br />
* [http://beagleboard.org/project BeagleBoard and BeagleBone projects list]<br />
* [https://docs.google.com/spreadsheet/ccc?key=0AtD7XdBlve3HdDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc&hl=en_US#gid=0 Capes Registry] and its [https://docs.google.com/spreadsheet/viewform?formkey=dDZqUk0xQ1dpV2NiNm43d0pNWmVGdmc6MQ registration page]<br />
* [http://www.adafruit.com/blog/category/beaglebone/ BeagleBone articles at Adafruit blog] -- products, projects and tutorials<br />
* Use [http://www.google.de/ Google] to search beagleboard.org (including [http://www.beagleboard.org/irclogs/ IRC logs]) using ''site:beagleboard.org <search term>''<br />
* [https://www.linux.com/news/embedded-mobile/mobile-linux/715298-45-beaglebone-black-keeps-eyes-on-raspberry-pi Linux.com report on BeagleBone Black] -- with words from beagleBoard.org's cofounder Jason Kridner<br />
* [https://github.com/selsinork/beaglebone-black-pinmux github.com/selsinork/beaglebone-black-pinmux] -- pinmux data for BeagleBone Black, including extraction scripts<br />
* [http://www.element14.com/community/community/knode/single-board_computers/next-gen_beaglebone/blog/2013/05/22/bbb--working-with-the-pru-icssprussv2 Element 14 knode blog: Working with the PRU-ICSS] -- detailed tutorial on starting with the PRU on BBB<br />
<br />
== Tutorials and Videos ==<br />
* [http://beagleboard.org/static/bonescript/bone101/index.html ''BeagleBone: BeagleBoard-101 Intro''] -- slides (turn off Javascript for single page)<br />
* [http://www.youtube.com/watch?v=EEnOWR-GXjk ''BeagleBone Intro''], video by Jason Kridner, Texas Instruments<br />
* [http://www.youtube.com/watch?v=Y0uqRVxismQ ''How-To: Get Started with the BeagleBone''], video by Matt Richardson, MakeMagazine<br />
* [http://www.youtube.com/watch?v=z6b4zlh0IrE ''The Beaglebone - Unboxing, Introduction Tutorial and First Example''], video by Derek Molloy, DCU/EE<br />
* [http://www.youtube.com/watch?v=vFv_-ykLppo ''Beaglebone: C/C++ Programming Introduction for ARM Embedded Linux Development using Eclipse''], video by Derek Molloy, DCU/EE<br />
* [http://www.youtube.com/watch?v=SaIpz00lE84 ''Beaglebone: GPIO Programming on ARM Embedded Linux''], video by Derek Molloy, DCU/EE<br />
* [https://gist.github.com/4013192 ''C code for GPIO polling''], sample code by Andrew Montag<br />
* [http://borderhack.com/?p=1062 First steps with the Beaglebone], introductory HOWTO by octavio at borderhack<br />
* [http://learn.adafruit.com/beaglebone Adafruit Learning System - BeagleBone] -- web page<br />
<br />
== Manuals and resources ==<br />
* [http://beagleboard.org/static/beaglebone/a3/Docs/Hardware/BONE_SRM.pdf BeagleBone System Reference Manual (rev. A3_1.0)]<br />
* [http://www.ti.com/am335x Texas Instruments - Sitara AM335x ARM Cortex-A8 Microprocessor overview]<br />
* [http://www.ti.com/product/am3359 Texas Instruments - AM3359 Sitara ARM Cortex-A8 Microprocessor full documentation]<br />
* [http://infocenter.arm.com/help/topic/com.arm.doc.subset.architecture.reference/index.html#v7AR ARM/ARMv7-AR Architecture] -- ARM Cortex-A8 architecture overview<br />
* [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0344d/DDI0344D_cortex_a8_r2p1_trm.pdf ARM Cortex-A8 Technical Reference Manual r2p1]<br />
* [http://www.arm.com/support/university/development-platforms/cortex-a8-development-platforms.php ARM Cortex-A Development Platforms] -- ARM page on Beagle boards<br />
* [http://www.ti.com/product/tps65217b TI TPS65217 Power Management IC], [http://www.ti.com/lit/ds/symlink/tps65217.pdf TPS65217 PMIC datasheet]<br />
* [http://www.ftdichip.com/Products/ICs/FT2232H.htm FTDI FT2232H Hi-Speed Dual USB UART/FIFO IC overview], [http://www.ftdichip.com/Support/Documents/DataSheets/ICs/DS_FT2232H.pdf FT2232H datasheet]<br />
* [http://www.linux-usb.org/gadget/index.html Linux-USB Gadget API Framework] and [http://www.linux-usb.org/gadget/h2-otg.html USB OTG], and [http://forums.gentoo.org/viewtopic-t-843255.html kernel config] -- Ethernet-over-USB<br />
<br />
== Translations ==<br />
* 한국어:[[KR:BeagleBone]]<br />
<br />
== Errata ==<br />
<br />
= Subpages =<br />
http://elinux.org/BeagleBone_Usb_Networking</div>Ever4everhttps://elinux.org/index.php?title=BeagleBone_Usb_Networking&diff=258674BeagleBone Usb Networking2013-05-29T14:12:53Z<p>Ever4ever: </p>
<hr />
<div>'''Troubleshooting:'''<br />
<br />
'''USB networking not available (192.168.7.2 not accessible):'''<br />
<br />
In some linux systems a few kernel modules might be needed to support the BeagleBone usb network.<br />
<br />
In case your usb network is unreachable and you cannot find the following line (or similar) in your dmesg log:<br />
<br />
"rndis_host 1-4.3:1.0: eth2: register 'rndis_host' at usb-0000:00:1a.7-4.3, RNDIS device, c8:a0:30:ad:27:19"<br />
<br />
Follow the next steps:<br />
<br />
1) find your kernel sources and edit them. (usually at /usr/src/linux)<br />
make menuconfig<br />
<br />
2) add the following options as Modules:<br />
<br />
Device Drivers ---> <br />
[*] Network device support ---><br />
USB Network Adapters ---><br />
<M> Multi-purpose USB Networking Framework <br />
<M> CDC Ethernet support (smart devices such as cable modems) <br />
<M> Host for RNDIS and ActiveSync devices (EXPERIMENTAL)<br />
<M> Simple USB Network Links (CDC Ethernet subset)<br />
<br />
Device Drivers ---> <br />
[*] USB support ---> <br />
<M> USB Gadget Support ---><br />
<M> Ethernet Gadget (with CDC Ethernet support)<br />
<M> CDC Composite Device (Ethernet and ACM)<br />
<M> Multifunction Composite Gadget (EXPERIMENTAL<br />
[*] RNDIS + CDC Serial + Storage configuration<br />
<br />
3) Recompile the kernel and install the modules<br />
make && make modules_install<br />
<br />
4) If everything went as expected a new network interface will be created the next time you connect your beaglebone.<br />
ip addr<br />
<br />
5) assign an IP address to the freshly created network interface and enjoy!</div>Ever4everhttps://elinux.org/index.php?title=BeagleBone_Usb_Networking&diff=258668BeagleBone Usb Networking2013-05-29T14:08:00Z<p>Ever4ever: added a missing module</p>
<hr />
<div>'''Troubleshooting:'''<br />
<br />
'''USB networking not available (192.168.7.2 not accessible):'''<br />
<br />
In some linux systems a few kernel modules might be needed to support the BeagleBone usb network.<br />
<br />
In case your usb network is unreachable and you cannot find the following line (or similar) in your dmesg log:<br />
<br />
"rndis_host 1-4.3:1.0: eth2: register 'rndis_host' at usb-0000:00:1a.7-4.3, RNDIS device, c8:a0:30:ad:27:19"<br />
<br />
Follow the next steps:<br />
<br />
1) find your kernel sources. (usually at /usr/src/linux)<br />
<br />
2) add the following options as Modules:<br />
<br />
Device Drivers ---> <br />
[*] Network device support ---><br />
USB Network Adapters ---><br />
<M> Multi-purpose USB Networking Framework <br />
<M> CDC Ethernet support (smart devices such as cable modems) <br />
<M> Host for RNDIS and ActiveSync devices (EXPERIMENTAL)<br />
<M> Simple USB Network Links (CDC Ethernet subset)<br />
<br />
Device Drivers ---> <br />
[*] USB support ---> <br />
<M> USB Gadget Support ---><br />
<M> Ethernet Gadget (with CDC Ethernet support)<br />
<M> CDC Composite Device (Ethernet and ACM)<br />
<M> Multifunction Composite Gadget (EXPERIMENTAL<br />
[*] RNDIS + CDC Serial + Storage configuration<br />
<br />
3) Recompile the kernel and install the modules<br />
make && make modules_install<br />
<br />
4) If everything went as expected a new network interface will be created the next time you connect your beaglebone.<br />
ifconfig -a<br />
<br />
5) assign an IP address to the freshly created network interface and enjoy!</div>Ever4everhttps://elinux.org/index.php?title=BeagleBone_Usb_Networking&diff=258662BeagleBone Usb Networking2013-05-29T14:04:52Z<p>Ever4ever: </p>
<hr />
<div>'''Troubleshooting:'''<br />
<br />
'''USB networking not available (192.168.7.2 not accessible):'''<br />
<br />
In some linux systems a few kernel modules might be needed to support the BeagleBone usb network.<br />
<br />
In case your usb network is unreachable and you cannot find the following line (or similar) in your dmesg log:<br />
<br />
"rndis_host 1-4.3:1.0: eth2: register 'rndis_host' at usb-0000:00:1a.7-4.3, RNDIS device, c8:a0:30:ad:27:19"<br />
<br />
Follow the next steps:<br />
<br />
1) find your kernel sources. (usually at /usr/src/linux)<br />
<br />
2) add the following options as Modules:<br />
<br />
Device Drivers ---> <br />
[*] Network device support ---><br />
USB Network Adapters ---><br />
<M> Multi-purpose USB Networking Framework <br />
<M> CDC Ethernet support (smart devices such as cable modems) <br />
<M> Host for RNDIS and ActiveSync devices (EXPERIMENTAL)<br />
<M> Simple USB Network Links (CDC Ethernet subset)<br />
<br />
Device Drivers ---> <br />
[*] USB support ---> <br />
<M> USB Gadget Support ---><br />
<M> CDC Composite Device (Ethernet and ACM)<br />
<M> Multifunction Composite Gadget (EXPERIMENTAL<br />
[*] RNDIS + CDC Serial + Storage configuration<br />
<br />
3) Recompile the kernel and install the modules<br />
make && make modules_install<br />
<br />
4) If everything went as expected a new network interface will be created the next time you connect your beaglebone.<br />
ifconfig -a<br />
<br />
5) assign an IP address to the freshly created network interface and enjoy!</div>Ever4everhttps://elinux.org/index.php?title=BeagleBone_Usb_Networking&diff=258656BeagleBone Usb Networking2013-05-29T14:02:07Z<p>Ever4ever: new USB networking toubleshooting page for the beaglebone</p>
<hr />
<div>'''Troubleshooting:'''<br />
<br />
'''USB networking not available (192.168.7.2 not accessible):'''<br />
<br />
In some linux systems a few kernel modules might be needed to support the BeagleBone usb network.<br />
<br />
In case your usb network is unreachable and you cannot find the following line (or similar) in your dmesg log:<br />
<br />
"rndis_host 1-4.3:1.0: eth2: register 'rndis_host' at usb-0000:00:1a.7-4.3, RNDIS device, c8:a0:30:ad:27:19"<br />
<br />
Follow the next steps:<br />
<br />
1) find your kernel sources. (usually at /usr/src/linux)<br />
2) add the following options as Modules:<br />
<br />
Device Drivers ---> <br />
[*] Network device support ---><br />
USB Network Adapters ---><br />
<M> Multi-purpose USB Networking Framework <br />
<M> CDC Ethernet support (smart devices such as cable modems) <br />
<M> Host for RNDIS and ActiveSync devices (EXPERIMENTAL)<br />
<M> Simple USB Network Links (CDC Ethernet subset)<br />
<br />
Device Drivers ---> <br />
[*] USB support ---> <br />
<M> USB Gadget Support ---><br />
<M> CDC Composite Device (Ethernet and ACM)<br />
<M> Multifunction Composite Gadget (EXPERIMENTAL<br />
[*] RNDIS + CDC Serial + Storage configuration<br />
<br />
3) Recompile the kernel and install the modules<br />
make && make modules_install<br />
<br />
4) If everything went as expected a new network interface will be created the next time you connect your beaglebone.<br />
ifconfig -a<br />
<br />
5) assign an IP address to the freshly created network interface and enjoy!</div>Ever4ever