BeagleBone defconfig broken?
Hello all,
I am currently trying to get the latest buildroot to run on my beaglebone with little success. The last version that seem to run out of the box is 2012.08, where I can simply copy MLO, u-boot.img and uImage to the boot partition, dd rootfs.ext2 to the second partition and the system works.
The current build fails to boot, because u-boot expects the image and dts in /boot within the root filesystem. After putting them there with a post build script, u-boot starts the kernel, but the kernel fails to mount root:
Quoted 1 line
[ 1.509962] Waiting for root device /dev/mmcblk0p2...
The SD partitions seem o.k.:
Quoted 10 lines
Disk
/dev/sdi: 3965 MB, 3965190144 bytes
255 heads, 63 sectors/track, 482 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier:0x00000000Device Boot Start End Blocks Id System /dev/sdi1 * 1 9 72292 c W95 FAT32 (LBA) /dev/sdi2 10 133 996030 83 Linux
and /dev/mmcblk0p2 sounds like the right partition.
Can anybody give a hint where to look further?
Kind regards
Stephan
Signature · 4 lines
reLinux - Stephan Hoffmann Am Schmidtgrund 124 50765 K?ln Tel. +49.221.95595-19 Fax: -64 www.reLinux.de sho at reLinux.de
Hi Stephan,
Does u-boot report that the device tree is loaded into memory just before booting? It should be named /boot/am335x-bone.dtb or /boot/am335x-boneblack.dtb on your rootfs partition, depending on if your BeagleBone hardware platform is White or Black, for u-boot to autoload it without further assistance in a uEnv.txt... The defaults are in buildroot/output/build/uboot-2013.04/include/configs/am335x_evm.h.
Thanks,
~vsergeev
Ivan Sergeev
Quoted 38 lines · Stephan Hoffmann
Hello all,
I am currently trying to get the latest buildroot to run on my beaglebone with little success. The last version that seem to run out of the box is 2012.08, where I can simply copy MLO, u-boot.img and uImage to the boot partition, dd rootfs.ext2 to the second partition and the system works.
The current build fails to boot, because u-boot expects the image and dts in /boot within the root filesystem. After putting them there with a post build script, u-boot starts the kernel, but the kernel fails to mount root:
Quoted 1 line
[ 1.509962] Waiting for root device /dev/mmcblk0p2...The SD partitions seem o.k.:
Quoted 10 lines
Disk
/dev/sdi: 3965 MB, 3965190144 bytes
255 heads, 63 sectors/track, 482 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier:0x00000000Device Boot Start End Blocks Id System /dev/sdi1 * 1 9 72292 c W95 FAT32 (LBA) /dev/sdi2 10 133 996030 83 Linuxand
/dev/mmcblk0p2sounds like the right partition.Can anybody give a hint where to look further?
Kind regards
Stephan
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64
www.reLinux.de sho at reLinux.de
Quoted 5 lines
_______________________________________________
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/20130818/5f39c32b/attachment.html>
Am 18.08.2013 19:48, schrieb Ivan Sergeev:
Quoted 1 line
Hi Stephan,
Hello Ivan,
thank you for your reply.
Quoted 3 lines
Does u-boot report that the device tree is loaded into memory just before booting?
Yes, that is obviously the case:
Quoted 16 lines
2857712 bytes read in 435 ms (6.3 MiB/s) 10537 bytes read in 55 ms (186.5 KiB/s) Booting from mmc ...
## Booting kernel from Legacy Image at 80200000 ...Image Name: Linux-3.8.11 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2857648 Bytes = 2.7 MiBLoad Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
## Flattened Device Tree blob at80f80000
Booting using the fdt blob at0x80f80000Loading Kernel Image ... OK
OK
Using Device Tree in place at80f80000, end80f85928
Quoted 7 lines
Starting kernel ...
It should be named
/boot/am335x-bone.dtbor/boot/am335x-boneblack.dtbon your rootfs partition, depending on if your BeagleBone hardware platform is White or Black, for u-boot to autoload it without further assistance in a uEnv.txt... The defaults are
inbuildroot/output/build/uboot-2013.04/include/configs/am335x_evm.h.
I tried the white one. Obviously the right files are loaded, at least the sizes match:
Review
Quoted 4 lines
ls -l output/target/boot/
insgesamt 2804(quoted diff) +0
-2-rw-rw-r-- 1 stephan users 10537 2013-08-19 09:47 am335x-bone.dtb -rw-r--r-- 1 stephan users 2857712 2013-08-19 09:47 uImage
I also verified the filenames in u-boot.
But the kernel still fails to mount root:
Quoted 1 line
[ 1.509906] Waiting for root device /dev/mmcblk0p2...
is the last sign of life it gives.
BTW: I changed the config by adding BR2_LINUX_KERNEL_INSTALL_TARGET=y, which is obviously missing in beaglebone_defconfig.
Any further idea?
Kind regards
Stephan
Quoted 56 lines
Thanks,
~vsergeev
Ivan SergeevOn Fri, Aug 16, 2013 at 1:23 AM, Stephan Hoffmann <[email protected] <mailto:[email protected]>> wrote:
Hello all,
I am currently trying to get the latest buildroot to run on my beaglebone with little success. The last version that seem to run out of
the box is 2012.08, where I can simply copy MLO, u-boot.img and uImage to the boot partition, dd rootfs.ext2 to the second partition and the system works.The current build fails to boot, because u-boot expects the image and dts in /boot within the root filesystem. After putting them there with a
post build script, u-boot starts the kernel, but the kernel fails to mount root:
> [ 1.509962] Waiting for root device/dev/mmcblk0p2...
The SD partitions seem o.k.:
> Disk/dev/sdi: 3965 MB, 3965190144 bytes
> 255 heads, 63 sectors/track, 482 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier:0x00000000
>
> Device Boot Start End Blocks Id System
>/dev/sdi1* 1 9 72292 c W95
FAT32 (LBA)
>/dev/sdi210 133 996030 83 Linux
and/dev/mmcblk0p2sounds like the right partition.Can anybody give a hint where to look further?
Kind regards
Stephan
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 <tel:%2B49.221.95595-19> Fax: -64
www.reLinux.de <http://www.reLinux.de> sho at reLinux.de_______________________________________________
buildroot mailing list
buildroot at busybox.net <mailto:[email protected]>
http://lists.busybox.net/mailman/listinfo/buildroot
Signature · 8 lines
reLinux - Stephan Hoffmann Am Schmidtgrund 124 50765 K?ln Tel. +49.221.95595-19 Fax: -64 www.reLinux.de sho at reLinux.de -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130819/fdf8d8bb/attachment-0001.html>
Hello Stephan,
Maybe it'd be worth double checking that the bootargs in u-boot has the right rootfstype?
The dts doesn't specify them so I'm assuming they're being passed entirely by u-boot.
Thanks,
~vsergeev
Ivan Sergeev
Quoted 118 lines · Stephan Hoffmann
Am 18.08.2013 19:48, schrieb Ivan Sergeev:
Hi Stephan,
Hello Ivan,
thank you for your reply.
Does u-boot report that the device tree is loaded into memory just
before booting?Yes, that is obviously the case:
2857712 bytes read in 435 ms (6.3 MiB/s) 10537 bytes read in 55 ms (186.5 KiB/s) Booting from mmc ...
## Booting kernel from Legacy Image at 80200000 ...Image Name: Linux-3.8.11 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2857648 Bytes = 2.7 MiBLoad Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
## Flattened Device Tree blob at80f80000
Booting using the fdt blob at0x80f80000Loading Kernel Image ... OK
OK
Using Device Tree in place at80f80000, end80f85928Starting kernel ...
It should be named
/boot/am335x-bone.dtbor/boot/am335x-boneblack.dtb
on your rootfs partition, depending on if your BeagleBone hardware platform is White or Black, for u-boot to autoload it without further assistance in a uEnv.txt... The defaults are
inbuildroot/output/build/uboot-2013.04/include/configs/am335x_evm.h.I tried the white one. Obviously the right files are loaded, at least the sizes match:
ls -l output/target/boot/
insgesamt 2804(quoted diff) +0
-2-rw-rw-r-- 1 stephan users 10537 2013-08-19 09:47 am335x-bone.dtb -rw-r--r-- 1 stephan users 2857712 2013-08-19 09:47 uImageI also verified the filenames in u-boot.
But the kernel still fails to mount root:
[ 1.509906] Waiting for root device /dev/mmcblk0p2...is the last sign of life it gives.
BTW: I changed the config by adding BR2_LINUX_KERNEL_INSTALL_TARGET=y, which is obviously missing in
beaglebone_defconfig.Any further idea?
Kind regards
Stephan
Thanks,
~vsergeev
Ivan SergeevQuoted 38 lines · Stephan Hoffmann
Hello all,
I am currently trying to get the latest buildroot to run on my beaglebone with little success. The last version that seem to run out of the box is 2012.08, where I can simply copy MLO, u-boot.img and uImage to the boot partition, dd rootfs.ext2 to the second partition and the system works.
The current build fails to boot, because u-boot expects the image and dts in /boot within the root filesystem. After putting them there with a post build script, u-boot starts the kernel, but the kernel fails to mount root:
Quoted 1 line
[ 1.509962] Waiting for root device /dev/mmcblk0p2...The SD partitions seem o.k.:
Quoted 10 lines
Disk
/dev/sdi: 3965 MB, 3965190144 bytes
255 heads, 63 sectors/track, 482 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier:0x00000000Device Boot Start End Blocks Id System /dev/sdi1 * 1 9 72292 c W95 FAT32 (LBA) /dev/sdi2 10 133 996030 83 Linuxand
/dev/mmcblk0p2sounds like the right partition.Can anybody give a hint where to look further?
Kind regards
Stephan
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64
www.reLinux.de sho at reLinux.deQuoted 5 lines
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
Quoted 6 lines
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64www.reLinux.de sho at reLinux.de
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130819/d68b8c2f/attachment-0001.html>
Also, are you building the kernel through buildroot, or using the latest patched one here? https://github.com/beagleboard/kernel/tree/3.8
I would try that patched kernel a try, if you aren't using it already.
Thanks,
~vsergeev
Ivan Sergeev
Quoted 7 lines · Ivan Sergeev
Hello Stephan,
Maybe it'd be worth double checking that the bootargs in u-boot has the right rootfstype?
The dts doesn't specify them so I'm assuming they're being passed entirely by u-boot.
Quoted 132 lines
Thanks,
~vsergeev
Ivan SergeevQuoted 124 lines · Stephan Hoffmann
Am 18.08.2013 19:48, schrieb Ivan Sergeev:
Hi Stephan,
Hello Ivan,
thank you for your reply.
Does u-boot report that the device tree is loaded into memory just
before booting?Yes, that is obviously the case:
2857712 bytes read in 435 ms (6.3 MiB/s) 10537 bytes read in 55 ms (186.5 KiB/s) Booting from mmc ...
## Booting kernel from Legacy Image at 80200000 ...Image Name: Linux-3.8.11 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2857648 Bytes = 2.7 MiBLoad Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
## Flattened Device Tree blob at80f80000
Booting using the fdt blob at0x80f80000Loading Kernel Image ... OK
OK
Using Device Tree in place at80f80000, end80f85928Starting kernel ...
It should be named
/boot/am335x-bone.dtbor/boot/am335x-boneblack.dtb
on your rootfs partition, depending on if your BeagleBone hardware platform is White or Black, for u-boot to autoload it without further assistance in a uEnv.txt... The defaults are
inbuildroot/output/build/uboot-2013.04/include/configs/am335x_evm.h.I tried the white one. Obviously the right files are loaded, at least the sizes match:
ls -l output/target/boot/
insgesamt 2804(quoted diff) +0
-2-rw-rw-r-- 1 stephan users 10537 2013-08-19 09:47 am335x-bone.dtb -rw-r--r-- 1 stephan users 2857712 2013-08-19 09:47 uImageI also verified the filenames in u-boot.
But the kernel still fails to mount root:
[ 1.509906] Waiting for root device /dev/mmcblk0p2...is the last sign of life it gives.
BTW: I changed the config by adding BR2_LINUX_KERNEL_INSTALL_TARGET=y, which is obviously missing in
beaglebone_defconfig.Any further idea?
Kind regards
Stephan
Thanks,
~vsergeev
Ivan SergeevQuoted 38 lines · Stephan Hoffmann
Hello all,
I am currently trying to get the latest buildroot to run on my beaglebone with little success. The last version that seem to run out of the box is 2012.08, where I can simply copy MLO, u-boot.img and uImage to the boot partition, dd rootfs.ext2 to the second partition and the system works.
The current build fails to boot, because u-boot expects the image and dts in /boot within the root filesystem. After putting them there with a post build script, u-boot starts the kernel, but the kernel fails to mount root:
Quoted 1 line
[ 1.509962] Waiting for root device /dev/mmcblk0p2...The SD partitions seem o.k.:
Quoted 10 lines
Disk
/dev/sdi: 3965 MB, 3965190144 bytes
255 heads, 63 sectors/track, 482 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier:0x00000000Device Boot Start End Blocks Id System /dev/sdi1 * 1 9 72292 c W95 FAT32 (LBA) /dev/sdi2 10 133 996030 83 Linuxand
/dev/mmcblk0p2sounds like the right partition.Can anybody give a hint where to look further?
Kind regards
Stephan
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64
www.reLinux.de sho at reLinux.deQuoted 5 lines
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64www.reLinux.de sho at reLinux.de
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130819/c7faa2e9/attachment.html>
Am 19.08.2013 19:57, schrieb Ivan Sergeev:
Quoted 3 lines
Also, are you building the kernel through buildroot, or using the latest patched one here? https://github.com/beagleboard/kernel/tree/3.8
I would try that patched kernel a try, if you aren't using it already.
Hello Ivan,
I'll check this out when I've got some time. I used the buildroot default config and only changed the option to copy kernel and dts to /boot in the root filesystem.
So u-boot and kernel are both built by buildroot. Kernel comed from ti:git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git and u-boot is version 2013.04, boardname am335x_evm.
Quoted 5 lines
Maybe it'd be worth double checking that the bootargs in u-boot has the right rootfstype?
The dts doesn't specify them so I'm assuming they're being passed entirely by u-boot.
I checked this, but the kernel does not come to the point where it sees any filesystem.
Regards
Stephan
Quoted 146 lines
Thanks,
~vsergeev
Ivan SergeevOn Mon, Aug 19, 2013 at 10:54 AM, Ivan Sergeev <[email protected] <mailto:[email protected]>> wrote:
Hello Stephan,
Maybe it'd be worth double checking that the bootargs in u-boot has the right rootfstype?
The dts doesn't specify them so I'm assuming they're being passed entirely by u-boot.Thanks,
~vsergeev
Ivan SergeevOn Mon, Aug 19, 2013 at 1:17 AM, Stephan Hoffmann <[email protected] <mailto:[email protected]>> wrote:
Am 18.08.2013 19:48, schrieb Ivan Sergeev:
Quoted 1 line
Hi Stephan,
Hello Ivan,
thank you for your reply.
Quoted 3 lines
Does u-boot report that the device tree is loaded into memory just before booting?
Yes, that is obviously the case:
Quoted 16 lines
2857712 bytes read in 435 ms (6.3 MiB/s) 10537 bytes read in 55 ms (186.5 KiB/s) Booting from mmc ...
## Booting kernel from Legacy Image at 80200000 ...
Image Name: Linux-3.8.11
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2857648 Bytes = 2.7 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
## Flattened Device Tree blob at80f80000
Booting using the fdt blob at0x80f80000Loading Kernel Image ... OK
OK
Using Device Tree in place at80f80000, end80f85928Quoted 8 lines
Starting kernel ...
It should be named
/boot/am335x-bone.dtbor/boot/am335x-boneblack.dtbon your rootfs partition, depending on if your BeagleBone hardware platform is White or Black, for u-boot to autoload it without further assistance in a uEnv.txt... The defaults are
inbuildroot/output/build/uboot-2013.04/include/configs/am335x_evm.h.I tried the white one. Obviously the right files are loaded, at least the sizes match:
Quoted 5 lines
ls -l output/target/boot/ insgesamt 2804 -rw-rw-r-- 1 stephan users 10537 2013-08-19 09:47 am335x-bone.dtb -rw-r--r-- 1 stephan users 2857712 2013-08-19 09:47 uImageI also verified the filenames in u-boot.
But the kernel still fails to mount root:
Quoted 1 line
[ 1.509906] Waiting for root device /dev/mmcblk0p2...is the last sign of life it gives.
BTW: I changed the config by adding BR2_LINUX_KERNEL_INSTALL_TARGET=y, which is obviously missing in
beaglebone_defconfig.Any further idea?
Kind regards
Stephan
Quoted 58 lines
Thanks,
~vsergeev
Ivan SergeevOn Fri, Aug 16, 2013 at 1:23 AM, Stephan Hoffmann <sho at relinux.de <mailto:[email protected]>> wrote:
Hello all,
I am currently trying to get the latest buildroot to run on my
beaglebone with little success. The last version that seem to run out of
the box is 2012.08, where I can simply copy MLO, u-boot.img and uImage
to the boot partition, dd rootfs.ext2 to the second partition and the
system works.The current build fails to boot, because u-boot expects the image and
dts in /boot within the root filesystem. After putting them there with a
post build script, u-boot starts the kernel, but the kernel fails to
mount root:
> [ 1.509962] Waiting for root device/dev/mmcblk0p2...
The SD partitions seem o.k.:
> Disk/dev/sdi: 3965 MB, 3965190144 bytes
> 255 heads, 63 sectors/track, 482 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disk identifier:0x00000000
>
> Device Boot Start End Blocks Id
System
>/dev/sdi1* 1 9 72292 c
W95 FAT32 (LBA)
>/dev/sdi210 133 996030 83
Linux
and/dev/mmcblk0p2sounds like the right partition.Can anybody give a hint where to look further?
Kind regards
Stephan
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 <tel:%2B49.221.95595-19> Fax: -64
www.reLinux.de <http://www.reLinux.de> sho at reLinux.de
<mailto:[email protected]>Quoted 6 lines
_______________________________________________
buildroot mailing list
buildroot at busybox.net <mailto:[email protected]>
http://lists.busybox.net/mailman/listinfo/buildroot
Quoted 8 lines
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 <tel:%2B49.221.95595-19> Fax: -64
www.reLinux.de <http://www.reLinux.de> sho at reLinux.de <mailto:[email protected]>-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130819/aa6a0a22/attachment-0001.html>