* [Buildroot] BeagleBoard-xM, booting 2.6.37, root=/dev/mmcblk0p2, kernel hangs
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 21:43 ` Steve Calfee
2011-03-24 21:19 ` [Buildroot] [beagleboard] " Torsten Mohr
2 siblings, 1 reply; 9+ messages in thread
From: bruce bushby @ 2011-03-23 21:33 UTC (permalink / raw)
To: buildroot
maybe a silly question.....have you tested your kernel/build via NFS....ie
"tftp boot uImage" & "NFS mount rootfs"?
On Wed, Mar 23, 2011 at 9:00 PM, Torsten Mohr <tmohr@s.netic.de> wrote:
> Hello,
>
> i've set up a micro SD card with VFAT on partition 1, EXT2 on partition 2.
>
> Partition 2 is buildroot's output/images/rootfs.ext2, copied with "dd" to
> the
> micro SD card.
>
> On partition 1 i have u-boot and i start the kernel like this:
> mmc init
> mmc rescan 0
> run loaduimage
> bootm 0x82000000
>
> Then i see the kernel boot log and i see it hanging:
>
> [ 1.215850] twl_rtc twl_rtc: setting system clock to 2000-01-01 00:05:25
> UTC (946685125)
> [ 1.226806] Waiting for root device /dev/mmcblk0p2...
> [ 1.369873] mmc0: host does not support reading read-only switch.
> assuming
> write-enable.
> [ 1.389953] mmc0: new SDHC card at address e624
> ---> no more output
>
>
> I use buildroot-2011.02, the kernel is 2.6.37.
>
> In the kernel configuration i have set:
>
> TI OMAP Multimedia Card Interface support (MMC_OMAP)
> TI OMAP High Speed Multimedia Card Interface support (MMC_OMAP_HS)
>
>
> Can anybody give me a hint why the kernel does not continue to boot?
>
>
> Best regards,
> Torsten.
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110323/8823d0ba/attachment.html>
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Buildroot] BeagleBoard-xM, booting 2.6.37, root=/dev/mmcblk0p2, kernel hangs
2011-03-23 21:33 ` bruce bushby
@ 2011-03-23 22:10 ` Torsten Mohr
2011-03-23 22:53 ` bruce bushby
0 siblings, 1 reply; 9+ messages in thread
From: Torsten Mohr @ 2011-03-23 22:10 UTC (permalink / raw)
To: buildroot
Hi,
no, i haven't set up tftp yet, but i can try that. It will be a good test to
see if the problem is the MMC or anything else related to mounting root,
correct?
Best regards,
Torsten.
Am Mittwoch, 23. M?rz 2011, 22:33:18 schrieb bruce bushby:
> maybe a silly question.....have you tested your kernel/build via NFS....ie
> "tftp boot uImage" & "NFS mount rootfs"?
>
> On Wed, Mar 23, 2011 at 9:00 PM, Torsten Mohr <tmohr@s.netic.de> wrote:
> > Hello,
> >
> > i've set up a micro SD card with VFAT on partition 1, EXT2 on partition
> > 2.
> >
> > Partition 2 is buildroot's output/images/rootfs.ext2, copied with "dd" to
> > the
> > micro SD card.
> >
> > On partition 1 i have u-boot and i start the kernel like this:
> > mmc init
> > mmc rescan 0
> > run loaduimage
> > bootm 0x82000000
> >
> > Then i see the kernel boot log and i see it hanging:
> >
> > [ 1.215850] twl_rtc twl_rtc: setting system clock to 2000-01-01
> > 00:05:25 UTC (946685125)
> > [ 1.226806] Waiting for root device /dev/mmcblk0p2...
> > [ 1.369873] mmc0: host does not support reading read-only switch.
> > assuming
> > write-enable.
> > [ 1.389953] mmc0: new SDHC card at address e624
> > ---> no more output
> >
> >
> > I use buildroot-2011.02, the kernel is 2.6.37.
> >
> > In the kernel configuration i have set:
> >
> > TI OMAP Multimedia Card Interface support (MMC_OMAP)
> > TI OMAP High Speed Multimedia Card Interface support (MMC_OMAP_HS)
> >
> >
> > Can anybody give me a hint why the kernel does not continue to boot?
> >
> >
> > Best regards,
> > Torsten.
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Buildroot] BeagleBoard-xM, booting 2.6.37, root=/dev/mmcblk0p2, kernel hangs
2011-03-23 22:10 ` Torsten Mohr
@ 2011-03-23 22:53 ` bruce bushby
2011-03-23 23:31 ` Steve Calfee
0 siblings, 1 reply; 9+ messages in thread
From: bruce bushby @ 2011-03-23 22:53 UTC (permalink / raw)
To: buildroot
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"
Hope that helps
On Wed, Mar 23, 2011 at 10:10 PM, Torsten Mohr <tmohr@s.netic.de> wrote:
> Hi,
>
> no, i haven't set up tftp yet, but i can try that. It will be a good test
> to
> see if the problem is the MMC or anything else related to mounting root,
> correct?
>
>
> Best regards,
> Torsten.
>
> Am Mittwoch, 23. M?rz 2011, 22:33:18 schrieb bruce bushby:
> > maybe a silly question.....have you tested your kernel/build via
> NFS....ie
> > "tftp boot uImage" & "NFS mount rootfs"?
> >
> > On Wed, Mar 23, 2011 at 9:00 PM, Torsten Mohr <tmohr@s.netic.de> wrote:
> > > Hello,
> > >
> > > i've set up a micro SD card with VFAT on partition 1, EXT2 on partition
> > > 2.
> > >
> > > Partition 2 is buildroot's output/images/rootfs.ext2, copied with "dd"
> to
> > > the
> > > micro SD card.
> > >
> > > On partition 1 i have u-boot and i start the kernel like this:
> > > mmc init
> > > mmc rescan 0
> > > run loaduimage
> > > bootm 0x82000000
> > >
> > > Then i see the kernel boot log and i see it hanging:
> > >
> > > [ 1.215850] twl_rtc twl_rtc: setting system clock to 2000-01-01
> > > 00:05:25 UTC (946685125)
> > > [ 1.226806] Waiting for root device /dev/mmcblk0p2...
> > > [ 1.369873] mmc0: host does not support reading read-only switch.
> > > assuming
> > > write-enable.
> > > [ 1.389953] mmc0: new SDHC card at address e624
> > > ---> no more output
> > >
> > >
> > > I use buildroot-2011.02, the kernel is 2.6.37.
> > >
> > > In the kernel configuration i have set:
> > >
> > > TI OMAP Multimedia Card Interface support (MMC_OMAP)
> > > TI OMAP High Speed Multimedia Card Interface support (MMC_OMAP_HS)
> > >
> > >
> > > Can anybody give me a hint why the kernel does not continue to boot?
> > >
> > >
> > > Best regards,
> > > Torsten.
> > >
> > > _______________________________________________
> > > buildroot mailing list
> > > buildroot at busybox.net
> > > http://lists.busybox.net/mailman/listinfo/buildroot
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110323/48a9d65a/attachment.html>
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Buildroot] BeagleBoard-xM, booting 2.6.37, root=/dev/mmcblk0p2, kernel hangs
2011-03-23 22:53 ` bruce bushby
@ 2011-03-23 23:31 ` Steve Calfee
2011-03-23 23:38 ` bruce bushby
0 siblings, 1 reply; 9+ messages in thread
From: Steve Calfee @ 2011-03-23 23:31 UTC (permalink / raw)
To: buildroot
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Buildroot] BeagleBoard-xM, booting 2.6.37, root=/dev/mmcblk0p2, kernel hangs
2011-03-23 23:31 ` Steve Calfee
@ 2011-03-23 23:38 ` bruce bushby
0 siblings, 0 replies; 9+ messages in thread
From: bruce bushby @ 2011-03-23 23:38 UTC (permalink / raw)
To: buildroot
unfortunately my uboot is the standard "factory" install of the module I'm
using :(
I think I have the uboot source code for the company that makes the module
(Telit) if that helps?
On Wed, Mar 23, 2011 at 11:31 PM, Steve Calfee <stevecalfee@gmail.com>wrote:
> 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 part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110323/3a7f2f35/attachment-0001.html>
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Buildroot] BeagleBoard-xM, booting 2.6.37, root=/dev/mmcblk0p2, kernel hangs
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 21:43 ` Steve Calfee
2011-03-23 22:19 ` Torsten Mohr
2011-03-24 21:19 ` [Buildroot] [beagleboard] " Torsten Mohr
2 siblings, 1 reply; 9+ messages in thread
From: Steve Calfee @ 2011-03-23 21:43 UTC (permalink / raw)
To: buildroot
On 03/23/11 14:00, Torsten Mohr wrote:
> Hello,
>
> i've set up a micro SD card with VFAT on partition 1, EXT2 on partition 2.
>
> Partition 2 is buildroot's output/images/rootfs.ext2, copied with "dd" to the
> micro SD card.
>
Hi Torsten,
Are you sure you are doing the copy correctly?
sudo tar -xzf rootfs.tar.gz -C media/destination
Always works for me.
> On partition 1 i have u-boot and i start the kernel like this:
> mmc init
> mmc rescan 0
> run loaduimage
> bootm 0x82000000
>
> Then i see the kernel boot log and i see it hanging:
>
> [ 1.215850] twl_rtc twl_rtc: setting system clock to 2000-01-01 00:05:25
> UTC (946685125)
> [ 1.226806] Waiting for root device /dev/mmcblk0p2...
> [ 1.369873] mmc0: host does not support reading read-only switch. assuming
> write-enable.
> [ 1.389953] mmc0: new SDHC card at address e624
> ---> no more output
>
>
> I use buildroot-2011.02, the kernel is 2.6.37.
>
> In the kernel configuration i have set:
>
> TI OMAP Multimedia Card Interface support (MMC_OMAP)
> TI OMAP High Speed Multimedia Card Interface support (MMC_OMAP_HS)
>
>
> Can anybody give me a hint why the kernel does not continue to boot?
Thats a tough call with this little info. Here is part of my xm bootlog:
[ 4.287384] mmc0: host does not support reading read-only switch.
assuming wr
ite-enable.
[ 4.298645] mmc0: new high speed SDHC card at address 1234
[ 4.307037] mmcblk0: mmc0:1234 SA04G 3.67 GiB
[ 4.318267] mmcblk0: p1 p2 p3
[ 4.512725] usb 1-2.1: new high speed USB device using ehci-omap and
address
3
[ 4.638244] usb 1-2.1: New USB device found, idVendor=0424,
idProduct=ec00
[ 4.645538] usb 1-2.1: New USB device strings: Mfr=0, Product=0,
SerialNumber
=0
[ 4.658721] smsc95xx v1.0.4
[ 4.749145] smsc95xx 1-2.1:1.0: usb0: register 'smsc95xx' at
usb-ehci-omap.0-
2.1, smsc95xx USB 2.0 Ethernet, 8e:bc:ee:cc:8a:9b
Regards, Steve
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Buildroot] BeagleBoard-xM, booting 2.6.37, root=/dev/mmcblk0p2, kernel hangs
2011-03-23 21:43 ` Steve Calfee
@ 2011-03-23 22:19 ` Torsten Mohr
0 siblings, 0 replies; 9+ messages in thread
From: Torsten Mohr @ 2011-03-23 22:19 UTC (permalink / raw)
To: buildroot
Hello,
i first investigated the file:
file rootfs.ext2
rootfs.ext2: Linux rev 0.0 ext2 filesystem data
That is why i used "dd" to copy it. Also, when i mount it at /dev/sdc2 on the
host PC, i can see a perfect root file system on it.
Best regards,
Torsten.
Am Mittwoch, 23. M?rz 2011, 22:43:12 schrieb Steve Calfee:
> On 03/23/11 14:00, Torsten Mohr wrote:
> > Hello,
> >
> > i've set up a micro SD card with VFAT on partition 1, EXT2 on partition
> > 2.
> >
> > Partition 2 is buildroot's output/images/rootfs.ext2, copied with "dd" to
> > the micro SD card.
>
> Hi Torsten,
>
> Are you sure you are doing the copy correctly?
>
> sudo tar -xzf rootfs.tar.gz -C media/destination
>
> Always works for me.
>
> > On partition 1 i have u-boot and i start the kernel like this:
> > mmc init
> > mmc rescan 0
> > run loaduimage
> > bootm 0x82000000
> >
> > Then i see the kernel boot log and i see it hanging:
> >
> > [ 1.215850] twl_rtc twl_rtc: setting system clock to 2000-01-01
> > 00:05:25 UTC (946685125)
> > [ 1.226806] Waiting for root device /dev/mmcblk0p2...
> > [ 1.369873] mmc0: host does not support reading read-only switch.
> > assuming write-enable.
> > [ 1.389953] mmc0: new SDHC card at address e624
> > ---> no more output
> >
> >
> > I use buildroot-2011.02, the kernel is 2.6.37.
> >
> > In the kernel configuration i have set:
> >
> > TI OMAP Multimedia Card Interface support (MMC_OMAP)
> > TI OMAP High Speed Multimedia Card Interface support (MMC_OMAP_HS)
> >
> >
> > Can anybody give me a hint why the kernel does not continue to boot?
>
> Thats a tough call with this little info. Here is part of my xm bootlog:
>
> [ 4.287384] mmc0: host does not support reading read-only switch.
> assuming wr
> ite-enable.
> [ 4.298645] mmc0: new high speed SDHC card at address 1234
> [ 4.307037] mmcblk0: mmc0:1234 SA04G 3.67 GiB
> [ 4.318267] mmcblk0: p1 p2 p3
> [ 4.512725] usb 1-2.1: new high speed USB device using ehci-omap and
> address
> 3
> [ 4.638244] usb 1-2.1: New USB device found, idVendor=0424,
> idProduct=ec00
> [ 4.645538] usb 1-2.1: New USB device strings: Mfr=0, Product=0,
> SerialNumber
> =0
> [ 4.658721] smsc95xx v1.0.4
> [ 4.749145] smsc95xx 1-2.1:1.0: usb0: register 'smsc95xx' at
> usb-ehci-omap.0-
> 2.1, smsc95xx USB 2.0 Ethernet, 8e:bc:ee:cc:8a:9b
>
> Regards, Steve
^ permalink raw reply [flat|nested] 9+ messages in thread
* [Buildroot] [beagleboard] BeagleBoard-xM, booting 2.6.37, root=/dev/mmcblk0p2, kernel hangs
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 21:43 ` Steve Calfee
@ 2011-03-24 21:19 ` Torsten Mohr
2 siblings, 0 replies; 9+ messages in thread
From: Torsten Mohr @ 2011-03-24 21:19 UTC (permalink / raw)
To: buildroot
Hello,
the problem was the kernel configuration, i configured MMC cards but i did not
enable the "Block Layer". It seems in the OMAP specific kernel you can't rely
that every dependency is correctly set (enabling MMC is possible without block
layer).
After adapting /etc/inittab i can start /bin/sh
Best regards,
Torsten.
Am Mittwoch, 23. M?rz 2011, 22:00:55 schrieb Torsten Mohr:
> Hello,
>
> i've set up a micro SD card with VFAT on partition 1, EXT2 on partition 2.
>
> Partition 2 is buildroot's output/images/rootfs.ext2, copied with "dd" to
> the micro SD card.
>
> On partition 1 i have u-boot and i start the kernel like this:
> mmc init
> mmc rescan 0
> run loaduimage
> bootm 0x82000000
>
> Then i see the kernel boot log and i see it hanging:
>
> [ 1.215850] twl_rtc twl_rtc: setting system clock to 2000-01-01 00:05:25
> UTC (946685125)
> [ 1.226806] Waiting for root device /dev/mmcblk0p2...
> [ 1.369873] mmc0: host does not support reading read-only switch.
> assuming write-enable.
> [ 1.389953] mmc0: new SDHC card at address e624
> ---> no more output
>
>
> I use buildroot-2011.02, the kernel is 2.6.37.
>
> In the kernel configuration i have set:
>
> TI OMAP Multimedia Card Interface support (MMC_OMAP)
> TI OMAP High Speed Multimedia Card Interface support (MMC_OMAP_HS)
>
>
> Can anybody give me a hint why the kernel does not continue to boot?
>
>
> Best regards,
> Torsten.
^ permalink raw reply [flat|nested] 9+ messages in thread