https://wiki.gumstix.com/api.php?action=feedcontributions&feedformat=atom&user=Dan+NelsonGumstix User Wiki - User contributions [en]2026-05-06T17:11:18ZUser contributionsMediaWiki 1.25.3https://wiki.gumstix.com/index.php?title=GPIO&diff=5887GPIO2012-09-21T09:18:42Z<p>Dan Nelson: /* Example: Changing the multiplexing for a pin */</p>
<hr />
<div>== Overo GPIO ==<br />
<br />
The Overo kernels support the sysfs gpio implementation for accessing GPIO from userspace. <br />
<br />
This allows you to control GPIO from the command line this way<br />
<br />
root@overo# echo 146 > /sys/class/gpio/export<br />
root@overo:/sys/class/gpio# cat gpio146/direction<br />
in<br />
root@overo# echo out > /sys/class/gpio/gpio146/direction<br />
root@overo:/sys/class/gpio# cat gpio146/direction<br />
out<br />
root@overo# cat /sys/class/gpio/gpio146/value<br />
0<br />
root@overo# echo 1 > /sys/class/gpio/gpio146/value<br />
root@overo# cat /sys/class/gpio/gpio146/value<br />
1<br />
<br />
If you have an expansion card with a 40 pin header, then this will be controlling pin 27. You can use pin 1 for a ground. (If you don't have a meter, a p/n 276-0330 1.8V Red LED from Radio Shack works for testing.) <br />
<br />
Schematics and pin-outs for the Gumstix expansion boards can be found [http://pubs.gumstix.com/boards/ here.]<br />
<br />
=== How It Works ===<br />
<br />
See the kernel docs [http://www.kernel.org/doc/Documentation/gpio.txt gpio.txt] for an overview of gpio and the userspace sysfs interface. The "Sysfs Interface for Userspace (OPTIONAL)" section near the end discusses the userspace implementation.<br />
<br />
See the [http://www-s.ti.com/sc/techlit/spruf98 OMAP35X Technical Reference Manual] Section 7.6.3 PADCONFS Register Description and Table 7.5 Core Control Module PadConf Register Field in Section 7.4.4.3 Pad Multiplexing Register Fields for identifying the possible MUX configuration for each GPIO.<br />
<br />
Then see the U-Boot source code, board/overo/overo.h for how the pins on the Overo are actually being muxed. See include/asm-arm/arch-omap3/mux.h in the U-Boot tree for the definitions used in overo.h. The pins in mux mode M4 are already configured for GPIO.<br />
<br />
=== Making Modifications ===<br />
<br />
Currently all the GPIO multiplexing for the Overo's is being done by the bootloader U-Boot, so the conventional way to modify the pin muxing is to edit overo.h and rebuild U-Boot.<br />
<br />
You can also change the mux configuration from within Linux. One simple approach is to do it from userspace accessing /dev/mem. A program devmem2 is part of the omap3-console-image and will work. See the remuxing example below.<br />
<br />
If you are writing your own kernel module, you can also read/write the PADCONF registers the way you normally would after an ioremap.<br />
<br />
Third, there is a Linux build config option CONFIG_OMAP_MUX, not normally enabled in the Overo configs, that will give you some additional utility functions to simplify mux changes within kernel or module code (see arch/arm/plat-omap/mux.c).<br />
<br />
Finally, it looks like the Linux OMAP34xx pin muxing code is getting a complete overhaul. See this [http://www.mail-archive.com/linux-omap@vger.kernel.org/msg18474.html thread] on the Linux OMAP mailing list. Judging from some posts on the Gumstix lists, it sounds like this will be available in 2.6.33.<br />
<br />
=== Overo Kernel Usage ===<br />
<br />
Just because pins are configured as GPIO in u-boot, doesn't necessarily mean you can use them. If you look at /sys/class/gpio on a default Overo, you'll get something like this.<br />
<br />
root@overo:~# ls /sys/class/gpio<br />
export gpio164 gpio65 gpiochip160 gpiochip64<br />
gpio15 gpio168 gpiochip0 gpiochip192 gpiochip96<br />
gpio16 gpio176 gpiochip128 gpiochip32 unexport<br />
<br />
The reason you see some GPIO already exported is because the linux code in arch/arm/mach-omap2/board-overo.c is explicitly exporting these pins for another use. Whether they are being used depends on the hardware you have attached. The kernel also uses pins configured as GPIO that it doesn't export. These depend on the board configuration and the kernel drivers being used.<br />
<br />
To be more explicit, look inside board-overo.c, you'll see these definitions<br />
<br />
#define OVERO_GPIO_BT_XGATE 15<br />
#define OVERO_GPIO_W2W_NRESET 16<br />
#define OVERO_GPIO_PENDOWN 114<br />
#define OVERO_GPIO_BT_NRESET 164<br />
#define OVERO_GPIO_USBH_CPEN 168<br />
#define OVERO_GPIO_USBH_NRESET 183<br />
...<br />
#define OVERO_SMSC911X_GPIO 176<br />
#define OVERO_SMSC911X2_GPIO 65<br />
...<br />
#define OVERO_GPIO_LCD_EN 144<br />
#define OVERO_GPIO_LCD_BL 145<br />
<br />
Follow their usage inside the file and you will be able to explain the /sys/class/gpio output you see above.<br />
<br />
=== Input or Output ===<br />
<br />
Pins configured as GPIO are sometimes also specified as being strictly input or output. <br />
<br />
This can happen when they are mux'd or when they are explicitly exported by the kernel. <br />
<br />
In either of those cases you won't be able to change the I/O direction from userspace.<br />
<br />
=== Electrical Specifications ===<br />
<br />
Voltage is 1.8v <br />
<br />
Current specifications <TODO ???> <br />
<br />
=== Usable Pins ===<br />
<br />
Here's a few GPIO you can use immediately from userspace without any u-boot or kernel changes.<br />
It will however require that the specific GPIO isn't used by the attached expansion board. <br />
<br />
==== 40 Pin Expansion Header ==== <br />
<br />
Pin 4 - gpio114<br /><br />
It's the pendown signal on the touchscreen controller but it's available if you aren't using a expansion board with touchscreen support.<br /><br />
This pin can not be configured as output, it is input only (see [http://www-s.ti.com/sc/techlit/spruf98 OMAP35X Technical Reference Manual] p. 3389).<br />
Pulled-low, reads 0 with no input, reads 1 with an input applied<br /><br />
<br />
Pin 19 - gpio170<br /><br />
The HDQ/1-Wire output. Not used unless you explicitly enable the 1-wire module.<br /><br />
User exportable<br /><br />
Output only - configured this way in the u-boot muxing<br /><br />
<br />
Pin 27 - gpio146<br /><br />
Pin 29 - gpio147<br /><br />
User exportable<br /><br />
Direction can be changed<br /><br />
Floating state<br /><br />
<br />
Pin 28 - gpio145<br /><br />
Pin 30 - gpio144<br /><br />
Used with LCD, but available if not using an LCD<br /><br />
Configured as output only when exported by the kernel in board-overo.h. Can't change direction from userspace without modifying kernel.<br /><br />
Set to ON by kernel during init (not all configs, see board-overo.c). This could be a problem for real use, but okay for testing.<br /><br />
<br />
==== Palo43 Board ====<br />
<br />
LED D2 - gpio21<br /><br />
LED D3 - gpio22<br /><br />
Userspace exportable, set the direction as out<br /><br />
echo 0 > gpioxx/value to turn on, echo 1 > gpioxx/value to turn off<br /><br />
<br />
Switch - gpio14<br /><br />
Switch - gpio23<br /><br />
Userspace exportable, leave direction as in<br /><br />
With the switch open (not pushed) will register a value of 1<br /><br />
Push the switch and the value will be 0<br /><br />
<br />
=== Example: Changing the multiplexing for a pin ===<br />
<br />
If you aren't using the first SPI bus, then there are 5 pins on the 40-pin expansion header that you could repurpose for GPIO.<br />
<br />
Pin 3 - gpio171(spi1_clk)<br /><br />
Pin 5 - gpio172 (spi1_mosi)<br /><br />
Pin 6 - gpio174 (spi1_cs0)<br /><br />
Pin 7 - gpio173 (spi1_miso)<br /><br />
Pin 8 - gpio175 (spi1_cs1)<br /><br />
<br />
The first step is to find the appropriate PADCONF register address for each gpio from Table 7.5 of the TRM. Pay attention to whether it is the low or high order 16 bits for each gpio. You should come up with these values.<br />
<br />
gpio171 : 0x4800 21C8<br /><br />
gpio172 : 0x4800 21CA<br /><br />
gpio173 : 0x4800 21CC<br /><br />
gpio174 : 0x4800 21CE<br /><br />
gpio175 : 0x4800 21D0<br /><br />
<br />
Using devmem2, here is how you could read the current PADCONF value for what could be gpio171<br />
<br />
root@overo# devmem2 0x480021c8 h<br />
...<br />
Value at address 0x480021C8 (0x400201c8): 0x100<br />
<br />
Which corresponds to a mux value of (IEN | PTD | DIS | M0) using the U-Boot mux.h definitions. Mux mode 0 for this pin is the spi1_clk configuration found by looking in Table 7.5 of the TRM.<br />
<br />
To reconfigure pin 3 to be gpio171, as input or output with inputs pulled low, write 0x010C to the controlling PADCONF register. This would correspond to (IEN | PTD | EN | M4). The bit fields are defined in the TRM Section 7.6.3.<br />
<br />
root@overo# devmem2 0x480021c8 h 0x10c<br />
<br />
Now you can export and configure gpio171 from userspace like the example with gpio146 at the beginning. To make it visible in sysfs:<br />
<br />
echo 172 > /sys/class/gpio/export<br />
<br />
If you want this multiplexing to be permanent, then you would modify the U-Boot file board/overo/overo.h and rebuild U-Boot. If you are using OE, then you'll want to generate a patch file to be used in the u-boot-omap3 recipe.<br />
<br />
There are additional pins on the header that can be reconfigured this way.<br />
<br />
To reconfigure pins from within a kernel module the following code can be used:<br />
<br />
void *addr = ioremap(spi1_clk, 4);<br />
if (!addr)<br />
{<br />
printk("Cannot ioremap 0x%lx\n", spi1_clk);<br />
} else {<br />
printk("ioremap OK: 0x%lx\n", spi1_clk);<br />
iowrite32( 0x010C | (0x010C << 16), addr);<br />
iounmap(addr);<br />
}<br />
<br />
This will make both gpio171 and gpio172 input or output with inputs pulled low.<br />
<br />
=== Interrupts on GPIO pins ===<br />
<br />
Here is an example on setting up an interrupt on GPIO pin 23 from within a kernel module:<br />
<br />
irqreturn_t gpio_irq_handler(int irq, void *dev_id) {<br />
static int cnt=0;<br />
printk("gpio_irq_handler %i\n", cnt++);<br />
return IRQ_HANDLED;<br />
}<br />
<br />
int gpio_irq= gpio_to_irq(23);<br />
int ret = request_irq(gpio_irq, gpio_irq_handler, IRQF_TRIGGER_FALLING, "gpio irq handler", gpio_irq_handler);<br />
if (ret)<br />
printk("gpio interrupt request failed\n");<br />
else<br />
printk("gpio interrupt request succeeded\n");<br />
<br />
=== GPIO Software for the Overo ===<br />
<br />
Dave Hylands has written several software packages to facilitate GPIO programming on the Overos.<br />
<br />
[[GPIO Event Driver]] allows multiple GPIO lines to be monitored from user-space.<br />
<br />
[[User GPIO Driver]] is a reflection of the kernel's gpiolib API into user space.<br />
<br />
=== More Links ===<br />
<br />
Here is another article [http://elinux.org/BeagleBoardPinMux BeagleBoardPinMux] talking about OMAP3 pin muxing.<br />
<br />
== Verdex GPIO ==<br />
{| border="1" cellpadding="5" cellspacing="0" style="width:100px"<br />
| style="background:yellow;" | GPIO(<i> n </i>)<br />
|}<br />
<br />
<br />
* Logic level (3.3V) signals <br />
* 3-4mA max<br />
<br />
<br />
all GPIO's information and examples should go here<br />
<br />
<br />
todo<br />
<br />
<br />
According to the PXA270 datasheet:<br />
http://pubs.gumstix.com/documents/PXA%20Documentation/PXA270/PXA270%20Electrical,%20Mechanical,%20and%20Thermal%20Specification%20%5b280002-005%5d.pdf<br />
most of the pins are limited to 3mA, and a few can go upto 4 mA (see page 5-9) <br />
<br />
<br><br />
<br><br />
<br />
<br />
=== Accessing GPIO's from userland ===<br />
<br />
<br />
If proc-gpio is a module, add it to /etc/modules or do a modprobe proc-gpio.<br />
<br />
A number of files exist under /proc/gpio, one for each GPIO on the PXA processor.<br />
<br />
If you cat one of these files, you get, eg:<br />
<pre><br />
# cat /proc/gpio/GPIO12<br />
12 GPIO in set<br />
</pre><br />
<br />
That tells you — GPIO number, function (either GPIO, AF 1, AF 2, or AF 3), in|out, set|clear.<br />
<br />
You can change any of those values, by writing to the file, eg:<br />
<pre><br />
# echo "AF1 out" > /proc/gpio/GPIO12<br />
</pre><br />
<br />
This sets GPIO12 to AF1, out mode. (In the case of GPIO12, the PXA defines this function as putting out the 32kHz clock signal.) this is currently case-sensitive<br />
<br />
If you have the GPIO set to an output, and GPIO mode, you can set or clear the signal:<br />
<pre><br />
# echo "GPIO out set" > /proc/gpio/GPIO12<br />
# echo "GPIO out clear" > /proc/gpio/GPIO12<br />
</pre><br />
The alternative functions are described in the PXA255 Developer's Manual (link should be found in the Featured links-box) section 4.1.2.<br />
<br />
=== Alternative method to access GPIO's from userland ===<br />
<br />
The [[User GPIO Driver]] provides a reflection of the kernel's gpiolib library into userspace.<br />
<br />
=== gpio-event driver ===<br />
<br />
The [[GPIO Event Driver]] allows gpio changes to be captured from user-space.<br />
<br />
<br><br />
<br><br />
<br><br />
-----------------------------<br />
<br />
Related pages on the old wiki:<br />
<br />
http://docwiki.gumstix.org/index.php/Tips_and_tricks#Access_GPIOs_from_user-space<br />
<br />
http://docwiki.gumstix.org/index.php/Sample_code/C/gpregs<br />
<br />
http://docwiki.gumstix.org/index.php/Kernel_programming<br />
<br />
.<br />
[[Category:Literature]]<br />
[[Category:GPIO]]</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=GPIO&diff=5886GPIO2012-09-21T07:28:59Z<p>Dan Nelson: /* Example: Changing the multiplexing for a pin */</p>
<hr />
<div>== Overo GPIO ==<br />
<br />
The Overo kernels support the sysfs gpio implementation for accessing GPIO from userspace. <br />
<br />
This allows you to control GPIO from the command line this way<br />
<br />
root@overo# echo 146 > /sys/class/gpio/export<br />
root@overo:/sys/class/gpio# cat gpio146/direction<br />
in<br />
root@overo# echo out > /sys/class/gpio/gpio146/direction<br />
root@overo:/sys/class/gpio# cat gpio146/direction<br />
out<br />
root@overo# cat /sys/class/gpio/gpio146/value<br />
0<br />
root@overo# echo 1 > /sys/class/gpio/gpio146/value<br />
root@overo# cat /sys/class/gpio/gpio146/value<br />
1<br />
<br />
If you have an expansion card with a 40 pin header, then this will be controlling pin 27. You can use pin 1 for a ground. (If you don't have a meter, a p/n 276-0330 1.8V Red LED from Radio Shack works for testing.) <br />
<br />
Schematics and pin-outs for the Gumstix expansion boards can be found [http://pubs.gumstix.com/boards/ here.]<br />
<br />
=== How It Works ===<br />
<br />
See the kernel docs [http://www.kernel.org/doc/Documentation/gpio.txt gpio.txt] for an overview of gpio and the userspace sysfs interface. The "Sysfs Interface for Userspace (OPTIONAL)" section near the end discusses the userspace implementation.<br />
<br />
See the [http://www-s.ti.com/sc/techlit/spruf98 OMAP35X Technical Reference Manual] Section 7.6.3 PADCONFS Register Description and Table 7.5 Core Control Module PadConf Register Field in Section 7.4.4.3 Pad Multiplexing Register Fields for identifying the possible MUX configuration for each GPIO.<br />
<br />
Then see the U-Boot source code, board/overo/overo.h for how the pins on the Overo are actually being muxed. See include/asm-arm/arch-omap3/mux.h in the U-Boot tree for the definitions used in overo.h. The pins in mux mode M4 are already configured for GPIO.<br />
<br />
=== Making Modifications ===<br />
<br />
Currently all the GPIO multiplexing for the Overo's is being done by the bootloader U-Boot, so the conventional way to modify the pin muxing is to edit overo.h and rebuild U-Boot.<br />
<br />
You can also change the mux configuration from within Linux. One simple approach is to do it from userspace accessing /dev/mem. A program devmem2 is part of the omap3-console-image and will work. See the remuxing example below.<br />
<br />
If you are writing your own kernel module, you can also read/write the PADCONF registers the way you normally would after an ioremap.<br />
<br />
Third, there is a Linux build config option CONFIG_OMAP_MUX, not normally enabled in the Overo configs, that will give you some additional utility functions to simplify mux changes within kernel or module code (see arch/arm/plat-omap/mux.c).<br />
<br />
Finally, it looks like the Linux OMAP34xx pin muxing code is getting a complete overhaul. See this [http://www.mail-archive.com/linux-omap@vger.kernel.org/msg18474.html thread] on the Linux OMAP mailing list. Judging from some posts on the Gumstix lists, it sounds like this will be available in 2.6.33.<br />
<br />
=== Overo Kernel Usage ===<br />
<br />
Just because pins are configured as GPIO in u-boot, doesn't necessarily mean you can use them. If you look at /sys/class/gpio on a default Overo, you'll get something like this.<br />
<br />
root@overo:~# ls /sys/class/gpio<br />
export gpio164 gpio65 gpiochip160 gpiochip64<br />
gpio15 gpio168 gpiochip0 gpiochip192 gpiochip96<br />
gpio16 gpio176 gpiochip128 gpiochip32 unexport<br />
<br />
The reason you see some GPIO already exported is because the linux code in arch/arm/mach-omap2/board-overo.c is explicitly exporting these pins for another use. Whether they are being used depends on the hardware you have attached. The kernel also uses pins configured as GPIO that it doesn't export. These depend on the board configuration and the kernel drivers being used.<br />
<br />
To be more explicit, look inside board-overo.c, you'll see these definitions<br />
<br />
#define OVERO_GPIO_BT_XGATE 15<br />
#define OVERO_GPIO_W2W_NRESET 16<br />
#define OVERO_GPIO_PENDOWN 114<br />
#define OVERO_GPIO_BT_NRESET 164<br />
#define OVERO_GPIO_USBH_CPEN 168<br />
#define OVERO_GPIO_USBH_NRESET 183<br />
...<br />
#define OVERO_SMSC911X_GPIO 176<br />
#define OVERO_SMSC911X2_GPIO 65<br />
...<br />
#define OVERO_GPIO_LCD_EN 144<br />
#define OVERO_GPIO_LCD_BL 145<br />
<br />
Follow their usage inside the file and you will be able to explain the /sys/class/gpio output you see above.<br />
<br />
=== Input or Output ===<br />
<br />
Pins configured as GPIO are sometimes also specified as being strictly input or output. <br />
<br />
This can happen when they are mux'd or when they are explicitly exported by the kernel. <br />
<br />
In either of those cases you won't be able to change the I/O direction from userspace.<br />
<br />
=== Electrical Specifications ===<br />
<br />
Voltage is 1.8v <br />
<br />
Current specifications <TODO ???> <br />
<br />
=== Usable Pins ===<br />
<br />
Here's a few GPIO you can use immediately from userspace without any u-boot or kernel changes.<br />
It will however require that the specific GPIO isn't used by the attached expansion board. <br />
<br />
==== 40 Pin Expansion Header ==== <br />
<br />
Pin 4 - gpio114<br /><br />
It's the pendown signal on the touchscreen controller but it's available if you aren't using a expansion board with touchscreen support.<br /><br />
This pin can not be configured as output, it is input only (see [http://www-s.ti.com/sc/techlit/spruf98 OMAP35X Technical Reference Manual] p. 3389).<br />
Pulled-low, reads 0 with no input, reads 1 with an input applied<br /><br />
<br />
Pin 19 - gpio170<br /><br />
The HDQ/1-Wire output. Not used unless you explicitly enable the 1-wire module.<br /><br />
User exportable<br /><br />
Output only - configured this way in the u-boot muxing<br /><br />
<br />
Pin 27 - gpio146<br /><br />
Pin 29 - gpio147<br /><br />
User exportable<br /><br />
Direction can be changed<br /><br />
Floating state<br /><br />
<br />
Pin 28 - gpio145<br /><br />
Pin 30 - gpio144<br /><br />
Used with LCD, but available if not using an LCD<br /><br />
Configured as output only when exported by the kernel in board-overo.h. Can't change direction from userspace without modifying kernel.<br /><br />
Set to ON by kernel during init (not all configs, see board-overo.c). This could be a problem for real use, but okay for testing.<br /><br />
<br />
==== Palo43 Board ====<br />
<br />
LED D2 - gpio21<br /><br />
LED D3 - gpio22<br /><br />
Userspace exportable, set the direction as out<br /><br />
echo 0 > gpioxx/value to turn on, echo 1 > gpioxx/value to turn off<br /><br />
<br />
Switch - gpio14<br /><br />
Switch - gpio23<br /><br />
Userspace exportable, leave direction as in<br /><br />
With the switch open (not pushed) will register a value of 1<br /><br />
Push the switch and the value will be 0<br /><br />
<br />
=== Example: Changing the multiplexing for a pin ===<br />
<br />
If you aren't using the first SPI bus, then there are 5 pins on the 40-pin expansion header that you could repurpose for GPIO.<br />
<br />
Pin 3 - gpio171(spi1_clk)<br /><br />
Pin 5 - gpio172 (spi1_mosi)<br /><br />
Pin 6 - gpio174 (spi1_cs0)<br /><br />
Pin 7 - gpio173 (spi1_miso)<br /><br />
Pin 8 - gpio175 (spi1_cs1)<br /><br />
<br />
The first step is to find the appropriate PADCONF register address for each gpio from Table 7.5 of the TRM. Pay attention to whether it is the low or high order 16 bits for each gpio. You should come up with these values.<br />
<br />
gpio171 : 0x4800 21C8<br /><br />
gpio172 : 0x4800 21CA<br /><br />
gpio173 : 0x4800 21CC<br /><br />
gpio174 : 0x4800 21CE<br /><br />
gpio175 : 0x4800 21D0<br /><br />
<br />
Using devmem2, here is how you could read the current PADCONF value for what could be gpio171<br />
<br />
root@overo# devmem2 0x480021c8 h<br />
...<br />
Value at address 0x480021C8 (0x400201c8): 0x100<br />
<br />
Which corresponds to a mux value of (IEN | PTD | DIS | M0) using the U-Boot mux.h definitions. Mux mode 0 for this pin is the spi1_clk configuration found by looking in Table 7.5 of the TRM.<br />
<br />
To reconfigure pin 3 to be gpio171, as input or output with inputs pulled low, write 0x010C to the controlling PADCONF register. This would correspond to (IEN | PTD | EN | M4). The bit fields are defined in the TRM Section 7.6.3.<br />
<br />
root@overo# devmem2 0x480021c8 h 0x10c<br />
<br />
Now you can export and configure gpio171 from userspace like the example with gpio146 at the beginning. To make it visible in sysfs.<br />
<br />
echo 172 > /sys/class/gpio/export<br />
<br />
If you want this multiplexing to be permanent, then you would modify the U-Boot file board/overo/overo.h and rebuild U-Boot. If you are using OE, then you'll want to generate a patch file to be used in the u-boot-omap3 recipe.<br />
<br />
There are additional pins on the header that can be reconfigured this way.<br />
<br />
To reconfigure pins from within a kernel module the following code can be used:<br />
<br />
void *addr = ioremap(spi1_clk, 4);<br />
if (!addr)<br />
{<br />
printk("Cannot ioremap 0x%lx\n", spi1_clk);<br />
} else {<br />
printk("ioremap OK: 0x%lx\n", spi1_clk);<br />
iowrite32( 0x010C | (0x010C << 16), addr);<br />
iounmap(addr);<br />
}<br />
<br />
This will make both gpio171 and gpio172 input or output with inputs pulled low.<br />
<br />
=== Interrupts on GPIO pins ===<br />
<br />
Here is an example on setting up an interrupt on GPIO pin 23 from within a kernel module:<br />
<br />
irqreturn_t gpio_irq_handler(int irq, void *dev_id) {<br />
static int cnt=0;<br />
printk("gpio_irq_handler %i\n", cnt++);<br />
return IRQ_HANDLED;<br />
}<br />
<br />
int gpio_irq= gpio_to_irq(23);<br />
int ret = request_irq(gpio_irq, gpio_irq_handler, IRQF_TRIGGER_FALLING, "gpio irq handler", gpio_irq_handler);<br />
if (ret)<br />
printk("gpio interrupt request failed\n");<br />
else<br />
printk("gpio interrupt request succeeded\n");<br />
<br />
=== GPIO Software for the Overo ===<br />
<br />
Dave Hylands has written several software packages to facilitate GPIO programming on the Overos.<br />
<br />
[[GPIO Event Driver]] allows multiple GPIO lines to be monitored from user-space.<br />
<br />
[[User GPIO Driver]] is a reflection of the kernel's gpiolib API into user space.<br />
<br />
=== More Links ===<br />
<br />
Here is another article [http://elinux.org/BeagleBoardPinMux BeagleBoardPinMux] talking about OMAP3 pin muxing.<br />
<br />
== Verdex GPIO ==<br />
{| border="1" cellpadding="5" cellspacing="0" style="width:100px"<br />
| style="background:yellow;" | GPIO(<i> n </i>)<br />
|}<br />
<br />
<br />
* Logic level (3.3V) signals <br />
* 3-4mA max<br />
<br />
<br />
all GPIO's information and examples should go here<br />
<br />
<br />
todo<br />
<br />
<br />
According to the PXA270 datasheet:<br />
http://pubs.gumstix.com/documents/PXA%20Documentation/PXA270/PXA270%20Electrical,%20Mechanical,%20and%20Thermal%20Specification%20%5b280002-005%5d.pdf<br />
most of the pins are limited to 3mA, and a few can go upto 4 mA (see page 5-9) <br />
<br />
<br><br />
<br><br />
<br />
<br />
=== Accessing GPIO's from userland ===<br />
<br />
<br />
If proc-gpio is a module, add it to /etc/modules or do a modprobe proc-gpio.<br />
<br />
A number of files exist under /proc/gpio, one for each GPIO on the PXA processor.<br />
<br />
If you cat one of these files, you get, eg:<br />
<pre><br />
# cat /proc/gpio/GPIO12<br />
12 GPIO in set<br />
</pre><br />
<br />
That tells you — GPIO number, function (either GPIO, AF 1, AF 2, or AF 3), in|out, set|clear.<br />
<br />
You can change any of those values, by writing to the file, eg:<br />
<pre><br />
# echo "AF1 out" > /proc/gpio/GPIO12<br />
</pre><br />
<br />
This sets GPIO12 to AF1, out mode. (In the case of GPIO12, the PXA defines this function as putting out the 32kHz clock signal.) this is currently case-sensitive<br />
<br />
If you have the GPIO set to an output, and GPIO mode, you can set or clear the signal:<br />
<pre><br />
# echo "GPIO out set" > /proc/gpio/GPIO12<br />
# echo "GPIO out clear" > /proc/gpio/GPIO12<br />
</pre><br />
The alternative functions are described in the PXA255 Developer's Manual (link should be found in the Featured links-box) section 4.1.2.<br />
<br />
=== Alternative method to access GPIO's from userland ===<br />
<br />
The [[User GPIO Driver]] provides a reflection of the kernel's gpiolib library into userspace.<br />
<br />
=== gpio-event driver ===<br />
<br />
The [[GPIO Event Driver]] allows gpio changes to be captured from user-space.<br />
<br />
<br><br />
<br><br />
<br><br />
-----------------------------<br />
<br />
Related pages on the old wiki:<br />
<br />
http://docwiki.gumstix.org/index.php/Tips_and_tricks#Access_GPIOs_from_user-space<br />
<br />
http://docwiki.gumstix.org/index.php/Sample_code/C/gpregs<br />
<br />
http://docwiki.gumstix.org/index.php/Kernel_programming<br />
<br />
.<br />
[[Category:Literature]]<br />
[[Category:GPIO]]</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Kernel_Build&diff=5811Kernel Build2012-04-11T07:48:28Z<p>Dan Nelson: </p>
<hr />
<div>11 April 2012<br />
<br />
This wiki entry explains how to build the Gumstix Linux kernel from source.<br />
<br />
Start by installing the [http://wiki.gumstix.org/index.php?title=Toolchain toolchain].<br />
<br />
You will also need the U-boot 'mkimage' utility. Debian and Ubuntu users can install it from their respective repositories. It's also compiled when U-boot is built if you can't get it otherwise. On top of that you will need 'git' and 'make'.<br />
$ sudo apt-get install uboot-mkimage git make<br />
<br />
Next we need to get the patched kernel source that's available at www.sakoman.com.<br />
You can browse Sakoman's git repository [http://www.sakoman.com/cgi-bin/gitweb.cgi?p=linux-omap-2.6.git;a=summary here].<br />
<br />
Decide where you want your kernel source to go an move to that directory. Then use git to download it.<br />
$ git clone git://www.sakoman.com/git/linux-omap-2.6 linux -b omap-3.2<br />
<br />
The above command pulls down the omap-3.2 branch. The omap-2.6.38 branch has proved stable for those who want to use Xenomai. Once the above process is complete move into the new directory. The first thing to do is to create a .config file.<br />
$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap2plus_defconfig (or maybe omap3_defconfig)<br />
<br />
If you need to configure the kernel:<br />
$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- menuconfig<br />
<br />
And now for the main kernel build.<br />
$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage -j4<br />
<br />
When the above completes, uImage can be found in arch/arm/boot/<br />
<br />
Build the kernel modules.<br />
$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules -j4<br />
<br />
To install your kernel modules into your root file system:<br />
$ make ARCH=arm modules_install INSTALL_MOD_PATH=/path-to-your-rootfs/</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Toolchain&diff=5810Toolchain2012-04-11T07:39:01Z<p>Dan Nelson: </p>
<hr />
<div>If you use Open Embedded you will find the toolchain in /path-to-overo-oe/tmp/sysroots/i686-linux/usr/armv7a.<br />
<br />
If you want the toolchain on its own without the weight of Open Embedded there are several options.<br />
<br />
Ubuntu:<br />
<br />
The toolchain is already in the Ubuntu 11.04 repository.<br />
$ sudo apt-get install gcc-arm-linux-gnueabi<br />
<br />
Debian:<br />
<br />
Emdebian provide the toolchain in their Debian repository. Add the following line to your sources.list file.<br />
deb http://www.emdebian.org/debian/ squeeze main<br />
<br />
Don't forget to update before the install.<br />
$ apt-get update<br />
$ apt-get install gcc-4.4-arm-linux-gnueabi<br />
<br />
g++ is available as well.<br />
$ apt-get install gobjc++-4.4-arm-linux-gnueabi<br />
<br />
Binaries and source:<br />
<br />
[https://launchpad.net/linaro-toolchain-binaries Linaro Toolchain Binaries]<br />
<br />
[https://launchpadlibrarian.net/98590974/README.txt Linaro README]<br />
<br />
[https://launchpad.net/gcc-arm-embedded GNU Tools for ARM Embedded Processors]</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Toolchain&diff=5809Toolchain2012-04-11T07:38:13Z<p>Dan Nelson: </p>
<hr />
<div>If you use Open Embedded you will find the toolchain in /path-to-overo-oe/tmp/sysroots/i686-linux/usr/armv7a.<br />
<br />
If you want the toolchain on its own without the weight of Open Embedded there are several options.<br />
<br />
Ubuntu:<br />
<br />
The toolchain is already in the Ubuntu 11.04 repository.<br />
$ sudo apt-get install gcc-arm-linux-gnueabi<br />
<br />
Debian:<br />
<br />
Emdebian provide the toolchain in their Debian repository. Add the following line to your sources.list file.<br />
deb http://www.emdebian.org/debian/ squeeze main<br />
<br />
Don't forget to update before the install.<br />
$ sudo apt-get update<br />
$ sudo apt-get install gcc-4.4-arm-linux-gnueabi<br />
<br />
g++ is available as well.<br />
$ sudo apt-get install gobjc++-4.4-arm-linux-gnueabi<br />
<br />
Binaries and source:<br />
<br />
[https://launchpad.net/linaro-toolchain-binaries Linaro Toolchain Binaries]<br />
<br />
[https://launchpadlibrarian.net/98590974/README.txt Linaro README]<br />
<br />
[https://launchpad.net/gcc-arm-embedded GNU Tools for ARM Embedded Processors]</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Kernel_Build&diff=5808Kernel Build2012-04-11T07:34:23Z<p>Dan Nelson: Created page with "11 April 2012 This wiki entry explains how to build the Gumstix Linux kernel from source. Start by installing the [http://wiki.gumstix.org/index.php?title=Toolchain toolchain]...."</p>
<hr />
<div>11 April 2012<br />
<br />
This wiki entry explains how to build the Gumstix Linux kernel from source.<br />
<br />
Start by installing the [http://wiki.gumstix.org/index.php?title=Toolchain toolchain].<br />
<br />
You will also need the U-boot 'mkimage' utility. Debian and Ubuntu users can install it from their respective repositories. It's also compiled when U-boot is built if you can't get it otherwise. On top of that you will need 'git' and 'make'.<br />
$ sudo apt-get install uboot-mkimage git make<br />
<br />
Next we need to get the patched kernel source that's available at www.sakoman.com.<br />
You can browse Sakoman's git repository [http://www.sakoman.com/cgi-bin/gitweb.cgi?p=linux-omap-2.6.git;a=summary here].<br />
<br />
Decide where you want your kernel source to go an move to that directory. Then use git to download it.<br />
$ git clone git://www.sakoman.com/git/linux-omap-2.6 linux -b omap-3.2<br />
<br />
The above command pulls down the omap-3.2 branch. The omap-2.6.38 branch has proved stable for those who want to use Xenomai. Once the above process is complete move into the new directory. The first thing to do is to create a .config file.<br />
$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- omap3_defconfig (or maybe omap2plus_defconfig)<br />
<br />
If you need to configure the kernel:<br />
$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- menuconfig<br />
<br />
And now for the main kernel build.<br />
$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage -j4<br />
<br />
When the above completes, uImage can be found in arch/arm/boot/<br />
<br />
Build the kernel modules.<br />
$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- modules -j4<br />
<br />
To install your kernel modules into your root file system:<br />
$ make ARCH=arm modules_install INSTALL_MOD_PATH=/path-to-your-rootfs/</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Main_Page&diff=5807Main Page2012-04-11T06:38:45Z<p>Dan Nelson: </p>
<hr />
<div><big>''Welcome to the Gumstix User Wiki''</big> <br />
<br />
This site is provided so that users of the Gumstix OpenEmbedded build system can share their knowledge, showcase their Gumstix-based projects, and pass on links to other sources of information and materials. This information is entirely user generated and supported. Please contribute your know-how to help your fellow developers.<br />
<br />
'''Customer additions and edits are encouraged, but please read the help page before you make any major edits.'''<br />
''Note: you will need to create a new user account if you would like to contribute or edit content on this site.''<br />
<br />
Go to the [http://gumstix.org Gumstix Developer's website] for official Gumstix supported documentation on OpenEmbedded and other information of interest to developers:<br />
<br />
{|<br />
| valign="top" |<br />
{|cellpadding="2" cellspacing="5" style="vertical-align:top;background-color:#f5fffa;border:1px solid #bcc"<br />
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:How-tos |User how to's - Focus]]<br />
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:How-tos |User how to's]]<br />
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:How-tos |User how to's]]<br />
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:How-tos |User how to's]]<br />
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:How-tos |User how to's]]<br />
<br />
|-<br />
| valign="top" |<br />
* [[:Category:how to - Android|Android]]<br />
* [[:Category:how to - eclipse|Eclipse]]<br />
* [[:Category:How_to_-_Migrate_to_Gumstix|Migrate to Gumstix]]<br />
* [[Linaro]]<br />
* [[:Category:how to - Ubuntu|Ubuntu]]<br />
* [[:Category:how to - Debian|Debian]]<br />
| valign="top" |<br />
* [[1-wire|1-wire]]<br />
* [[:Category:how to - audio|Audio]]<br />
* [[:Category:how to - adc|ADC]]<br />
* [[AutoLogin|Automatic Logins]]<br />
* [[:Category:how to - batteries|Batteries]]<br />
* [[:Category:how to - bluetooth|Bluetooth]]<br />
* [[:Category:how to - Buildroot overo|Buildroot (overo)]]<br />
* [[:Category:Connect_hardware|Connect Hardware]]<br />
* [[Caspa_camera_boards|Caspa camera boards]]<br />
* [[:Category:how to - displays|Displays]]<br />
* [[:Category:how to - DSP|DSP]]<br />
* [[:Category:how_to_-_ethernet|Ethernet]]<br />
* [[:Category:how_to_-_expansion_boards|Expansion Boards]]<br />
* [[:Category:how to - fedora|Fedora]]<br />
* [[:Category:how to - Fast Boot|Fast Boot]]<br />
* [[:Category:how to - Fortran|Fortran]]<br />
<br />
<br />
| valign="top" |<br />
* [[Gaining Console Connection via Terminal]]<br />
* [[:Category:how to - git|Git]]<br />
* [[GPIO|GPIO]]<br />
* [[GPS|GPS]]<br />
* [[:Category:how to - gui|GUI]]<br />
* [[:Category:how to - general|General]]<br />
* [[:Category:how to - Build helloworld|HelloWorld]]<br />
* [[HelloWorld|HelloWorld in Python, C, C++]]<br />
* [[HelloWorld in Java|HelloWorld in Java]]<br />
* [[:Category:how to - i2c|I2C]]<br />
* [[:Category:how to - IMU|IMU]]<br />
* [[:Category:how to - JAVA|JAVA]]<br />
* [[Kernel Build]]<br />
* [[Kernel Reconfiguration|Kernel Reconfiguration]]<br />
* [[:Category:how to - Known Issues|Known Issues]]<br />
* [[:Category:how to - LCD|LCD]]<br />
* [[:Category:how to - Low Power|Low Power]]<br />
| valign="top" |<br />
* [[:Category:how to - linux|Linux]]<br />
* [[AudioIn | Use a microphone]]<br />
* [[MicroSd |MicroSD Duplication]]<br />
* [[:Category:how to - Network_Boot|Network Boot]]<br />
* [[:Category:how to - OpenEmbedded|OpenEmbedded]]<br />
* [[:Category:how to - player|Player]]<br />
* [[:Category:How to - PWM|PWM]]<br />
* [[:Category:How_to_-_qemu|Qemu]]<br />
* [[:Category:How_to_-_Qt|Qt]]<br />
* [[:Category:how to - robotics|Robotics]]<br />
* [[ROS|ROS]]<br />
* [[RoboVero|RoboVero]]<br />
* [[:Category:how to - security|Security]]<br />
* [[:Category:SPI|SPI]]<br />
| valign="top" |<br />
* [[:Category:SUSE|SUSE]]<br />
* [[Remote Debugging with GDB|Remote Debugging with GDB]]<br />
* [[Toolchain]]<br />
* [[U-Boot|UBoot]]<br />
* [[:Category:how to - usb|USB]]<br />
* [[Verdex Git Repository]]<br />
* [[Verdex JTAG]]<br />
* [[VerdexPro U-Boot Flashing Fix]]<br />
* [[:Category:how to - virtual machine|Virtual Machine]]<br />
* [[:Category:how to - webcams|Webcams]]<br />
* [[:Category:how to - wifi|Wifi]]<br />
<br />
|}<br />
<br />
<br />
{|<br />
| valign="top" |<br />
{|cellpadding="2" cellspacing="5" style="vertical-align:top;background-color:#f5fffa;border:1px solid #bcc"<br />
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:projects|User projects]]<br />
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:User_pics_videos|User Pics & Videos]]<br />
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:resources|Resources]]<br />
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:faqs|Questions and Answers]]<br />
<br />
|-<br />
| valign="top" |<br />
* [[:Category:projects - audio|Audio]]<br />
* [[:Category:projects - competitions|Competitions]]<br />
* [[:Category:projects - displays|Displays]]<br />
* [[:Category:projects - pdas|PDA's]]<br />
* [[:Category:Projects_-Research_and_Education|Research & Education]]<br />
* [[:Category:projects - monitoring and control|Monitoring and Control]]<br />
* [[:Category:projects - robotics|Robotics & UAV's]]<br />
| valign="top" |<br />
* [http://www.youtube.com/results?uploaded=m&search_query=gumstix&search_type=videos&suggested_categories=28&uni=3&search_sort=video_date_uploaded Gumstix on Youtube]<br />
* [http://www.flickr.com/search/?q=gumstix&s=rec Gumstix in Flickr]<br />
* [http://www.cs.umd.edu/alandaluz/nchen/ebook/dualdisp-chi.mov Dual Display device at UMD]<br />
| valign="top" |<br />
* [[Windows CE solution|Solutions for Windows CE]]<br />
* [[Qt solution|Solutions for Qt]]<br />
* [[Manufacturer's specifications|Specifications for Processors & Components]]<br />
* [[Software information]]<br />
* [[Supported hardware]]<br />
* [[Third Party Boards]]<br />
| valign="top" |<br />
Gumstix Community Mailing List (no cost)<br />
* [https://lists.sourceforge.net/lists/listinfo/gumstix-users Sign-up]<br />
* [http://old.nabble.com/Gumstix-f22543.html Archives]<br />
|}<br />
<br />
<br />
<br />
<br />
For information and support for the legacy gumstix buildroot build system:<br />
[http://docwiki.gumstix.com/Main_Page docwiki.gumstix.com]<br />
.</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Toolchain&diff=5806Toolchain2012-04-11T02:15:35Z<p>Dan Nelson: Created page with "If you use Open Embedded you will find the toolchain in /path-to-overo-oe/tmp/sysroots/i686-linux/usr/armv7a. If you want the toolchain on its own without the weight of Open Emb..."</p>
<hr />
<div>If you use Open Embedded you will find the toolchain in /path-to-overo-oe/tmp/sysroots/i686-linux/usr/armv7a.<br />
<br />
If you want the toolchain on its own without the weight of Open Embedded there are several options.<br />
<br />
Ubuntu:<br />
<br />
The toolchain is already in the Ubuntu 11.04 repository.<br />
$ sudo apt-get install gcc-arm-linux-gnueabi<br />
<br />
Debian:<br />
<br />
Emdebian provide the toolchain in their Debian repository. Add the following line to your sources.list file.<br />
deb http://www.emdebian.org/debian/ squeeze main<br />
<br />
Don't forget to update before the install.<br />
$ apt-get update<br />
$ apt-get install gcc-4.4-arm-linux-gnueabi<br />
<br />
g++ is available as well.<br />
$ apt-get install gobjc++-4.4-arm-linux-gnueabi<br />
<br />
Binaries and source:<br />
<br />
[https://launchpad.net/linaro-toolchain-binaries Linaro Toolchain Binaries]<br />
<br />
[https://launchpadlibrarian.net/98590974/README.txt Linaro README]<br />
<br />
[https://launchpad.net/gcc-arm-embedded GNU Tools for ARM Embedded Processors]</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Main_Page&diff=5805Main Page2012-04-11T01:36:54Z<p>Dan Nelson: </p>
<hr />
<div><big>''Welcome to the Gumstix User Wiki''</big> <br />
<br />
This site is provided so that users of the Gumstix OpenEmbedded build system can share their knowledge, showcase their Gumstix-based projects, and pass on links to other sources of information and materials. This information is entirely user generated and supported. Please contribute your know-how to help your fellow developers.<br />
<br />
'''Customer additions and edits are encouraged, but please read the help page before you make any major edits.'''<br />
''Note: you will need to create a new user account if you would like to contribute or edit content on this site.''<br />
<br />
Go to the [http://gumstix.org Gumstix Developer's website] for official Gumstix supported documentation on OpenEmbedded and other information of interest to developers:<br />
<br />
{|<br />
| valign="top" |<br />
{|cellpadding="2" cellspacing="5" style="vertical-align:top;background-color:#f5fffa;border:1px solid #bcc"<br />
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:How-tos |User how to's - Focus]]<br />
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:How-tos |User how to's]]<br />
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:How-tos |User how to's]]<br />
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:How-tos |User how to's]]<br />
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:How-tos |User how to's]]<br />
<br />
|-<br />
| valign="top" |<br />
* [[:Category:how to - Android|Android]]<br />
* [[:Category:how to - eclipse|Eclipse]]<br />
* [[:Category:How_to_-_Migrate_to_Gumstix|Migrate to Gumstix]]<br />
* [[Linaro]]<br />
* [[:Category:how to - Ubuntu|Ubuntu]]<br />
* [[:Category:how to - Debian|Debian]]<br />
| valign="top" |<br />
* [[1-wire|1-wire]]<br />
* [[:Category:how to - audio|Audio]]<br />
* [[:Category:how to - adc|ADC]]<br />
* [[AutoLogin|Automatic Logins]]<br />
* [[:Category:how to - batteries|Batteries]]<br />
* [[:Category:how to - bluetooth|Bluetooth]]<br />
* [[:Category:how to - Buildroot overo|Buildroot (overo)]]<br />
* [[:Category:Connect_hardware|Connect Hardware]]<br />
* [[Caspa_camera_boards|Caspa camera boards]]<br />
* [[:Category:how to - displays|Displays]]<br />
* [[:Category:how to - DSP|DSP]]<br />
* [[:Category:how_to_-_ethernet|Ethernet]]<br />
* [[:Category:how_to_-_expansion_boards|Expansion Boards]]<br />
* [[:Category:how to - fedora|Fedora]]<br />
* [[:Category:how to - Fast Boot|Fast Boot]]<br />
* [[:Category:how to - Fortran|Fortran]]<br />
<br />
<br />
| valign="top" |<br />
* [[Gaining Console Connection via Terminal]]<br />
* [[:Category:how to - git|Git]]<br />
* [[GPIO|GPIO]]<br />
* [[GPS|GPS]]<br />
* [[:Category:how to - gui|GUI]]<br />
* [[:Category:how to - general|General]]<br />
* [[:Category:how to - Build helloworld|HelloWorld]]<br />
* [[HelloWorld|HelloWorld in Python, C, C++]]<br />
* [[HelloWorld in Java|HelloWorld in Java]]<br />
* [[:Category:how to - i2c|I2C]]<br />
* [[:Category:how to - IMU|IMU]]<br />
* [[:Category:how to - JAVA|JAVA]]<br />
* [[Kernel Reconfiguration|Kernel Reconfiguration]]<br />
* [[:Category:how to - Known Issues|Known Issues]]<br />
* [[:Category:how to - LCD|LCD]]<br />
* [[:Category:how to - Low Power|Low Power]]<br />
| valign="top" |<br />
* [[:Category:how to - linux|Linux]]<br />
* [[AudioIn | Use a microphone]]<br />
* [[MicroSd |MicroSD Duplication]]<br />
* [[:Category:how to - Network_Boot|Network Boot]]<br />
* [[:Category:how to - OpenEmbedded|OpenEmbedded]]<br />
* [[:Category:how to - player|Player]]<br />
* [[:Category:How to - PWM|PWM]]<br />
* [[:Category:How_to_-_qemu|Qemu]]<br />
* [[:Category:How_to_-_Qt|Qt]]<br />
* [[:Category:how to - robotics|Robotics]]<br />
* [[ROS|ROS]]<br />
* [[RoboVero|RoboVero]]<br />
* [[:Category:how to - security|Security]]<br />
* [[:Category:SPI|SPI]]<br />
| valign="top" |<br />
* [[:Category:SUSE|SUSE]]<br />
* [[Remote Debugging with GDB|Remote Debugging with GDB]]<br />
* [[Toolchain]]<br />
* [[U-Boot|UBoot]]<br />
* [[:Category:how to - usb|USB]]<br />
* [[Verdex Git Repository]]<br />
* [[Verdex JTAG]]<br />
* [[VerdexPro U-Boot Flashing Fix]]<br />
* [[:Category:how to - virtual machine|Virtual Machine]]<br />
* [[:Category:how to - webcams|Webcams]]<br />
* [[:Category:how to - wifi|Wifi]]<br />
<br />
|}<br />
<br />
<br />
{|<br />
| valign="top" |<br />
{|cellpadding="2" cellspacing="5" style="vertical-align:top;background-color:#f5fffa;border:1px solid #bcc"<br />
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:projects|User projects]]<br />
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:User_pics_videos|User Pics & Videos]]<br />
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:resources|Resources]]<br />
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:faqs|Questions and Answers]]<br />
<br />
|-<br />
| valign="top" |<br />
* [[:Category:projects - audio|Audio]]<br />
* [[:Category:projects - competitions|Competitions]]<br />
* [[:Category:projects - displays|Displays]]<br />
* [[:Category:projects - pdas|PDA's]]<br />
* [[:Category:Projects_-Research_and_Education|Research & Education]]<br />
* [[:Category:projects - monitoring and control|Monitoring and Control]]<br />
* [[:Category:projects - robotics|Robotics & UAV's]]<br />
| valign="top" |<br />
* [http://www.youtube.com/results?uploaded=m&search_query=gumstix&search_type=videos&suggested_categories=28&uni=3&search_sort=video_date_uploaded Gumstix on Youtube]<br />
* [http://www.flickr.com/search/?q=gumstix&s=rec Gumstix in Flickr]<br />
* [http://www.cs.umd.edu/alandaluz/nchen/ebook/dualdisp-chi.mov Dual Display device at UMD]<br />
| valign="top" |<br />
* [[Windows CE solution|Solutions for Windows CE]]<br />
* [[Qt solution|Solutions for Qt]]<br />
* [[Manufacturer's specifications|Specifications for Processors & Components]]<br />
* [[Software information]]<br />
* [[Supported hardware]]<br />
* [[Third Party Boards]]<br />
| valign="top" |<br />
Gumstix Community Mailing List (no cost)<br />
* [https://lists.sourceforge.net/lists/listinfo/gumstix-users Sign-up]<br />
* [http://old.nabble.com/Gumstix-f22543.html Archives]<br />
|}<br />
<br />
<br />
<br />
<br />
For information and support for the legacy gumstix buildroot build system:<br />
[http://docwiki.gumstix.com/Main_Page docwiki.gumstix.com]<br />
.</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Debian_Root_File_System&diff=5784Debian Root File System2012-03-08T07:33:30Z<p>Dan Nelson: </p>
<hr />
<div>Embedded Linux has always been constrained by available memory, cut-down distributions such as Angstrom and EmDebian have addressed those constraints. Debian is a stable, full featured distribution that has a very large repository of packages. With the generous amount of memory available on a micro SD card there's no reason not to use it.<br />
<br />
This how-to describes the procedure to build a Debian root file system for a micro SD card. Gumstix's how-to on creating a bootable micro SD card can be found [http://gumstix.org/create-a-bootable-microsd-card.html here]. We'll follow the same procedure but will substitute our Debian root file system for the Gumstix Angstrom one.<br />
<br />
Start by creating some working directories in some place convenient:<br />
<br />
$ mkdir images<br />
$ mkdir debian<br />
<br />
Now Download some required images from the [http://cumulus.gumstix.org/images/angstrom/developer/ Gumstix repository]. This includes the bootloaders MLO and u-boot.bin. We also need uImage, the Linux kernel. Put them in the 'images' directory. <br />
<br />
On top of that we need the Angstrom file system. There are several to chose from, don't use any with 'nand' in the name. The one you want will be called something like, omap3-console-image-overo.tar.bz2. We'll pilfer the kernel modules from this tarball along with some important configuration files. We can, or course, build our own kernel and modules, but this way will prove to be quick and easy.<br />
<br />
Create a directory to extract the downloaded file system and then untar it.<br />
$ cd /your-path-to/images<br />
$ mkdir angstrom<br />
$ cd angstrom<br />
$ tar xjvf ../omap3-console-image-overo.tar.bz2<br />
<br />
Leave this for now, we'll get back to it later.<br />
<br />
$ cd ../../debian<br />
<br />
The Debian root file system is built with 'debootstrap'. Install it onto your host machine with apt-get, along with 'qemu-arm-static' (qemu-user-static on Debian):<br />
<br />
$ sudo apt-get install debootstrap qemu-arm-static<br />
<br />
Once these are installed run the following:<br />
<br />
$ sudo debootstrap --foreign --verbose --arch=armel --include=vim-nox,openssh-server,ntpdate,less --exclude=nano squeeze ./squeeze http://ftp.au.debian.org/debian<br />
<br />
The --include and --exclude packages are optional. I prefer vim to the standard vim-tiny, vim-nox is the non-gui version. I don't use nano so I've excluded it from the build. The above command will download the packages required to create a basic squeeze root file system in a directory called squeeze. You can use a closer Debian mirror rather than the one that I've used in the above example.<br />
<br />
Now we chroot into our newly created file system to finish off. But the packages in the new file system are for the arm architecture so we need an emulator. We installed it earlier, copy the relevant file:<br />
<br />
$ cp /usr/bin/qemu-arm-static squeeze/usr/bin<br />
<br />
Now chroot into our new file system:<br />
<br />
$ sudo chroot squeeze<br />
<br />
Chroot has trapped us in our new root file system, isolating us from the file system of the host computer. You will see a directory named debootstrap. Go to it:<br />
<br />
$ cd debootstrap<br />
<br />
Finish off the installation:<br />
<br />
$ ./debootstap --second-stage<br />
<br />
The above command will install all the Debian packages into our file system.<br />
<br />
We now need to create a password for the root user or we'll have a system that we can't log into:<br />
<br />
$ passwd<br />
<br />
Delete the .deb packages now that we've installed them:<br />
<br />
$ apt-get clean<br />
<br />
With that done we can exit:<br />
<br />
$ exit<br />
<br />
Our root file system needs kernel modules. You'll find a directory under /your-path-to/images/angstrom/lib/modules with a name that reflects the kernel version. In this example it's '3.0.0'. Copy the whole directory to the new Debian file system:<br />
<br />
$ sudo cp -r ../images/angstrom/lib/modules/3.0.0/ squeeze/lib/modules/<br />
<br />
We also need the fstab and inittab configuration files from Angstrom:<br />
<br />
$ sudo cp ../images/angstrom/etc/inittab squeeze/etc<br />
$ sudo cp ../images/angstrom/etc/fstab squeeze/etc<br />
<br />
If fstab is wrong then our new Debian system won't boot properly.<br />
<br />
If inittab is wrong then we won't get a console login prompt, we'll get an error along the lines of "init: Id 'x' respawning too fast: disabled for 5 minutes".<br />
<br />
You can also copy the interfaces file:<br />
<br />
$ sudo cp ../images/angstrom/etc/network/interfaces squeeze/etc/network/<br />
<br />
Edit the newly copied file and change eth0 to eth1.<br />
<br />
Now go to the root directory of your Debian file system:<br />
<br />
$ cd squeeze<br />
<br />
And tar it up:<br />
<br />
$ sudo tar -cjvf ../squeeze.tar.bz2 *<br />
<br />
Create a bootable micro SD card following the Gumstix tutorial found [http://gumstix.org/create-a-bootable-microsd-card.html here], but use the above squeeze.tar.bz2 in place of roofs.tar.bz2.<br />
<br />
You now have a bootable Debian micro SD card. Put it in your Gumstix COM and boot it up. If all goes well you should get a logon prompt at the console.<br />
<br />
There are still a couple of things left to do. The kernel module dependencies need to be set up. On your new Debian install go to the modules directory:<br />
<br />
$ cd /lib/modules/3.0.0<br />
$ depmod<br />
<br />
The above command will build the modules dependencies files. When you reboot, the kernel will find its modules and use them.<br />
<br />
If you have wifi on your COM you'll have to install some more software. But first we need to put something in /etc/apt/sources.list.<br />
<br />
$ vi /etc/apt/sources.list<br />
<br />
Put in something like the following, replace with your closest mirror. Make sure you include the 'non-free' repositories:<br />
<br />
deb http://ftp.iinet.net.au/debian/debian squeeze main non-free<br />
<br />
$ apt-get update<br />
<br />
Install wifi packages.<br />
<br />
$ apt-get install wireless-tools libertas-firmware<br />
<br />
There's a wifi howto at the Gumstix wiki [http://wiki.gumstix.org/index.php?title=Overo_Wifi here].<br />
<br />
I like to edit the vimrc configuration file and un-comment the lines to enable syntax highlighting and mouse. It's at /etc/vim/vimrc.<br />
<br />
You might also want to edit /etc/hostname.</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Debian_Root_File_System&diff=5783Debian Root File System2012-03-08T07:28:37Z<p>Dan Nelson: </p>
<hr />
<div>Embedded Linux has always been constrained by available memory, cut-down distributions such as Angstrom and EmDebian have addressed those constraints. Debian is a stable, full featured distribution that has a very large repository of packages. With the generous amount of memory available on a micro SD card there's no reason not to use it.<br />
<br />
This how-to describes the procedure to build a Debian root file system for a micro SD card. Gumstix's how-to on creating a bootable micro SD card can be found [http://gumstix.org/create-a-bootable-microsd-card.html here]. We'll follow the same procedure but will substitute our Debian root file system for the Gumstix Angstrom one.<br />
<br />
Start by creating some working directories in some place convenient:<br />
<br />
$ mkdir images<br />
$ mkdir debian<br />
<br />
Now Download some required images from the [http://cumulus.gumstix.org/images/angstrom/developer/ Gumstix repository]. This includes the bootloaders MLO and u-boot.bin. We also need uImage, the Linux kernel. Put them in the 'images' directory. <br />
<br />
On top of that we need the Angstrom file system. There are several to chose from, don't use any with 'nand' in the name. The one you want will be called something like, omap3-console-image-overo.tar.bz2. We'll pilfer the kernel modules from this tarball along with some important configuration files. We can, or course, build our own kernel and modules, but this way will prove to be quick and easy.<br />
<br />
Create a directory to extract the downloaded file system and then untar it.<br />
$ cd /your-path-to/images<br />
$ mkdir angstrom<br />
$ cd angstrom<br />
$ tar xjvf ../omap3-console-image-overo.tar.bz2<br />
<br />
Leave this for now, we'll get back to it later.<br />
<br />
$ cd ../../debian<br />
<br />
The Debian root file system is built with 'debootstrap'. Install it onto your host machine with apt-get, along with 'qemu-arm-static' (qemu-user-static on Debian):<br />
<br />
$ sudo apt-get install debootstrap qemu-arm-static<br />
<br />
Once these are installed run the following:<br />
<br />
$ sudo debootstrap --foreign --verbose --arch=armel --include=vim-nox,openssh-server,ntpdate,less --exclude=nano squeeze ./squeeze http://ftp.au.debian.org/debian<br />
<br />
The --include and --exclude packages are optional. I prefer vim to the standard vim-tiny, vim-nox is the non-gui version. I don't use nano so I've excluded it from the build. The above command will download the packages required to create a basic squeeze root file system in a directory called squeeze. You can use a closer Debian mirror rather than the one that I've used in the above example.<br />
<br />
Now we chroot into our newly created file system to finish off. But the packages in the new file system are for the arm architecture so we need an emulator. We installed it earlier, copy the relevant file:<br />
<br />
$ cp /usr/bin/qemu-arm-static squeeze/usr/bin<br />
<br />
Now chroot into our new file system:<br />
<br />
$ sudo chroot squeeze<br />
<br />
Chroot has trapped us in our new root file system, isolating us from the file system of the host computer. You will see a directory named debootstrap. Go to it:<br />
<br />
$ cd debootstrap<br />
<br />
Finish off the installation:<br />
<br />
$ ./debootstap --second-stage<br />
<br />
The above command will install all the Debian packages into our file system.<br />
<br />
We now need to create a password for the root user or we'll have a system that we can't log into:<br />
<br />
$ passwd<br />
<br />
Delete the .deb packages now that we've installed them:<br />
<br />
$ apt-get clean<br />
<br />
With that done we can exit:<br />
<br />
$ exit<br />
<br />
Our root file system needs kernel modules. You'll find a directory under /your-path-to/images/angstrom/lib/modules with a name that reflects the kernel version. In this example it's '3.0.0'. Copy the whole directory to the new Debian file system:<br />
<br />
$ sudo cp -r ../images/angstrom/lib/modules/3.0.0/ squeeze/lib/modules/<br />
<br />
We also need the fstab and inittab configuration files from Angstrom:<br />
<br />
$ sudo cp ../images/angstrom/etc/inittab squeeze/etc<br />
$ sudo cp ../images/angstrom/etc/fstab squeeze/etc<br />
<br />
If fstab is wrong then our new Debian system won't boot properly.<br />
<br />
If inittab is wrong then we won't get a console login prompt, we'll get an error along the lines of "init: Id 'x' respawning too fast: disabled for 5 minutes".<br />
<br />
You can also copy the interfaces file:<br />
<br />
$ sudo cp ../images/angstrom/etc/network/interfaces squeeze/etc/network/<br />
<br />
Edit the newly copied file and change eth0 to eth1.<br />
<br />
Now go to the root directory of your Debian file system:<br />
<br />
$ cd squeeze<br />
<br />
And tar it up:<br />
<br />
$ sudo tar -cjvf ../squeeze.tar.bz2 *<br />
<br />
Create a bootable micro SD card following the Gumstix tutorial found [http://gumstix.org/create-a-bootable-microsd-card.html here], but use the above squeeze.tar.bz2 in place of roofs.tar.bz2.<br />
<br />
Put the SD card in your Gumstix COM and boot it up. If all goes well you should get a logon prompt at the console.<br />
<br />
There are still a couple of things left to do. The kernel module dependencies need to be set up. On your new Debian install go to the modules directory:<br />
<br />
$ cd /lib/modules/3.0.0<br />
$ depmod<br />
<br />
The above command will build the modules dependencies files. When you reboot, the kernel will find its modules and use them.<br />
<br />
If you have wifi on your COM you'll have to install some more software. But first we need to put something in /etc/apt/sources.list.<br />
<br />
$ vi /etc/apt/sources.list<br />
<br />
Put in something like the following, replace with your closest mirror. Make sure you include the 'non-free' repositories:<br />
<br />
deb http://ftp.iinet.net.au/debian/debian squeeze main non-free<br />
<br />
$ apt-get update<br />
<br />
Install wifi packages.<br />
<br />
$ apt-get install wireless-tools libertas-firmware<br />
<br />
There's a wifi howto at the Gumstix wiki [http://wiki.gumstix.org/index.php?title=Overo_Wifi here].<br />
<br />
I like to edit the vimrc configuration file and un-comment the lines to enable syntax highlighting and mouse. It's at /etc/vim/vimrc.<br />
<br />
You might also want to edit /etc/hostname.</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Debian_Root_File_System&diff=5782Debian Root File System2012-03-08T07:25:32Z<p>Dan Nelson: </p>
<hr />
<div>Embedded Linux has always been constrained by available memory, cut-down distributions such as Angstrom and EmDebian have addressed those constraints. Debian is a stable, full featured distribution that has a very large repository of packages. With the generous amount of memory available on a micro SD card there's no reason not to use it.<br />
<br />
This how-to describes the procedure to build a Debian root file system for a micro SD card. Gumstix's how-to on creating a bootable micro SD card can be found [http://gumstix.org/create-a-bootable-microsd-card.html here]. We'll follow the same procedure but will substitute our Debian root file system for the Gumstix Angstrom one.<br />
<br />
Start by creating some working directories in some place convenient:<br />
<br />
$ mkdir images<br />
$ mkdir debian<br />
<br />
Now Download some required images from the [http://cumulus.gumstix.org/images/angstrom/developer/ Gumstix repository]. This includes the bootloaders MLO and u-boot.bin. We also need uImage, the Linux kernel. Put them in the 'images' directory. <br />
<br />
On top of that we need the Angstrom file system. There are several to chose from, don't use any with 'nand' in the name. The one you want will be called something like, omap3-console-image-overo.tar.bz2. We'll pilfer the kernel modules from this tarball along with some important configuration files. We can, or course, build our own kernel and modules, but this way will prove to be quick and easy.<br />
<br />
Create a directory to extract the downloaded file system and then untar it.<br />
$ cd /your-path-to/images<br />
$ mkdir angstrom<br />
$ cd angstrom<br />
$ tar xjvf ../omap3-console-image-overo.tar.bz2<br />
<br />
Leave this for now, we'll get back to it later.<br />
<br />
$ cd ../../debian<br />
<br />
The Debian root file system is built with 'debootstrap'. Install it onto your host machine with apt-get, along with 'qemu-arm-static' (qemu-user-static on Debian):<br />
<br />
$ sudo apt-get install debootstrap qemu-arm-static<br />
<br />
Once these are installed run the following:<br />
<br />
$ sudo debootstrap --foreign --verbose --arch=armel --include=vim-nox,openssh-server,ntpdate,less --exclude=nano squeeze ./squeeze http://ftp.au.debian.org/debian<br />
<br />
The --include and --exclude packages are optional. I prefer vim to the standard vim-tiny, vim-nox is the non-gui version. I don't use nano so I've excluded it from the build. The above command will download the required packages and create a squeeze root file system in a directory called squeeze. You can use a closer Debian mirror rather than the one that I've used in the above example.<br />
<br />
Now we chroot into our newly created file system to finish off. But the packages in the new file system are for the arm architecture so we need an emulator. We installed it earlier, copy the relevant file:<br />
<br />
$ cp /usr/bin/qemu-arm-static squeeze/usr/bin<br />
<br />
Now chroot into our new file system:<br />
<br />
$ sudo chroot squeeze<br />
<br />
Chroot has trapped us in our new root file system, isolating us from the file system of the host computer. You will see a directory named debootstrap. Go to it:<br />
<br />
$ cd debootstrap<br />
<br />
Finish off the installation:<br />
<br />
$ ./debootstap --second-stage<br />
<br />
The above command will install all the Debian packages into our file system.<br />
<br />
We now need to create a password for the root user or we'll have a system that we can't log into:<br />
<br />
$ passwd<br />
<br />
Delete the .deb packages now that we've installed them:<br />
<br />
$ apt-get clean<br />
<br />
With that done we can exit:<br />
<br />
$ exit<br />
<br />
Our root file system needs kernel modules. You'll find a directory under /your-path-to/images/angstrom/lib/modules with a name that reflects the kernel version. In this example it's '3.0.0'. Copy the whole directory to the new Debian file system:<br />
<br />
$ sudo cp -r ../images/angstrom/lib/modules/3.0.0/ squeeze/lib/modules/<br />
<br />
We also need the fstab and inittab configuration files from Angstrom:<br />
<br />
$ sudo cp ../images/angstrom/etc/inittab squeeze/etc<br />
$ sudo cp ../images/angstrom/etc/fstab squeeze/etc<br />
<br />
If fstab is wrong then our new Debian system won't boot properly.<br />
<br />
If inittab is wrong then we won't get a console login prompt, we'll get an error along the lines of "init: Id 'x' respawning too fast: disabled for 5 minutes".<br />
<br />
You can also copy the interfaces file:<br />
<br />
$ sudo cp ../images/angstrom/etc/network/interfaces squeeze/etc/network/<br />
<br />
Edit the newly copied file and change eth0 to eth1.<br />
<br />
Now go to the root directory of your Debian file system:<br />
<br />
$ cd squeeze<br />
<br />
And tar it up:<br />
<br />
$ sudo tar -cjvf ../squeeze.tar.bz2 *<br />
<br />
Create a bootable micro SD card following the Gumstix tutorial found [http://gumstix.org/create-a-bootable-microsd-card.html here], but use the above squeeze.tar.bz2 in place of roofs.tar.bz2.<br />
<br />
Put the SD card in your Gumstix COM and boot it up. If all goes well you should get a logon prompt at the console.<br />
<br />
There are still a couple of things left to do. The kernel module dependencies need to be set up. On your new Debian install go to the modules directory:<br />
<br />
$ cd /lib/modules/3.0.0<br />
$ depmod<br />
<br />
The above command will build the modules dependencies files. When you reboot, the kernel will find its modules and use them.<br />
<br />
If you have wifi on your COM you'll have to install some more software. But first we need to put something in /etc/apt/sources.list.<br />
<br />
$ vi /etc/apt/sources.list<br />
<br />
Put in something like the following, replace with your closest mirror. Make sure you include the 'non-free' repositories:<br />
<br />
deb http://ftp.iinet.net.au/debian/debian squeeze main non-free<br />
<br />
$ apt-get update<br />
<br />
Install wifi packages.<br />
<br />
$ apt-get install wireless-tools libertas-firmware<br />
<br />
There's a wifi howto at the Gumstix wiki [http://wiki.gumstix.org/index.php?title=Overo_Wifi here].<br />
<br />
I like to edit the vimrc configuration file and un-comment the lines to enable syntax highlighting and mouse. It's at /etc/vim/vimrc.<br />
<br />
You might also want to edit /etc/hostname.</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Debian_Root_File_System&diff=5781Debian Root File System2012-03-08T07:22:41Z<p>Dan Nelson: </p>
<hr />
<div>Embedded Linux has always been constrained by available memory, cut-down distributions such as Angstrom and EmDebian have addressed those constraints. Debian is a stable, full featured distribution that has a very large repository of packages. With the generous amount of memory available on a micro SD card there's no reason not to use it.<br />
<br />
This how-to describes the procedure to build a Debian root file system for a micro SD card. Gumstix's how-to on creating a bootable micro SD card can be found [http://gumstix.org/create-a-bootable-microsd-card.html here]. We'll follow the same procedure but will substitute our Debian root file system for the Gumstix Angstrom one.<br />
<br />
Start by creating some working directories in some place convenient:<br />
<br />
$ mkdir images<br />
$ mkdir debian<br />
<br />
Now Download some required images from the [http://cumulus.gumstix.org/images/angstrom/developer/ Gumstix repository]. This includes the bootloaders MLO and u-boot.bin. We also need uImage, the Linux kernel. Put them in the 'images' directory. <br />
<br />
On top of that we need the Angstrom file system. There are several to chose from, don't use any with 'nand' in the name. The one you want will be called something like, omap3-console-image-overo.tar.bz2. We'll pilfer the kernel modules from this tarball along with some important configuration files. We can, or course, build our own kernel and modules, but this way will prove to be quick and easy.<br />
<br />
Create a directory to extract the downloaded file system and then untar it.<br />
$ cd /your-path-to/images<br />
$ mkdir fsystem<br />
$ cd fsystem<br />
$ tar xjvf ../omap3-console-image-overo.tar.bz2<br />
<br />
Leave this for now, we'll get back to it later.<br />
<br />
$ cd ../../debian<br />
<br />
The Debian root file system is built with 'debootstrap'. Install it onto your host machine with apt-get, along with 'qemu-arm-static' (qemu-user-static on Debian):<br />
<br />
$ sudo apt-get install debootstrap qemu-arm-static<br />
<br />
Once these are installed run the following:<br />
<br />
$ sudo debootstrap --foreign --verbose --arch=armel --include=vim-nox,openssh-server,ntpdate,less --exclude=nano squeeze ./squeeze http://ftp.au.debian.org/debian<br />
<br />
The --include and --exclude packages are optional. I prefer vim to the standard vim-tiny, vim-nox is the non-gui version. I don't use nano so I've excluded it from the build. The above command will download the required packages and create a squeeze root file system in a directory called squeeze. You can use a closer Debian mirror rather than the one that I've used in the above example.<br />
<br />
Now we chroot into our newly created file system to finish off. But the packages in the new file system are for the arm architecture so we need an emulator. We installed it earlier, copy the relevant file:<br />
<br />
$ cp /usr/bin/qemu-arm-static squeeze/usr/bin<br />
<br />
Now chroot into our new file system:<br />
<br />
$ sudo chroot squeeze<br />
<br />
Chroot has trapped us in our new root file system, isolating us from the file system of the host computer. You will see a directory named debootstrap. Go to it:<br />
<br />
$ cd debootstrap<br />
<br />
Finish off the installation:<br />
<br />
$ ./debootstap --second-stage<br />
<br />
The above command will install all the Debian packages into our file system.<br />
<br />
We now need to create a password for the root user or we'll have a system that we can't log into:<br />
<br />
$ passwd<br />
<br />
Delete the .deb packages now that we've installed them:<br />
<br />
$ apt-get clean<br />
<br />
With that done we can exit:<br />
<br />
$ exit<br />
<br />
Our root file system needs kernel modules. You'll find a directory under /your-path-to/images/fsystem/lib/modules with a name that reflects the kernel version. In this example it's '3.0.0'. Copy the whole directory to the new Debian file system:<br />
<br />
$ sudo cp -r ../images/fsystem/lib/modules/3.0.0/ squeeze/lib/modules/<br />
<br />
We also need the fstab and inittab configuration files from Angstrom:<br />
<br />
$ sudo cp ../images/fsystem/etc/inittab squeeze/etc<br />
$ sudo cp ../images/fsystem/etc/fstab squeeze/etc<br />
<br />
If fstab is wrong then our new Debian system won't boot properly.<br />
<br />
If inittab is wrong then we won't get a console login prompt, we'll get an error along the lines of "init: Id 'x' respawning too fast: disabled for 5 minutes".<br />
<br />
You can also copy the interfaces file:<br />
<br />
$ sudo cp ../images/fsystem/etc/network/interfaces squeeze/etc/network/<br />
<br />
Edit the newly copied file and change eth0 to eth1.<br />
<br />
Now go to the root directory of your Debian file system:<br />
<br />
$ cd squeeze<br />
<br />
And tar it up:<br />
<br />
$ sudo tar -cjvf ../squeeze.tar.bz2 *<br />
<br />
Create a bootable micro SD card following the Gumstix tutorial found [http://gumstix.org/create-a-bootable-microsd-card.html here], but use the above squeeze.tar.bz2 in place of roofs.tar.bz2.<br />
<br />
Put the SD card in your Gumstix COM and boot it up. If all goes well you should get a logon prompt at the console.<br />
<br />
There are still a couple of things left to do. The kernel module dependencies need to be set up. On your new Debian install go to the modules directory:<br />
<br />
$ cd /lib/modules/3.0.0<br />
$ depmod<br />
<br />
The above command will build the modules dependencies files. When you reboot, the kernel will find its modules and use them.<br />
<br />
If you have wifi on your COM you'll have to install some more software. But first we need to put something in /etc/apt/sources.list.<br />
<br />
$ vi /etc/apt/sources.list<br />
<br />
Put in something like the following, replace with your closest mirror. Make sure you include the 'non-free' repositories:<br />
<br />
deb http://ftp.iinet.net.au/debian/debian squeeze main non-free<br />
<br />
$ apt-get update<br />
<br />
Install wifi packages.<br />
<br />
$ apt-get install wireless-tools libertas-firmware<br />
<br />
There's a wifi howto at the Gumstix wiki [http://wiki.gumstix.org/index.php?title=Overo_Wifi here].<br />
<br />
I like to edit the vimrc configuration file and un-comment the lines to enable syntax highlighting and mouse. It's at /etc/vim/vimrc.<br />
<br />
You might also want to edit /etc/hostname.</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Debian_Root_File_System&diff=5780Debian Root File System2012-03-07T12:21:21Z<p>Dan Nelson: </p>
<hr />
<div>This how-to describes the procedure to build a Debian root file system. Emdebian is smaller, but I've had dependency problems with some packages. With the generous amount of memory on a micro SD card there's no reason not to use Debian. I built the Debian root file system from the command line of Ubuntu.<br />
<br />
Start by creating a bootable micro SD card following the instructions on the Gumstix wiki. This will have the Angstrom distro that Gumstix uses. We can use the kernel modules from the Angstrom root file system along with some other files.<br />
<br />
To get the kernel modules you can either log onto your Gumstix, tar them up from there, and then scp them to your host machine. Or you can unzip the Angstrom root file system to the working directory of your host machine. Change directory to /lib/modules of either your Gumstix machine or your untarred Angstrom file system. You will see a directory named something like 2.6.39. This contains all the kernel modules. Tar them up:<br />
<br />
$ tar zcvf modules.tar.gz 2.6.39/<br />
<br />
Now copy or scp the tarred file to the working directory of your host machine.<br />
<br />
You will also need to edit some of the configuration files of your Debian file system once it's built. Of particular importance is /etc/fstab. You can use what's in Angstrom as long as you take it from the image for the SD card rather than from the 'nand' one. Another important file is /etc/inittab, if this isn't right then you won't be able to log onto the console. You can use the one from Angstrom as well. Also /etc/network/interfaces. <br />
<br />
The Debian root file system is built with 'debootstrap'. Install it onto your host machine with apt-get, along with 'qemu-arm-static' (qemu-user-static on Debian):<br />
<br />
$ sudo apt-get install debootstrap qemu-arm-static<br />
<br />
Once these are installed run the following:<br />
<br />
$ sudo debootstrap --foreign --verbose --arch=armel --include=vim-nox,openssh-server --exclude=nano squeeze ./squeeze http://ftp.au.debian.org/debian<br />
<br />
The --include options are optional. I prefer vim to the standard vim-tiny, vim-nox is the non-gui version. I don't use nano so I've excluded it from the build. The above command will download the required packages and create a squeeze root file system in a directory called squeeze. You can use a closer Debian mirror rather than the one that I've used in the above example.<br />
<br />
Now we chroot into our newly created file system to finish off. But the packages in the new file system are for the arm architecture so we need an emulator. We installed it onto our development machine earlier, copy the relevant file:<br />
<br />
$ cp /usr/bin/qemu-arm-static squeeze/usr/bin<br />
<br />
Now chroot into our new file system:<br />
<br />
$ sudo chroot squeeze<br />
<br />
Chroot has trapped us in our new root file system. You will see a directory named debootstrap. Go to it:<br />
<br />
$ cd debootstrap<br />
<br />
Finish off the installation:<br />
<br />
$ ./debootstap --second-stage<br />
<br />
The above command will install all the Debian packages into our file system.<br />
<br />
We now need to create a password for the root user or we'll have a system that we can't log into:<br />
<br />
$ passwd<br />
<br />
Delete the .deb packages now that we've installed them:<br />
<br />
$ apt-get clean<br />
<br />
With that done we can exit:<br />
<br />
$ exit<br />
<br />
Our root file system needs kernel modules:<br />
<br />
$ tar zxvf modules.tar.gz squeeze/lib/modules<br />
<br />
Copy the fstab, inittab and interfaces files that you took from Anstrom into your Debian file system. Other files that need our attention are /etc/hostname and /etc/apt/sources.list. Edit interfaces and change eth2 to eth1.<br />
<br />
Now go to the root directory of your Debian file system:<br />
<br />
$ cd squeeze<br />
<br />
And tar it up:<br />
<br />
$ sudo tar -czf ../squeeze.tar.gz *<br />
<br />
And that's about it. Follow the same procedure that you did when you originally installed Angstrom on your SD card, this time using the Debian squeeze tarball.</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Installing_Debian_and_Xenomai_on_gumstix_Overo&diff=5772Installing Debian and Xenomai on gumstix Overo2012-02-23T13:29:02Z<p>Dan Nelson: /* Compiling the kernel */</p>
<hr />
<div>This document describes how I (Sagar Behere) installed Debian squeeze and vanilla linux kernel 2.6.38.8 patched with Xenomai 2.6.0 on the gumstix Overo. The contents of this document are probably applicable to other software versions as well. Note that this isn't a newbie tutorial. You still need to know what you are doing.<br />
<br />
DISCLAIMER: There may be better ways to do this.<br />
<br />
The standard method to compile a kernel and rootfs is to use the Open Embedded build system that is described [http://gumstix.org/software-development/open-embedded/61-using-the-open-embedded-build-system.html here]. However, I did not use that method because I couldn't figure out how to build any of the kernel versions for which xenomai patches could be found (at the time of writing, the virtual/kernel pointed to version 3.0). Also, I prefer to use the debian userland, rather than Ångstrom. Therefore, the method described here does NOT use Open Embedded.<br />
<br />
==Preparing the host==<br />
<br />
The ''host'' is the computer you will use to build the kernel and rootfs. The ''target'' is the gumstix Overo COM on which the kernel and rootfs will be deployed. My host is an x86 computer running Debian squeeze. The method described here will probably work on a host running Ubuntu, with some modifications<br />
<br />
Add emdebian to your apt sources and get needed packages<br />
sudo apt-get install emdebian-archive-keyring<br />
sudo apt-get install gcc-4.3-arm-linux-gnueabi binutils-arm-linux-gnueabi<br />
<br />
This should pull in all the dependencies and you'll now have an arm cross-toolchain installed on your system. For Ubuntu users also, cross tool chains are available. See the http://www.linaro.org/.<br />
<br />
==Compiling the kernel==<br />
<br />
* Download and extract xenomai. Let's call the resulting xenomai-2.6.0 dir as {xenomaisourcedir}<br />
wget -c http://download.gna.org/xenomai/stable/xenomai-2.6.0.tar.bz2; tar jxvf xenomai-2.6.0.tar.bz2; <br />
* Supported kernels can be found in {xenomaisourcedir}/ksrc/arch/arm/patches/. I saw the file adeos-ipipe-2.6.38.8-arm-1.18-04.patch and so decided to use that kernel<br />
* Download the kernel and extract it. Let's call the resulting linux-2.6.38.8 directory {kernelsourcedir}<br />
wget -c http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.38.8.tar.bz2; tar jxvf linux-2.6.38.8.tar.bz2<br />
* Patch the kernel sources with Xenomai. Go to {xenomaisourcedir} and <br />
scripts/prepare-kernel.sh --arch=arm --linux=/path/where/you/untarred/linux-2.6.38.8.tar.bz2<br />
It'll suggest the right patch to be applied.<br />
* Set the default kernel configuration<br />
cd {kernelsourcedir}; cp arch/arm/configs/omap2plus_defconfig .config<br />
* Configure the kernel with<br />
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- menuconfig<br />
I removed support for almost all the boards except the Overo and also removed support for everything execpt OMAP3. Configure the xenomai related stuff too.<br />
* Build the kernel with<br />
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- uImage modules<br />
* To deploy the kernel, you'll need the uImage which can be found at {kernelsourcedir}/arch/arm/boot/uImage You'll also need to put the resulting modules into the debian rootfs that we'll create later. For now, I merely put all the modules in some directory {modulesdirectory} with<br />
make ARCH=arm INSTALL_MOD_PATH=/path/to/{modulesdirectory} modules_install; <br />
You can optionally also put the firmware in some directory {firmwaredirectory} with<br />
make ARCH=arm INSTALL_FW_PATH=/path/to/{firmwaredirectory} firmware_install<br />
The {modulesdirectory} will contain a directory lib/modules/kernel-version that we'll copy over to our rootfs later.<br />
<br />
We still need to compile the xenomai userspace stuff, but we'll do that after setting up the rootfs<br />
<br />
==The debian rootfs==<br />
<br />
These instructions are based on http://gobysoft.com/wiki/InstallOnGumstixOvero and http://paul-strefling.blogspot.com/2011/06/installing-debian-on-gumstix-overo.html<br />
<br />
* Get the qemu-arm-static binary. <br />
sudo apt-get install qemu-user-static<br />
for ubuntu use <br />
apt-get install qemu-kvm-extras-static<br />
* Get multistrap<br />
sudo apt-get install multistrap<br />
* Make a directory to create the debian rootfs with<br />
mkdir overorootfs<br />
* Create a file called emdebian.conf and put in the following (add whatever packages you wish)<br />
<pre><br />
[General]<br />
arch=armel<br />
noauth=true<br />
unpack=true<br />
debootstrap=Grip Networking Debian Misc<br />
aptsources=Grip Debian<br />
<br />
[Grip]<br />
packages=locales udev adduser sudo nano build-essential less module-init-tools <br />
source=http://www.emdebian.org/grip<br />
keyring=emdebian-archive-keyring<br />
components=main dev<br />
suite=stable<br />
<br />
[Misc]<br />
packages=wget<br />
source=http://www.emdebian.org/grip<br />
keyring=emdebian-archive-keyring<br />
components=main dev<br />
suite=stable<br />
<br />
[Networking]<br />
packages=netbase ifupdown iproute net-tools iputils-ping ntp wireless-tools isc-dhcp-client wpasupplicant<br />
source=http://www.emdebian.org/grip<br />
keyring=emdebian-archive-keyring<br />
suite=stable<br />
<br />
[Debian]<br />
packages=zile tsocks<br />
source=http://ftp.se.debian.org/debian/<br />
keyring=debian-archive-keyring<br />
suite=stable<br />
</pre><br />
* Create the root filesystem with<br />
sudo multistrap -a armel -d overorootfs/ -f emdebian.conf<br />
* Copy the qemu binary so we can chroot<br />
sudo cp /usr/bin/qemu-arm-static overorootfs/usr/bin<br />
* Chroot into the system<br />
sudo chroot overorootfs /bin/bash<br />
* Finish setting up the packages with<br />
dpkg --configure -a<br />
Answer "no" when asked if you want to use "dash" as "/bin/sh". If ifupdown fails, just run again<br />
dpkg --configure -a<br />
* Add a user and give him sudo permissions<br />
adduser sagar;printf "sagar ALL=(ALL) ALL" >> /etc/sudoers<br />
* Configure locales. 136 is en_US.UTF-8<br />
dpkg-reconfigure locales<br />
* Set the DNS with<br />
printf "nameserver 8.8.8.8" > /etc/resolv.conf<br />
* create /etc/fstab and add the following<br />
<pre><br />
# /etc/fstab: static file system information.<br />
#<br />
# <file system> <mount point> <type> <options> <dump> <pass><br />
proc /proc proc defaults 0 0<br />
</pre><br />
* Configure hostname<br />
printf "gumstix" > /etc/hostname<br />
printf "127.0.0.1 gumstix\n" >> /etc/hosts<br />
* Get out of the chroot by pressing Ctrl+D and get in again with<br />
sudo chroot overorootfs<br />
At this point, you should be able to<br />
ping www.google.com<br />
if your host has internet access<br />
* The final task inside the chroot environment is to enable the serial console. Edit /etc/inittab and add the following line in the end<br />
T0:2345:respawn:/sbin/getty -L 115200 ttyO2 vt102<br />
* Update apt sources<br />
apt-get update<br />
* Exit the chroot and copy the modules over to the overorootfs<br />
cp -a {modulesdirectory}/lib/modules/2.6.38.8-ipipe overorootfs/lib/modules<br />
<br />
==Xenomai user space==<br />
<br />
This section is based on instructions at http://www.xenomai.org/index.php/Building_Debian_packages<br />
<br />
The userspace part of Xenomai needs to be compiled now. The traditional way is to cross-compile it, as described in the xenomai documentation. However, we can take advantage of our arm chroot environment to avoid cross-compilation. Also, we will create debian packages i.e. .deb files for the userspace part of the xenomai installation. We proceed as follows<br />
* copy {xenomaisourcedir} to overorootfs and<br />
<pre><br />
sudo chroot overorootfs<br />
apt-get install devscripts debhelper dh-kpatches findutils<br />
cd {xenomaisourcedir};DEBEMAIL="your@email" DEBFULLNAME="Your Name" debchange -v 2.6.0 Release 2.6.0<br />
debuild -uc -us<br />
cd ../; dpkg -i libxenomai1_2.6.0_armel.deb libxenomai-dev_2.6.0_armel.deb xenomai-runtime_2.6.0_armel.deb<br />
</pre><br />
<br />
==Preparing the SD card==<br />
<br />
There are a lot of guides describing how to partition and format a SD card for using on the overo. I used the one at http://johnwoconnor.blogspot.com/2009/04/installing-ubuntu-on-gumstix-overo.html. The official guide is at http://gumstix.org/create-a-bootable-microsd-card.html. Read those guides and come to a point where you have created the two partitions and formatted them. Then continue reading here. <br />
<br />
[NOTE: I am assuming that the first partition of your card is mounted under /media/FAT and the 2nd partition is under /media/rootfs]<br />
<br />
Get pre-built MLO and u-boot.bin from http://gumstix.org/download-prebuilt-images.html . I got mine from http://cumulus.gumstix.org/images/angstrom/factory/2011-08-30-1058/<br />
cp MLO /media/FAT; cp u-boot.bin /media/FAT<br />
cp {kernelsourcedir}/arch/arm/boot/uImage /media/FAT<br />
cd overorootfs; sudo rsync -aP . /media/rootfs/<br />
sync<br />
<br />
==Testing the install==<br />
Boot the gumstix from the SD card and log in as the user you created. Then wrap up the installation with<br />
sudo dpkg --configure -a<br />
<br />
In order to get wireless working, I had to add the files sd8686.bin and sd8686_helper.bin to /lib/firmware/ on the rootfs. Sorry, I don't remember where I got them from.<br />
<br />
To test xenomai<br />
cd /usr/lib/xenomai;./latency -p0 -t1<br />
You can also run the other programs in that directory</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Debian_Root_File_System&diff=5771Debian Root File System2012-02-22T14:17:39Z<p>Dan Nelson: </p>
<hr />
<div>This how-to describes the procedure to build a Debian root file system. Emdebian is smaller, but I've had dependency problems with some packages. With the generous amount of memory on a micro SD card there's no reason not to use Debian. I built the Debian root file system from the command line of Ubuntu.<br />
<br />
Start by creating a bootable micro SD card following the instructions on the Gumstix wiki. This will have the Angstrom distro that Gumstix uses. We can use the kernel modules from the Angstrom root file system along with some other files.<br />
<br />
To get the kernel modules you can either log onto your Gumstix, tar them up from there, and then scp them to your host machine. Or you can unzip the Angstrom root file system to the working directory of your host machine. Change directory to /lib/modules of either your Gumstix machine or your untarred Angstrom file system. You will see a directory named something like 2.6.39. This contains all the kernel modules. Tar them up:<br />
<br />
$ tar zcvf modules.tar.gz 2.6.39/<br />
<br />
Now copy or scp the tarred file to the working directory of your host machine.<br />
<br />
You will also need to edit some of the configuration files of your Debian file system once it's built. Of particular importance is /etc/fstab. You can use what's in Angstrom as long as you take it from the image for the SD card rather than from the 'nand' one. Another important file is /etc/inittab, if this isn't right then you won't be able to log onto the console. You can use the one from Angstrom as well. Also /etc/network/interfaces. <br />
<br />
The Debian root file system is built with 'debootstrap'. Install it onto your host machine with apt-get, along with 'qemu-arm-static' (qemu-user-static on Debian):<br />
<br />
$ sudo apt-get install debootstrap qemu-arm-static<br />
<br />
Once these are installed run the following:<br />
<br />
$ sudo debootstrap --foreign --verbose --arch=armel --include=debootstrap,vim-nox,openssh-server --exclude=nano squeeze ./squeeze http://ftp.au.debian.org/debian<br />
<br />
The --include option must include debootstrap, the others are optional. I prefer vim to the standard vim-tiny, vim-nox is the non-gui version. I don't use nano so I've excluded it from the build. The above command will download the required packages and create a squeeze root file system in a directory called squeeze. You can use a closer Debian mirror rather than the one that I've used in the above example.<br />
<br />
Now we chroot into our newly created file system to finish off. But the packages in the new file system are for the arm architecture so we need an emulator. We installed it onto our development machine earlier, copy the relevant file:<br />
<br />
$ cp /usr/bin/qemu-arm-static squeeze/usr/bin<br />
<br />
Now chroot into our new file system:<br />
<br />
$ sudo chroot squeeze<br />
<br />
Chroot has trapped us in our new root file system. You will see a directory named debootstrap. Go to it:<br />
<br />
$ cd debootstrap<br />
<br />
Finish off the installation:<br />
<br />
$ ./debootstap --second-stage<br />
<br />
The above command will install all the Debian packages into our file system.<br />
<br />
We now need to create a password for the root user or we'll have a system that we can't log into:<br />
<br />
$ passwd<br />
<br />
Delete the .deb packages now that we've installed them:<br />
<br />
$ apt-get clean<br />
<br />
With that done we can exit:<br />
<br />
$ exit<br />
<br />
Our root file system needs kernel modules:<br />
<br />
$ tar zxvf modules.tar.gz squeeze/lib/modules<br />
<br />
Copy the fstab, inittab and interfaces files that you took from Anstrom into your Debian file system. Other files that need our attention are /etc/hostname and /etc/apt/sources.list. Edit interfaces and change eth2 to eth1.<br />
<br />
Now go to the root directory of your Debian file system:<br />
<br />
$ cd squeeze<br />
<br />
And tar it up:<br />
<br />
$ sudo tar -czf ../squeeze.tar.gz *<br />
<br />
And that's about it. Follow the same procedure that you did when you originally installed Angstrom on your SD card, this time using the Debian squeeze tarball.</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Debian_Root_File_System&diff=5770Debian Root File System2012-02-20T14:24:43Z<p>Dan Nelson: </p>
<hr />
<div>This how-to describes the procedure to build a Debian root file system. I originally installed an Emdebian file system, but had dependency problems with some packages. But with the generous amount of memory on a micro SD card there's no reason not to build Debian itself. I worked from the command line of Ubuntu.<br />
<br />
Start by creating a bootable micro SD card following the instructions on the Gumstix wiki. This will have the Angstrom distro that Gumstix uses. We can take the kernel modules from the Angstrom root file system along with some other files. Log into Angstrom on Gumstix and go to /lib/modules. You will see a directory named something similar to 2.6.39. This contains all the kernel modules. Tar it up:<br />
<br />
$ tar zcvf modules.tar.gz 2.6.39/<br />
<br />
Now copy it to your development machine:<br />
<br />
$ scp modules.tar.gz ip.address.of.dev.machine:/path/to/dev/area<br />
<br />
You can scp /etc/inittab, /etc/fstab and /etc/network/interfaces as well. Use these as a reference in when you build your Debian root file system.<br />
<br />
The Debian root file system is built with 'debootstrap'. Install it with apt-get, along with 'qemu-arm-static' (qemu-user-static on Debian):<br />
<br />
$ sudo apt-get install debootstrap qemu-arm-static<br />
<br />
Once these are installed run the following:<br />
<br />
$ sudo debootstrap --foreign --verbose --arch=armel --include=debootstrap,vim-nox,openssh-server --exclude=nano squeeze ./squeeze http://ftp.au.debian.org/debian<br />
<br />
The --include option must include debootstrap, the others are optional. I prefer vim to the standard vim-tiny, vim-nox is the non-gui version. I don't use nano so I've excluded it from the build. The above command will download the required packages and create a squeeze root file system in a directory called squeeze.<br />
<br />
Now we chroot into our newly created file system to finish off. But the packages in the new file system are for the arm architecture so we need an emulator. We installed it onto our development machine earlier, copy the relevant file:<br />
<br />
$ cp /usr/bin/qemu-arm-static squeeze/usr/bin<br />
<br />
Now chroot into our new file system:<br />
<br />
$ sudo chroot squeeze<br />
<br />
You will see a directory named debootstrap. Go to it:<br />
<br />
$ cd debootstrap<br />
<br />
Finish off the installation:<br />
<br />
$ ./debootstap --second-stage<br />
<br />
The above command will install all the Debian packages into our file system.<br />
<br />
We now need to create a password for the root user or we'll have a system that we can't log into:<br />
<br />
$ passwd<br />
<br />
Delete the .deb packages now that we've installed them:<br />
<br />
$ apt-get clean<br />
<br />
With that done we can exit:<br />
<br />
$ exit<br />
<br />
Our root file system needs kernel modules:<br />
<br />
$ tar zxvf modules.tar.gz squeeze/lib/modules<br />
<br />
More to come.....</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Debian_Root_File_System&diff=5769Debian Root File System2012-02-20T14:23:07Z<p>Dan Nelson: </p>
<hr />
<div>This how-to describes the procedure to build a Debian root file system. I originally installed an Emdebian file system, but had dependency problems with some packages. But with the generous amount of memory on a micro SD card there's no reason not to build Debian itself. I worked from the command line of Ubuntu.<br />
<br />
Start by creating a bootable micro SD card following the instructions on the Gumstix wiki. This will have the Angstrom distro that Gumstix uses. We can take the kernel modules from the Angstrom root file system along with some other files. Log into Angstrom on Gumstix and go to /lib/modules. You will see a directory named something similar to 2.6.39. This contains all the kernel modules. Tar it up:<br />
<br />
$ tar zcvf modules.tar.gz 2.6.39/<br />
<br />
Now copy it to your development machine:<br />
<br />
$ scp modules.tar.gz ip.address.of.dev.machine:/path/to/dev/area<br />
<br />
You can scp /etc/inittab, /etc/fstab and /etc/network/interfaces as well. Use these as a reference in when you build your Debian root file system.<br />
<br />
The Debian root file system is built with 'debootstrap'. Install it with apt-get, along with 'qemu-arm-static' (qemu-user-static on Debian):<br />
<br />
$ sudo apt-get install debootstrap qemu-arm-static<br />
<br />
Once these are installed run the following:<br />
<br />
$ sudo debootstrap --foreign --verbose --arch=armel --include=debootstrap,vim-nox,openssh-server --exclude=nano squeeze ./squeeze http://ftp.au.debian.org/debian<br />
<br />
The --include option must include debootstrap, the others are optional. I prefer vim to the standard vim-tiny, vim-nox is the non-gui version. I don't use nano so I've excluded it from the build. The above command will download the required packages and create a squeeze root file system in a directory called squeeze.<br />
<br />
Now we chroot into our newly created file system to finish off. But the packages in the new file system are for the arm architecture so we need an emulator. We installed it onto our development machine earlier, copy the relevant file:<br />
<br />
$ cp /usr/bin/qemu-arm-static squeeze/usr/bin<br />
<br />
Now chroot into our new file system:<br />
<br />
$ sudo chroot squeeze<br />
<br />
You will see a directory named debootstrap. Go to it:<br />
<br />
$ cd debootstrap<br />
<br />
Finish off the installation:<br />
<br />
$ ./debootstap --second-stage<br />
<br />
The above command will install all the Debian packages into our file system.<br />
<br />
We now need to create a password for the root user or we'll have a system that we can't log into:<br />
<br />
$ passwd<br />
<br />
Delete the .deb packages now that we've installed them:<br />
<br />
$ apt-get clean<br />
<br />
With that done we can exit:<br />
<br />
$ exit<br />
<br />
Our root file system needs kernel modules:<br />
<br />
$ tar zxvf modules.tar.gz squeeze/lib/modules</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Debian_Root_File_System&diff=5768Debian Root File System2012-02-20T14:22:24Z<p>Dan Nelson: </p>
<hr />
<div>This how-to describes the procedure to build a Debian root file system. I originally installed an Emdebian file system, but had dependency problems with some packages. But with the generous amount of memory on a micro SD card there's no reason not to build Debian itself. I worked from the command line of Ubuntu.<br />
<br />
Start by creating a bootable micro SD card following the instructions on the Gumstix wiki. This will have the Angstrom distro that Gumstix uses. We can take the kernel modules from the Angstrom root file system along with some other files. Log into Angstrom on Gumstix and go to /lib/modules. You will see a directory named something similar to 2.6.39. This contains all the kernel modules. Tar it up:<br />
<br />
$ tar zcvf modules.tar.gz 2.6.39/<br />
<br />
Now copy it to your development machine:<br />
<br />
$ scp modules.tar.gz ip.address.of.dev.machine:/path/to/dev/area<br />
<br />
You can scp /etc/inittab, /etc/fstab and /etc/network/interfaces as well. Use these as a reference in when you build your Debian root file system.<br />
<br />
The Debian root file system is built with 'debootstrap'. Install it with apt-get, along with 'qemu-arm-static' (qemu-user-static on Debian):<br />
<br />
$ sudo apt-get install debootstrap qemu-arm-static<br />
<br />
Once these are installed run the following:<br />
<br />
$ sudo debootstrap --foreign --verbose --arch=armel --include=debootstrap,vim-nox,openssh-server --exclude=nano squeeze ./squeeze http://ftp.au.debian.org/debian<br />
<br />
The --include option must include debootstrap, the others are optional. I prefer vim to the standard vim-tiny, vim-nox is the non-gui version. I don't use nano so I've excluded it from the build. The above command will download the required packages and create a squeeze root file system in a directory called squeeze.<br />
<br />
Now we chroot into our newly created file system to finish off. But the packages in the new file system are for the arm architecture so we need an emulator. We installed it onto our development machine earlier, copy the relevant file:<br />
<br />
$ cp /usr/bin/qemu-arm-static squeeze/usr/bin<br />
<br />
Now chroot into our new file system:<br />
<br />
$ sudo chroot squeeze<br />
<br />
You will see a directory named debootstrap. Go to it:<br />
<br />
$ cd debootstrap<br />
<br />
Finish off the installation:<br />
<br />
$ ./debootstap -- second-stage<br />
<br />
The above command will install all the Debian packages into our file system.<br />
<br />
We now need to create a password for the root user or we'll have a system that we can't log into:<br />
<br />
$ passwd<br />
<br />
Delete the .deb packages now that we've installed them:<br />
<br />
$ apt-get clean<br />
<br />
With that done we can exit:<br />
<br />
$ exit<br />
<br />
Our root file system needs kernel modules:<br />
<br />
$ tar zxvf modules.tar.gz squeeze/lib/modules</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Debian_Root_File_System&diff=5767Debian Root File System2012-02-20T14:20:39Z<p>Dan Nelson: </p>
<hr />
<div>This how-to describes the procedure to build a Debian root file system. I originally installed an Emdebian file system, but had dependency problems with some packages. But with the generous amount of memory on a micro SD card there's no reason not to build Debian itself. I worked from the command line of Ubuntu.<br />
<br />
Start by creating a bootable micro SD card following the instructions on the Gumstix wiki. This will have the Angstrom distro that Gumstix uses. We can take the kernel modules from the Angstrom root file system along with some other files. Log into Angstrom on Gumstix and go to /lib/modules. You will see a directory named something similar to 2.6.39. This contains all the kernel modules. Tar it up:<br />
<br />
$ tar zcvf modules.tar.gz 2.6.39/<br />
<br />
Now copy it to your development machine:<br />
<br />
$ scp modules.tar.gz ip.address.of.dev.machine:/path/to/dev/area<br />
<br />
You can scp /etc/inittab, /etc/fstab and /etc/network/interfaces as well. Use these as a reference in when you build your Debian root file system.<br />
<br />
The Debian root file system is built with 'debootstrap'. Install it with apt-get, along with 'qemu-arm-static' (qemu-user-static on Debian):<br />
<br />
$ sudo apt-get install debootstrap qemu-arm-static<br />
<br />
Once these are installed run the following:<br />
<br />
$ sudo debootstrap --foreign --verbose --arch=armel --include=debootstrap,vim-nox,openssh-server --exclude=nano squeeze ./squeeze http://ftp.au.debian.org/debian<br />
<br />
The --include option must include debootstrap, the others are optional. I prefer vim to the standard vim-tiny, vim-nox is the non-gui version. I don't use nano so I've excluded it from the build. The above command will download the required packages and create a squeeze root file system in a directory called squeeze.<br />
<br />
Now we chroot into our newly created file system to finish off. But the packages in the new file system are for the arm architecture so we need an emulator. We installed it onto our development machine earlier, copy the relevant file:<br />
<br />
$ cp /usr/bin/qemu-are-static squeeze/usr/bin<br />
<br />
Now chroot into our new file system:<br />
<br />
$ sudo chroot squeeze<br />
<br />
You will see a directory named debootstrap. Go to it:<br />
<br />
$ cd debootstrap<br />
<br />
Finish off the installation:<br />
<br />
$ ./debootstap -- second-stage<br />
<br />
The above command will install all the Debian packages into our file system.<br />
<br />
We now need to create a password for the root user or we'll have a system that we can't log into:<br />
<br />
$ passwd<br />
<br />
Delete the .deb packages now that we've installed them:<br />
<br />
$ apt-get clean<br />
<br />
With that done we can exit:<br />
<br />
$ exit<br />
<br />
Our root file system needs kernel modules:<br />
<br />
$ tar zxvf modules.tar.gz squeeze/lib/modules</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Debian_Root_File_System&diff=5766Debian Root File System2012-02-20T14:19:23Z<p>Dan Nelson: Created page with "This how-to describes the procedure to build a Debian root file system. I originally installed an Emdebian file system, but had dependency problems with some packages. But with..."</p>
<hr />
<div>This how-to describes the procedure to build a Debian root file system. I originally installed an Emdebian file system, but had dependency problems with some packages. But with the generous amount of memory on a micro SD card there's no reason not to build Debian itself. I worked from the command line of Ubuntu.<br />
<br />
Start by creating a bootable micro SD card following the instructions on the Gumstix wiki. This will have the Angstrom distro that Gumstix uses. We can take the kernel modules from the Angstrom root file system along with some other files. Log into Angstrom on Gumstix and go to /lib/modules. You will see a directory named something similar to 2.6.39. This contains all the kernel modules. Tar it up:<br />
<br />
$ tar zcvf modules.tar.gz 2.6.39/<br />
<br />
Now copy it to your development machine:<br />
<br />
$ scp module.tar.gz ip.address.of.dev.machine:/path/to/dev/area<br />
<br />
You can scp /etc/inittab, /etc/fstab and /etc/network/interfaces as well. Use these as a reference in when you build your Debian root file system.<br />
<br />
The Debian root file system is built with 'debootstrap'. Install it with apt-get, along with 'qemu-arm-static' (qemu-user-static on Debian):<br />
<br />
$ sudo apt-get install debootstrap qemu-arm-static<br />
<br />
Once these are installed run the following:<br />
<br />
$ sudo debootstrap --foreign --verbose --arch=armel --include=debootstrap,vim-nox,openssh-server --exclude=nano squeeze ./squeeze http://ftp.au.debian.org/debian<br />
<br />
The --include option must include debootstrap, the others are optional. I prefer vim to the standard vim-tiny, vim-nox is the non-gui version. I don't use nano so I've excluded it from the build. The above command will download the required packages and create a squeeze root file system in a directory called squeeze.<br />
<br />
Now we chroot into our newly created file system to finish off. But the packages in the new file system are for the arm architecture so we need an emulator. We installed it onto our development machine earlier, copy the relevant file:<br />
<br />
$ cp /usr/bin/qemu-are-static squeeze/usr/bin<br />
<br />
Now chroot into our new file system:<br />
<br />
$ sudo chroot squeeze<br />
<br />
You will see a directory named debootstrap. Go to it:<br />
<br />
$ cd debootstrap<br />
<br />
Finish off the installation:<br />
<br />
$ ./debootstap -- second-stage<br />
<br />
The above command will install all the Debian packages into our file system.<br />
<br />
We now need to create a password for the root user or we'll have a system that we can't log into:<br />
<br />
$ passwd<br />
<br />
Delete the .deb packages now that we've installed them:<br />
<br />
$ apt-get clean<br />
<br />
With that done we can exit:<br />
<br />
$ exit<br />
<br />
Our root file system needs kernel modules:<br />
<br />
$ tar zxvf modules.tar.gz squeeze/lib/modules</div>Dan Nelsonhttps://wiki.gumstix.com/index.php?title=Category:How_to_-_Debian&diff=5765Category:How to - Debian2012-02-20T13:07:51Z<p>Dan Nelson: </p>
<hr />
<div>* [[Installing Debian and Xenomai on gumstix Overo]]<br />
* [[Debian Root File System]]</div>Dan Nelson