From: stefano babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Help Required [imx35pdk]
Date: Wed, 12 Sep 2012 23:44:15 +0200 [thread overview]
Message-ID: <5051022F.2090700@denx.de> (raw)
In-Reply-To: <201209122307.20680.marex@denx.de>
Am 12/09/2012 23:07, schrieb Marek Vasut:
> Dear Muhammad Usman,
>
Hi Muhammad,
> Ccing Stefano.
>
>> I am adding support of imx35pdk in yocto.
>> I have done with my bsp. But the u-boot that build in response of my bsp
>> only runs over NOR and not on NAND. I spend 2 days on it but failed to do
>> so.
U-Boot for mx35pdk runs from NOR and not from NAND. There is no support
to run from NAND. Even if I can "convince" the board to boot from NAND,
this was not pushed to mainline. I explain why.
You have found nand_spl with support for mx31pdk. This was the method we
have previously to boot from NAND. We have now a generic framework for
SPL, and all new boards (or added support for booting from NAND) must
use it. A board using the old nand_spl will not be merged into mainline.
The mx35pdk was not ported to this generic SPL. We are really merging
this framework now to make it available for all SOC, because it was
common only for TI processor.
> I read some where that mx35pdk required some external 4-pins bla bla
>> something like that.
It does not require external pins. You have to configure the dip
switches on the mx35pdk.
>>
>> Also the u-boot running on NOR is not configuring uImage. I am using tftp
>> but when it comes on loading, it keeps on showing "T T T T T..." (time-out
>> response).
I think I have tested it recently, and it worked - which of the two
interfaces have you used in u-boot ? Both (FEC and SMC) are supported in
the mx35pdk u-boot, and both should work, as far as I know.
>> One thing more, in the above mentioned repository, there is a directory
>> like spl_nand in which they have already add mx31pdk for u-boot-nand.bin
>> support but not mx35pdk. What should i do to overcome all this ???
This is what I talked about before. All boards using spl_nand were added
a lot of time ago. spl_nand requires a separate driver for SPL, and this
is highly inefficient. The way we decided to go is to use a generic SPL,
valid for all SOC. And there is not yet a port for mx35pdk to boot
directly from NAND.
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:[~2012-09-12 21:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 10:03 [U-Boot] Help Required [imx35pdk] Muhammad Usman
2012-09-12 21:07 ` Marek Vasut
2012-09-12 21:44 ` stefano babic [this message]
2012-09-13 4:55 ` Fabio Estevam
2012-09-13 6:18 ` Muhammad Usman
2012-09-13 7:48 ` stefano babic
2012-09-13 6:13 ` Muhammad Usman
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=5051022F.2090700@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