From: Samuel Stirtzel <s.stirtzel@googlemail.com>
To: Fabian van der Werf <fvanderwerf@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Booting Pandaboard from SD card
Date: Thu, 13 Oct 2011 11:29:40 +0200 [thread overview]
Message-ID: <CAGiJk9eM=Fi+9uQEMM-64cZPGTjOvvBuy1jV60O_kXFmLD0J4Q@mail.gmail.com> (raw)
In-Reply-To: <CAJeSw6BJqdBON18UDRsBJgPov5iqXKmYRROnEyoH6SkNhOJg3w@mail.gmail.com>
2011/10/13 Fabian van der Werf <fvanderwerf@gmail.com>:
> On Thu, Oct 13, 2011 at 10:49 AM, Samuel Stirtzel
> <s.stirtzel@googlemail.com> wrote:
>>
>> Starting kernel ...
>>
>> commandline: <NULL>
>> arch_number: 2791
>> Uncompressing Linux... done, booting the kernel.
>>
>> -
>> The screen just stays blank after the last message.
>> This looks to me like it is (obviously) caused by an incorrect
>> environment loaded.
>>
>>
>> Help would be appreciated.
>
> Hi
>
> I am also trying to get things up and running using barebox. I am at
> about the same stage where you are. Though I am loading the kernel
> over TFTP instead from SD. Like you, I get "Uncompressing Linux...
> done, booting the kernel" and then nothing.
Well it is not the problem, I know that my kernel args are missing,
I'm just missing informations about how i can pass them to the kernel.
With u-boot the following command would get passed for the SD card:
setenv bootargs console=ttyO2,115200n8 vram=16M root=/dev/mmcblk0p2 rw
rootfstype=ext3 rootwait
Another question, is it possible to set these variables without
altering the Barebox files (like at run time or between configuring
and compiling).
>
> Note that this last line is not printed by barebox but by the kernel.
> There is a separate kernel build option to enable a console on the
> omap serial port. Then you still need to add console=ttyOx,115200n8 to
> your boot arguments. I think it needs to be ttyO2, though I am not
> sure. I haven't had the time yet to try these options (it's just for a
> hobby project).
>
>
>>
>> [1] http://www.omappedia.com/wiki/Minimal-FS_SD_flashing (using 2
>> partitions, one for boot files and the other for the rootfs)
>>
>> --
>> Regards
>> Samuel
>>
>> _______________________________________________
>> barebox mailing list
>> barebox@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/barebo
>
>
> Regards,
>
> Fabian
>
--
Regards
Samuel
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-10-13 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 8:49 Samuel Stirtzel
2011-10-13 9:07 ` Samuel Stirtzel
2011-10-13 9:14 ` Fabian van der Werf
2011-10-13 9:29 ` Samuel Stirtzel [this message]
2011-10-13 9:45 ` Samuel Stirtzel
2011-10-14 7:17 ` Fabian van der Werf
2011-10-13 9:36 ` Uwe Kleine-König
2011-10-13 15:25 ` Sascha Hauer
2011-10-17 14:44 ` Samuel Stirtzel
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='CAGiJk9eM=Fi+9uQEMM-64cZPGTjOvvBuy1jV60O_kXFmLD0J4Q@mail.gmail.com' \
--to=s.stirtzel@googlemail.com \
--cc=barebox@lists.infradead.org \
--cc=fvanderwerf@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