From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] AM335x Boot Device 6 (NAND?)
Date: Tue, 11 Nov 2014 10:10:41 +0100 [thread overview]
Message-ID: <5461D291.5000604@denx.de> (raw)
Hi Tom,
we have equipped some of our am335x boards (draco from mainline U-Boot)
with NAND devices from Hynix. And as it seems, the BootROM passes
now a different bootdevice number to SPL. Its not 5 as it used to be
for NAND but 6 instead. So SPL hangs of course as this boot-device is
not "supported".
Could you please let me know what this boot-device == 6 means /
represents? Should it be handled identical as the "normal" NAND
boot-device (5)?
Just to make this clear. This is the code that I'm referring to:
arch/arm/cpu/armv7/omap-common/boot-common.c:
/*
* rom_params can be type casted to omap_boot_parameters and
* used. But it not correct to assume that romcode structure
* encoding would be same as u-boot. So use the defined offsets.
*/
gd->arch.omap_boot_params.omap_bootdevice = boot_device =
*((u8 *)(rom_params + BOOT_DEVICE_OFFSET));
BTW: U-Boot can handle this Hynix NAND (same layout as the other NAND
chips we use) without any problems.
Thanks,
Stefan
next reply other threads:[~2014-11-11 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 9:10 Stefan Roese [this message]
2014-11-11 12:17 ` [U-Boot] AM335x Boot Device 6 (NAND?) Tom Rini
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=5461D291.5000604@denx.de \
--to=sr@denx.de \
--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