No edit summary |
|||
| Line 131: | Line 131: | ||
==== Oddities: ==== | ==== Oddities: ==== | ||
Load script.bin at 0x43000000 | |||
| Line 224: | Line 224: | ||
==== Oddities: ==== | ==== Oddities: ==== | ||
Requires a signed kernel | Requires a signed kernel | ||
=== Arndale Board === | |||
==== Install Mechanism: ==== | |||
disk image | |||
==== Boot Loader:==== | |||
uboot (bootm w/ 0x40007000/0x42000000/0x41f00000 kernel/initramfs/dtb addrs) | |||
==== Media:==== | |||
mmcblk | |||
==== Partition layout: ==== | |||
/boot / | |||
==== File systems: ==== | |||
ext2 | |||
==== Special Packages: ==== | |||
==== Kernel: ==== | |||
kernel (unified) | |||
==== Console: ==== | |||
console=ttySAC2,115200n8 | |||
==== DTB Files: ==== | |||
exynos5250-arndale.dtb | |||
==== Oddities: ==== | |||
Revision as of 16:08, 27 April 2013
About
The idea behind this page is to describe the parameters for all the ARM systems we intend to support.
Systems
OMAP & AM335x
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
Special Packages:
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. Requires setting fdt_high and initrd_high to 0x2C000000 in uboot environment to boot.
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
Special Packages:
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)
Cubie Board
Install Mechanism:
disk image
Boot Loader:
uboot (bootm w/ 0x40300000/0x41600000/0x12345678 kernel/initramfs/dtb addrs)
Media:
mmcblk
Partition layout:
/boot /
File systems:
ext2
Special Packages:
Kernel:
kernel-??? (not unified)
Console:
console=ttyS0,115200
DTB Files:
Embedded in uboot
Oddities:
Load script.bin at 0x43000000
Highbank
Install Mechanism:
pxe
Boot Loader:
uboot (bootz)
Media:
scsi
Partition layout:
/boot /
File systems:
ext2 or ext3 /boot
Special Packages:
Kernel:
kernel (unified)
Console:
console=ttyAMA0
DTB Files:
Uses built-in
Oddities:
None.
Versatile Express
Install Mechanism:
disk image
Boot Loader:
None (qemu-system-arm)
Media:
mmcblk
Partition layout:
/boot / (/boot is optional)
File systems:
Any supported by kernel module in initramfs
Special Packages:
Kernel:
kernel (unified)
Console:
console=ttyAMA0,115200n8
DTB Files:
vexpress-v2p-ca9.dtb
Oddities:
This uses qemu to boot into either console mode or into X.
Chromebook
Install Mechanism:
Disk image with post processing
Boot Loader:
vboot
Media:
mmcblk or sda
Partition layout:
? (gpt)
File systems:
?
Special Packages:
?
Kernel:
kernel-lpae
Console:
?
DTB Files:
?
Oddities:
Requires a signed kernel
Arndale Board
Install Mechanism:
disk image
Boot Loader:
uboot (bootm w/ 0x40007000/0x42000000/0x41f00000 kernel/initramfs/dtb addrs)
Media:
mmcblk
Partition layout:
/boot /
File systems:
ext2
Special Packages:
Kernel:
kernel (unified)
Console:
console=ttySAC2,115200n8
DTB Files:
exynos5250-arndale.dtb