From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] mx6qsabrelite U-Boot from SPI-NOR
Date: Fri, 20 Jan 2012 06:54:55 -0700 [thread overview]
Message-ID: <4F19722F.3090008@boundarydevices.com> (raw)
In-Reply-To: <4F193094.1020900@grandegger.com>
On 01/20/2012 02:15 AM, Wolfgang Grandegger wrote:
>
> On 01/20/2012 01:56 AM, Eric Nelson wrote:
>>
>> Yes. If you program u-boot.imx to offset 0x400, it will boot.
>>
>> I just did so as shown below.
>>
>> I started by placing SW1 in the 01 position (boot to USB), and
>> used imx_usb to dowload u-boot.imx:
>>
>> MX6QSABRELITE U-Boot> dhcp 10800000 192.168.0.112:u-boot.imx
>> fec_open:Speed=100
>> BOOTP broadcast 1
>> BOOTP broadcast 2
>> DHCP client bound to address 29.6.1.24
>> Using FEC device
>> TFTP from server 192.168.0.112; our IP address is 29.6.1.24;
>> sending through gateway 29.6.1.1
>> Filename 'u-boot.imx'.
>> Load address: 0x10800000
>> Loading: #########################################
>> done
>> Bytes transferred = 207112 (32908 hex)
>> MX6QSABRELITE U-Boot> sf write 0x10800000 0x400 $filesize
>
> But above you used the network to load u-boot.imx. With imx_usb you
> loaded and booted an image via USB first, I assume.
>
Yeah. USB to execute U-Boot, then Ethernet to get a pristine
image into RAM for programming.
I'd love to get USB support for MX6Q into U-Boot, but that's another
project...
prev parent reply other threads:[~2012-01-20 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-26 7:34 [U-Boot] [PATCH v3] i.mx: i.mx6q: add the initial support for i.mx6q Sabre Lite board Dirk Behme
2011-12-28 12:32 ` Stefano Babic
2011-12-29 7:09 ` Dirk Behme
2011-12-29 8:06 ` Liu Hui-R64343
2011-12-29 16:13 ` Eric Nelson
2012-01-19 9:58 ` Wolfgang Grandegger
2012-01-19 10:26 ` Dirk Behme
2012-01-20 0:56 ` [U-Boot] mx6qsabrelite U-Boot from SPI-NOR Eric Nelson
2012-01-20 9:15 ` Wolfgang Grandegger
2012-01-20 13:54 ` Eric Nelson [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=4F19722F.3090008@boundarydevices.com \
--to=eric.nelson@boundarydevices.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 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.