[Buildroot] bootm - "Starting kernel"

[Buildroot] bootm - "Starting kernel"

[Lee, Tommy]

Hi Buildroot mailing list,

My host is Ubuntu-14.04 LTS. My Buildroot release is 2015.05. I have made the former meet the latter's requirements. My target is Marvell ARMADA A385 (ARM-Cortex-A9) DB-88F6820-GP. This board is bootable using the U-Boot-1.73 and the USB which are given by Marvell.

I used Buildroot-2015.05 and built the uImage and rootfs.cpio.uboot with no problems. I enabled the TFTP server on my host.

On my target, the execution of the following commands, listed below, ended up with "Starting kernel", no display of kernel booting messages. The attached is the .config file I created this the make process.

I am resolving this issue now. Your experience sharing is extremely grateful.

Tommy

Marvell>> tftp 02000000 10.28.1.20:uImage
Using egiga0 device
TFTP from server 10.28.1.20; our IP address is 10.28.1.47
Filename 'uImage'.
Load address: 0x2000000
Loading: #################################################################
         #################################################################
         #################################################################
         ##############
         1.6 MiB/s
done
Bytes transferred = 1066696 (1046c8 hex)
Marvell>> tftp 02200000 10.28.1.20:rootfs.cpio.uboot
Using egiga0 device
TFTP from server 10.28.1.20; our IP address is 10.28.1.47
Filename 'rootfs.cpio.uboot'.
Load address: 0x2200000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ######################
         1.7 MiB/s
done
Bytes transferred = 4769344 (48c640 hex)
Marvell>> bootm 02000000 02200000
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   Linux-4.0.4
   Created:      2015-08-11   0:21:58 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1066632 Bytes = 1 MiB
   Load Address: 02000000
   Entry Point:  02000000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02200000 ...
   Image Name:
   Created:      2015-08-11  15:25:49 UTC
   Image Type:   ARM Linux RAMDisk Image (uncompressed)
   Data Size:    4769280 Bytes = 4.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK
OK

Starting kernel ...



________________________________
This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150811/7a72281d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.aug11tue15
Type: application/octet-stream
Size: 1332 bytes
Desc: .config.aug11tue15
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150811/7a72281d/attachment.obj>

[Buildroot] bootm - "Starting kernel"

[Jörg Krause]

Hi Tommy Lee,

On Di, 2015-08-11 at 16:27 -0700, Lee, Tommy wrote:
> Hi Buildroot mailing list,
>  
> My host is Ubuntu-14.04 LTS. My Buildroot release is 2015.05. I have
> made the former meet the latter?s requirements. My target is Marvell
> ARMADA A385 (ARM-Cortex-A9) DB-88F6820-GP. This board is bootable
> using the U-Boot-1.73 and the USB which are given by Marvell.
>  
> I used Buildroot-2015.05 and built the uImage and rootfs.cpio.uboot
> with no problems. I enabled the TFTP server on my host.
>  
> On my target, the execution of the following commands, listed below,
> ended up with ?Starting kernel?, no display of kernel booting
> messages. The attached is the .config file I created this the make
> process.
>  
> I am resolving this issue now. Your experience sharing is extremely
> grateful.
>  
> Tommy
>  
> Marvell>> tftp 02000000 10.28.1.20:uImage
> Using egiga0 device
> TFTP from server 10.28.1.20; our IP address is 10.28.1.47
> Filename 'uImage'.
> Load address: 0x2000000
> Loading:
> #################################################################
>         
> #################################################################
>         
> #################################################################
>          ##############
>          1.6 MiB/s
> done
> Bytes transferred = 1066696 (1046c8 hex)
> Marvell>> tftp 02200000 10.28.1.20:rootfs.cpio.uboot
> Using egiga0 device
> TFTP from server 10.28.1.20; our IP address is 10.28.1.47
> Filename 'rootfs.cpio.uboot'.
> Load address: 0x2200000
> Loading:
> #################################################################
>         
> #################################################################
>         
> #################################################################
>         
> #################################################################
>         
> #################################################################
>         
> #################################################################
>         
> #################################################################
>         
> #################################################################
>         
> #################################################################
>         
> #################################################################
>         
> #################################################################
>         
> #################################################################
>         
> #################################################################
>         
> #################################################################
>          ######################
>          1.7 MiB/s
> done
> Bytes transferred = 4769344 (48c640 hex)
> Marvell>> bootm 02000000 02200000
> ## Booting kernel from Legacy Image at 02000000 ...
>    Image Name:   Linux-4.0.4
>    Created:      2015-08-11   0:21:58 UTC
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    1066632 Bytes = 1 MiB
>    Load Address: 02000000
>    Entry Point:  02000000
>    Verifying Checksum ... OK
> ## Loading init Ramdisk from Legacy Image at 02200000 ...
>    Image Name:
>    Created:      2015-08-11  15:25:49 UTC
>    Image Type:   ARM Linux RAMDisk Image (uncompressed)
>    Data Size:    4769280 Bytes = 4.5 MiB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    XIP Kernel Image ... OK
> OK
>  
> Starting kernel ...

