From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eric Nelson <eric.nelson@boundarydevices.com>
Date: Fri, 20 Jan 2012 06:54:55 -0700
Subject: [U-Boot] mx6qsabrelite U-Boot from SPI-NOR
In-Reply-To: <4F193094.1020900@grandegger.com>
References: <1324884888-9618-1-git-send-email-dirk.behme@gmail.com>
	<4F17E928.3090208@grandegger.com> <4F17EFC9.10804@de.bosch.com>
	<4F18BBAA.5060000@boundarydevices.com>
	<4F193094.1020900@grandegger.com>
Message-ID: <4F19722F.3090008@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 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...