Add Yocto support for Juno development board: - add machine definition - add kernel configuration - add u-boot patch to get the environment from a file in flash - add trusted firmware extension to produce a firmware image - add ifupdown interfaces to start eth0 and eth1 on startup Change-Id: I5046166cf1cc9e80a57815ef6bfb0cbb263a704e Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>
1.9 KiB
Juno Development Platform Support in meta-arm-platforms
Howto Build and Run
Configuration:
In the local.conf file, MACHINE should be set as follow: MACHINE ?= "juno"
Build:
bash$ bitbake core-image-minimal
Update Juno SD card:
The SD card content is generated during the build here: tmp/deploy/images/juno/juno-oe-uboot.tar.gz
Its content must be written on the Juno firmware SD card. To do this:
-
extract the content of the tar file:
bash$ tar -xzf tmp/deploy/images/juno/juno-oe-uboot.tar.gz -
insert the sdcard of the Juno in an SD card reader and mount it:
bash$ sudo mount /dev/sdx1 /mnt(replace sdx by the device of the SD card) -
erase its content and put the new one:
bash$ sudo rm -rf /mnt/*bash$ sudo cp -rf juno-oe-uboot/* /mnt/.bash$ sudo umount /mnt -
reinsert the SD card in the Juno board
Create an USB hard drive:
Linux root file system should be stored on the second partition of an USB drive that must be plugged on the Juno Platform.
This partition should be initialized with the content of the filesystem generated by yocto that you can find here: tmp/deploy/images/juno/core-image-minimal-juno.tar.bz2
To do this
- Format a USB disk, create two primary partitions (ext4).
- mount the secondary partition
- untar tmp/deploy/images/juno/core-image-minimal-juno.tar.bz2 on to the secondary partition.
Run:
You must insert the SD card and the USB drive and power-on the Juno board. The console should be available on the second serial line: screen -L /dev/tty.usbserial 115200
On the first boot the images will be flashed which can take some time.
Devices supported in the kernel
- serial
- usb
- network
- watchdog
- rtc
- mmc
Untested:
- i2c
- dma
- pci
- sata
- sound
Devices not supported or not functional
- framebuffer: not functional The HDMI is not properly detected.
- GPU (no user land libraries). The mali-midgard-kernel can be used to have a kernel driver