I guess for a misconfigured console... TI has very helpful
documentation about using U-Boot and Linux [1].

Best regards
J?rg Krause

[1] http://processors.wiki.ti.com/index.php/Kernel_-_Common_Problems_Bo
oting_Linux#Problem_.231_
-_No_more_output_is_seen_on_the_console_after_.22Starting_Kernel....22

[Buildroot] bootm - "Starting kernel"

[Lee, Tommy]

Hi Buildroot mailing list,

My yesterday's U-Boot bootargs for my bootm was "console=/dev/ttyS0,115200n8 mem=32M initrd=0x02200000 rw root=/dev/ram0 rw eth=${ethaddr}

The original bootargs was given by Marvell for booting from their USB storage device.

Tommy
________________________________________
From: Lee, Tommy
Sent: Tuesday, August 11, 2015 4:27 PM
To: buildroot at busybox.net
Subject: bootm - "Starting kernel"

Hi Buildroot mailing list,

My host is Ubuntu-14.04 LTS. My Buildroot release is 2015.05. I have made the former meet the latter?s requirements. My target is Marvell ARMADA A385 (ARM-Cortex-A9) DB-88F6820-GP. This board is bootable using the U-Boot-1.73 and the USB which are given by Marvell.

I used Buildroot-2015.05 and built the uImage and rootfs.cpio.uboot with no problems. I enabled the TFTP server on my host.

On my target, the execution of the following commands, listed below, ended up with ?Starting kernel?, no display of kernel booting messages. The attached is the .config file I created this the make process.

I am resolving this issue now. Your experience sharing is extremely grateful.

Tommy

Marvell>> tftp 02000000 10.28.1.20:uImage
Using egiga0 device
TFTP from server 10.28.1.20; our IP address is 10.28.1.47
Filename 'uImage'.
Load address: 0x2000000
Loading: #################################################################
         #################################################################
         #################################################################
         ##############
         1.6 MiB/s
done
Bytes transferred = 1066696 (1046c8 hex)
Marvell>> tftp 02200000 10.28.1.20:rootfs.cpio.uboot
Using egiga0 device
TFTP from server 10.28.1.20; our IP address is 10.28.1.47
Filename 'rootfs.cpio.uboot'.
Load address: 0x2200000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ######################
         1.7 MiB/s
done
Bytes transferred = 4769344 (48c640 hex)
Marvell>> bootm 02000000 02200000
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   Linux-4.0.4
   Created:      2015-08-11   0:21:58 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1066632 Bytes = 1 MiB
   Load Address: 02000000
   Entry Point:  02000000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02200000 ...
   Image Name:
   Created:      2015-08-11  15:25:49 UTC
   Image Type:   ARM Linux RAMDisk Image (uncompressed)
   Data Size:    4769280 Bytes = 4.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK
OK

Starting kernel ...



This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.

[Buildroot] bootm - "Starting kernel"

[Brendan Heading]

> My yesterday's U-Boot bootargs for my bootm was "console=/dev/ttyS0,115200n8 mem=32M initrd=0x02200000 rw root=/dev/ram0 rw eth=${ethaddr}
>
> The original bootargs was given by Marvell for booting from their USB storage device.

Tommy.

If I can ask a silly question .. the kernel configuration within your
buildroot .config is called:

../../ARMADA/ARMADAsoftware/buildroot/configs/marvell_ca9_armv7_le_uclibc_sfp_reduced_defconfig

This is normally the directory where *buildroot* configs are kept, and
the filename strongly implies that it's a buildroot config. However
this configuration option is supposed to denote the *kernel* config.

If so, it would cause the kernel to be built wrongly. Can you attach a
copy of this file ? Can you also attach a copy of your complete
buildroot .config, ie without pieces removed ?

Brendan

[Buildroot] bootm - "Starting kernel"

[Brendan Heading]

[cc list]

