summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorUwe Kleine-König <u.kleine-koenig@pengutronix.de>2017-06-30 11:51:45 +0200
committerSascha Hauer <s.hauer@pengutronix.de>2017-06-30 13:33:27 +0200
commite2de305f11864a92cd1ce6ce6a7a42f098f754b6 (patch)
tree950a3d614ff4fe27f56ed6a305feb4d158c8b622
parentd6fce00c3b5c6a039c1d8515c20f62cead19a762 (diff)
downloadbarebox-e2de305f11864a92cd1ce6ce6a7a42f098f754b6.tar.gz
barebox-e2de305f11864a92cd1ce6ce6a7a42f098f754b6.tar.xz
docs: mvebu: describe -n more accurately in the sphinx document
Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
-rw-r--r--Documentation/boards/mvebu.rst12
1 files changed, 9 insertions, 3 deletions
diff --git a/Documentation/boards/mvebu.rst b/Documentation/boards/mvebu.rst
index 8e5612283..b28fd443b 100644
--- a/Documentation/boards/mvebu.rst
+++ b/Documentation/boards/mvebu.rst
@@ -37,9 +37,15 @@ Booting from UART
The mvebu SoCs support booting from UART. For this there is a tool available in
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.)
+they already started to read the first block of the image to boot which
+obviously results in a failure to boot this image. If you want to boot such a
+board, use the parameter ``-n 15`` for ``kwboot`` to delay uploading the image
+and try to hit the right (i.e. second) window harder.
+(The number might have to be adapted per board. The semantic is that the magic
+string is sent until the 15th NAK is seen and only then the image is sent.) A
+typical commandline is:
+
+ kwboot -b barebox.img -n 15 -B 115200 -t /dev/ttyUSB
mvebu boards
------------