From: Sascha Hauer <s.hauer@pengutronix.de>
To: Vanalme Filip <F.Vanalme@TELEVIC.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: i.MX27 ?
Date: Thu, 27 Jan 2011 08:40:23 +0100 [thread overview]
Message-ID: <20110127074023.GS9041@pengutronix.de> (raw)
In-Reply-To: <6EE7D1502C48E44E92DCADF9DD3E0DB9017FEA303C69@SRV-VS06.TELEVIC.COM>
Hi,
On Wed, Jan 26, 2011 at 09:20:11AM +0100, Vanalme Filip wrote:
> Hi,
>
> Anyone ported Barebox to Freescale's i.MX27PDK 3-stack ? I'm new to
> Barebox (or any bootloader...) and I try to port it for my i.MX27PDK,
> but did not succeed yet. I don't get anything on the console port yet.
> I took the i.MX27ADS as a reference, copied all its files to a new
> board directory, and started adjusting the files. Via the debug board
> of the i.MX27PDK (containing a CPLD), I should be able to turn on some
> debug leds very early in the boot process, but even this did not
> succeed (yet...). I made changes in board_init_lowlevel() of
> lowlevel_init.S to initialize the hardware. I guess
> board_init_lowlevel() is one of the first functions that is executed.
> Correct ? Because I didn't get it up and running, I tried to do
> debugging with a PEEDI debugger. Anyone experience with it for
> debugging Barebox ? I'm using PEEDI in combination with Eclipse
> (Zylin) debugger. It looks like I have problems when trying to step in
> assembler sources...
As a first step I would try to use barebox as a second stage loader
behind U-Boot or redboot or whatever is on your board. What do you have
on your board?
When using barebox as a second stage loader you can comment out
everything in board_init_lowlevel. Provided that you are using the
correct UART you should see something at this stage.
What silicon revision do you have on your board? Our i.MX27ads is rev
1 which has some incompatibilities to other revs, so maybe this is
where it breaks. Also, make sure that the SDRAM setup fits for your
board. For the lowlevel setup you might want to look at Freescale
provided sources.
Hope that helps
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-01-27 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 8:20 Vanalme Filip
2011-01-27 7:40 ` Sascha Hauer [this message]
2011-01-27 12:04 ` James Robinson
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=20110127074023.GS9041@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=F.Vanalme@TELEVIC.com \
--cc=barebox@lists.infradead.org \
/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