User manual

10 Buildroot
10.3. Copying the Created Image to the System
OpenNetCom You can copy the newly created image via RedBoot and console. This will require a
special Service Board to interact with RedBoot. It is very important that write-protection jumper
is set in order to protect RedBoot from getting corrupted. Please refer to OpenNetCom’s user
manual.
OnRISC You’ll need to create a ext2 partition on your media (CF or microSD-card). Then insert
your media in OnRISC and go to “BIOS->System Console” and execute following actions:
1. OnRISC: nc -l -p 5000 | cat > /dev/hda1
2. PC: nc 192.168.254.254 5000 < output/images/rootfs.ext2
3. OnRISC: reboot
This will copy ext2 image to the first partition of your CF card. For microSD-card just change
/dev/hda1 to /dev/sda1.
Type “root” to login to the system. No password is required.
10.4. Customizing the Image
Buildroot uses Kconfig
63
subsystem to manage the process of configuration just like Linux kernel
does. Following bigger parts can be configured:
• make menuconfig - configures Buildroot: toolchain, rootfs, packages
• make busybox-menuconfig - configures BusyBox
64
• make uclibc-menuconfig - configures uClibc
65
• make linux26-menuconfig - configures Kernel
First place to look for choosing new packages is BusyBox configuration. If the package is not
available there then it can be found in Buildroot itself if it was included into its repository.
You can specify a special script, that will be running before the file system image is built. In this
script you can change your file system image via adding or modifying files. See following script,
that copies device specific interfaces files: target/devices/vscom/OnRISC/custom.sh.
63
en.wikipedia.org/wiki/Kconfig
64
www.busybox.net
65
www.uclibc.org
May 2014 OnRISC User Manual 69