Linux 3.13.5 hansg at "Starting kernel ..."

GoogleGroups
1

HiAll,

I have built kernel version 3.13.5 for the Beagleboard-xM. At boot it hangs at “Starting kernel …” (see capture below). Has any one had success with 3.13?

Regards,
Ralph

U-Boot SPL (Feb 28 2014 - 11:58:43)
reading u-boot.img
reading u-boot.img

U-Boot 2014.04-rc1-00190-geeb72e6 (Feb 28 2014 - 11:59:40)

OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 Ghz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 512 MiB
NAND: 0 MiB
MMC: OMAP SD/MMC: 0
*** Warning - readenv() failed, using default environment

In: serial
Out: serial
Err: serial
Beagle xM Rev C
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus 1 are properly configured
No EEPROM on expansion board
Die ID #023200029ff80000016849a90301801c
Net: usb_ether
Hit any key to stop autoboot: 0
mmc0 is current device
gpio: pin 173 (gpio 173) value is 0
gpio: pin 4 (gpio 4) value is 0
SD/MMC found on device 0
reading uEnv.txt
106 bytes read in 3 ms (34.2 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc …
** File not found /boot/uImage **
Booting from nand …

no devices available
Wrong Image Format for bootm command
ERROR: can’t get kernel image!
2692216 bytes read in 212 ms (12.1 MiB/s)
15670 bytes read in 45 ms (339.8 KiB/s)
Booting with DT from mmc0 …
Kernel image @ 0x80200000 [ 0x000000 - 0x291478 ]

Flattened Device Tree blob at 80f80000

Booting using the fdt blob at 0x80f80000
Using Device Tree in place at 80f80000, end 80f86d35

Starting kernel …

2

mainline u-boot is looking for "uImage" at /boot/.

so fix that..

Or use the patches posted here:

http://eewiki.net/display/linuxonarm/BeagleBoard

Regards,

3

Yes, u-boot looks for uImage at first. When it doesn’t find it it looks for zImage. You can see from the log that it’s read the kernel and the FDT:

2692216 bytes read in 212 ms (12.1 MiB/s)
15670 bytes read in 45 ms (339.8 KiB/s)
Booting with DT from mmc0 …
Kernel image @ 0x80200000 [ 0x000000 - 0x291478 ]

Regards,
Ralph

4

Yes, u-boot looks for uImage at first. When it doesn't find it it looks for
zImage. You can see from the log that it's read the kernel and the FDT:

okay

2692216 bytes read in 212 ms (12.1 MiB/s)
15670 bytes read in 45 ms (339.8 KiB/s)
Booting with DT from mmc0 ...
Kernel image @ 0x80200000 [ 0x000000 - 0x291478 ]

Shove the load image address to 0x8030000

Regards,

5

Shove the load image address to 0x80300000

(missed a zero there..)

Regards,

6

Hi Robert,

Same thing at 0x80300000:

Booting with DT from mmc0 …
Kernel image @ 0x80300000 [ 0x000000 - 0x291478 ]

Flattened Device Tree blob at 80f80000

Booting using the fdt blob at 0x80f80000
Using Device Tree in place at 80f80000, end 80f86d35

Starting kernel …

Has the serial port changed maybe? I added bootargs “console=ttyO2,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait” to the FDT.

Regards,
Ralph

7

So if I build a uImage and load it directly from u-boot and run it with:

fatload mmc 0 0x80300000 uImage
bootm 0x80300000

then the kernel boots and I can get a command prompt. The USB phy is not found, however, so no network is available. Anyone have a fix for that?

Regards,
Ralph

8

usb was fixed in v3.13.x, so no external patches are required, so just
compare your config with:

https://github.com/RobertCNelson/armv7-multiplatform/blob/v3.13.x/patches/defconfig

Regards,

9

Hi Robert,

Just to verify, after cloning armv7-multiplatform I don’t see armv7-multiplatform/blob/v3.13.x/patches/defconfig but I do see armv7-multiplatform/patches/defconfig. Is that the correct config file?

Regards,
Ralph

10

here's the wget address:

https://raw.github.com/RobertCNelson/armv7-multiplatform/v3.13.x/patches/defconfig

(master branch is just a readme.)

Regards,