From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] mx35pdk vs. mx35_3stack
Date: Tue, 06 Sep 2011 09:06:07 +0200 [thread overview]
Message-ID: <4E65C65F.4060301@denx.de> (raw)
In-Reply-To: <E25187DA1B6BED42A600EBDF4CE04518D22F24C2@MAIL-UA.ccs.local>
On 09/06/2011 06:29 AM, Teemu Keskinarkaus wrote:
> Hi,
>
Hi Teemu,
> -----Original Message----- From: Stefano Babic
> [mailto:sbabic at denx.de]
>
> Take into account that the u-boot.bin in the last release must be
> stored on the NOR flash of your board - the board has both NAND and
> NOR flash. The DIP switch on the main board and on the Debug
> extension must be set to boot from the NOR flash.
>
> Yes, I just realized that it might be the cause. I our hw doesn't
> have NOR, only NAND.
Well, the mx35pdk (aka mx35_3stack) has always NOR flash, so far as I
know. Do you mean you are running a custom board ?
> I looked in mx35pdk.h config-header, but
> couldn't find place where to config U-boot for NAND. I'm compiling
> U-boot myself and not using precompiled binary.
There is no such a simple CONFIG_ to switch them and you must add
support for it.
To boot with NAND, you have to use the SPL mechanism. This set up the
RAM and copies the u-boot image from NAND to RAM. NAND driver for the
MX35 is supported, so it should be not a big effort to add the board.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2011-09-06 7:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 10:44 [U-Boot] mx35pdk vs. mx35_3stack Teemu Keskinarkaus
2011-09-05 11:09 ` Stefano Babic
2011-09-06 4:29 ` Teemu Keskinarkaus
2011-09-06 7:06 ` Stefano Babic [this message]
2011-09-07 7:45 ` Teemu Keskinarkaus
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=4E65C65F.4060301@denx.de \
--to=sbabic@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