On Thu, May 22, 2014 at 2:14 AM, Yassin Jaffer <yassinjaf...@gmail.com> wrote: > sorry I did not realize that your are booting from NFS, I had my own mmc > driver. I guess you could use initramfs. I've not tried to boot from NFS > before. > > > On Thu, May 22, 2014 at 3:56 PM, Yassin Jaffer <yassinjaf...@gmail.com> > wrote: >> >> setenv bootargs console=ttyS0,115200 loglevel=9 earlyprintk >> root=/dev/mmcblk0p2 ro rootwait
So part of the problem is boot args. I can fix the rootfs once the kernel starts booting. I got a little further... sun7i# setenv bootargs console=ttyS0,115200 loglevel=9 earlyprintk root=/dev/mmcblk0p2 ro rootwait sun7i# bootm 0x46000000 - 0x60000000 ## Booting kernel from Legacy Image at 46000000 ... Image Name: Linux-3.15.0-rc5-80186-gb9505da Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1846144 Bytes = 1.8 MiB Load Address: 40008000 Entry Point: 40008000 Verifying Checksum ... OK ## Flattened Device Tree blob at 60000000 Booting using the fdt blob at 0x60000000 Loading Kernel Image ... OK Loading Device Tree to 4fff7000, end 4ffffddd ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. ����������������|�����p ��x~���� ���������������������x�������������������������������������>�����~����������������������������������������������������������������� That looks like the baud rate of early printk is not 115200. Once I can see what is going on, this feels to me like the kernel is not finding a machine name in the device tree that it likes. But I am using the cubietruck DT from that same kernel tree. >> >> >> On Thu, May 22, 2014 at 2:26 PM, jonsm...@gmail.com <jonsm...@gmail.com> >> wrote: >>> >>> I can't get anywhere trying to boot a devel device tree kernel on >>> Cubietruck. >>> >>> This is with https://github.com/jwrdegoede/linux-sunxi.git and the >>> linux-devel branch. >>> I don't get any boot output. I can boot a 3.4 kernel without problem. >>> >>> I followed these steps. http://linux-sunxi.org/Mainline_Kernel_Howto >>> I also tried turning on low level printk but still no output >>> >>> U-Boot SPL 2014.04-10675-g44b53fd (May 19 2014 - 20:39:18) >>> Board: Cubietruck >>> DRAM: 2048 MiB >>> CPU: 960000000Hz, AXI/AHB/APB: 3/2/2 >>> spl: not an uImage at 1600 >>> >>> >>> U-Boot 2014.04-10675-g44b53fd (May 19 2014 - 20:39:18) Allwinner >>> Technology >>> >>> CPU: Allwinner A20 (SUN7I) >>> Board: Cubietruck >>> I2C: ready >>> DRAM: 2 GiB >>> MMC: SUNXI SD/MMC: 0 >>> In: serial >>> Out: serial >>> Err: serial >>> Net: dwmac.1c50000 >>> Hit any key to stop autoboot: 0 >>> sun7i# tftp 0x49000000 /var/lib/tftpboot/ct.dtb >>> dwmac.1c50000 Waiting for PHY auto negotiation to complete........ done >>> Speed: 1000, full duplex >>> Using dwmac.1c50000 device >>> TFTP from server 192.168.1.50; our IP address is 192.168.1.51 >>> Filename '/var/lib/tftpboot/ct.dtb'. >>> Load address: 0x49000000 >>> Loading: ## >>> 7.6 MiB/s >>> done >>> Bytes transferred = 24030 (5dde hex) >>> sun7i# tftp 0x46000000 /var/lib/tftpboot/uImage >>> Speed: 1000, full duplex >>> Using dwmac.1c50000 device >>> TFTP from server 192.168.1.50; our IP address is 192.168.1.51 >>> Filename '/var/lib/tftpboot/uImage'. >>> Load address: 0x46000000 >>> Loading: >>> ################################################################# >>> ############################################################# >>> 12.3 MiB/s >>> done >>> Bytes transferred = 1837040 (1c07f0 hex) >>> sun7i# env set fdt_high ffffffff >>> sun7i# >>> sun7i# bootm 0x46000000 - 0x49000000 >>> ## Booting kernel from Legacy Image at 46000000 ... >>> Image Name: Linux-3.15.0-rc5-80186-gb9505da >>> Image Type: ARM Linux Kernel Image (uncompressed) >>> Data Size: 1836976 Bytes = 1.8 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 49008ddd >>> >>> Starting kernel ... >>> >>> >>> >>> >>> >>> -- >>> Jon Smirl >>> jonsm...@gmail.com >>> >>> -- >>> 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. -- Jon Smirl jonsm...@gmail.com -- 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.
