public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Andy Pont <andy.pont@sdcsystems.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Falcon mode boot support
Date: Tue, 16 Dec 2014 14:48:21 -0000	[thread overview]
Message-ID: <00ec01d0193f$5b9e27f0$12da77d0$@pont@sdcsystems.com> (raw)
In-Reply-To: <20141216143041.GK20704@bill-the-cat>

Hi Tom,

> eMMC is likely to be faster, yes.  You may also want to see what can be
> trimmed from the kernel binary, in either case, and if going with an
> uncompressed kernel ends up being quicker.

There are I think two issues going on here one with decompression time
which, as you say, I can resolve by using an uncompressed kernel.  The other
is with the SPI transfer time and some testing has shown that if I boot to
U-Boot and then run:

U-Boot> time sf read ${loadaddr} 0x200000 ${loadsize}

I get the following back:

SF: 2541352 bytes @ 0x200000 Read: OK
time: 2.447 seconds

The Spansion datasheet states that in read mode it can transfer 6.25Mbytes/s
in standard read mode at 50MHz clock.  I have the clock at 40MHz as the
device on the other SPI interface won't support anything faster.

When I tested this on the Starter Kit reference board and again on the
target hardware I had to increase the value of SPI_WAIT_TIMEOUT in
driver/spi/omap3_spi.c from 3000000 by adding an extra '0' in order to stop
getting read failures with "sf read" commands with more than about 2MB of
data as per the discussion on the TI E2E community here:
http://e2e.ti.com/support/arm/sitara_arm/f/791/p/366019/1293837.aspx#1293837
.

Regards,

Andy.

  reply	other threads:[~2014-12-16 14:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <548f0a77.c768c20a.2e45.26a0SMTPIN_ADDED_BROKEN@mx.google.com>
2014-12-15 17:23 ` [U-Boot] Falcon mode boot support Tom Rini
2014-12-15 21:08   ` Andy Pont
     [not found]   ` <548f4dd3.0677c20a.5db4.14a9SMTPIN_ADDED_BROKEN@mx.google.com>
2014-12-15 22:08     ` Tom Rini
2014-12-16 12:58       ` Andy Pont
     [not found]       ` <54902c90.e44bc20a.557b.5c5bSMTPIN_ADDED_BROKEN@mx.google.com>
2014-12-16 14:30         ` Tom Rini
2014-12-16 14:48           ` Andy Pont [this message]
2014-12-17 16:27             ` Andy Pont
     [not found]             ` <5491af14.42fac20a.10ed.3bd4SMTPIN_ADDED_BROKEN@mx.google.com>
2014-12-17 21:02               ` Tom Rini
2014-12-18 12:28                 ` Andy Pont
2014-12-15 16:20 Andy Pont

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='00ec01d0193f$5b9e27f0$12da77d0$@pont@sdcsystems.com' \
    --to=andy.pont@sdcsystems.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