From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from asavdk3.altibox.net ([109.247.116.14]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1hBNks-0003Kh-IP for barebox@lists.infradead.org; Tue, 02 Apr 2019 18:03:27 +0000 Date: Tue, 2 Apr 2019 20:03:23 +0200 From: Sam Ravnborg Message-ID: <20190402180323.GF18142@ravnborg.org> References: <20190401101822.7392-1-a.fatoum@pengutronix.de> <20190401101822.7392-16-a.fatoum@pengutronix.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20190401101822.7392-16-a.fatoum@pengutronix.de> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "barebox" Errors-To: barebox-bounces+u.kleine-koenig=pengutronix.de@lists.infradead.org Subject: Re: [PATCH v3 15/15] doc: microchip-ksz9477-evb: add documentation To: Ahmad Fatoum Cc: barebox@lists.infradead.org Hi Ahmad. Thanks for adding the docs. On Mon, Apr 01, 2019 at 12:18:23PM +0200, Ahmad Fatoum wrote: > Signed-off-by: Ahmad Fatoum > --- > .../boards/at91/microchip-ksz9477-evb.rst | 38 ++++++++++++++++++- > 1 file changed, 36 insertions(+), 2 deletions(-) > > diff --git a/Documentation/boards/at91/microchip-ksz9477-evb.rst b/Documentation/boards/at91/microchip-ksz9477-evb.rst > index 4c4c4aecbfb3..2a68c2a552cd 100644 > --- a/Documentation/boards/at91/microchip-ksz9477-evb.rst > +++ b/Documentation/boards/at91/microchip-ksz9477-evb.rst > @@ -1,11 +1,45 @@ > Microchip KSZ 9477 Evaluation board > =================================== > > -This is an evaluation board for a switch that uses the at91sam9x5 CPU. > +This is an evaluation board for the KSZ9477 switch that uses the sama5d36 CPU. > The board uses Device Tree and supports multi image. > > -Building barebox: > +Building barebox as second stage bootloader: > > .. code-block:: sh > > make ARCH=arm microchip_ksz9477_evb_defconfig > + > +There are also a separate defconfig for operating barebox as first stage > +bootloader originating from SD Card. > +This configuration doesn't yet support device-tree use as the NVM bootloader > +(SoC ROM code) requires the first stage bootloader to fit into 64K. > + > +Generally, the first stage may comes from any of the following boot > +sources (in that order): > + > +* SPI0 CS0 Flash > +* SD Card > +* NAND Flash > +* SPI0 CS1 Flash > +* I2C EEPROM > + > +After being loaded into SRAM by the NVM bootloader, the first stage does low > +level clock initialization, configuration of the DDRAM controller and > +bootstraps the second stage boot loader. > + > +SD Card Bootstrap > +----------------- > + > +For boot from SD card, barebox additionally needs to be configured as > +first stage bootloader: > + > +.. code-block:: sh > + > + make ARCH=arm microchip_ksz9477_evb_bootstrap_mmc_defconfig > + > +The resulting barebox image must be renamed to ``BOOT.BIN`` When I am away from barebox development for some weeks I always have troubles what it the right file to use. I suggest to use specific filename rather than the vauge "resulting barebox image". Sam _______________________________________________ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox