From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eric Nelson <eric.nelson@boundarydevices.com>
Date: Wed, 03 Apr 2013 07:06:48 -0700
Subject: [U-Boot] [PATCH 1/1] i.MX6: mx6qsabrelite: README: don't pass
 chip-select to sf probe command
In-Reply-To: <515BF56F.9050209@denx.de>
References: <1364228037-21962-1-git-send-email-javier.martinez@collabora.co.uk>
	<515BF56F.9050209@denx.de>
Message-ID: <515C3778.6050409@boundarydevices.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 04/03/2013 02:25 AM, Stefano Babic wrote:
> On 25/03/2013 17:13, Javier Martinez Canillas wrote:
>> since commit "c1173bd0: sf command: allow default bus and chip selects"
>> the chip-select and bus arguments for the sf probe command are optional.
>>
>
> Hi Javier,
>
>> Even when passing the chip-select to sf probe says to be optional, it
>> makes "sf erase" and "sf write" to fail on a mx6qsabrelite board. e.g:
>>
>> 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
>
> Well, the real reason is that the passed chipselect is wrong. Checking
> in the configuration file, I see that the value to be passed should be
> 0x7300. I suppose (I am not testing) that "sf probe 0x7300" make sf
> erase and sw write working.
>
It's 0x5300 as listed in commit c1173bd0.

And the SABRE Lite README definitely needs updates.

Regards,


Eric