public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] AM335x SPI boot not working
Date: Thu, 14 Jan 2016 16:01:00 -0500	[thread overview]
Message-ID: <20160114210100.GY3359@bill-the-cat> (raw)
In-Reply-To: <1578508.0Ss7qeH1tP@lem-wkst-02>

On Wed, Dec 16, 2015 at 03:34:24PM +0100, Lars Poeschel wrote:

> Hi!
> 
> I played a bit with spi boot on my am3359. It is currently not working with u-
> boot at least with the machine I work here. Has anyone else problems with spi 
> boot on am335x ?
> 
> On boot SPL reads a value from a processor register to determine from which 
> device it was booting and it uses that value to continue booting process from 
> that same device.
> I found, that in my case the processor register contained a 0x0b and SPL could 
> not match that to a hardware device. BOOT_DEVICE_SPI is defined as 0x15 in 
> arch/arm/include/asm/arch-am33xx/spl.h. SPL does not find a mathch for 0x0b, 
> decides this is an unknown value and stalls. So far so good.
> 
> I looked up in the technical reference manual if the value 0x15 is correct. I 
> had TRM rev. F on my harddrive and found the value in 26.1.10.2, on page 4295 
> and it is indeed 0x15 as in u-boot.
> I looked on TI website for a new version of the TRM and they currently have 
> rev. L. There I found in 26.1.10.2 on page 4960 that SPI boot has 0x0b!
> 
> My question is now how to best cope with this issue and if anybody has more 
> information on what happend.
> I don't know if they only made a mistake in the TRM and fixed that or if they 
> have new silicone revisions that really have another boot device value for spi 
> boot.
> What can we do ?

Sorry for the late reply.  It sounds like at some point post PG2.1 TI
changed at least the value used for SPI boot.  I have in the past
validated SPI boot on my AM335x GP EVM with PG2.1 silicon.  SPI boot on
this hardware is not supported officially due to I believe hardware
design issues.  Did you make any further progress here?  Did making the
value U-Boot checks by 0x0b make things suddenly work?  Thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160114/cd5a753b/attachment.sig>

  reply	other threads:[~2016-01-14 21:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-16 14:34 [U-Boot] AM335x SPI boot not working Lars Poeschel
2016-01-14 21:01 ` Tom Rini [this message]
2016-01-18  9:02   ` Lars Poeschel
2016-01-19 16:01     ` Tom Rini

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=20160114210100.GY3359@bill-the-cat \
    --to=trini@konsulko.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox