[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 9/9] docs: aspeed: Add fby35 multi-SoC machine section
From: |
Peter Delevoryas |
Subject: |
Re: [PATCH v2 9/9] docs: aspeed: Add fby35 multi-SoC machine section |
Date: |
Wed, 6 Jul 2022 00:54:20 -0700 |
On Wed, Jul 06, 2022 at 07:58:44AM +0200, Cédric Le Goater wrote:
> On 7/5/22 21:14, Peter Delevoryas wrote:
> > Signed-off-by: Peter Delevoryas <peter@pjd.dev>
>
> Reviewed-by: Cédric Le Goater <clg@kaod.org>
>
> I fixed inline the URL links and moved the section at the end of the file.
>
> Thanks,
>
> C.
Thanks for that!
>
> > ---
> > docs/system/arm/aspeed.rst | 48 ++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 48 insertions(+)
> >
> > diff --git a/docs/system/arm/aspeed.rst b/docs/system/arm/aspeed.rst
> > index 5d0a7865d3..b233191b67 100644
> > --- a/docs/system/arm/aspeed.rst
> > +++ b/docs/system/arm/aspeed.rst
> > @@ -136,6 +136,54 @@ AST1030 SoC based machines :
> > - ``ast1030-evb`` Aspeed AST1030 Evaluation board (Cortex-M4F)
> > +Facebook Yosemite v3.5 Platform and CraterLake Server (``fby35``)
> > +==================================================================
> > +
> > +Facebook has a series of multi-node compute server designs named
> > +Yosemite. The most recent version released was
> > +`Yosemite v3
> > <https://www.opencompute.org/documents/ocp-yosemite-v3-platform-design-specification-1v16-pdf>`.
> > +
> > +Yosemite v3.5 is an iteration on this design, and is very similar: there's
> > a
> > +baseboard with a BMC, and 4 server slots. The new server board design
> > termed
> > +"CraterLake" includes a Bridge IC (BIC), with room for expansion boards to
> > +include various compute accelerators (video, inferencing, etc). At the
> > moment,
> > +only the first server slot's BIC is included.
> > +
> > +Yosemite v3.5 is itself a sled which fits into a 40U chassis, and 3 sleds
> > +can be fit into a chassis. See `here
> > <https://www.opencompute.org/products/423/wiwynn-yosemite-v3-server>`
> > +for an example.
> > +
> > +In this generation, the BMC is an AST2600 and each BIC is an AST1030. The
> > BMC
> > +runs `OpenBMC <https://github.com/facebook/openbmc>`, and the BIC runs
> > +`OpenBIC <https://github.com/facebook/openbic>`.
> > +
> > +Firmware images can be retrieved from the Github releases or built from the
> > +source code, see the README's for instructions on that. This image uses the
> > +"fby35" machine recipe from OpenBMC, and the "yv35-cl" target from OpenBIC.
> > +Some reference images can also be found here:
> > +
> > +.. code-block:: bash
> > +
> > + $ wget
> > https://github.com/facebook/openbmc/releases/download/openbmc-e2294ff5d31d/fby35.mtd
> > + $ wget
> > https://github.com/peterdelevoryas/OpenBIC/releases/download/oby35-cl-2022.13.01/Y35BCL.elf
> > +
> > +Since this machine has multiple SoC's, each with their own serial console,
> > the
> > +recommended way to run it is to allocate a pseudoterminal for each serial
> > +console and let the monitor use stdio. Also, starting in a paused state is
> > +useful because it allows you to attach to the pseudoterminals before the
> > boot
> > +process starts.
> > +
> > +.. code-block:: bash
> > +
> > + $ qemu-system-arm -machine fby35 \
> > + -drive file=fby35.mtd,format=raw,if=mtd \
> > + -device loader,file=Y35BCL.elf,addr=0,cpu-num=2 \
> > + -serial pty -serial pty -serial mon:stdio \
> > + -display none -S
> > + $ screen /dev/tty0 # In a separate TMUX pane, terminal window, etc.
> > + $ screen /dev/tty1
> > + $ (qemu) c # Start the boot process once screen is
> > setup.
> > +
> > Supported devices
> > -----------------
>