> The attached are the files you like to see. I used BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE because Marvell's CA9 defconfig files do not exist in the buildroot-2015.05/configs folder. Altogether Marvell gave me four defconfig files shows as below:
>
> tclee at Latitude-E6400:~/Downloads/aug10mon15/buildroot-2015.05$ ls -lrt ../../ARMADA/ARMADAsoftware/buildroot/configs/marvell_ca9*defconfig
> -rw-r--r-- 1 tclee tclee   659 Feb 27 17:52 ../../ARMADA/ARMADAsoftware/buildroot/configs/marvell_ca9_armv7_le_uclibc_sfp_reduced_defconfig
> -rwxr-xr-x 1 tclee tclee 30708 Feb 27 17:52 ../../ARMADA/ARMADAsoftware/buildroot/configs/marvell_ca9_armv7_le_uclibc_sfp_defconfig
> -rwxr-xr-x 1 tclee tclee 30488 Feb 27 17:52 ../../ARMADA/ARMADAsoftware/buildroot/configs/marvell_ca9_armv7_le_hfp_defconfig
> -rwxr-xr-x 1 tclee tclee 30055 Feb 27 17:52 ../../ARMADA/ARMADAsoftware/buildroot/configs/marvell_ca9_armv7_be_hfp_defconfig

Tommy,

These are buildroot configurations. You're passing them to the kernel
build, which will definitely not work.

I'd suggest using the mvebu_v7_defconfig which is part of the kernel
tree (in recent kernel versions). In Buildroot, under Linux kernel,
set the "in-tree defconfig file" option, and set "defconfig name" to
mvebu_v7.

Marvell appear to have their own toolchain, which they expect to find
in /opt. It's probably nothing special, though.

Brendan

[Buildroot] bootm - "Starting kernel"

[Brendan Heading]

Tommy,

Please keep the list CC'd.

> tclee at Latitude-E6400:~/Downloads/aug10mon15/buildroot-2015.05$ find . -name "*mvebu*v7*defconfig"|xargs ls -lrt
> -rw-rw-r-- 1 tclee tclee 2957 May 17 09:55 ./output/build/linux-headers-4.0.4/arch/arm/configs/mvebu_v7_defconfig
> -rw-rw-r-- 1 tclee tclee 2957 May 17 09:55 ./output/build/linux-4.0.4/arch/arm/configs/mvebu_v7_defconfig
>
> The md5sum shows that they are identical. Please tell me how to use it for the make process. I wonder if I need to copy it to the configs folder for using the "in-tree defconfig file" option.

The above directories are where buildroot has unpacked your kernel to build it.

No, you don't need to copy anything. Set up buildroot as I described
in my previous email.

Brendan

[Buildroot] bootm - "Starting kernel"

[Lee, Tommy]

I will do it this afternoon.

-----Original Message-----
From: buildroot [mailto:buildroot-bounces at busybox.net] On Behalf Of Brendan Heading
Sent: Wednesday, August 12, 2015 11:51 AM
To: Lee, Tommy; buildroot at buildroot.org
Subject: Re: [Buildroot] bootm - "Starting kernel"

Tommy,

Please keep the list CC'd.

> tclee at Latitude-E6400:~/Downloads/aug10mon15/buildroot-2015.05$ find .
> -name "*mvebu*v7*defconfig"|xargs ls -lrt
> -rw-rw-r-- 1 tclee tclee 2957 May 17 09:55
> ./output/build/linux-headers-4.0.4/arch/arm/configs/mvebu_v7_defconfig
> -rw-rw-r-- 1 tclee tclee 2957 May 17 09:55
> ./output/build/linux-4.0.4/arch/arm/configs/mvebu_v7_defconfig
>
> The md5sum shows that they are identical. Please tell me how to use it for the make process. I wonder if I need to copy it to the configs folder for using the "in-tree defconfig file" option.

The above directories are where buildroot has unpacked your kernel to build it.

No, you don't need to copy anything. Set up buildroot as I described in my previous email.

Brendan
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.

[Buildroot] bootm - "Starting kernel"

[Lee, Tommy]

Brendan,

I just did the make process again, with BR2_LINUX_KERNEL_DEFCONFIG="mvebu_v7" which is the only change. This time the uImage and rootfs sizes are much bigger than the ones of yesterday:

-rw-r--r-- 1 root root 7776320 Aug 12 14:53 rootfs.cpio.uboot
-rw-r--r-- 1 root root 3539008 Aug 12 14:53 uImage

On my target, I did the TFTP downloads of the above two files in SDRAM. The uImage is loaded at 0x02000000; rootfd.cpio.uboot:

Marvell>> tftp 02000000 10.28.1.20:uImage
Using egiga0 device
TFTP from server 10.28.1.20; our IP address is 10.28.1.47
Filename 'uImage'.
Load address: 0x2000000
Loading: #################################################################
         .....
         ##########################################
         1.6 MiB/s
done
Bytes transferred = 3539008 (360040 hex)
Marvell>>
doneMarvell>> tftp 02400000 10.28.1.20:rootfs.cpio.uboot
Using egiga0 device
TFTP from server 10.28.1.20; our IP address is 10.28.1.47
Filename 'rootfs.cpio.uboot'.
Load address: 0x2400000
Loading: #################################################################
         .....
         ########################
         1.7 MiB/s
