Re: flash-kernel and dtb
Hi Karsten,
thanks for your response.
On Saturday 14 June 2014 23:56:01 Karsten Merker wrote:
> On Sat, Jun 14, 2014 at 10:36:43PM +0200, Rainer Dorsch wrote:
> > I try to get the kernel up with manual tweaks in u-boot first:
> >
> > CPU: Freescale i.MX6Q rev1.2 at 792 MHz
> > Reset cause: POR
> > Board: MX6-CuBox-i
> > DRAM: 2 GiB
> > MMC: FSL_SDHC: 0
> > In: serial
> > Out: vga
> > Err: vga
> > Net: FEC
> > (Re)start USB...
> > USB0: lowlevel init failed
> > USB1: USB EHCI 1.00
> > scanning bus 1 for devices... 1 USB Device(s) found
> >
> > scanning usb for storage devices... 0 Storage Device(s) found
> > scanning usb for ethernet devices... 0 Ethernet Device(s) found
> >
> > Hit any key to stop autoboot: 0
> > CuBox-i U-Boot > setenv mmcdev 0
> > CuBox-i U-Boot > setenv mmcpart 2
> > CuBox-i U-Boot > setenv ramdiskaddr 0x11800000
> > CuBox-i U-Boot > setenv fdt_addr 0x18000000
> > CuBox-i U-Boot > setenv scr_addr 0x19900000
> > CuBox-i U-Boot > ext4load mmc 0:2 0x19900000 /boot/boot.scr
> > 637 bytes read in 94 ms (5.9 KiB/s)
> > CuBox-i U-Boot > source 0x19900000
> > ## Executing script at 19900000
> > 2857680 bytes read in 248 ms (11 MiB/s)
> > 28603 bytes read in 126 ms (221.7 KiB/s)
> > 10934444 bytes read in 620 ms (16.8 MiB/s)
> > Booting Debian 3.15-rc8-armmp from mmc 0:2...
> > Kernel image @ 0x10800000 [ 0x000000 - 0x2b9ad0 ]
> > ## Flattened Device Tree blob at 18000000
> >
> > Booting using the fdt blob at 0x18000000
> >
> > EHCI failed to shut down host controller.
> >
> > Loading Ramdisk to 8ecf1000, end 8f75e8ac ... OK
> > Using Device Tree in place at 18000000, end 18009fba
> >
> > Starting kernel ...
> >
> > but then the boot process is stuck.
>
> It looks like you might not have set a console device, so
> possibly the kernel boots, but you do not see any output. Try
> setting the console device on the kernel commandline with a
> command like:
>
> setenv bootargs 'console=ttyS0,115200 rootwait panic=10'
>
> (The example assumes that the serial port on the i.MX6 is ttyS0 and
> not something else such as ttyAMA0.)
The boot process is not successful. I have an ssh server running on the cubox
and this is also not reachable.
I my post a few minutes back I also showed that setting bootargs does not
change something.
I also added the panic=10 now
rd@bokocube:~$ cat /etc/default/flash-kernel
#LINUX_KERNEL_CMDLINE="quiet"
LINUX_KERNEL_CMDLINE="root=/dev/mmcblk0p2 rootfstype=ext4 ro rootwait
console=ttymxc0,115200 panic=10"
rd@bokocube:~$
but then after 10s the system reboots and the default boot process starts the
standard image.
Thanks,
Rainer
--
Rainer Dorsch
http://bokomoko.de/
Reply to: