From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 5348FC433F5 for ; Thu, 16 Dec 2021 17:55:50 +0000 (UTC) Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 4918C8304A; Thu, 16 Dec 2021 18:55:45 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=fail (p=none dis=none) header.from=arm.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Received: by phobos.denx.de (Postfix, from userid 109) id BB1618303C; Thu, 16 Dec 2021 18:55:39 +0100 (CET) Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by phobos.denx.de (Postfix) with ESMTP id 5F91780335 for ; Thu, 16 Dec 2021 18:55:34 +0100 (CET) Authentication-Results: phobos.denx.de; dmarc=pass (p=none dis=none) header.from=arm.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=andre.przywara@arm.com Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 867031435; Thu, 16 Dec 2021 09:55:33 -0800 (PST) Received: from donnerap.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 6A1863F774; Thu, 16 Dec 2021 09:55:32 -0800 (PST) Date: Thu, 16 Dec 2021 17:55:27 +0000 From: Andre Przywara To: Sudeep Holla Cc: Simon Glass , Tom Rini , Linus Walleij , u-boot@lists.denx.de, Peter Hoyes , Liviu Dudau , David Feng Subject: Re: [PATCH 2/2] doc: add Arm Juno board documentation Message-ID: <20211216175527.3ad944ed@donnerap.cambridge.arm.com> In-Reply-To: <20211215124416.nflvqibpfnr4376k@bogus> References: <20211214175539.3173701-1-andre.przywara@arm.com> <20211214175539.3173701-3-andre.przywara@arm.com> <20211215124416.nflvqibpfnr4376k@bogus> Organization: ARM X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; aarch64-unknown-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.38 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.2 at phobos.denx.de X-Virus-Status: Clean On Wed, 15 Dec 2021 12:44:16 +0000 Sudeep Holla wrote: Hi Sudeep, > On Tue, Dec 14, 2021 at 05:55:39PM +0000, Andre Przywara wrote: > > The Juno Arm development board is an open, vendor-neutral, Armv8-A > > development platform. > > Add documentation that briefly outlines the hardware, and describes > > building and installation of U-Boot. > > > > Signed-off-by: Andre Przywara > > --- > > doc/board/armltd/index.rst | 1 + > > doc/board/armltd/juno.rst | 117 +++++++++++++++++++++++++++++++++++++ > > 2 files changed, 118 insertions(+) > > create mode 100644 doc/board/armltd/juno.rst > > > > diff --git a/doc/board/armltd/index.rst b/doc/board/armltd/index.rst > > index caa6fd2bb0..68d938c647 100644 > > --- a/doc/board/armltd/index.rst > > +++ b/doc/board/armltd/index.rst > > @@ -8,3 +8,4 @@ ARM Ltd. boards and emulated systems > > :maxdepth: 2 > > > > fvp64 > > + juno > > diff --git a/doc/board/armltd/juno.rst b/doc/board/armltd/juno.rst > > new file mode 100644 > > index 0000000000..f37bc2c78e > > --- /dev/null > > +++ b/doc/board/armltd/juno.rst > > @@ -0,0 +1,117 @@ > > +.. SPDX-License-Identifier: GPL-2.0 > > +.. Copyright (C) 2021 Arm Ltd. > > + > > +Arm Juno board > > +============== > > + > > +The `Juno development board`_ is an open, vendor-neutral, Armv8-A > > +development platform, made by Arm Ltd. It is based on the former Versatile > > +Express series. > > +There are three revisions of the board: > > + > > +* Juno r0, with two Cortex-A57 and four Cortex-A53 cores, without PCIe. > > +* Juno r1, with two Cortex-A57 and four Cortex-A53 cores, in later silicon > > + revisions, and with PCIe slots, Gigabit Ethernet and two SATA ports. > > +* Juno r2, with two Cortex-A72 and four Cortex-A53 cores, otherwise the > > + same as r1. > > + > > +Among other things, the motherboard contains a management controller (MCP), > > IIRC the MCP is new and inside the SoC. You may refer [1], [2] and use the > terminologies from there to be consistent with the documentation. IIRC this > one is referred as MCC. So I would prefer s/MCP/MCC or MB throughout this > document. True, I managed to mix that up, thanks for pointing this out! > > +an FPGA providing I/O interfaces (IOFPGA) and 64MB of NOR flash. The provided > > +platform devices resemble the VExpress peripherals. > > +The actual SoC also contains a Cortex-M3 based System Control Processor (SCP). > > + > > +U-Boot build > > +------------ > > +There is only one defconfig and one binary build that covers all three board > > +revisions, so to generate the needed ``u-boot.bin``: > > + > > +.. code-block:: bash > > + > > + $ make vexpress_aemv8a_juno_defconfig > > + $ make > > + > > +The automatic distro boot sequence looks for UEFI boot applications and > > +``boot.scr`` scripts on various boot media, starting with USB, then on disks > > +connected to the two SATA ports, PXE, DHCP and eventually on the NOR flash. > > + > > +U-Boot installation > > +------------------- > > +This assumes there is some firmware on the SD card or NOR flash (see below > > +for more details). The U-Boot binary is included in the Trusted Firmware > > +FIP image, so after building U-Boot, this needs to be repackaged or recompiled. > > + > > +The NOR flash will be updated by the MCP, based on the content of a micro-SD > > +card, which will be exported as a USB mass storage device via the rear USB-B > > +socket. So to access that SD card, connect a USB-A->USB-B cable between some > > +host computer and the board, and mount the FAT partition on the UMS device. > > +If there is no device, check the upper serial port for a prompt, and > > +explicitly enable the USB interface:: > > + > > + Cmd> usb_on > > + Enabling debug USB... > > + > > Not sure if you need these details(above one paragraph) here if we can direct > to one of the pages I have pointed out or specifically [3]. I guess you can > add other topics from there and links to those subsections if you need more > details. I am fine either way. Yeah, I will add a link to the Juno TRM, and refer to that. But at least on the Linux side I have seen pushback against deep links to manufacturer websites in documentation, since those URLs tend to 404 sooner or later. So I am tempted to keep at least that usb_on command in, since I needed to use that at times, and it's a quick solution to a common problem. Thanks for your comments! Andre