[PATCH 1/2] docs: mvebu can do 2nd stage booting

[PATCH 1/2] docs: mvebu can do 2nd stage booting

[Uwe Kleine-König]

Since commit

	823d08e3e261 ("kwbimage_v1: add support to boot a mvebu image")

barebox can use bootm to load a 2nd barebox image. Update the
documentation accordingly.

Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
---
 Documentation/boards/mvebu.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/boards/mvebu.rst b/Documentation/boards/mvebu.rst
index b4f8e6043dac..4dfdc4a8f761 100644
--- a/Documentation/boards/mvebu.rst
+++ b/Documentation/boards/mvebu.rst
@@ -28,8 +28,8 @@ initialisation that could be taken.
 Booting second stage
 --------------------
 
-This is currently not possible because barebox assumes the registers are mapped
-at 0xd0000000 as is the case when the boot ROM gives control to the bootloader.
+Since ``v2017.04.0`` barebox can boot a barebox image even if the register
+window is moved. This is implemented by writing the actual window position into the image where it is then picked up by the second stage bootloader.
 
 Booting from UART
 -----------------
-- 
2.11.0


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

[PATCH 2/2] docs: move kwboot description to generic mvebu section

[Uwe Kleine-König]

Expand the generic part about kwboot to the mvebu page and advertise the
parameter -n to make it simpler to boot some machines.

Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
---
 Documentation/boards/mvebu.rst                       |  5 ++++-
 Documentation/boards/mvebu/Netgear-ReadyNAS-2120.rst | 13 ++-----------
 2 files changed, 6 insertions(+), 12 deletions(-)

diff --git a/Documentation/boards/mvebu.rst b/Documentation/boards/mvebu.rst
index 4dfdc4a8f761..18a5c150bb95 100644
--- a/Documentation/boards/mvebu.rst
+++ b/Documentation/boards/mvebu.rst
@@ -35,7 +35,10 @@ Booting from UART
 -----------------
 
 The mvebu SoCs support booting from UART. For this there is a tool available in
-barebox called kwboot.
+barebox called ``kwboot``. Quite some mvebu boards are reset once more when
+they already started to read the first block of the image to boot. If you want
+to boot such a board, use the parameter ``-n 15`` for ``kwboot``. (The number
+might have to be adapted per board.)
 
 mvebu boards
 ------------
diff --git a/Documentation/boards/mvebu/Netgear-ReadyNAS-2120.rst b/Documentation/boards/mvebu/Netgear-ReadyNAS-2120.rst
index 5bee03af9d38..488af2d7acfe 100644
--- a/Documentation/boards/mvebu/Netgear-ReadyNAS-2120.rst
+++ b/Documentation/boards/mvebu/Netgear-ReadyNAS-2120.rst
@@ -6,14 +6,5 @@ This is a rack mountable 4 bay NAS using an Armada XP dual-core processor.
 UART booting
 ------------
 
-The first UART hides behind a sticker on 4 pins.
-
-The machine seems to do two resets at power on which makes UART booting hard. A
-trick to work around this is::
-
-  scripts/kwboot -d /dev/ttyUSB0; kwboot -b images/barebox-netgear-rn2120.img -t /dev/ttyUSB0
-
-This way the first window in which the CPU accepts the magic string is taken by
-the first invokation which blocks until the second reset happens. The second
-window is then hit with the image to boot. This is not 100% reliable but works
-most of the time.
+The UART that can be used to boot via RS232 (using ``kwboot``) hides behind a
+sticker on the backside of the machine. It uses TTL levels.
-- 
2.11.0


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: [PATCH 1/2] docs: mvebu can do 2nd stage booting

[Sascha Hauer]

On Fri, Jun 02, 2017 at 08:22:03PM +0200, Uwe Kleine-König wrote:
> Since commit
> 
> 	823d08e3e261 ("kwbimage_v1: add support to boot a mvebu image")
> 
> barebox can use bootm to load a 2nd barebox image. Update the
> documentation accordingly.
> 
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
>  Documentation/boards/mvebu.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/boards/mvebu.rst b/Documentation/boards/mvebu.rst
> index b4f8e6043dac..4dfdc4a8f761 100644
> --- a/Documentation/boards/mvebu.rst
> +++ b/Documentation/boards/mvebu.rst
> @@ -28,8 +28,8 @@ initialisation that could be taken.
>  Booting second stage
>  --------------------
>  
> -This is currently not possible because barebox assumes the registers are mapped
> -at 0xd0000000 as is the case when the boot ROM gives control to the bootloader.
> +Since ``v2017.04.0`` barebox can boot a barebox image even if the register
> +window is moved. This is implemented by writing the actual window position into the image where it is then picked up by the second stage bootloader.

Applied with an additional line break, thanks

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox