mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Igor <igt1972@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Booting linux on a custom iMX27 board
Date: Fri, 27 Jan 2012 11:46:31 +0100	[thread overview]
Message-ID: <20120127104631.GX6305@pengutronix.de> (raw)
In-Reply-To: <CALQ+5adUr7Sy2z-irN=1eeGGFPu=L9bqBMtmU7JtYJh_tK1NAg@mail.gmail.com>

Hello,

On Thu, Jan 26, 2012 at 09:23:32PM +0100, Igor wrote:
> Hi,
> 
> I 'm trying to port Barebox (2012.01.0) and make it successfully booting
> Linux
> on a custom board based on iMX27.
> I could successfully configure, compile and use Barebox on my MX27ADS board,
> making it work both as a second stage bootloader (after Redboot)
> and as the first stage bootloader (booting the system from flash).
> 
> I modified the sources to adapt the low level init functions to my HW
> that has half the ram of the ev.board and a different flash
> (a Spansion S29GLxxx, same size of the one in the eva board).
> With my customized version of Barebox I can:
> - boot Linux (zImage, 2.6.32.3) using Barebox as a second stage bootloader
> (after Redboot)
> - start from Flash as a first stage bootloader, correctly initializing the
> system.
> 
> In the second case, indeed, the system seems to be fully working:
> I can read and write the flash partitions, I can complete successfully
> the ram test with "mtest", but... I cannot boot Linux!
> 
> I just get:
> "uncompressing linux... done booting the kernel"
> and then it's silence...
> 
> architecture_type is 846 (it's the one of the mx27ads).
> It should be right  considering that I used both for the kernel and for the
> bootloader
> the configuration for imx27ads.
> 
> I also tryed to make it boot a more recent kernel version;
> I compiled a 3.0.8 with early_printk anabled to get more info about
> the initial crash/problem  but... Nothing!
> I didn't get nothing after "... done booting the kernel" also with the 3.0.8
> with low level debug and early_printk enabled.
Do you have configured the right output port for low level debug? Did
you pass the earlyprintk kernel parameter?

Do you have a jtag debugger?
 
> What's the reason for the boot failure?
Probably not a bootloader problem.

Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2012-01-27 10:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 20:23 Igor
2012-01-27 10:46 ` Uwe Kleine-König [this message]
2012-01-27 11:23   ` Igor

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=20120127104631.GX6305@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=igt1972@gmail.com \
    /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