done
Bytes transferred = 7776320 (76a840 hex)
Marvell>>

Then I changed the bootargs string:

Marvell>> env print bootargs
bootargs=console=ttyS0,115200n8 mem=2G initrd=0x02400000,8M rw root=/dev/ram0 rw eth=00:50:43:ec:16:4d
Marvell>>

After that, unfortunately,my bootm command still shows no more than "Starting kernel". The attached are the defconfig and .config files used for this make process. I hope you would review them to see the cause of the booting hang.

Tommy

Marvell>> bootm 0x02000000 0x02400000
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   Linux-4.0.4
   Created:      2015-08-12  21:51:11 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3538944 Bytes = 3.4 MiB
   Load Address: 02000000
   Entry Point:  02000000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02400000 ...
   Image Name:
   Created:      2015-08-12  21:51:55 UTC
   Image Type:   ARM Linux RAMDisk Image (uncompressed)
   Data Size:    7776256 Bytes = 7.4 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK
OK

Starting kernel ...




This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config
Type: application/octet-stream
Size: 54022 bytes
Desc: config
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150812/45b45148/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mvebu_v7_defconfig
Type: application/octet-stream
Size: 2957 bytes
Desc: mvebu_v7_defconfig
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150812/45b45148/attachment-0001.obj>

[Buildroot] bootm - "Starting kernel"

[Brendan Heading]

> -rw-r--r-- 1 root root 7776320 Aug 12 14:53 rootfs.cpio.uboot
> -rw-r--r-- 1 root root 3539008 Aug 12 14:53 uImage
>
> On my target, I did the TFTP downloads of the above two files in SDRAM. The uImage is loaded at 0x02000000; rootfd.cpio.uboot:

Tommy,

Can you send through the System.map file generated by the kernel ?
It's interesting that the kernel has apparently been linked to start
at 0x0000 0000. I'm not so familiar with ARM; maybe that's normal.

Also, can you run the test again, except without loading the ramdisk.
Just load the kernel. It will probably still fail but it's one less
variable.

Is there a device tree file for this board ? If so you probably need
to configure it in buildroot and load it using u-boot/pass it to the
kernel.

regards

Brendan

[Buildroot] bootm - "Starting kernel"

[Lee, Tommy]

Brendan,

The Marvell's USB has a n armada-385-db-ap.dtb file. My .config file has no such setting yet:

tclee at Latitude-E6400:~/Downloads/aug10mon15/buildroot-2015.05$ egrep DTS .config
# BR2_LINUX_KERNEL_DTS_SUPPORT is not set

I discovered only two map files through the make process. They are not map of kernel:

tclee at Latitude-E6400:~/Downloads/aug10mon15/buildroot-2015.05$ find . -name "*.map"|xargs ls -l|egrep "Aug 12"
-rw-rw-r-- 1 tclee tclee 8691522 Aug 12 16:56 ./output/build/busybox-1.23.2/busybox_unstripped.map
-rw-rw-r-- 1 tclee tclee   22576 Aug 12 16:54 ./output/build/host-gcc-final-4.8.4/build/arm-buildroot-linux-uclibcgnueabi/libgcc/libgcc.map
tclee at Latitude-E6400:~/Downloads/aug10mon15/buildroot-2015.05$

I tried the " bootm 0x02000000" command. The result is same.

Marvell>> print bootargs
bootargs=console=ttyS0,115200n8 mem=2G initrd=0x02400000,8M rw root=/dev/ram0 rw
 eth=00:50:43:ec:16:4d
Marvell>> bootm 0x02000000
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   Linux-4.0.4
   Created:      2015-08-12  21:51:11 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3538944 Bytes = 3.4 MiB
   Load Address: 02000000
   Entry Point:  02000000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK
OK

Starting kernel ...

-----Original Message-----
From: Brendan Heading [mailto:brendanheading at gmail.com]
Sent: Wednesday, August 12, 2015 4:48 PM
To: Lee, Tommy
Cc: buildroot at busybox.net
Subject: Re: bootm - "Starting kernel"

> -rw-r--r-- 1 root root 7776320 Aug 12 14:53 rootfs.cpio.uboot
> -rw-r--r-- 1 root root 3539008 Aug 12 14:53 uImage
>
> On my target, I did the TFTP downloads of the above two files in SDRAM. The uImage is loaded at 0x02000000; rootfd.cpio.uboot:

Tommy,

Can you send through the System.map file generated by the kernel ?
It's interesting that the kernel has apparently been linked to start at 0x0000 0000. I'm not so familiar with ARM; maybe that's normal.

Also, can you run the test again, except without loading the ramdisk.
Just load the kernel. It will probably still fail but it's one less variable.

