[PATCH 1/9] doc: board: enclustra: add Enclustra Intel AA1 SoM

[Lothar Rubusch]

On Fri, Sep 13, 2024 at 1:11 AM Marek Vasut <marex at denx.de> wrote:
>
> On 9/12/24 8:06 AM, Lothar Rubusch wrote:
> [...]
>
> > +Mercury AA1 Module (Arria1 10)
> > +==============================
> > +
> > +- SoM: https://www.enclustra.com/en/products/system-on-chip-modules/mercury-aa1/
> > +- Carrier board Mercury+ ST1: https://www.enclustra.com/en/products/base-boards/mercury-st1/
> > +- Carrier board Mercury+ PE1: https://www.enclustra.com/en/products/base-boards/mercury-pe1-200-300-400/
> > +- Carrier board Mercury+ PE3: https://www.enclustra.com/en/products/base-boards/mercury-pe3/
> > +
> > +There are slightly different variants of the AA1 SoM, going by the identifier.
> > +
> > +- Me-aa1-270-2i2-d11e-nfx3
> > +- Me-aa1-270-3e4-d11e-nfx3
> > +- Me-aa1-480-2i3-d12e-nfx3
> > +
> > +The u-boot setup is specific to a quartus design. Generate handoff files from
> > +the design. Pass them to a python script to produce a handoff.h file. This is
> > +needed as input for building the device-tree for u-boot. Eventually, building
> > +the final u-boot depends on the particular Quartus design, the particular
> > +carrier board, the selected boot media and boot mode.
> > +
> > +Enclustra provides reference design examples which can be built with yocto
> > +using their meta-layer.
> > +
> > +- Reference Design AA1 on ST1: https://github.com/enclustra/Mercury_AA1_ST1_Reference_Design
> > +- Reference Design AA1 on PE1: https://github.com/enclustra/Mercury_AA1_PE1_Reference_Design
> > +- Reference Design AA1 on PE3: https://github.com/enclustra/Mercury_AA1_PE3_Reference_Design
> > +- Yocto meta-layer: https://github.com/enclustra/meta-enclustra-socfpga
>
> OpenEmbedded .
>

Ok

> > +Quick Start
> > +-----------
> > +
> > +- Setup and build a Quartus design project
> > +- Obtain the hps.xml file from the Quartus design project
> > +- Generate the handoff.h file for u-boot
> > +- Adjust the device-tree file according to your setup
> > +- Build u-boot
> > +- Flash u-boot
> > +
> > +Build U-Boot
> > +------------
> > +
> > +The Quartus design produces a design specific ``hps.xml``, an ``emif.xml`` and
> > +a corresponding ``id`` file contained in a folder ``handoff``.
>
> s at folder@directory@ on unix systems.
>

Ok

> [...]
>
> > +.. code-block:: bash
> > +
> > +    $ sudo fdisk /dev/sda
> > +        n,p,1,2048,+20M
> > +        t,1,c
> > +        n,p,2,409600,+1M
> > +        t,2,a2
> > +        n,p,3,425984,<REST>
> > +        t,3,83
> > +        w
>
> Have a look at 'sfdisk' tool, scriptable fdisk , that is preferable .
>

Ok, ich changed it using sfdisk

> [...]
>
> > +Boot Media
> > +----------
> > +
> > +Alternative boot media are possible as officially documented by Enclustra.
> > +
> > +* Micro-SD card
> > +* eMMC
> > +* QSPI
> > +
> > +NB: eMMC and QSPI can be flashed from off the u-boot shell. Usually after
>
> What does 'NB:' stand for ?
>

I'll change this for "Note:"

> > +flashing, the coorect boot mode needs to be set by a BSEL switch. Approaches
> > +are described consistently in the offical Enclustra documentation according to
>
> "official", typo, run the docs through e.g. aspell to catch those typos.
>

Thank you for the review and the hints. I'll apply the changes in the
next version of this set.

> [...]