From: Paul B. Henson <henson@acm.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] NXP lpc31xx support
Date: Wed, 12 Dec 2012 17:13:29 -0800 [thread overview]
Message-ID: <50C92BB9.2040007@acm.org> (raw)
A friend of mine (who is more of a low-level hardware guy) is trying to
put together a project based on the NXP lpc3130 processor, and asked me
to help him out. I've got a reasonable OS/development background, but
not much of any experience in the embedded realm, so apologies in
advance for any cluelessness I might spew :).
NXP has a board support package for this processor:
http://ics.nxp.com/support/software/lpc313x.bsp.linux/
It includes a patch based on top of u-boot 2009.11 that adds
functionality specific to their processor. They also have a community
site for that processor (and others), including a git repo of their
u-boot 2009.11 fork:
http://git.lpclinux.com/?p=uboot-2009.11-lpc313x.git;a=summary
That looks pretty dead though, and it doesn't appear NXP has any plans
to update their BSP to a current u-boot or try to integrate support into
upstream u-boot.
My friend would prefer to use a more current u-boot; while the rather
old NXP fork would probably work for now, if he ever wanted to use more
current features such as device trees he'd rather already be in a
position to do so than have to scramble at that point. Ideally it would
also be nice for the processor to be directly supported by upstream
u-boot so it would just come along for the ride as features were added ;).
Jon Smirl started porting the NXP patch to u-boot 2011.12:
https://github.com/jonsmirl/lpc31xx-uboot
With some help from Jon, I've got that running on a dev board. However,
he was only interested in booting from SD/mmc, which is all his current
work supports. I'd like to get NAND booting working, and ideally get
support accepted upstream, which presumably will require updating his
work to current u-boot. I started working on the NAND boot support, but
as already confessed my background in embedded is a bit light and I'm
having some trouble with it.
I thought I'd take a step back and ask for some more general advice. NXP
to some extent went and did their own thing (for example, evidently
u-boot 2009.11 didn't support SPL, so they implemented their own), and
while Jon has modified the original NXP implementation to a point to fit
better within the u-boot 2011.12 he's working with, from my
(inexperienced) eye it still differs a bit from the rest of the u-boot
code. If the end goal is to get lpc31xx support in upstream u-boot, what
would be the most efficient path to pursue? If the code currently in
Jon's 2011.12 repo was fleshed out to full functionality, then brought
up to a current u-boot version, is that something that would be accepted
into upstream? Or would you recommend a different path?
Thanks much?
reply other threads:[~2012-12-13 1:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50C92BB9.2040007@acm.org \
--to=henson@acm.org \
--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