On 06/11/12 09:47, Mark Jackson wrote: > On 06/11/12 06:16, Hiremath, Vaibhav wrote: >> >> Where is your DTB? Is it appended to Kernel image? >> Can you try below sequence/commands from u-boot? >> >> >> mmc rescan 0 >> fatload mmc 0 80000000 am335x-bone.dtb >> fatload mmc 0 81000000 uImage >> setenv bootargs console=ttyO0,115200n8 mem=256M root=/dev/mmcblk0p2 rw >> noinitrd rootfstype=ext3 rootwait earlyprink=serial >> sendln 'bootm 81000000 - 80000000' >> >> >> >> To build DTB files, use "make dtbs" command on your kernel home directory. > > That works ... great !! > > But now I'm confused, since I thought the DTB was appended to the uImage file. > > I have the following in my .config:- > > ARM_ATAG_DTB_COMPAT=y > ARM_APPENDED_DTB=y > ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y > > And then I create my uImage file using:- > > $ make -j 8 ARCH=arm CROSS_COMPILE=arm-linux- uImage > $ make -j 8 ARCH=arm CROSS_COMPILE=arm-linux- am335x-bone.dtb > $ cat arch/arm/boot/uImage arch/arm/boot/am335x-bone.dtb > > arch/arm/boot/uImage-dtb.am335x-bone > $ cp arch/arm/boot/uImage-dtb.am335x-bone /media/boot/uImage > > Do you now have to load the DTB as a separate file ? > > Or should the appended DTB still work ?
Any update on this ? Cheers Mark J. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