Is there a device tree file for this board ? If so you probably need to configure it in buildroot and load it using u-boot/pass it to the kernel.

regards

Brendan

This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.

[Buildroot] bootm - "Starting kernel"

[Lee, Tommy]

Brendan,

I added one line and changed one line in my .config file:

BR2_LINUX_KERNEL_INTREE_DTS_NAME="armada-385-db-ap"
BR2_LINUX_KERNEL_UIMAGE_LOADADDR="0x02080000"

The reason for 0x02080000 is that the Marvell U-Boot has predefined this value for the kernel_addr_r variable. The U-Boot commands I ran were:

Marvell>> tftp 0x02080000 10.28.1.20:uImage - Bytes transferred = 3539008 (360040 hex)
Marvell>> tftp 0x02400000 10.28.1.20:rootfs.cpio.uboot - Bytes transferred = 7776320 (76a840 hex)
Marvell>> tftp 0x02c00000 10.28.1.20:armada-385-db-ap.dtb - Bytes transferred = 13286 (33e6 hex)
Marvell>> setenv bootargs console=ttyS0,115200n8 mem=2G initrd=0x02400000,8M rw root=/dev/ram0 rw eth=00:50:43:ec:16:4d
Marvell>> bootm 0x02080000 0x02400000 0x02c00000

This time, I saw lots of garbage following "Starting kernel". It looks like that the Buildroot system is bootable but the console= part of bootargs needs to be adjusted.

I am resolving this issue. Your experience is definitely welcome.

Tommy

Marvell>> bootm 0x02080000 0x02400000 0x02c00000
## Booting kernel from Legacy Image at 02080000 ...
   Image Name:   Linux-4.0.4
   Created:      2015-08-12  21:51:11 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3538944 Bytes = 3.4 MiB
   Load Address: 02000000
   Entry Point:  02000000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02400000 ...
   Image Name:
   Created:      2015-08-12  21:51:55 UTC
   Image Type:   ARM Linux RAMDisk Image (uncompressed)
   Data Size:    7776256 Bytes = 7.4 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 02c00000
   Booting using the fdt blob at 0x02c00000
   Loading Kernel Image ... OK
OK
   Loading Ramdisk to 7f261000, end 7f9cb800 ... OK
   Loading Device Tree to 00ff9000, end 00fff3e5 ... OK

   Starting Device Tree update ('fdt_skip_update' = no)
Updating device tree failed

Starting kernel ...

??????????????????p?????????????????????????????
.....

-----Original Message-----
From: Lee, Tommy
Sent: Wednesday, August 12, 2015 5:32 PM
To: 'Brendan Heading'
Cc: buildroot at busybox.net
Subject: RE: bootm - "Starting kernel"

Brendan,

The Marvell's USB has a n armada-385-db-ap.dtb file. My .config file has no such setting yet:

tclee at Latitude-E6400:~/Downloads/aug10mon15/buildroot-2015.05$ egrep DTS .config # BR2_LINUX_KERNEL_DTS_SUPPORT is not set

I discovered only two map files through the make process. They are not map of kernel:

tclee at Latitude-E6400:~/Downloads/aug10mon15/buildroot-2015.05$ find . -name "*.map"|xargs ls -l|egrep "Aug 12"
-rw-rw-r-- 1 tclee tclee 8691522 Aug 12 16:56 ./output/build/busybox-1.23.2/busybox_unstripped.map
-rw-rw-r-- 1 tclee tclee   22576 Aug 12 16:54 ./output/build/host-gcc-final-4.8.4/build/arm-buildroot-linux-uclibcgnueabi/libgcc/libgcc.map
tclee at Latitude-E6400:~/Downloads/aug10mon15/buildroot-2015.05$

I tried the " bootm 0x02000000" command. The result is same.

Marvell>> print bootargs
bootargs=console=ttyS0,115200n8 mem=2G initrd=0x02400000,8M rw root=/dev/ram0 rw  eth=00:50:43:ec:16:4d
Marvell>> bootm 0x02000000
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   Linux-4.0.4
   Created:      2015-08-12  21:51:11 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3538944 Bytes = 3.4 MiB
   Load Address: 02000000
   Entry Point:  02000000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK
OK

Starting kernel ...

-----Original Message-----
From: Brendan Heading [mailto:brendanheading at gmail.com]
Sent: Wednesday, August 12, 2015 4:48 PM
To: Lee, Tommy
Cc: buildroot at busybox.net
Subject: Re: bootm - "Starting kernel"

> -rw-r--r-- 1 root root 7776320 Aug 12 14:53 rootfs.cpio.uboot
> -rw-r--r-- 1 root root 3539008 Aug 12 14:53 uImage
>
> On my target, I did the TFTP downloads of the above two files in SDRAM. The uImage is loaded at 0x02000000; rootfd.cpio.uboot:

