Other Parts Discussed in Thread: PMP
Tool/software: Linux
Hi,
We have am5708 based custom board. we have successfully get uboot console and tested ethernet and mmc from uboot and working fine, But when we boot kernel from uboot it hangs at "Starting kernel..."
I have verified my Debug uart port in uboot and kernel, It is same UART3 and I am passing ttyO2 in bootargs. We followed the guide http://processors.wiki.ti.com/index.php/Kernel_-_Common_Problems_Booting_Linux and enabled CONFIG_DEBUG_OMAP2UART3=y and CONFIG_EARLY_PRINTK=y and tried to boot it but no luck
Here is my booting prings :
U-Boot SPL EDGE
DRA722-GP ES2.0
Trying to boot from MMC1
spl: mmc boot mode: fs
reading args
reading u-boot.img
reading u-boot.img
reading u-boot.img
config name match : TODO am570x-edge
reading u-boot.img
U-Boot 2016.05-gcdf63adf23 (Jul 12 2017 - 12:47:44 +0530)
CPU : DRA722-GP ES2.0
Model: TI AM5708 EDGE
Board: AM570x EDGE REV
DRAM: hwinit dram_init
>>sdram_init()
1 GiB
MMC: no pinctrl for sdr104
no pinctrl for ddr50
no pinctrl for sdr50
no pinctrl for sdr25
no pinctrl for sdr12
no pinctrl for hs200_1_8v
OMAP SD/MMC: 0, OMAP SD/MMC: 1
reading uboot.env
** Unable to read "uboot.env" from mmc0:1 **
Using default environment
BOard ID => 0
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: ethernet driver probe
Warning: ethernet@48484000 using MAC address from ROM
eth0: ethernet@48484000
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
** Unable to read file uEnv.txt **
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
reading zImage
3847224 bytes read in 173 ms (21.2 MiB/s)
reading am570x-edge.dtb
100013 bytes read in 9 ms (10.6 MiB/s)
Kernel image @ 0x82000000 [ 0x000000 - 0x3ab438 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Device Tree to 8ffe4000, end 8ffff6ac ... OK
Starting kernel ...
