Thanks Nikolay, It looks like that discussion was about a 'missing' dtb file, device tree therefor no terminal to display kernel bootup info.
I use the command in u-boot to pass the blob location in sdram. bootz 0x40400000 - 0x40700000 my boot arguments are bootargs=earlyprintk console=ttyAMA0,115200n8 mem=nopentium I dont think that the kernel ever gets to that point because it seem to lockup when the mmu is enabled. head.S - command mcr p15, 0, r0, c1, c0, 0 @ write control reg To see what would happen I did comment out that line and the kernel continued on for a little while, finding the device tree blob. All of my debugging says that this line locks up the cpu. I don't believe that the kernel ever gets to the point of using the blob. Am I completely wrong here? I have not updated my code from linux-fslc since June (30 days old code) this year because it looks like a lot of changes are going on to up to linux 4.x. https://github.com/Freescale/linux-fslc.git https://github.com/Freescale/u-boot-fslc.git On Wed, Aug 5, 2015 at 8:41 AM, Nikolay Dimitrov <[email protected]> wrote: > Hi Justin, > > Please check this Yocto discussion from May 2015: > > https://lists.yoctoproject.org/pipermail/meta-freescale/2015-May/013953.html > > Regards, > Nikolay -- _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
