On Thursday, 27 March 2014 00:48:18 UTC+11, Stefan Monnier wrote: > Since my Mele A2000 keeps locking up when using the 3.4 kernel (as > > reported here several months ago), I decided I should try the sunxi-next > > kernel (my machine can be headless, it just needs USB and SATA support, > > basically). > > > > So I got the sunxi-next branch from Github's linux-sunxi. Then did > > > > make sunxi_defconfig > > LOADADDR=0x40008000 make uImage dtbs > > > > (note: this was run under Debian "stable" armhf on my Mele A2000) > > then copied the files to my SD card. > > Then at U-Boot's prompt I did: > > > > ext2load mmc 0 0x46000000 uImage > > ext2load mmc 0 0x49000000 sun4i-a10-a1000.dtb > > env set fdt_high ffffffff > > bootm 0x46000000 - 0x49000000 > > > > Admittedly, there's no initramfs set, but I figured I'll see about that later. > > Problem is, this doesn't give me much. I get: > > > > ## Booting kernel from Legacy Image at 46000000 ... > > Image Name: Linux-3.14.0-rc5-00084-ge8176a3 > > Created: 2014-03-26 12:57:21 UTC > > Image Type: ARM Linux Kernel Image (uncompressed) > > Data Size: 1784832 Bytes = 1.7 MiB > > Load Address: 40008000 > > Entry Point: 40008000 > > Verifying Checksum ... OK > > ## Flattened Device Tree blob at 49000000 > > Booting using the fdt blob at 0x49000000 > > Loading Kernel Image ... OK > > Using Device Tree in place at 49000000, end 49006bde > > > > Starting kernel ... > > > > and that's it: no more output after that. > > I'm using the U-Boot that comes with the "Fedora 19 remix", and my > > "uEnv.txt" says "console=ttyS0,115200". With the 3.4 kernel, I usually > > get output starting with > > > > [ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), > cr=10c5387d > > > > any idea what might be going on? Is there a problem with the build > > itself so Linux doesn't even get to outputting this first line. Or is > > it outputting it somewhere else? Or did I get unlucky with a transient > > problem in sunxi-next? > > > > > > Stefan
Thanks for the config file and post. My starting point is Fedora 19 booting ok on my MK802II ( so working u-boot). Because I have not found a way to access the u-boot prompt on the MK802II the steps I have used are: make -j5 ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- menuconfig make -j5 ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- LOADADDR=0x40008000 uImage dtbs make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- -j5 INSTALL_MOD_PATH=output modules make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- -j5 INSTALL_MOD_PATH=output modules_install put a copy of the created uImage and arch/arm/boot/sun4i-a10-a1000.dtb into the boot partition of the sdcard copy the created modules to the /lib/modules on the rootfs partition In case the existing boot.scr has some inconsistency I save this to boot.cmd: setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootwait ro earlyprintk debug ext2load mmc 0 0x46000000 uImage ext2load mmc 0 0x49000000 sun4i-a10-a1000.dtb env set fdt_high ffffffff bootm 0x46000000 - 0x49000000 and run: mkimage -C none -A arm -T script -d boot.cmd boot.scr copy this boot.scr to the boot partition of the sdcard But alas it fails to boot so I am missing something somewhere. Also tried this alternative method: cat arch/arm/boot/zImage arch/arm/boot/dts/sun4i-a10-a1000.dtb > zImage_w_dtb mkimage -A arm -O linux -C none -T kernel -a 40008000 -e 40008000 -d zImage_w_dtb uImage but maybe should be ..... -a 0x00008000 -e 0x00008000 Any thoughts? -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
