From Fedora Project Wiki
(Created page with "Lately, I got a shiny new Wandboard Quad into my fingers, and it's "enabled hardware" on Fedora 20. I took a TC4 test build from http://koji.fedoraproject.org/koji/taskinfo?t...") |
(beta tc2) |
||
| (12 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
Wandboard Quad belongs to "enabled hardware" in Fedora 20. | |||
from http:// | Take the Beta TC2 build from http://dl.fedoraproject.org/pub/alt/stage/20-Beta-TC2/Images/armhfp/Fedora-Minimal-armhfp-20-Beta-TC2-sda.raw.xz | ||
wget http:// | wget http://dl.fedoraproject.org/pub/alt/stage/20-Beta-TC2/Images/armhfp/Fedora-Minimal-armhfp-20-Beta-TC2-sda.raw.xz \ | ||
xzcat Fedora-Minimal-armhfp-20-Alpha- | http://dl.fedoraproject.org/pub/alt/stage/20-Beta-TC2/Images/armhfp/Fedora-Images-armhfp-20-Beta-TC2-CHECKSUM | ||
sha256sum -c Fedora-Images-armhfp-20-Beta-TC2-CHECKSUM | |||
... | |||
xzcat Fedora-Minimal-armhfp-20-Alpha-2-sda.raw.xz | sudo dd of=/dev/mmcblk0 bs=4M conv=fsync | |||
sudo sync | sudo sync | ||
Sadly, it's not bootable by default, we need to write a bootblock. From the package uboot-wandboard_quad, we'll take the file | Sadly, it's not bootable by default, we need to write a bootblock. | ||
From the package uboot-wandboard_quad, we'll take the file | |||
/usr/share/uboot-imx6quad/u-boot.imx | |||
/ | wget http://kojipkgs.fedoraproject.org/packages/uboot-tools/2013.10/0.5.rc4.fc20/armv7hl/uboot-wandboard_quad-2013.10-0.5.rc4.fc20.armv7hl.rpm | ||
rpm2cpio uboot-wandboard_quad-2013.10-0.5.rc4.fc20.armv7hl.rpm | cpio -idv | |||
and dd it to the sdcard: | and dd it to the sdcard: | ||
sudo dd if=u-boot.imx of=/dev/mmcblk0 bs=1k seek=1 | sudo dd if=./usr/share/uboot-imx6quad/u-boot.imx of=/dev/mmcblk0 bs=1k seek=1 | ||
sudo sync | sudo sync | ||
Place the flattened Device Tree Blob in the correct location | |||
from the boot filesystem: | |||
mkdir dtb | |||
cp dtb-3.11.3-301.fc20.armv7hl/imx6q-wandboard.dtb dtb/. | |||
Currently, the image creation has a known bug: extlinux.conf is missing, though we create one by hand and write it to /boot/extlinux/extlinux.conf on the sdcard: : | Currently, the image creation has a known bug: extlinux.conf is missing, though we create one by hand and write it to /boot/extlinux/extlinux.conf on the sdcard: : | ||
# extlinux.conf generated by anaconda | # extlinux.conf generated by anaconda | ||
ui menu.c32 | #ui menu.c32 | ||
menu autoboot Welcome to Fedora. Automatic boot in # second{,s}. Press a key for options. | menu autoboot Welcome to Fedora. Automatic boot in # second{,s}. Press a key for options. | ||
menu title Fedora Boot Options. | #menu title Fedora Boot Options. | ||
menu hidden | #menu hidden | ||
timeout 60 | timeout 60 | ||
#totaltimeout 9000 | #totaltimeout 9000 | ||
label Fedora (3.11. | label Fedora (3.11.3-301.fc20.armv7hl) 20 (Null) | ||
kernel /vmlinuz-3.11.3-301.fc20.armv7hl | |||
append console=ttymxc0,115200 root=UUID=e72ec2c4-bd9e-4100-85be-df34e7f01e53 ro rhgb quiet LANG=en_US.UTF-8 | |||
fdt /dtb/imx6q-wandboard.dtb | |||
initrd /initramfs-3.11.3-301.fc20.armv7hl.img | |||
Finally, we'd need to update the UUID of the root partition: | Finally, we'd need to update the UUID of the root partition: | ||
blkid /dev/mmcblk0p3 | sudo blkid -ovalue -sUUID /dev/mmcblk0p3 | ||
will report the name of the partition and the UUID, which we'd need to insert to the kernel append line in extlinux.conf | |||
The above will report the name of the partition and the UUID, which we'd need to insert to the kernel append line in extlinux.conf | |||
Also ensure the same UUID is in the /etc/fstab of the rootfs. | |||
Now you are ready to boot, follow these steps | |||
* Insert the micro SDCard to the card reader on the EDM system module (directly below the heat sink). | |||
** There are two micro SDcard slots, the Freescale EDM system-on-module board, and the carrier board. | |||
* connect the serial cable (DB9 female). | |||
* Connect the power supply (5 volt, 3 amp). | |||
Maybe you'd need to type boot, when you're dropped to the uboot prompt. | Maybe you'd need to type boot, when you're dropped to the uboot prompt. | ||
boot | |||
Latest revision as of 08:05, 10 October 2013
Wandboard Quad belongs to "enabled hardware" in Fedora 20. Take the Beta TC2 build from http://dl.fedoraproject.org/pub/alt/stage/20-Beta-TC2/Images/armhfp/Fedora-Minimal-armhfp-20-Beta-TC2-sda.raw.xz
wget http://dl.fedoraproject.org/pub/alt/stage/20-Beta-TC2/Images/armhfp/Fedora-Minimal-armhfp-20-Beta-TC2-sda.raw.xz \ http://dl.fedoraproject.org/pub/alt/stage/20-Beta-TC2/Images/armhfp/Fedora-Images-armhfp-20-Beta-TC2-CHECKSUM sha256sum -c Fedora-Images-armhfp-20-Beta-TC2-CHECKSUM ... xzcat Fedora-Minimal-armhfp-20-Alpha-2-sda.raw.xz | sudo dd of=/dev/mmcblk0 bs=4M conv=fsync sudo sync
Sadly, it's not bootable by default, we need to write a bootblock. From the package uboot-wandboard_quad, we'll take the file /usr/share/uboot-imx6quad/u-boot.imx
wget http://kojipkgs.fedoraproject.org/packages/uboot-tools/2013.10/0.5.rc4.fc20/armv7hl/uboot-wandboard_quad-2013.10-0.5.rc4.fc20.armv7hl.rpm rpm2cpio uboot-wandboard_quad-2013.10-0.5.rc4.fc20.armv7hl.rpm | cpio -idv
and dd it to the sdcard:
sudo dd if=./usr/share/uboot-imx6quad/u-boot.imx of=/dev/mmcblk0 bs=1k seek=1 sudo sync
Place the flattened Device Tree Blob in the correct location from the boot filesystem:
mkdir dtb cp dtb-3.11.3-301.fc20.armv7hl/imx6q-wandboard.dtb dtb/.
Currently, the image creation has a known bug: extlinux.conf is missing, though we create one by hand and write it to /boot/extlinux/extlinux.conf on the sdcard: :
# extlinux.conf generated by anaconda
#ui menu.c32
menu autoboot Welcome to Fedora. Automatic boot in # second{,s}. Press a key for options.
#menu title Fedora Boot Options.
#menu hidden
timeout 60
#totaltimeout 9000
label Fedora (3.11.3-301.fc20.armv7hl) 20 (Null)
kernel /vmlinuz-3.11.3-301.fc20.armv7hl
append console=ttymxc0,115200 root=UUID=e72ec2c4-bd9e-4100-85be-df34e7f01e53 ro rhgb quiet LANG=en_US.UTF-8
fdt /dtb/imx6q-wandboard.dtb
initrd /initramfs-3.11.3-301.fc20.armv7hl.img
Finally, we'd need to update the UUID of the root partition:
sudo blkid -ovalue -sUUID /dev/mmcblk0p3
The above will report the name of the partition and the UUID, which we'd need to insert to the kernel append line in extlinux.conf Also ensure the same UUID is in the /etc/fstab of the rootfs.
Now you are ready to boot, follow these steps
- Insert the micro SDCard to the card reader on the EDM system module (directly below the heat sink).
- There are two micro SDcard slots, the Freescale EDM system-on-module board, and the carrier board.
- connect the serial cable (DB9 female).
- Connect the power supply (5 volt, 3 amp).
Maybe you'd need to type boot, when you're dropped to the uboot prompt.
boot