From: Steffen Trumtrar <s.trumtrar@pengutronix.de>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: Booting Linux on Altera's socfpga
Date: Mon, 13 Apr 2015 15:04:11 +0200 [thread overview]
Message-ID: <20150413130411.GB19889@pengutronix.de> (raw)
In-Reply-To: <CAHQ1cqGVK7z-joRkPEWvswo4JDw6BgPxM9TNVgrsZAyN8cmqUg@mail.gmail.com>
Hi!
On Mon, Apr 13, 2015 at 05:43:39AM -0700, Andrey Smirnov wrote:
> Hi All,
>
> I am trying to use Barebox on Terasic's SoCKit board and so far I've
> had limited success.
>
> My sequence of actions is the following:
>
> 1. Get zImage, device tree file and .rbf file from a pre-built image
> available here:
> http://www.rocketboards.org/foswiki/Documentation/ArrowSoCKITEvaluationBoard140LinuxGettingStarted
>
> 2. Boot into barebox
>
> 3. cp /boot/soc_system.rbf /dev/socfpga-fpga (This step initially
> didn't work for me, so I had to make a change to the firmware driver
> http://lists.infradead.org/pipermail/barebox/2015-April/023194.html)
>
This is interesting, because all rbf's I generated myself worked fine.
I wonder why this is different...
> 4. global.linux.bootargs.base="console=ttyS0,115200"
>
> 5. global.bootm.oftree=/boot/soc_system.dtb
>
> 6. global.bootm.image=/boot/zImage
>
> 7. bootm
>
> After the last step I and barebox jumps to the kernel code I don't see
> any output on the serial at all.
>
Wild guess: does the Rocketboards kernel define "CONFIG_VMSPLIT_2G=y"?
It is possible, that this produces errors when you use barebox.
Try setting
global.linux.bootargs.base="console=ttyS0,115200 earlyprintk"
if early printk is enabled in the rocketboards kernel.
> I feel like I am missing something obvious, but I can't figure out
> what it is. If anyone has had experience booting Linux using barebox
> on aforementioned board I'd greatly appreciate to hear about how you
> did it.
>
I'm booting the mainline kernel with barebox since a v3.15ish kernel
and it works fine. I have no idea about the state of the rocketboards
kernel, though.
Regards,
Steffen
--
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:[~2015-04-13 13:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 12:43 Andrey Smirnov
2015-04-13 13:04 ` Steffen Trumtrar [this message]
2015-04-20 12:41 ` Andrey Smirnov
2015-04-20 12:58 ` Lucas Stach
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=20150413130411.GB19889@pengutronix.de \
--to=s.trumtrar@pengutronix.de \
--cc=andrew.smirnov@gmail.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