Bump buildroot to 2020.11-rc1 (#985)
* Update buildroot-patches for 2020.11-rc1 buildroot * Update buildroot to 2020.11-rc1 Signed-off-by: Stefan Agner <stefan@agner.ch> * Don't rely on sfdisk --list-free output The --list-free (-F) argument does not allow machine readable mode. And it seems that the output format changes over time (different spacing, using size postfixes instead of raw blocks). Use sfdisk json output and calculate free partition space ourselfs. This works for 2.35 and 2.36 and is more robust since we rely on output which is meant for scripts to parse. * Migrate defconfigs for Buildroot 2020.11-rc1 In particular, rename BR2_TARGET_UBOOT_BOOT_SCRIPT(_SOURCE) to BR2_PACKAGE_HOST_UBOOT_TOOLS_BOOT_SCRIPT(_SOURCE). * Rebase/remove systemd patches for systemd 246 * Drop apparmor/libapparmor from buildroot-external * hassos-persists: use /run as directory for lockfiles The U-Boot tools use /var/lock by default which is not created any more by systemd by default (it is under tmpfiles legacy.conf, which we no longer install). * Disable systemd-update-done.service The service is not suited for pure read-only systems. In particular the service needs to be able to write a file in /etc and /var. Remove the service. Note: This is a static service and cannot be removed using systemd-preset. * Disable apparmor.service for now The service loads all default profiles. Some might actually cause problems. E.g. the profile for ping seems not to match our setup for /etc/resolv.conf: [85503.634653] audit: type=1400 audit(1605286002.684:236): apparmor="DENIED" operation="open" profile="ping" name="/run/resolv.conf" pid=27585 comm="ping" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
This commit is contained in:
@@ -12,32 +12,14 @@ through the serial console.
|
||||
How to build
|
||||
============
|
||||
|
||||
There are two build options: mainline support and vendor support.
|
||||
Default configuration provides the following BSP versions:
|
||||
- Linux v5.6.3 (mainline)
|
||||
- U-Boot v2020.01 (mainline)
|
||||
- ATF v1.5-18.12.2 (Marvell)
|
||||
|
||||
For the mainline BSP, we use:
|
||||
- Linux v4.19.2
|
||||
- U-Boot v2018.11
|
||||
To build images run the following commands:
|
||||
|
||||
For the vendor BSP, we use the sources available from Marvell Github
|
||||
page at https://github.com/MarvellEmbeddedProcessors, which uses:
|
||||
- Linux v4.4.120
|
||||
- U-Boot v2018.03
|
||||
|
||||
At the moment mainline support for the board is a work in
|
||||
progress. Mainline kernel 4.19 enables eth2 in 1Gb (RJ45 connector J5),
|
||||
copper 10Gb interfaces, and automatic configuration of select SFP
|
||||
modules on the SFP cages. The vendor BSP enables more hardware features
|
||||
out of the box, but lacks support for SFP detection and automatic
|
||||
configuration.
|
||||
|
||||
To use the mainline BSP run the following commands:
|
||||
|
||||
$ make solidrun_macchiatobin_mainline_defconfig
|
||||
$ make
|
||||
|
||||
To use the vendor BSP run the following commands:
|
||||
|
||||
$ make solidrun_macchiatobin_marvell_defconfig
|
||||
$ make solidrun_macchiatobin_defconfig
|
||||
$ make
|
||||
|
||||
How to write the SD card
|
||||
@@ -74,13 +56,15 @@ Insert the micro SDcard in the MacchiatoBin board and power it up.
|
||||
The serial console is accessible at the micro-USB Type-B connector
|
||||
marked CON9. The serial line settings are 115200 8N1.
|
||||
|
||||
Note: the following text only applies to the vendor BSP from
|
||||
solidrun_macchiatobin_marvell_defconfig.
|
||||
U-Boot environment
|
||||
==================
|
||||
|
||||
By default Marvell provided U-Boot will load its environment from the
|
||||
SPI flash. On the first boot SPI flash may be empty or it may contain a
|
||||
legacy environment that prevents proper boot. Then the following
|
||||
commands can be used to boot the board:
|
||||
By default current configuration provides U-Boot that keeps environment
|
||||
in SD/eMMC. However, if needed, u-boot-fragment.config can be tweaked
|
||||
so that U-Boot will keep environment in SPI flash. On the first boot
|
||||
SPI flash may be empty or it may contain a stale environment that
|
||||
prevents proper boot. Then the following commands can be used
|
||||
to boot the board:
|
||||
|
||||
=> ext4load mmc 1:1 0x01700000 /boot/uEnv-example.txt
|
||||
=> env import -t 0x01700000 $filesize
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
setenv finduuid "part uuid mmc 0:1 uuid"
|
||||
setenv finduuid "part uuid mmc 1:1 uuid"
|
||||
run finduuid
|
||||
run findfdt
|
||||
setenv bootargs "console=ttymxc0,115200 root=PARTUUID=${uuid} rootwait rootfstype=ext4"
|
||||
load mmc 0:1 ${fdt_addr} boot/${fdtfile}
|
||||
load mmc 0:1 ${loadaddr} boot/zImage
|
||||
load mmc 1:1 ${fdt_addr} boot/${fdtfile}
|
||||
load mmc 1:1 ${loadaddr} boot/zImage
|
||||
bootz ${loadaddr} - ${fdt_addr}
|
||||
|
||||
Reference in New Issue
Block a user