From e4ea72fe47249fa17b6fd64b03bc26734f6dd746 Mon Sep 17 00:00:00 2001 From: Xavier Ruppen Date: Sun, 16 Oct 2016 13:00:59 +0200 Subject: [PATCH] README: enlgish --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index df3e886..dd4dc84 100644 --- a/README.md +++ b/README.md @@ -3,7 +3,7 @@ Synology's U-boot for the DS211j "modified" to load a uImage by tftp instead of This document describes a very hacky process I came up with to create and flash a new U-Boot on the DS211j. # toolchain -Syno's U-Boot barely compiles. To avoid as many side effects as possible, I personnally create a symbolic link in /usr/local like so: +Syno's U-Boot barely compiles. To avoid as many side effects as possible, I chose to create a symbolic link in /usr/local like so: ln -s /opt/toolchains/arm-none-linux-gnueabi/ /usr/local/arm-none-linux-gnueabi # image creation @@ -72,6 +72,6 @@ There is NO jtag access on the DS211j board (at least, I was unable to find one) 2 other solutions: - manually load a custom crafted Linux kernel and use a USB stick with a custom rootfs (with all the flashcp stuff), that's what I did -- use a 3rd party flashing tool and access the NOR chip's pins directly. It's a standard m25p32 SPI flash chip. I personnally unsoldered it and used a RPi with a custom DTB to restore the flash to its original content after screwing up (using the SPI pins on the main RPi header). +- use a 3rd party flashing tool and access the NOR chip's pins directly. It's a standard m25p32 SPI flash chip. I unsoldered it and used a RPi with a custom DTB to restore the flash to its original content after screwing up (using the SPI pins on the main RPi header). If you screw up at this stage, the DS211j won't boot (you will hear the fan go wild) and you will need physical access to the flash chip to restore its content. Proceed at your own risks.