Welcome! Log In Create A New Profile

Advanced

After installation of the latest UBoot, it stuck at "Starting kernel ..."

Posted by bchen 
After installation of the latest UBoot, it stuck at "Starting kernel ..."
March 15, 2018 02:24AM
I installed the latest uboot and its environment settings by following this post. https://forum.doozan.com/read.php?3,12381

After that, I used a new USB drive to load the rootfs (Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2) by following https://forum.doozan.com/read.php?2,12096.

When I reboot it, it's stuck at "Starting kernel" as shown below

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:13:18 -0700)
Pogo E02
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
Hit any key to stop autoboot:  0
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'

Partition Map for USB device 0  --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
  1     2048            7825408         8b357a98-01     83 Boot

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
87 bytes read in 754 ms (0 Bytes/s)
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
importing envs ...
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 692 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
3926040 bytes read in 1001 ms (3.7 MiB/s)
loading uInitrd ...
8104328 bytes read in 1109 ms (7 MiB/s)
loading DTB /boot/dts/kirkwood-pogo_e02.dtb ...
10444 bytes read in 3583 ms (2 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.15.2-kirkwood-tld-1
   Created:      2018-03-14   5:36:31 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3925976 Bytes = 3.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.15.2-kirkwood-tld-1
   Created:      2018-03-14   8:56:52 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    8104264 Bytes = 7.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000


Starting kernel ...

I compared the above booting messages with normal ones, I noticed that there should be a message like "loading kernel" after the last line "Booting using the fdt blob at 0x1c00000" but it's missing here and directly dump to "Starting kernel..." That's normal?

This is the printenv. Can anyone help please?

PogoE02> printenv
arcNumber=3542
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogo_e02.dtb
ethact=egiga0
ethaddr=52:3b:20:9c:11:51
if_netconsole=ping $serverip
ipaddr=192.168.2.19
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
machid=dd6
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
nc_ready=1
ncip=192.168.2.118
partition=nand0,2
preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
serverip=192.168.2.118
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_ready_retry=15

Environment size: 3039/131068 bytes
Re: After installation of the latest UBoot, it stuck at "Starting kernel ..."
March 15, 2018 02:03PM
bchen,

No, that's not normal. Try this.

Power up, interrupt serial console at countdown and

setenv custom_params 'earlyprintk=serial'
printenv
boot
Please post the entire serial console here.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: After installation of the latest UBoot, it stuck at "Starting kernel ..."
March 16, 2018 10:25AM
bodhi,

I resolved it by using a different SD card. I don't understand but who cares :P
Re: After installation of the latest UBoot, it stuck at "Starting kernel ..."
March 16, 2018 02:40PM
bchen Wrote:
-------------------------------------------------------
> bodhi,
>
> I resolved it by using a different SD card. I
> don't understand but who cares :P

Cool :) the problem might be during you created the rootfs, you've missed some step/requirements, or the SD card itself is not good for booting (there are brands that really bad for rootfs). Doing it the 2nd time with a different card is alwasy a good idea.

-bodhi
===========================
Forum Wiki
bodhi's corner
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: