diff options
| -rw-r--r-- | Documentation/boards/mvebu.rst | 5 | ||||
| -rw-r--r-- | 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 42dcdb8c85..8e5612283e 100644 --- a/Documentation/boards/mvebu.rst +++ b/Documentation/boards/mvebu.rst @@ -36,7 +36,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 5bee03af9d..488af2d7ac 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. |