From: Steve Calfee <stevecalfee@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] BeagleBoard-xM, booting 2.6.37, root=/dev/mmcblk0p2, kernel hangs
Date: Wed, 23 Mar 2011 16:31:31 -0700 [thread overview]
Message-ID: <4D8A82D3.9020704@gmail.com> (raw)
In-Reply-To: <AANLkTikPixoYQfWYnnKKBb6TuXOMXt165gkfVAzL-OPR@mail.gmail.com>
On 03/23/11 15:53, bruce bushby wrote:
> I've only just started using buildroot but I found the NFS setup simplifies
> things and it also makes testing new builds very easy.
>
> I can help with the NFS setup if you need.....it's about the only part of
> things I'm any good at :)
>
> my uboot settings:
>
> U-Boot> printenv
> bootdelay=3
> baudrate=115200
> AutoRamSizeCfg=ON
> AutoLinuxEnvCfg=ON
> ethact=macb0
> autostart=
> autoload=no
> ipaddr=192.100.1.102
> ethaddr=192.100.1.102
> bootcmd=ethinit $ipaddr ; tftp 0x20200000 uImage ; bootm 0x20200000
> serverip=192.100.1.108
> bootargs=console=ttyS0,115200 mem=64M ver=4384k icofat=257k root=/dev/nfs
> nfsroot=192.100.1.108:/nfsroot ip=192.100.1.102
> mtdparts=atmel_nand:7936k(ARMboot)ro,- at 7936k(root)
> stdin=serial
> stdout=serial
> stderr=serial
>
> Environment size: 431/32764 bytes
> U-Boot>
>
>
> 1. setup tftpboot (I use /tftpboot)
> 2. Create an nfs share (I use /nfsroot)
> 2. Copy uImage to /tftpboot/uImage (give /tftpboot 777 file perms)
> 4. Copy rootfs.tar to /nfsroot ; tar -xf rootfs.tar
>
> uboot:
> setenv ipaddr 192.100.1.102
> setenv bootcmd "...your bootcmd"
> setenv bootargs "..your bootargs"
> saveenv
>
> I set my bootcmd to include "ethinit $ipaddr;" .... otherwise you have to
> manually "ethinit $ipaddr"
>
>
>
Hi Bruce,
What u-boot are you using and what is it's config. I see here you got
both usb ethernet to work and also saveenv to mmc. I would like to see
your u-boot config.
I gave up on u-boot, but do mount nfs from the bb-xm. then if needed I
copy over a new uImage and reboot. Obviously either tftp or nfs booting
would be even nicer.
I tried to get kexec to work on the bb, but it doesn't. Lots of people
are saying kexec is not working in 2.6.38, but I haven't seen fixes yet.
The nice thing about kexec is it uses a less bloated u-boot, gives
better scripting capability (and for me without the ability to saveenv),
easier customizing. But alas....
Regards, Steve
next prev parent reply other threads:[~2011-03-23 23:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 21:00 [Buildroot] BeagleBoard-xM, booting 2.6.37, root=/dev/mmcblk0p2, kernel hangs Torsten Mohr
2011-03-23 21:33 ` bruce bushby
2011-03-23 22:10 ` Torsten Mohr
2011-03-23 22:53 ` bruce bushby
2011-03-23 23:31 ` Steve Calfee [this message]
2011-03-23 23:38 ` bruce bushby
2011-03-23 21:43 ` Steve Calfee
2011-03-23 22:19 ` Torsten Mohr
2011-03-24 21:19 ` [Buildroot] [beagleboard] " Torsten Mohr
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=4D8A82D3.9020704@gmail.com \
--to=stevecalfee@gmail.com \
--cc=buildroot@busybox.net \
/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