Starting kernel ...

nallapaneni venkata subbaiah

Other Parts Discussed in Thread: DRA752, PMP

Hi,

Background:

We are working on the am57xx-evm with ti-processor-sdk-linux-am57xx-evm-02.00.01.07. With pre built images we are getting linux login prompt and web matrix browser. Every thing working fine. After the we build the kernel using the default tisdk_am57xx-evm_defconfig. we have copied the zImage, vmlinux, dtb and as well as installed the modules. It is getting stuck at Starting kernel ....

U-Boot SPL 2015.07 (Jan 08 2016 - 18:45:34)
DRA752 ES1.1
reading args
spl_load_image_fat_os: error reading image args, err - -1
reading u-boot.img
reading u-boot.img

U-Boot 2015.07 (Jan 08 2016 - 18:45:34 -0500)

CPU : DRA752 ES1.1
BoaI2C:   ready
DRAM: 2 GiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
reading uboot.env

** Unable to read "uboot.env" from mmc0:1 **
Using default environment

SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst
SCSI: SATA link 0 timeout.
AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst
scanning bus for devices...
Found 0 device(s).
Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
reading boot.scr
** Unable to read file boot.scr **
reading uEnv.txt
574 bytes read in 3 ms (186.5 KiB/s)
Loaded env from uEnv.txt
Importing environment from mmc0 ...
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
3337192 bytes read in 182 ms (17.5 MiB/s)
90972 bytes read in 36 ms (2.4 MiB/s)
Booting from mmc0 ...
Kernel image @ 0x82000000 [ 0x000000 - 0x32ebe8 ]
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Loading Device Tree to 8ffe6000, end 8ffff35b ... OK

Starting kernel ...

We have gone through all the options mentioned in the earlier posts as well as "Kernel - Common Problems Booting Linux" document available in the following path http://processors.wiki.ti.com/index.php/Kernel_-_Common_Problems_Booting_Linux

we have verified the boot arguments and please find the attached boot arguments(from U-BOOT printenv)

printenv with rebuilt Images:

board=beagle_x15
board_name=beagle_x15
bootenv=uEnv.txt
loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenv}
mmcboot=mmc dev ${mmcdev}; if mmc rescan; then echo SD/MMC found on device ${mmcdev};if run loadbootenv; then echo Loaded environment from ${b;
ver=U-Boot 2015.07 (Oct 07 2015 - 14:54:21 -0400)
Environment size: 3534/65532 bytes

printenv with kernel build Images:

board=am57xx
board_name=am57xx_evm
board_rev=A.20
board_serial=40154P550203
bootenvfile=uEnv.txt
dfu_alt_info_qspi=MLO raw 0x0 0x010000;MLO.backup1 raw 0x010000 0x010000;MLO.backup2 raw 0x020000 0x010000;MLO.backup3 raw 0x030000 0x010000;u0
envboot=mmc dev ${mmcdev}; if mmc rescan; then echo SD/MMC found on device ${mmcdev};if run loadbootscript; then run bootscript;else if run lo;
loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenvfile}
mmcboot=mmc dev ${mmcdev}; if mmc rescan; then echo SD/MMC found on device ${mmcdev};if run loadimage; then run loadfdt; echo Booting from mmc;
ver=U-Boot 2015.07 (Jan 08 2016 - 18:45:34 -0500)
Environment size: 4438/65532 bytes
U-Boot#

Please find the difference b/n the two environments and suggest what might be the issue.

Thanks & Regards,

N.V.Subbaiah.

over 9 years ago

0 Titusrathinaraj Stalin over 9 years ago

TI__Guru** 116100 points

Dear N.V.Subbaiah,
Did you rebuild the u-boot also ?
Can you use the pre-built "uEnv.txt" file ?
If you see changes in "printenv" then it seems you are using different u-boot binary or "uEnv.txt" file.

I hope, you are just rebuild the kernel with dtb, then you should not see different prints from "printenv" command. Please make sure.

0 nallapaneni venkata subbaiah over 9 years ago in reply to Titusrathinaraj Stalin

Expert 1200 points

Hi,

First we created the SD card using ./create-sdcard.sh. Later we build the kernel from linux folder. we have overwrite the zImage, vmlinux and System.map files. Sill there are same differences in u-boot environments. We are not getting any clue. Please have a look at this.

Thanks & Regards,
N.V.Subbaiah

0 Ondrej Ton over 9 years ago in reply to nallapaneni venkata subbaiah

Prodigy 180 points

Hi N.V.Subbaiah,

I'm just a beginner playing with AM437x SK board now, not an expert. But I had a similar problem with starting kernel from QSPI Flash memory.

From wiki I used this command

U-Boot # setenv bootargs console=${console} spi-ti-qspi.enable_qspi=1 root=/dev/mtdblock6 rootfstype=jffs2

But I had no rootfs copied to QSPI Flash (this step I'm missing in the wiki), so booting process freezed like this:

Kernel image @ 0x82000000 [ 0x000000 - 0x330750 ]
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Loading Device Tree to 8fff1000, end 8ffff2c2 ... OK

Starting kernel ...

Then I used rootfs from SD Card

setenv bootargs console=${console} spi-ti-qspi.enable_qspi=1 ${optargs} root=PARTUUID=${uuid} rw rootfstype=${mmcrootfstype}

and it worked..

My mmcboot env variable look like this:

mmcboot=mmc dev ${mmcdev}; setenv devnum ${mmcdev}; setenv devtype mmc; if mmc rescan; then echo SD/MMC found on device ${devnum};if run loadimage; then run loadfdt; echo Booting from mmc${mmcdev} ...; run args_mmc; bootz ${loadaddr} - ${fdtaddr}; fi;fi;

args_mmc=run finduuid;setenv bootargs console=${console} ${optargs} root=PARTUUID=${uuid} rw rootfstype=${mmcrootfstype};

Regards, Ondra

Processors

Processors forum

Starting kernel ...