All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/1] i.MX6: mx6qsabrelite: README: don't pass chip-select to sf probe command
Date: Wed, 03 Apr 2013 12:15:55 +0200	[thread overview]
Message-ID: <515C015B.3000205@denx.de> (raw)
In-Reply-To: <1364983043-8488-1-git-send-email-javier.martinez@collabora.co.uk>

On 03/04/2013 11:57, Javier Martinez Canillas wrote:
> 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>
> ---


Applied to u-boot-imx, thanks.

Best regards,
Stefano

-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================

      reply	other threads:[~2013-04-03 10:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03  9:57 [U-Boot] [PATCH v2 1/1] i.MX6: mx6qsabrelite: README: don't pass chip-select to sf probe command Javier Martinez Canillas
2013-04-03 10:15 ` Stefano Babic [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=515C015B.3000205@denx.de \
    --to=sbabic@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.