From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mark Jackson <mpfj-list@newflow.co.uk>
Date: Mon, 17 Jun 2013 15:43:21 +0100
Subject: [U-Boot] [PATCH v2 7/7] am335x_evm: Add support to boot from
 NOR.
In-Reply-To: <1368469719-22406-7-git-send-email-trini@ti.com>
References: <1368469719-22406-1-git-send-email-trini@ti.com>
	<1368469719-22406-7-git-send-email-trini@ti.com>
Message-ID: <51BF2089.90605@newflow.co.uk>
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 13/05/13 19:28, Tom Rini wrote:
> From: Steve Kipisz <s-kipisz2@ti.com>
> 
> NOR requires that s_init be within the first 4KiB of the image so that
> we can perform the rest of the required pinmuxing to talk with the rest
> of NOR that we are found on.  When NOR_BOOT is set we save our
> environment in NOR at 512KiB and a redundant copy at 768KiB.  We avoid
> using SPL for this case and u-boot.bin is written directly to the start
> of NOR.

I'm trying to get this up and running our NanoBone platform, but I'm having
no success.

Using a non "NOR_BOOT" version, I can boot u-boot and read / write to the
NOR device (located at 0x08000000).

So I've compiled my "NOR_BOOT" version and stored it at the start of the
flash device.

But when I switch to booting from NOR (rather than SD) I get no output on
the serial console.

Using an oscilloscope, I can see the NOR chip select is active for a while
(approx 350us), so *something* is trying to boot.

How can I debug such an early part of the boot process ?

Thanks for any help you can give me.

Regards
Mark J.