Changes

Jump to: navigation, search
m
Introduction
== Introduction ==
Installing Funtoo to a Raspberry Pi is fun, but there are a lot more boards out there. For example, the carrier boards that hold a DIMM mounted AM335x series cpu. To get this going, we need to use the U-Boot bootloader, some knowledge of serial consolesdevice tree blobs, and a lot of patience.
For this article, we are using this [http://www.goembed.com/index.php/Products/detail/tpid/49 board]. You can read all about it [https://www.dropbox.com/sh/qk4fligwqth7547/AADVvhXGAOxkbqFRKPP8eeSja/SBC335x-B2A?dl=0 here] but hopefully the steps depicted here will should get you a manufacturer supplied 4.1.8 kernel with a Funtoo stage3 running on it. Amazing, hopefullyPossibly. Don't buy it if you don't absolutely need it. There are far better choices.
{{note|When you pick a board, documentation is just as important as hardware features. Without it, you WILL be hunting down someone in Shenzhen to explain why the board refuses to boot (you forgot to ground C8, of course).}}
{{warning|This is kind of a ridiculous exercise, given the author's limited level and the wild idiosyncrasies of board programming, but it may be instructive. It helps me.}}
== Making the Environment ==
Edit xcompile_variables to set XC_WORK, XC_LINUX_PREFIX, ARCH, CROSSDEV_TARGET, and STAGE3 variables to taste.For this board, we use:* CROSSDEV_TARGET="arm-linux-gnueabihf"* ARCH=arm* STAGE3=funtoo-current/arm-32bit/armv7a_neon_hardfp* STAGE3_CFLAGS="-O2 -pipe -march=armv7-a -mfpu=neon -mfloat-abi=hard"* STAGE3_NAME=stage3-latest.tar.xz 
{{console|body=
# . xcompile_variables.sh
# mkdir -p $CONFIGS $FIRMWARE $LINUX $UBOOTS $STAGE3S
Your current cross compilation environment:
==============================
ARCH
arm
==============================
CROSSDEV_TARGET
arm-linux-gnueabihf
==============================
STAGE3_CFLAGS
-O2 -pipe -march=armv7-a -mfpu=neon -mfloat-abi=hard
...<more output>...
}}
 
== Retrieve Sources ==
{{console|body=
{{console|body=
# . xcompile_variables
# echo $KERNEL_VERSIONget_kernel_version
4.1.18
# set_kernel_extraversion = -defconfig && . xcompile_variables.sh
# get_kernel_version
4.1.18-defconfig
# cd $XC_KERNEL_SRC
# alias make="make -j<N>"
Setting XC_KERNEL_OLDCONFIG to /usr/src/fun_kernel/configs/<XC_LINUX_PREFIX>/4.1.18.kconf
# cp XC_KERNEL_OLDCONFIG .config
# ARCH=$ARCH CROSS_COMPILE=$CROSSDEV_TARGET- make zImage modules dtbs
}}
 
== U-Boot Building ==
Notice the use of O=$XC_LINUX_PREFIX to control output. Remove this directory if you need to clean for a rebuild. DTC is the device tree compiler location that permits the use of Device Tree Blobs, and an absolutely essential tool for managing the wild forest of ARM processors and base boards. See this [http://xillybus.com/tutorials/device-tree-zynq-1 tutorial] on the Device Tree.
{{console|body=
# cd $XC_UBOOT
== Setup Stage3 ==
Follow the steps in http://funtoo.org/Crossdev_Automation#Stage3_Configuration but do not set up a software clock. Our board has a hardware clock.
===Copy Over Kernel Filesand Firmware===
{{console|body=
# cd $XC_KERNEL_SRC
# ARCH=$ARCH CROSS_COMPILE=$CROSSDEV_TARGET- INSTALL_MOD_PATH=$XC_STAGE3S INSTALL_MOD_STRIP=1 make modules_install
# ARCH=$ARCH CROSS_COMPILE=$CROSSDEV_TARGET- INSTALL_FW_PATH=$XC_STAGE3S make firmware_install
# cp $XC_FIRMWARE/* $XC_STAGE3S/lib/firmware# cp arch/arm/boot/uImage zImage $XC_STAGE3S/boot/uboot# get_kernel_release() { (cd cp arch/arm/boot/dts/*.dtb $XC_KERNEL_SRC ; ARCH=$ARCH CROSS_COMPILE=$CROSSDEV_TARGET- make kernelrelease;) }XC_STAGE3S/boot
# rm $XC_STAGE3S/lib/modules/`get_kernel_release`/{build,source}
}}
===Copy Over U-Boot Files===
Leave a blank line at the end of the u-boot config. For some reason or other.
{{console|body=
# cp $XC_UBOOT/$XC_LINUX_PREFIX/{MLO,u-boot.img} $XC_STAGE3S/boot/uboot# echo "mmcrootfstype=ext4bootargs=console=ttyO0,115200n8 root=/dev/mmcblk0p2 mem=128M rootwaitbootcmd=mmc rescan; fatload mmc 0 0x82000000 uImage; bootm 0x82000000uenvcmd=boot" > $XC_STAGE3S/boot/uboot/uEnv.txt
}}
# mkdir -p /mnt/funtoo
# mount /dev/<your_dev>2 /mnt/funtoo
# mkdir -p /mnt/funtoo/boot/uboot# mount /dev/<your_dev>1 /mnt/funtoo/boot/uboot
# rsync -avz --exclude "usr/portage/*" $XC_STAGE3S/{boot,bin,etc,home,lib,mnt,opt,root,run,sbin,srv,tmp,usr,var,dev} /mnt/funtoo
# mkdir -p /mnt/funtoo/{proc,sys}
# umount -R /mnt/funtoo
}}
 
Reboot! Moment of truth: do you really know what you are doing?
 
{{tip|Once you get the board up and sshd running on it, then use rsync -e "ssh" $XC_STAGE3S/{boot,lib} <board_ip>:/ to do the kernel hacking. How long can you keep it up?}}
 
== If It Boots... ==
=== Device Tree Fun ===
This is important. In embedded world we need to always handle the relationship between the cpu and baseboard that carries it. We can use the u-boot shell to find this out.
 
{{console|body=
=> bdinfo
arch_number = 0x00000F8C
boot_params = 0x10000100
DRAM bank = 0x00000000
-> start = 0x10000000
-> size = 0x80000000
eth0name = FEC
ethaddr = (not set)
current eth = FEC
ip_addr = <NULL>
baudrate = 115200 bps
TLB addr = 0x8FFF0000
relocaddr = 0x8FF4A000
reloc off = 0x7874A000
irq_sp = 0x8EF47EA0
sp start = 0x8EF47E90
FB base = 0x8EF4B7C0
}}
 
This structure is extremely useful in finding an appropriate device tree file so that the cpu can talk to the registers on the hardware and engage with interupts. It's pretty cool.
wiki-users
735
edits

Navigation menu