* Booting linux on a custom iMX27 board
@ 2012-01-26 20:23 Igor
2012-01-27 10:46 ` Uwe Kleine-König
0 siblings, 1 reply; 3+ messages in thread
From: Igor @ 2012-01-26 20:23 UTC (permalink / raw)
To: barebox
[-- Attachment #1.1: Type: text/plain, Size: 1690 bytes --]
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.
What's the reason for the boot failure?
I'm desperately looking for new ideas and suggestions!
Thanks in advance for every possible hint,
Igor.
--
"Don't find fault, find a remedy."
(Henry Ford)
[-- Attachment #1.2: Type: text/html, Size: 1941 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Booting linux on a custom iMX27 board
2012-01-26 20:23 Booting linux on a custom iMX27 board Igor
@ 2012-01-27 10:46 ` Uwe Kleine-König
2012-01-27 11:23 ` Igor
0 siblings, 1 reply; 3+ messages in thread
From: Uwe Kleine-König @ 2012-01-27 10:46 UTC (permalink / raw)
To: Igor; +Cc: barebox
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Booting linux on a custom iMX27 board
2012-01-27 10:46 ` Uwe Kleine-König
@ 2012-01-27 11:23 ` Igor
0 siblings, 0 replies; 3+ messages in thread
From: Igor @ 2012-01-27 11:23 UTC (permalink / raw)
To: barebox
Hi Uwe,
first of all thanks for the answer.
A few minutes ago I could see the answer that Sasha Hauer sent to Marek Belisko
(that was having a problem similar to mine) and it was "illuminating"!
> Do you have configured the right output port for low level debug? Did
> you pass the earlyprintk kernel parameter?
I didn't know that early printk has to be enabled with a cmd line option!
Sorry...
So I changed Barebox bootargs and I could see my 3.0.8 kernel talking to me!
And this helped the following debug...
>
>> What's the reason for the boot failure?
> Probably not a bootloader problem.
>
You were "probably" right... ;-)
Thanks,
I.
--
"Don't find fault, find a remedy."
(Henry Ford)
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-01-27 11:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-01-26 20:23 Booting linux on a custom iMX27 board Igor
2012-01-27 10:46 ` Uwe Kleine-König
2012-01-27 11:23 ` Igor
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox