From: Mark Jackson <mpfj-list@newflow.co.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 7/7] am335x_evm: Add support to boot from NOR.
Date: Mon, 17 Jun 2013 15:43:21 +0100 [thread overview]
Message-ID: <51BF2089.90605@newflow.co.uk> (raw)
In-Reply-To: <1368469719-22406-7-git-send-email-trini@ti.com>
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.
next prev parent reply other threads:[~2013-06-17 14:43 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 18:28 [U-Boot] [PATCH v2 1/7] am33xx/omap3: Clean up gpmc_init slightly Tom Rini
2013-05-13 18:28 ` [U-Boot] [PATCH v2 2/7] am335x_evm: Drop useless CONFIG_ENV_IS_NOWHERE Tom Rini
2013-05-13 18:28 ` [U-Boot] [PATCH v2 3/7] am335x_evm: Update SPI_BOOT support, add MTDPARTS info Tom Rini
2013-05-15 20:41 ` Peter Korsgaard
2013-05-13 18:28 ` [U-Boot] [PATCH v2 4/7] am335x_evm: Only set CONFIG_NAND when !CONFIG_SPI_BOOT Tom Rini
2013-05-15 20:42 ` Peter Korsgaard
2013-05-13 18:28 ` [U-Boot] [PATCH v2 5/7] am335x_evm: Rework board_is_foo() checks Tom Rini
2013-05-15 20:43 ` Peter Korsgaard
2013-05-13 18:28 ` [U-Boot] [PATCH v2 6/7] am335x_evm: Add support for the NOR module on the memory cape Tom Rini
2013-05-16 14:32 ` Peter Korsgaard
2013-05-16 14:46 ` Tom Rini
2013-05-16 18:54 ` Peter Korsgaard
2013-05-16 19:27 ` Tom Rini
2013-05-16 19:32 ` Peter Korsgaard
2013-05-13 18:28 ` [U-Boot] [PATCH v2 7/7] am335x_evm: Add support to boot from NOR Tom Rini
2013-05-16 14:36 ` Peter Korsgaard
2013-05-16 14:49 ` Tom Rini
2013-05-16 18:55 ` Peter Korsgaard
2013-05-16 19:30 ` Tom Rini
2013-05-16 19:32 ` Peter Korsgaard
2013-06-17 14:43 ` Mark Jackson [this message]
2013-06-17 14:49 ` Tom Rini
2013-06-17 14:59 ` Mark Jackson
2013-06-17 15:01 ` Tom Rini
2013-06-17 15:23 ` Mark Jackson
2013-06-17 15:23 ` Mark Jackson
2013-06-17 15:29 ` Tom Rini
2013-06-17 16:01 ` Stefan Roese
2013-06-17 16:10 ` Mark Jackson
2013-06-17 17:04 ` Kipisz, Steven
2013-06-17 18:38 ` Mark Jackson
2013-06-18 12:11 ` Mark Jackson
2013-07-11 13:06 ` Mark Jackson
2013-07-11 13:28 ` Tom Rini
2013-07-11 13:45 ` Mark Jackson
2013-07-11 14:34 ` Albert ARIBAUD
2013-07-11 15:54 ` Tom Rini
2013-07-11 16:08 ` Albert ARIBAUD
2013-07-11 16:14 ` Albert ARIBAUD
2013-07-11 16:17 ` Tom Rini
2013-07-17 12:58 ` Mark Jackson
2013-07-17 13:32 ` Tom Rini
2013-05-15 20:39 ` [U-Boot] [PATCH v2 1/7] am33xx/omap3: Clean up gpmc_init slightly Peter Korsgaard
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=51BF2089.90605@newflow.co.uk \
--to=mpfj-list@newflow.co.uk \
--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