summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorJavier Martinez Canillas <javier@dowhile0.org>2013-04-02 23:57:23 +0000
committerStefano Babic <sbabic@denx.de>2013-04-03 12:15:17 +0200
commit7a3f481c6d75b51e9e7b1aa0ebb7cd2c826c0886 (patch)
tree6169adf6ccf92d8c0f908991683e8c06bc83a4c7 /drivers
parentd8e9eb9c042ce55538ebd3194d1ffe75c791fb7c (diff)
downloadu-boot-imx-7a3f481c6d75b51e9e7b1aa0ebb7cd2c826c0886.zip
u-boot-imx-7a3f481c6d75b51e9e7b1aa0ebb7cd2c826c0886.tar.gz
u-boot-imx-7a3f481c6d75b51e9e7b1aa0ebb7cd2c826c0886.tar.bz2
i.MX6: mx6qsabrelite: README: don't pass chip-select to sf probe command
board/freescale/mx6qsabrelite/README explain a procedure to update the SPI-NOR on the SabreLite board without Freescale manufacturing tool but following this procedure leads to both "sf erase" and "sf write" failing on a mx6qsabrelite board: MX6QSABRELITE U-Boot > sf probe 1 MX6QSABRELITE U-Boot > sf erase 0 0x40000 SPI flash erase failed MX6QSABRELITE U-Boot > sf write 0x10800000 0 0x40000 SPI flash write failed This is because the chip-select 1 is wrong and the correct value is 0x7300. Since commit c1173bd0 ("sf command: allow default bus and chip selects") the chip-select and bus arguments for the sf probe command are optional so let's just remove it and use "sf probe" instead. Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions