kumquat-buildroot/board/armadeus
Julien BOIBESSOT 612a349c06 configs/armadeus_apf51: bump Linux version to 5.10.215
Since the switch to binutils 2.41 as default version [1], the arm Linux
kernel build is broken with:

  arch/arm/mm/proc-v7.S: Assembler messages:
  arch/arm/mm/proc-v7.S:640: Error: junk at end of line, first unrecognized character is `#'

A similar issue has already be fixed for qemu m68k [2].

Bump to the latest kernel 5.10 that already include the backport
of 790756c7e022 ("ARM: 8933/1: replace Sun/Solaris style flag on section directive")

Select BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y to fix the following
build error:

  scripts/extract-cert.c:21:25: fatal error: openssl/bio.h: No such file or directory
  #include <openssl/bio.h>

[1] e88225ed88
[2] a1ce9474e4

Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/6655119389

Signed-off-by: Julien BOIBESSOT <julien.boibessot@armadeus.com>
[Romain:
  - improve commit log
  - Select BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL
]
Signed-off-by: Romain Naour <romain.naour@smile.fr>
2024-04-30 23:34:43 +02:00
..
apf27
apf51
readme.txt

Introduction
============

Armadeus APFxx are Systems On Module (SOM) based on Freescale/NXP i.MX
processors associated with an FPGA (except on APF28). Non volatile
data are stored in on-module NOR or NAND Flash, depending on the
model. These SOM can be used on Armadeus development boards or with
custom docking boards.

Supported platforms
===================

Buildroot currently supports the following Armadeus platforms with the
associated defconfigs:

 * APF27 SOM + devt board    -> armadeus_apf27_defconfig
 * APF51 SOM + devt board    -> armadeus_apf51_defconfig
 * APF28 SOM + devt board    -> armadeus_apf28_defconfig

Vanilla Linux versions are preferred to Freescale's one in these
configurations.

How to build it
===============

Configure Buildroot
-------------------

Let's say you own an APFxx SOM with it's corresponding development
board, all you have to do is:

  $ make armadeus_apfxx_defconfig

where "apfxx" is the version of your SOM.

Launch build
------------

  $ make

Result of the build
-------------------

When the build is finished, you will end up with:

    output/images/
    +-- imx**-apfxxdev.dtb	[1]
    +-- rootfs.tar
    +-- rootfs.ubi
    +-- rootfs.ubifs
    +-- uImage

[1] Only if the kernel version used uses a Device Tree.

Building U-Boot is currently not supported in these configurations.

Installation
============

You will require a serial connection to the board and a TFTP server on
your Host PC. Assuming your server is configured for exporting
/tftpboot/ directory, you will have to copy the generated images to
it:

  $ cp output/images/uImage /tftpboot/apfxx-linux.bin
  $ cp output/images/*.dtb /tftpboot/
  $ cp output/images/rootfs.ubi /tftpboot/apfxx-rootfs.ubi

where "apfxx" is the version of your SOM, as used with _defconfigs.

Then on your serial terminal, all you have to do is:

* interrupt the boot process and access U-Boot console by pressing any
  key when booting,
* configure board and server IP addresses with "ipaddr" and "serverip"
  environment variables,
* if you want to update kernel:
  BIOS > run update_kernel
* if you want to update device tree:
  BIOS > run update_dtb
* if you want to update rootfs:
  BIOS > run update_rootfs

That's it !