Tommy,

Can you send through the System.map file generated by the kernel ?
It's interesting that the kernel has apparently been linked to start at 0x0000 0000. I'm not so familiar with ARM; maybe that's normal.

Also, can you run the test again, except without loading the ramdisk.
Just load the kernel. It will probably still fail but it's one less variable.

Is there a device tree file for this board ? If so you probably need to configure it in buildroot and load it using u-boot/pass it to the kernel.

regards

Brendan

This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.

[Buildroot] bootm - "Starting kernel"

[Lee, Tommy]

Hi Buildroot mailing list,

My host is Ubuntu-14.04 LTS. My Buildroot release is 2015.05. I have made the former meet the latter's requirements. My target is Marvell ARMADA A385 (ARM-Cortex-A9) DB-88F6820-GP. This board is bootable using the U-Boot-1.73 and the USB which are given by Marvell.

The two attachments are my .config file and bootz log file for your review.

I am trying to boot my Buildroot Linux system using Marvell's bootable USB template. I have replaced two Marvell's files with the ones I built using my .config in the Buildroot-2015.05 root folder:


1.      -rwxr-xr-x 1 tclee tclee 3538952 Aug 19 11:37 /media/tclee/24e7139b-655a-45d2-a333-72181bca2e7d/boot/zImage

2.      -rw-r--r-- 1 tclee tclee 13286 Aug 19 11:37 /media/tclee/24e7139b-655a-45d2-a333-72181bca2e7d/boot/armada-385-db-ap.dtb

The original Marvell bootamd, bootargs, fdtfile, image_name console, mtdpars and bootargs_root are:


*        bootcmd=usb reset; ext2load usb 0:1 0x2000000  $image_name; ext2load usb 0:1 0x1000000 $fdtfile; setenv bootargs $console $mtdparts $bootargs_root; bootz 0x2000000 - 0x1000000

*        printenv bootargs

*        bootargs=console=ttyS0,115200 mtdparts=spi_flash:4m(boot),-(spi-rootfs) root=/de

*        v/sda1 rw rootdelay=2

*        fdtfile=/boot/armada-385-db-linux-3.10.39-2014_T3.0p5.dtb - change to /boot/ armada-385-db-ap.dtb

*        image_name=/boot/zImage-linux-3.10.39-2014_T3.0p5-armada_mvebu_smp - changed to =/boot/zImage

*        console=console=ttyS0,115200

*        mtdparts=mtdparts=spi_flash:4m(boot),-(spi-rootfs)

*        bootargs_root=root=/dev/sda1 rw rootdelay=2

I did all the bootcmd commands step by step. The final bootz command ended up with a kernel panic message:

[    3.482970] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

I am reporting this panic to see any adjustments I need to do in my .config file.

Tommy







From: Lee, Tommy
Sent: Tuesday, August 11, 2015 4:28 PM
To: 'buildroot at busybox.net'
Subject: bootm - "Starting kernel"

Hi Buildroot mailing list,

My host is Ubuntu-14.04 LTS. My Buildroot release is 2015.05. I have made the former meet the latter's requirements. My target is Marvell ARMADA A385 (ARM-Cortex-A9) DB-88F6820-GP. This board is bootable using the U-Boot-1.73 and the USB which are given by Marvell.

I used Buildroot-2015.05 and built the uImage and rootfs.cpio.uboot with no problems. I enabled the TFTP server on my host.

On my target, the execution of the following commands, listed below, ended up with "Starting kernel", no display of kernel booting messages. The attached is the .config file I created this the make process.

I am resolving this issue now. Your experience sharing is extremely grateful.

Tommy

Marvell>> tftp 02000000 10.28.1.20:uImage
Using egiga0 device
TFTP from server 10.28.1.20; our IP address is 10.28.1.47
Filename 'uImage'.
Load address: 0x2000000
Loading: #################################################################
         #################################################################
         #################################################################
         ##############
         1.6 MiB/s
done
Bytes transferred = 1066696 (1046c8 hex)
Marvell>> tftp 02200000 10.28.1.20:rootfs.cpio.uboot
Using egiga0 device
TFTP from server 10.28.1.20; our IP address is 10.28.1.47
Filename 'rootfs.cpio.uboot'.
Load address: 0x2200000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ######################
         1.7 MiB/s
done
Bytes transferred = 4769344 (48c640 hex)
Marvell>> bootm 02000000 02200000
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   Linux-4.0.4
   Created:      2015-08-11   0:21:58 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1066632 Bytes = 1 MiB
   Load Address: 02000000
   Entry Point:  02000000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02200000 ...
   Image Name:
   Created:      2015-08-11  15:25:49 UTC
   Image Type:   ARM Linux RAMDisk Image (uncompressed)
   Data Size:    4769280 Bytes = 4.5 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK
