Hi Stefan, I also have the A2000 and did have problems with it booting until MrNuke fixed the MMC(the latest on sunxi-devel is 3.14.0.rc6). My setup is very similar to yours(running Debian headless although without any external devices). Looking at the size of the kernel then it seems that you will have to configure some of the features that you will need. This is what I add to the sunxi_defconfig to get the device to boot. +CONFIG_USB=y +CONFIG_MMC=y +#CONFIG_MMC_DEBUG=y +CONFIG_USB_SUPPORT=y +CONFIG_PPS=y +CONFIG_USB_ANNOUNCE_NEW_DEVICES=y +CONFIG_MMC_SUNXI=y +CONFIG_RTC_CLASS=y +CONFIG_EXT3_FS=y +CONFIG_EXT4_FS=y +#CONFIG_EXT4_DEBUG=y +CONFIG_BTRFS_FS=y +CONFIG_FUSE_FS=y +CONFIG_MAGIC_SYSRQ=y +CONFIG_IKCONFIG=y +CONFIG_IKCONFIG_PROC=y +CONFIG_MD=y +CONFIG_NET_VENDOR_STMICRO=y +CONFIG_USB_EHCI_HCD=y +CONFIG_RTC_DRV_SUNXI=y +CONFIG_BLK_DEV_DM=y +CONFIG_STMMAC_ETH=y +CONFIG_PTP_1588_CLOCK=y +CONFIG_USB_EHCI_HCD_PLATFORM=y +CONFIG_DM_MIRROR=y +CONFIG_SPI_SUN4I=y
Some of them are probably not required but this seems to work for me. You will also need to use Hans' u-boot for the sunxi-devel track. CK On 26 March 2014 14:48, Stefan Monnier <monn...@iro.umontreal.ca> 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 > > -- > 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 linux-sunxi+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
