Architectures/ARM/Anaconda Boot Config

About

The idea behind this page is to describe the parameters for all the ARM systems we intend to support.

Systems

OMAP

Install Mechanism:

disk image

Boot Loader:

u-boot with bootz

Media:

mmcblk

Partition layout:

/boot/uboot /boot / msdos labels

File systems:

/boot/uboot needs to be partition #1 and vfat with specific sector boundaries, /boot needs to be ext2 or ext3, / can be

Special Packages:

uboot-panda uboot-beagle uboot-beaglebone

Kernel:

kernel (unified)

Console:

console=ttyO2,115200n8

DTB Files:

Device tree loading prevents boot in kernel 3.9

Oddities:

MLO file needs to be first thing copied to the vfat partition, then a uboot.img and a uEnv.txt file written. It is anticipated that a deoployment tool will populate /boot/uboot for the target-board

Trimslice

Install Mechanism:

anaconda sdcard

Boot Loader:

u-boot with bootz

Media:

mmcblk, sda

Partition layout:

/boot /

File systems:

/boot needs to be ext2 or ext3

Kernel:

kernel-tegra

Console:

console=ttyS0,115200n8

DTB Files:

tegra20-trimslice.dtb

Oddities:

sata disk is connected via usb to sata bridge requiring "usb" bootloader commands

Armada XP

Install Mechanism:

pxe

Boot Loader:

uboot (bootm w/ 0x2080000/0x2880000 kernel/initramfs addrs)

Media:

scsi ide

Partition layout:

/boot /

File systems:

/boot needs to be ext2 or ext3

Kernel:

kernel (unified, but with 0x00008000 load address for mkimage)

Console:

console=ttyS0,115200n8

DTB Files:

Appended dtb required

Oddities:

Uses a unified kernel, but needs a custom dtb appended to the kernel before running mkimage. (no dtb support in uboot)