eLinux.org - Changes related to "Category:BeagleBoard" [en]

BeagleBone

2013-05-24T15:11:36Z

‎Debian: Wheezy released

BeagleBone

2013-05-22T04:35:57Z

‎Home page and Community:

BeagleBone

2013-05-20T16:45:05Z

Add a kernel/Capemgr section

Capemgr

2013-05-20T16:38:29Z

Capemgr page. Take from Capebus which I made a minute ago, but was told was the wrong name.

New page

[[Category: Linux]]
[[Category: BeagleBoard]]
[[Category: BeagleBone]]
[[Category: Kernel]]

This page contains information on Capemgr, an in-kernel mechanism for dynamically loading [[Device_Trees|Device Tree]] fragments from userspace.

<br>

= About =

Capemgr was created out of a need for boards like the [[BeagleBone|BeagleBone]] to be able to detect installed expansion boards at boot time and allocate appropriate resources (load drivers, allocate GPIO, reserve bus addresses, etc) on kernels which use Device Tree. Traditionally, a Device Tree was a static file (or set of files) which described a machine (often an Embedded SoC and the board it's installed on). This of course is not able to support dynamically changing hardware, such as the BeagleBone and its add-on capes.

Further, it is one of the goals of the BeagleBone to allow 3rd parties to create their own capes and to allow users to install and use these capes without re-compiling the kernel.

A key feature of Capemgr is the ability to load Device Tree fragments as overlays to the existing Device Tree at runtime. On the BeagleBone, each cape has a Device Tree fragment which describes it.

= Implementation =

Capemgr is completely implemented in the kernel. There is no userspace component. Since the BeagleBone uses a kernel which is ahead of mainline, the Capemgr implementation is currently located in the BeagleBone kernel patch set at https://github.com/beagleboard/kernel/tree/3.8 .

In the BeagleBone kernel, cape Device Tree fragments are located in <code>firmware/capes</code>. Each cape is represented by a single DTS (Device Tree Source) fragment file. At kernel build time, these fragments are compiled by the Device Tree Compiler into dtbo files (Device Tree Blob Object). At install time, these dtbo objects are copied to <code>/lib/firmware</code>.

Each BeagleBone capes has an EEPROM on SPI bus 0 which contains information about the cape. The format of the data in the EEPROM is described in the System Reference Manual (SRM) [http://circuitco.com/support/index.php Available from CircuitCo]. The Board Name EEPROM field is used by Capemgr to determine which cape fragment to load. There are two ways this board name can be used. The first method is that the Board Name can be mapped in the BeagleBone's main Device Tree Source file (<code>arch/arm/boot/dts/am335x-bone-common.dtsi</code>) to a filename using a structure like the following:

/* mrf24j40 cape */
cape@10 {
part-number = "BB-BONE-MRF24J40";
version@00A0 {
version = "00A0";
dtbo = "cape-bone-mrf24j40-00A0.dtbo";
};
};

The above DT snippet maps the device named BB-BONE-MRF24J40 version 00A0 to the file <code>/lib/firmware/cape-bone-mrf24j40-00A0.dtbo</code>

Alternatively, if there is no mapping the the main DTS file, the Capemgr loader will attempt to load a filename which matches the Board Name and Version fields in the EEPROM. For example, for a board named BB-BONE-LCD7-01 with version 00A2, the Capemgr loader will try to load <code>/lib/firmware/BB-BONE-LCD7-01-00A2.dtbo</code> . This way capes can be added to a system without modifying the BeagleBone's main Device Tree (<code>arch/arm/boot/dts/am335x-bone-common.dtsi</code>).

== Loading a Fragment at Runtime ==

Capemgr provides a sysfs interface to load Device Tree fragments at runtime. <code>/sys/devices/bone_capemgr*/</code>contains information and controls for the Capemgr system. To manually load a DTBO fragment, one can run:

echo BB-BONE-MRF24J40 >/sys/devices/bone_capemgr.7/slots

The above command will cause Capemgr to act as though a device with a Board Name of BB-BONE-MRF24J40 was detected. It will then check if there is a mapping in <code>arch/arm/boot/dts/am335x-bone-common.dtsi</code> and load the appropriate dtbo file from <code>/lib/firmware</code>. If not, it will attempt to load <code>/lib/firmware/BB-BONE-MRF24J40-00A0.dtbo</code> as described in the above section.

One can also specify a version number on the command line:

echo BB-BONE-MRF24J40:00A1 >/sys/devices/bone_capemgr.7/slots

This will attempt to load revision 00A1, first using the mapping in <code>arch/arm/boot/dts/am335x-bone-common.dtsi</code>, and then trying to load <code>/lib/firmware/BB-BONE-MRF24J40-00A1.dtbo</code>.

== Compiling a DTS Fragment Outside the kernel build ==

On a BeagleBone, with the default Angstrom image, use the <code>dtc</code> compiler located at <code>/usr/bin/dtc</code> to compile Device Tree sources into DTBO Device Tree objects without modifying any kernel source. The resulting dtbo can be manually copied into <code>/lib/firmware</code>.

BeagleBoardUbuntu

2013-05-20T15:27:33Z

wording...

BeagleBoardDebian

2013-05-20T15:26:53Z

‎Debian Wheezy snapshot: debian-7.0.0-console-armhf-2013-05-18

BeagleBoardUbuntu

2013-05-20T15:25:05Z

‎Quantal 12.10 armhf: ubuntu-12.10-console-armhf-2013-05-18

ECE497 Calendar and Exercises - Fall 2013

2013-05-18T15:53:13Z

Updating for Fall 2013

New page

[[Category:ECE497 |Calendar]]
[[Category:BeagleBoard]]
{{YoderHead}}

Here's what you'll need to do for the class. Unless stated otherwise these are individual exercises, not team.

I'm updating this from last year, so be sure to check the year to be sure it's been refreshed. If the background is white, it hasn't been updated.

'''All assignments are due the start of the following week. Initially that is a Thursday!'''

== Week 1 ==

{| style="color:blue; background-color:#ffffff;" cellpadding="10" cellspacing="0" border="1"
! Day !! Date !! Reading !! Topic !! Exercise !! Assignment Links
|-
| 1-1
| 30-Aug-2012
|
| Introductions, Demos
| Fire up your Beagle and see it work. Do everything in Exercise 09. Due Friday.
'''[[EBC Exercise 01 Start Here]]''' gives an overview of what we'll be doing over the next few days. Start setting up your Linux development computer now. You can do either a native install, or a virtual machine. [[EBC Exercise 06 Notes on VirtualBox | Here]] and [[EBC Exercise 07 Notes on Installing Ubuntu in VMware Player | here]] are some notes in virtual machine installs. They are out of date. Feel free to update them.

I suggest Ubuntu 12.04 LTS. Some of the TI software may require it. I may not be able to help with other versions of distributions.

| [[ECE497 - 32-bit Embedded Linux, Rose-Hulman]]
[[EBC_Exercise_01_Start_Here#The_Linux_host_computer | EBC Exercise 01 Start Here]]

[[EBC Exercise 02 Out-of-the-Box, Bone]]

[[EBC Exercise 09 Working With Open Source]]
|-
| 1-2
| 31
|
| General Purpose IO, LEDs and push buttons.
| Set up a Beagle, demo in class. Get reference manuals and clone git repository.
| [[EBC Exercise 03 Installing a Beagle OS]]

[[EBC Exercise 05 Getting Exercise Support Materials]]

[[EBC Exercise 10 Flashing an LED]]
|-
| 1-3
| 3-Sept-2012
|
| Interrupts and gpio
|
| [[EBC Exercise 08 Installing Development Tools]]

[[EBC Exercise 11 gpio Polling and Interrupts]]
|-
| 1-4
| 4
|
| i2c, git
|
| [[EBC Exercise 16 git]]
|-
|
| "
|
|
| Add your project ideas
| [[ECE497 Project Ideas]]
|}

== Week 2 ==

{| style="color:blue; background-color:#ffffff;" cellpadding="10" cellspacing="0" border="1"
! Day !! Date !! Reading !! Topic !! Exercise !! Links
|-
| 2-1
| 6-Sept
|
| Pulse Width Modulation
|
| [[EBC Exercise 12 I2C]]

[[EBC Exercise 13 Pulse Width Modulation]]
|-
| 2-2
| 7
|
| Lab Time, Mini Project 01
| Measure gpio and pwm with oscilloscope.
| [[EBC Mini Project 01]]
|-
| 2-3
| 10
|
| gdb, Lab Time
|
| [[EBC Exercise 14 gdb Debugging]]
|-
| 2-4
| 11
|
| Lab Time
|
|
|}

== Week 3 ==

{| style="color:blue; background-color:#ffffff;" cellpadding="10" cellspacing="0" border="1"
! Day !! Date !! Reading !! Topic !! Exercise !! Links
|-
| 3-1
| 13
|
| make, Mini Project 02
| Flash ETC 2012 image on SD card for xM
| [[EBC Exercise 15 make]]

[[EBC Mini Project 02]]

[[EBC Exercise 03 Installing a Beagle OS]]
|-
| 3-2
| 14
|
| Advanced Linux Sound Architecture (ALSA)
|
| [[EBC Exercise 17 Using ALSA for Audio Processing]]
|-
| 3-3
| 17
|
| Using the DSP (c6run)
|
| [[EBC Exercise 18 Using the DSP for Audio Processing]]
|-
| 3-4
| 18
|
| Lab Time, Mini Project 1 demo time
|
|
|}

== Week 4 ==

{|style="color:blue; background-color:#ffffff;" cellpadding="10" cellspacing="0" border="1"
! Day !! Date !! Reading !! Topic !! Exercise !! Links
|-
| 4-1
| 20
|
| Video Processing
|
| [[EBC Exercise 19 DSS2 and sysfs]]

[[EBC Exercise 20 The Display SubSystem (DSS)]]
|-
| 4-2
| 21
|
| Lab Time
|
|
|-
| 4-3
| 24
|
| Threads
|
| [[EBC Exercise 21 Running Audio and Video]]
|-
| 4-4
| 25
|
| Lab Time
|
|
|}

== Week 5 ==

{| style="color:blue; background-color:#ffffff;" cellpadding="10" cellspacing="0" border="1"
! Day !! Date !! Reading !! Topic !! Exercise !! Links
|-
| 5-1
| 27-Sept-2012
|
| Graphical Interfaces and node.js
|
|
|-
| 5-2
| 28
|
| Lab Time
|
|
|-
| 5-3
| 1-Oct-2012
| 2.1-2.3.5, 3.2.13
| Booting, Memory Map, Cross-Development, Processor Basics, TI ARM
|
|
|-
| 5-4
| 2
| 4.1-4.3.3
| The Kernel
|
| [[EBC Exercise 22 Cross-Compiling]]
|}

== Week 6 ==

{| style="color:blue; background-color:#ffffff;" cellpadding="10" cellspacing="0" border="1"
! Day !! Date !! Reading !! Topic !! Exercise !! Links
|-
| 6-1
| 4
| 4.4-4.5, 5.1-5.2
| Adding to the Kernel makefile, Kernel Initialization
| Find the Beagle version of Figure 2-5 on page 25. Be sure to find a numeric value for the starting address of the POP SDRAM. Note where you found this information.
| [[EBC Exercise 23 Configuring the Kernel]]
|-
| "
| "
| 5.3-5.6
| Command Line Processing, __setup Macro
| Configuring the Kernel Lab
| [[EBC Exercise 24 Kconfig Edits]]
|-
| 6-2
| 5
|
| Lab Time
|
|
|-
| 6-3
| 8
| 6.1-6.3
| System Initialization
| Project Status Report, update your project status page.
| [[EBC Exercise 21a Boot Sequence]]
[[ECE497 Contributions and Project Status]]
|-
| 6-4
| 9
| 6.4-6.7
| Initial RAM Disk, Using initramfs
|
|
|}

== Week 7 ==

{| style="color:blue; background-color:#ffffff;" cellpadding="10" cellspacing="0" border="1"
! Day !! Date !! Reading !! Topic !! Exercise !! Links
|-
| 7-1
| 15
| 7.1-7.3
| Bootloaders, Das U-Boot
|
| [[EBC Exercise 25 Configuring U-boot]]
|-
| 7-2
| 16
|
| Demo and Work Day
|
|
|-
| 7-3
| 18
| 8.1-8.4
| Device Driver Basics, Driver Methods
|
| [[EBC Exercise 08 Installing Development Tools]]
[[EBC Exercise 26 Device Drivers]]
|-
| 7-4
| 19
| 11.1-11.4
| BusyBox
| In B105
| [[EBC Exercise 27 BusyBox]]

|}

== Week 8 ==

{| style="color:blue; background-color:#ffffff;" cellpadding="10" cellspacing="0" border="1"
! Day !! Date !! Reading !! Topic !! Exercise !! Links
|-
| 8-1
| 22
| [http://gstreamer.freedesktop.org/ GStreamer]
| GStreamer ([http://wiki.oz9aec.net/index.php/Gstreamer_cheat_sheet Cheat Sheet],
[http://www.oz9aec.net/index.php/gstreamer/345-a-weekend-with-gstreamer Weekend with GStreamer])
| Status Report
| [[EBC Exercise 29 GStreamer]] (optional)
|-
| 8-2
| 23
|
|
| Project Time
|
|-
| 8-3
| 25
|
| Remote debugging with gdb, cbrowser/cscope and strace
| Project Time
| [[EBC Exercise 28 Remote gdb and more]] (optional)
|-
| 8-4
| 26
|
| Project Time
|
| [[ECE497 Contributions and Project Status]]
|}

== Week 9 ==

{| style="color:blue; background-color:#ffffff;" cellpadding="10" cellspacing="0" border="1"
! Day !! Date !! Reading !! Topic !! Exercise !! Links
|-
| 9-1
| 29
|
| Project Time all week
|
|
|-
| 9-2
| 30
|
|
|
|
|-
| 9-3
| 1-Nov-2012
|
|
|
|
|-
| 9-4
| 2
|
|
|
|
|}

== Week 10 ==

{| style="color:blue; background-color:#ffffff;" cellpadding="10" cellspacing="0" border="1"
! Day !! Date !! Reading !! Topic !! Exercise !! Links
|-
| 10-1
| 5
|
|
| Project Time all week
|
|-
| 10-2
| 6
|
|
|
|
|-
| 10-3
| 8
|
|
| Meet in B105
|
|-
| 10-4
| 9
|
|
| Demo Time
|
|}

{{YoderFoot}}

ECE497 Calendar and Exercises

2013-05-18T15:50:39Z

BeagleBoard Hardware Interfacing

2013-05-18T15:46:15Z

BeagleBrick

2013-05-18T15:43:54Z

BeagleBoardPWM

2013-05-18T15:42:44Z

Moved to ECE597

BeagleBoard Education Workshops

2013-05-18T15:32:02Z

‎2012 ASEE Workshop:

@@ Line 171: / Line 171: @@
 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).
+Starting with Debian 7.0 (Wheezy) there is a port targeted at newer (armv7 with fpu) hardware with another ABI ("armhf").
 The [http://www.debian.org/intro/about Debian Project] is strongly committed to software freedom, and has a long pedigree and a good reputation.

@@ Line 277: / Line 277: @@
 = Links =
-== Home page and Community ==
+== Home site and Community ==
 * [http://beagleboard.org/ beagleboard.org] -- home for BeagleBoard and BeagleBone products
 * [http://beagleboard.org/Products/BeagleBone%20Black BeagleBone Black] -- manufacturer's page for the second BeagleBone board
@@ Line 288: / Line 288: @@
 * [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
 * [https://github.com/selsinork/beaglebone-black-pinmux github.com/selsinork/beaglebone-black-pinmux] -- pinmux data for BeagleBone Black, including extraction scripts
 == Tutorials and Videos ==

@@ Line 262: / Line 262: @@
 * Download Netbeans (Windows/Linux/OS-X/Solaris): http://www.netbeans.org/
 * Example tutorial on setting this up: http://mechomaniac.com/BeagleboardDevelopmentWithNetbeans
 = FAQ =

@@ Line 104: / Line 104: @@
 Services Active:
   Note: Depending on your internal network these may work out the box
-  Apache, Port 80: http://arm/ (Bone: or via usb) http://192.168.7.2
+  Apache, Port 80: http://arm/ (Bone: via usb) http://192.168.7.2
-  SSH, Port 22: ssh ubuntu@arm (Bone: or via usb) ubuntu@192.168.7.2
+  SSH, Port 22: ssh ubuntu@arm (Bone: via usb) ubuntu@192.168.7.2
-  shellinabox, Port 4200: https://arm:4200/ (Bone: or via usb) https://192.168.7.2:4200
+  shellinabox, Port 4200: https://arm:4200/ (Bone: via usb) https://192.168.7.2:4200
   Getty, Serial Port

@@ Line 73: / Line 73: @@
 Image Updated:
 *2013-04-26
 ** Beagle/Panda/Panda ES: v3.7.10-x10 kernel
@@ Line 80: / Line 84: @@
 ** Beagle/Panda/Panda ES: v3.7.10-x10 kernel
 ** Bone: v3.2.33-psp26 kernel (--uboot bone_dtb = v3.8.4-bone9)
 Services Active:
   Note: Depending on your internal network these may work out the box
-  Apache, Port 80: http://arm/
+  Apache, Port 80: http://arm/ (Bone: via usb) http://192.168.7.2
-  SSH, Port 22: ssh ubuntu@arm
+  SSH, Port 22: ssh ubuntu@arm (Bone: via usb) ubuntu@192.168.7.2
   Getty, Serial Port
 Get prebuilt image:
-  wget http://rcn-ee.net/deb/rootfs/wheezy/debian-wheezy-console-armhf-2013-04-26.tar.xz
+  wget http://rcn-ee.net/deb/rootfs/wheezy/debian-7.0.0-console-armhf-2013-05-18.tar.xz
 Verify Image with:
-  md5sum debian-wheezy-console-armhf-2013-04-26.tar.xz
+  md5sum debian-7.0.0-console-armhf-2013-05-18.tar.xz
-a1c4ff53f3b2a42419ee1c7c1f47e40  debian-wheezy-console-armhf-2013-04-26.tar.xz
+  dfe308e3e534d8adef75db5308174cf6  debian-7.0.0-console-armhf-2013-05-18.tar.xz
 Unpack Image:
-  tar xJf debian-wheezy-console-armhf-2013-04-26.tar.xz
+  tar xJf debian-7.0.0-console-armhf-2013-05-18.tar.xz
-  cd debian-wheezy-console-armhf-2013-04-26
+  cd debian-7.0.0-console-armhf-2013-05-18
 Install Image:

@@ Line 90: / Line 90: @@
 === Raring 13.04 armhf ===
 Image Updated:
 *2013-04-26
 ** Beagle/Panda/Panda ES: v3.7.10-x10 kernel
@@ Line 97: / Line 101: @@
 ** Beagle/Panda/Panda ES: v3.7.10-x10 kernel
 ** Bone: v3.2.33-psp26 kernel (--uboot bone_dtb = v3.8.4-bone9)
 Services Active:
   Note: Depending on your internal network these may work out the box
-  Apache, Port 80: http://arm/
+  Apache, Port 80: http://arm/ (Bone: or via usb) http://192.168.7.2
-  SSH, Port 22: ssh ubuntu@arm
+  SSH, Port 22: ssh ubuntu@arm (Bone: or via usb) ubuntu@192.168.7.2
   Getty, Serial Port
@@ Line 111: / Line 113: @@
 Get prebuilt image:
-  wget http://rcn-ee.net/deb/rootfs/raring/ubuntu-13.04-console-armhf-2013-04-26.tar.xz
+  wget http://rcn-ee.net/deb/rootfs/raring/ubuntu-13.04-console-armhf-2013-05-18.tar.xz
   mirrors (will take some time to update):
-  wget http://ynezz.ibawizard.net/beagleboard/raring/ubuntu-13.04-console-armhf-2013-04-26.tar.xz
+  wget http://ynezz.ibawizard.net/beagleboard/raring/ubuntu-13.04-console-armhf-2013-05-18.tar.xz
 Verify image with:
-  md5sum ubuntu-13.04-console-armhf-2013-04-26.tar.xz
+  md5sum ubuntu-13.04-console-armhf-2013-05-18.tar.xz
-  e54b8693cb92b40d694e5885e4a1b86c  ubuntu-13.04-console-armhf-2013-04-26.tar.xz
+c791b69ee4c6ddfd1ce4c9049ecf23e  ubuntu-13.04-console-armhf-2013-05-18.tar.xz
 Unpack image:
-  tar xJf ubuntu-13.04-console-armhf-2013-04-26.tar.xz
+  tar xJf ubuntu-13.04-console-armhf-2013-05-18.tar.xz
-  cd ubuntu-13.04-console-armhf-2013-04-26
+  cd ubuntu-13.04-console-armhf-2013-05-18
 If you don't know the location of your SD card:
@@ Line 202: / Line 204: @@
   git clone git://github.com/RobertCNelson/omap-image-builder.git
   cd omap-image-builder
-  git checkout v2013.04 -b v2013.04
+  git checkout v2013.05 -b v2013.05
   touch release
   ./build_image.sh
@@ Line 209: / Line 211: @@
 Image Updated:
 *2013-04-26
 ** Beagle/Panda/Panda ES: v3.7.10-x10 kernel
@@ Line 216: / Line 222: @@
 ** Beagle/Panda/Panda ES: v3.7.10-x10 kernel
 ** Bone: v3.2.33-psp26 kernel (--uboot bone_dtb = v3.8.4-bone9)
 Get prebuilt image:
-  wget http://rcn-ee.net/deb/rootfs/quantal/ubuntu-12.10-console-armhf-2013-04-26.tar.xz
+  wget http://rcn-ee.net/deb/rootfs/quantal/ubuntu-12.10-console-armhf-2013-05-18.tar.xz
 Verify image with:
-  md5sum ubuntu-12.10-console-armhf-2013-04-26.tar.xz
+  md5sum ubuntu-12.10-console-armhf-2013-05-18.tar.xz
-  b7cd2f94c0dbc75f8d6897e559d52c0a  ubuntu-12.10-console-armhf-2013-04-26.tar.xz
+  feb3e41208dba6ec1593ac0b910cff3d  ubuntu-12.10-console-armhf-2013-05-18.tar.xz
 Unpack image:
-  tar xJf ubuntu-12.10-console-armhf-2013-04-26.tar.xz
+  tar xJf ubuntu-12.10-console-armhf-2013-05-18.tar.xz
-  cd ubuntu-12.10-console-armhf-2013-04-26
+  cd ubuntu-12.10-console-armhf-2013-05-18
 Then follow directions show above with the other images...

@@ Line 1: / Line 1: @@
-[[Category:ECE497 |Calendar]]
+[[Category:ECE497Fall2012 |Calendar]]
 [[Category:BeagleBoard]]
 {{YoderHead}}

@@ Line 1: / Line 1: @@
 [[Category:BeagleBoard]]
-[[Category:ECE497]]
+[[Category:ECE597]]
-<analytics uacct="UA-119847-6" ></analytics>
 This page is meant to help anyone who wants to create an expansion board to interface with the [[BeagleBoard]].  It summarizes some of the commercial options, and includes some recommendations for components for a custom board.

← Older revision		Revision as of 15:43, 18 May 2013
Line 1:		Line 1:
−	[[Category:~~ECE497~~]]	+	[[Category:ECE497Winter1112]]
	[[Category:BeagleBoard]]		[[Category:BeagleBoard]]