- 1 이벤트
- 2 설명
- 3 스펙
- 4 확장 커넥터
- 5 확장 보드와 악세사리
- 6 BeagleBone Operating Systems
- 7 Board recovery
- 8 Software Development
- 9 FAQ
- 10 Links
- 11 Subpages
- 진행중인 2009: 비글 스폰서 프로젝트 프로그램 - 참신한 프로젝트를 추가하고 무료로 비글보드를 얻어가세요!
비글본(BeagleBone)은 BeagleBoard 제품 라인으로 저렴하며 높은 확장성을 가진다. ARM Cortex-A8 프로세서 코어를 기반으로 TI AM3358/9 SoC를 사용한다. ARMv7-A 구조를 기반으로 한다. 초기 비글보드의 목적과 유사해서 독립적으로 사용하거나 비글보드나 다른 시스템에 이더넷 연결 확장하여 사용할 수 있다. 비글본은 표준 비글보드도 작으면서도 상당한 성능과 용량을 제공한다.
비글본은 4GB 마이크로 SD카드에 Angstrom ARM Linux 배포판과 함께 제공된다.
입력 전력이 가변적이더라도 안정적인 전압을 생성할 수 있도록 TI TPS65217B PMIC를 사용한다. +5V DC는 배럴 커넥터(barrel connector)나 미니-USB를 통해 공급된다. 이 둘은 모두 RJ45 이더넷 커넥터 근처에 위치하고 있다.
mini-USB type-A OTG 장치 클라이언트 모드 소켓은 다양한 기능이 있다. 선택 가능한 전원을 제공하며 온보드 프론트 엔드 2포트 USB 클라이언트 사이드 허브에 접근할 수 있게 한다.(나중에 소개할 독립된 호스트 모드 USB 소켓과는 관련이 없다.) 허브 중 하나는 TI AM3358/9 SoC의 USB0 포트에 직접적으로 연결되지만 다른 포트는 듀얼-포트 FTDI FT2232H USB-to-시리얼 컨버터에 연결되며 이는 보드에서 외부 호스트와 시리얼 통신이나 JTAG 디버깅에 이용된다. 비글본의 리눅스 시리얼 콘솔은 이 USB 시리얼 연결을 통해 가능하다.
프론트 엔드 허브에 SoC의 USB0 연결은 2가지 모드 중에 하나로 동작한다. 언제든 이 2모드 사이에서 토글이 가능하다. 호스트에 마운팅 가능한 USB 저장장치처럼 SD카드나 혹은 Ethernet-over-USB 네트워킹 인터페이스를 제공한다. Ethernet-over-USB 기능은 비글본의 기본 10/100 이더넷 인터페이스에 추가되어 있으며 이는 직접 SoC에 구현되어 있다. 제공한 리눅스 시스템에서 완전한 IPv4와 IPv6 네트워킹을 제공한다.
이미 설명한 USB OTG 장치나 클라이언트 모드 기능 이외에, 비글본은 보드의 다른 가장자리에 호스트 모드 USB type-A 소켓도 제공한다. AM3358/9 SoC에 있는 USB1 연결이며 마우스나 키보드, 저장장치, wifi, 블루투스 동글, USB 허브 등과 같은 USB 호스트 주변장치에 연결을 제공한다.
- 최대 720-MHz superscalar ARM Cortex-A8
- 256-MB DDR2 RAM
- 10/100 이더넷 RJ45 소켓, IPv4 and IPv6 네트워킹
- 마이크로SD 슬롯과 4GB 마이크로SD 카드 제공
- Angstrom ARM 리눅스 배포판
- 단일 USB 2.0 타입 A 호스트 포트
- 듀얼 USB 허브 USB 2.0 타입 mini-A OTG 장치 포트
- On-board USB-to-serial/JTAG 하나의 공유 USB 장치 포트
- Storage-over-USB or Ethernet-over-USB on other USB device port
- Extensive I/O: 2 I2C, 5 UART, SPI, CAN, 66 GPIO, 8 PWM, 8 ADC
- +5V DC power (배럴 커넥터 or USB 장치 포트)
- 2개 46-pin 3.3-V peripheral headers with multiplexed LCD signals
- 보드 크기 : 86.4mm x 53.3mm(3.4" × 2.1") -- Altoid tin에 적합
비글본은 2개의 46핀 2열 확장 커넥트인 "Expansion A"와 "Expansion B"로 알려진 "P9"와 "P8" 를 제공한다. 이 커넥터의 위치와 핀아웃은 아래에 나와 있다.(크게 볼려면 테이블을 클릭하라). 다른 표시가 없으면 확장 헤더에 모든 신호는 3.3V이다.
P9과 P8 - 각 2x23 pins
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: 위에 2개의 넓은 허더에 추가로 작은 10-pin 두 행 커넥터는 "P6"과 "PMIC Expansion"를 제공한다. 다음 핀아웃을 이용해서 TPS65217B Power Management IC로부터 추가 신호를 끌어낸다.
P6 - 2x5 pins
P6 다이어그램은 아랫부분 PINOUT을 보여준다.
It is therefore laterally inverted relative to the photograph.
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.
확장 보드와 악세사리
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).
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.
This section lists only those capes which are available commercially or which are close to a production release, as well as open hardware designs.
- CircuitCo BeagleBone DVI-D cape
- CircuitCo BeagleBone Breadboard cape
- CircuitCo BeagleBone Breakout cape
- CircuitCo BeagleBone CANBus cape
- CircuitCo BeagleBone RS232 cape
- CircuitCo BeagleBone Battery cape
- Adafruit Proto Cape kit for BeagleBone
- TowerTech TT3201 Multi-Channel CAN Cape
- Special Computing Spartan-3A FPGA cape for BeagleBone -- in development
- Thinking Machines LCD-IO Expansion Cape -- in development
- Open Source BeagleBone Prototyping Board -- piranha32 GitHub repository
LCD 디스플레이와 다른 확장
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.
- NAXING Electronics BeadaFrame with BeagleBone companion board
- Expanded Hardware Features:
- 7" 800x480 TFT LCD screen
- PWM Backlight control
- Resistive touch panel
- Plastic frame
- 256MB Nand flash(K9F2G08)
- RS232 serial ports(UART1 w/ CTS&RTS)
- Stereo audio out
- Micro-phone in
- 6 x USER buttons
- PWM Beeper
- RTC with Battery(DS1302)
- 3.5" TFT LCD screen, resolution 320x240, 4-wire resistive touchscreen, seven buttons at finger-friendly positions.
- 7" TFT LCD screen, resolution 800x480, 4-wire resistive touchscreen, rear mount for BeagleBone and capes.
- Adafruit Bone Box - Enclosure for Beagle Bone
- SK Pang Acrylic Cover for BeagleBone
- Special Computing Bone Acrylic Case
- canadaduane's 3D-printable BeagleBone Case design
- NinjaBlock's 3D-printable Beaglebone front panel design
- builttospec's laser-cut design for BeagleBone Enclosure with DVI Cape
- Built to Spec BeagleBone Case Update, and final product
BeagleBone Operating Systems
BeagleBone's default operating system is 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.
- Home site: http://www.angstrom-distribution.org/
- Mailing lists: angstrom-distro-devel and angstrom-distro-users
- IRC channel: irc://irc.freenode.net/#angstrom
Å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. Ångström can scale down to devices with only 4MB of flash storage.
The Angstrom community does not provide a forum, intentionally.
Angstrom uses 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.
Angstrom uses 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.
- Home site: http://wiki.debian.org/ArmEabiPort
- Mailing list: http://lists.debian.org/debian-arm/
- IRC channel: irc://irc.debian.org/debian-arm
The ARM EABI port is the default port of the standard Debian distribution of Linux for the ARM architecture ("armel"). 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. A newer port targeted at newer hardware with another ABI ("armhf") is currently under development and is expected to ship with Debian 7.0 (Wheezy).
The Debian Project is strongly committed to software freedom, and has a long pedigree and a good reputation.
- See BeagleBoardUbuntu
- Home site: https://wiki.ubuntu.com/ARM
- IRC channel: irc://irc.freenode.net/#ubuntu-arm
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.
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.
- See BeagleBoardFedora.
- Home site: http://fedoraproject.org/wiki/Architectures/ARM
- Mailing list: http://lists.fedoraproject.org/pipermail/arm/
- IRC channel: irc://irc.freenode.net/#fedora-arm
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.
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).
- Home site: http://archlinuxarm.org/platforms/armv7/beaglebone
- Source repository: https://github.com/archlinuxarm/PKGBUILDs
- IRC channel: irc://irc.freenode.net/#archlinux-arm
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.
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.
- Home site: http://dev.gentoo.org/~armin76/arm/beaglebone/install.xml
- IRC channel: irc://irc.freenode.net/#gentoo-embedded
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.
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 distcc can overcome this problem, but they add complexity.
- Home site: wiki.sabayon.org/Hitchhikers Guide to the BeagleBone
- IRC channel: irc://irc.freenode.net/#sabayon
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.
Although it is still early days for Sabayon on ARM (and hence on BeagleBone), there is regular progress reported on lxnay's blog, and contributions from the community would probably accelerate the work.
- Home site: http://www.zoobab.com/beaglebone
- Source repository: https://github.com/fhunleth/buildroot-beaglebone
- Buildroot project site: http://buildroot.uclibc.org/
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.
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.
- Home site: http://nerves-project.org/
- Source repository: https://github.com/nerves-project/bbone-erlang-buildroot
- Erlang project site: http://www.erlang.org/
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.
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.
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.
- See BeagleBoardRecovery --- (*) Check applicability
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.
Cloud9 IDE and Bonescript
..... description here .....
BeagleBone JTAG Debugging
..... description here .....
Home page and Community
- beagleboard.org -- home for BeagleBoard and BeagleBone products
- irc://irc.freenode.net/#beagle -- official combined IRC channel
- Google Groups forums/mailing list -- English, Japan, Brasil, Turkey
- BeagleBoard and BeagleBone projects list
- Capes Registry and its registration page
- BeagleBone articles at Adafruit blog -- products, projects and tutorials
- Use Google to search beagleboard.org (including IRC logs) using site:beagleboard.org <search term>
Tutorials and Videos
- BeagleBone Intro, video by Jason Kridner, Texas Instruments
- How-To: Get Started with the BeagleBone, video by Matt Richardson, MakeMagazine
- The Beaglebone - Unboxing, Introduction Tutorial and First Example, video by Derek Molloy, DCU/EE
- Beaglebone: C/C++ Programming Introduction for ARM Embedded Linux Development using Eclipse, video by Derek Molloy, DCU/EE
- Beaglebone: GPIO Programming on ARM Embedded Linux, video by Derek Molloy, DCU/EE
- First steps with the Beaglebone, introductory HOWTO by octavio at borderhack
Manuals and resources
- BeagleBone System Reference Manual (rev. A3_1.0).
- Texas Instruments - Sitara ARM Cortex-A8 Microprocessor overview.
- ARM/ARMv7-AR Architecture -- ARM Cortex-A8 architecture overview
- ARM Cortex-A8 Technical Reference Manual r2p1
- ARM Cortex-A Development Platforms -- ARM page on Beagle boards
- TI TPS65217 Power Management IC, TPS65217 PMIC datasheet
- FTDI FT2232H Hi-Speed Dual USB UART/FIFO IC overview, FT2232H datasheet
- Linux-USB Gadget API Framework and USB OTG, and kernel config -- Ethernet-over-USB
<splist parent= showparent=no sort=desc sortby=title liststyle=ordered showpath=no kidsonly=no debug=0/>