From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: Booting Linux on Altera's socfpga
Date: Mon, 20 Apr 2015 05:41:34 -0700 [thread overview]
Message-ID: <CAHQ1cqFsmdJn9JWzbHbRP-9CFBUi5Xk_O66btO1Png8cwn0zyA@mail.gmail.com> (raw)
In-Reply-To: <20150413130411.GB19889@pengutronix.de>
>> 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...
>
My guess is that all of the .rbfs you generated had their length be
multiple of 4
>> 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.
>
You wild guess was spot on, thank you! It was indeed the reason and as
soon as I recompiled a Rocketboards kernel without that option
everything started to work just fine.
Andrey
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-04-20 12:41 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
2015-04-20 12:41 ` Andrey Smirnov [this message]
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=CAHQ1cqFsmdJn9JWzbHbRP-9CFBUi5Xk_O66btO1Png8cwn0zyA@mail.gmail.com \
--to=andrew.smirnov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.trumtrar@pengutronix.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