OK

Starting kernel ...



________________________________
This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150819/5352bab1/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.aug19wed15
Type: application/octet-stream
Size: 54123 bytes
Desc: config.aug19wed15
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150819/5352bab1/attachment-0001.obj>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: aug18tue15bad.txt
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150819/5352bab1/attachment-0001.txt>

[Buildroot] bootm - "Starting kernel"

[Brendan Heading]

> I did all the bootcmd commands step by step. The final bootz command ended
> up with a kernel panic message:
>
> [    3.482970] ---[ end Kernel panic - not syncing: VFS: Unable to mount
> root fs on unknown-block(0,0)
>
> I am reporting this panic to see any adjustments I need to do in my .config
> file.

Tommy,

(please don't quote large parts of older emails in replies)

You seem to be setting your rootfs to /dev/sda in your u-boot command
line option. This only makes sense if your root filesystem is an
attached ATA or SCSI hard disk, which is probably not the case.

The fix for this depends on what you intend to do. You can either
download the rootfs image separately, or you can bake it into the
kernel, or you can flash it separately to an MTD partition and then
mount it when the kernel starts. Personally I prefer to start out with
the initramfs baked into the kernel.

Brendan

[Buildroot] bootm - "Starting kernel"

[Lee, Tommy]

Brendan,



Thanks for your suggestion. Please view my in-line replies.



Tommy



-----Original Message-----
From: Brendan Heading [mailto:brendanheading at gmail.com]
Sent: Thursday, August 20, 2015 12:08 PM
To: Lee, Tommy
Cc: buildroot at busybox.net
Subject: Re: [Buildroot] bootm - "Starting kernel"



You seem to be setting your rootfs to /dev/sda in your u-boot command line option. This only makes sense if your root filesystem is an attached ATA or SCSI hard disk, which is probably not the case.



Marvell?s DB-88F6820-GP board has four SDRAM devices and four SATA connectors. With no SATA devices connected, the Linux system in Marvell?s USB is bootable with root=/dev/sda1. You probably know the reason for the booting success.



In my situation I suppose I need /dev/ram or /dev/ram0 to attach my root filesystem; I need not to use Marvell?s mtdparts string (spi_flash:4m(boot),-(spi-rootfs) .



Comment please.



The fix for this depends on what you intend to do. You can either download the rootfs image separately, or you can bake it into the kernel, or you can flash it separately to an MTD partition and then mount it when the kernel starts. Personally I prefer to start out with the initramfs baked into the kernel.



The kernel binary format is selected as zImage for the U-Boot bootz command. For baking my root filesystem.into the kernel, I suppose my root filesystem?s compression method should be ?no compression?.



Comment please.



Following is the ?filesystem images? configuration I am going to use. I hope you see the configuration is proper.

?..

-*- cpio the root filesystem (for use as an initial RAM filesyste

Compression method (no compression)  --->



[*] initial RAM filesystem linked into linux kernel

?..



Brendan

________________________________
This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150820/56e3c8e5/attachment.html>

[Buildroot] bootm - "Starting kernel"

[Lee, Tommy]

Brendan,

This time the ?VFS: Unable to mount?? issue is resolved. The new issue is the repetition of the of following message:

Starting network...
[    1.618745] mvneta f1030000.ethernet eth0: could not find the PHY
[    1.624877] mvneta f1030000.ethernet eth0: cannot probe MDIO bus
ip: SIOCSIFFLAGS: No such device
Starting netwogetty: bad speedgetty: bad speedgetty: bad speedgetty: bad speedge
tty: bad speedgetty: bad speedgetty: bad speedgetty: bad speedgetty: bad speedge
?..

The attachments are my .config file and the details of my U-Boot log.

I am trying to figure out the cause of this problem. You experience is extremely welcome.

Tommy

________________________________
This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150820/5e4c48e7/attachment-0001.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: aug20thu15bad.txt
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150820/5e4c48e7/attachment-0001.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.aug20thu15
Type: application/octet-stream
Size: 54045 bytes
Desc: config.aug20thu15
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150820/5e4c48e7/attachment-0001.obj>

[Buildroot] bootm - "Starting kernel"

[Lee, Tommy]

Brendan,

FYI, I unplugged the Ethernet cable and did the steps again. This time the same ?tty: bad speedgetty? message is still repeated.

Tommy

From: Lee, Tommy
Sent: Thursday, August 20, 2015 4:47 PM
To: 'Brendan Heading'
Cc: 'buildroot at busybox.net'
Subject: RE: [Buildroot] bootm - "Starting kernel"

Brendan,

This time the ?VFS: Unable to mount?? issue is resolved. The new issue is the repetition of the of following message:

Starting network...
[    1.618745] mvneta f1030000.ethernet eth0: could not find the PHY
[    1.624877] mvneta f1030000.ethernet eth0: cannot probe MDIO bus
ip: SIOCSIFFLAGS: No such device
Starting netwogetty: bad speedgetty: bad speedgetty: bad speedgetty: bad speedge
tty: bad speedgetty: bad speedgetty: bad speedgetty: bad speedgetty: bad speedge
?..

The attachments are my .config file and the details of my U-Boot log.

I am trying to figure out the cause of this problem. You experience is extremely welcome.

Tommy

________________________________
This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150820/00ee76e5/attachment.html>

[Buildroot] bootm - "Starting kernel"

[Brendan Heading]

> FYI, I unplugged the Ethernet cable and did the steps again. This time the
> same ?tty: bad speedgetty? message is still repeated.

Nothing to do with ethernet - it sounds like it's trying to start
getty but there's an issue with the speeds. The error message comes
from loginutils/getty.c inside busybox.

Did you mess around with /etc/inittab, or did you leave it at the defaults ?

Brendan

[Buildroot] bootm - "Starting kernel"

[Lee, Tommy]

Brendan,

I did not touch the inittab files in my buildroot-2015.05. There are five files in the folder as:

tclee at Latitude-E6400:~/Downloads/aug10mon15/buildroot-2015.05$ find . -name inittab|xargs ls -lrt
-rw-rw-r-- 1 tclee tclee 3067 Mar 22 20:06 ./output/build/busybox-1.23.2/examples/inittab
-rw-rw-r-- 1 tclee tclee  100 Mar 22 20:06 ./output/build/busybox-1.23.2/examples/bootfloppy/etc/inittab
-rw-rw-r-- 1 tclee tclee 1053 May 31 14:15 ./system/skeleton/etc/inittab
-rw-rw-r-- 1 tclee tclee  747 May 31 14:15 ./package/sysvinit/inittab
-rw-rw-r-- 1 tclee tclee 1056 Aug 20 15:49 ./output/target/etc/inittab

My booting process must use the last inittab  which was built yesterday. Following are the TTY settings in my current .config file:

tclee at Latitude-E6400:~/Downloads/aug10mon15/buildroot-2015.05$ egrep -n TTY .config
286:BR2_TARGET_GENERIC_GETTY=y
291:BR2_TARGET_GENERIC_GETTY_PORT="ttyS0"
292:# BR2_TARGET_GENERIC_GETTY_BAUDRATE_KEEP is not set
293:# BR2_TARGET_GENERIC_GETTY_BAUDRATE_9600 is not set
294:# BR2_TARGET_GENERIC_GETTY_BAUDRATE_19200 is not set
295:# BR2_TARGET_GENERIC_GETTY_BAUDRATE_38400 is not set
296:# BR2_TARGET_GENERIC_GETTY_BAUDRATE_57600 is not set
297:BR2_TARGET_GENERIC_GETTY_BAUDRATE_115200=y
298:BR2_TARGET_GENERIC_GETTY_BAUDRATE="115200"
299:BR2_TARGET_GENERIC_GETTY_TERM="vt100"
300:BR2_TARGET_GENERIC_GETTY_OPTIONS="n81"

My U-Boot console string is " ttyS0,115200". I doubt whether the settings on Line 299 and Line 300 are improper.

Tommy




-----Original Message-----
From: Brendan Heading [mailto:brendanheading at gmail.com]
Sent: Thursday, August 20, 2015 5:12 PM
To: Lee, Tommy
Cc: buildroot at busybox.net
Subject: Re: [Buildroot] bootm - "Starting kernel"

> FYI, I unplugged the Ethernet cable and did the steps again. This time
> the same ?tty: bad speedgetty? message is still repeated.

Nothing to do with ethernet - it sounds like it's trying to start getty but there's an issue with the speeds. The error message comes from loginutils/getty.c inside busybox.

Did you mess around with /etc/inittab, or did you leave it at the defaults ?

Brendan

This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.

[Buildroot] bootm - "Starting kernel"

[Lee, Tommy]

Brendan,

I just succeeded in the booting of my Buildroot-2015.5 Linux-4.0.4 system on Marvell?s DB-88F6820-GP board. The solution to the "getty: bad speed" problem is the change of the "BR2_TARGET_GENERIC_GETTY_OPTIONS=8n1" line to "BR2_TARGET_GENERIC_GETTY_OPTIONS=""".

Thanks for your help on my Buildroot/Marvell work.

Tommy

This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. If you are the intended recipient, please be advised that the content of this message is subject to access, review and disclosure by the sender's e-mail System Administrator.