< Architectures | ARM
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
==== Boot Loader:==== | ==== Boot Loader:==== | ||
u-boot | u-boot with bootz | ||
==== Media:==== | ==== Media:==== | ||
| Line 27: | Line 27: | ||
==== DTB Files: ==== | ==== DTB Files: ==== | ||
Device tree loading prevents boot | |||
==== Odities: ==== | ==== Odities: ==== | ||
| Line 37: | Line 38: | ||
==== Boot Loader:==== | ==== Boot Loader:==== | ||
u-boot | u-boot with bootz | ||
==== Media:==== | ==== Media:==== | ||
| Line 51: | Line 52: | ||
==== DTB Files: ==== | ==== DTB Files: ==== | ||
tegra20-trimslice.dtb | |||
==== Odities: ==== | ==== Odities: ==== | ||
Revision as of 01:41, 26 April 2013
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
DTB Files:
Device tree loading prevents boot
Odities:
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:
DTB Files:
tegra20-trimslice.dtb
Odities:
sata disk is connected via usb to sata bridge requiring "usb" bootloader commands