> It's pretty close to this: > > $ make zImage dtbs > $ cat arch/arm/boot/zImage arch/arm/boot/dts/am3517-evm.dtb > /tmp/zImage-dtb.am3517-evm > $ mkimage -A arm -O linux -C none -T kernel -a 0x80008000 -e 0x80008000 -n 'Linux-' -d /tmp/zImage-dtb.am3517-evm uImage-dtb.am3517-evm > > The binary output from this on my testbed is below - don't sue me if it > fries your board, eats your household pets, propositions your significant > other while you're not around, etc.: > > http://www.pwsan.com/omap/testlogs/test_v4.5-rc2/20160131225233/dtcat/omap2plus_defconfig/uImage-dtb.am3517-evm > > Unfortunately my AM3517 EVM stopped powering up about a year ago, so I > don't know if that board is still working with mainline. But I have no > reason to believe that it no longer works, considering that the CM-T3517 > still boots. > > > I would like to confirm I can produce the same thing, and I'm not quite > > sure what to look for in the output that it has successfully found a > > device tree vs just defaulting to something. > > If it doesn't find a DT file appended to the uImage, the board probably > won't even make it past "Starting kernel". Well after turning off CONFIG_FIT in u-boot, I sat staring at 'Starting kernel ...' and then a root login popped up. So it does not seem to like 'console=ttyS2,115200n8' very much.. and for that matter ttyO2 doesn't work either... hrrm. Now to figure out if I can make LCD/omapfb work again... (FYI, it seems 3.14-3.18 mainline series kernels would work with the am3517-evm with 'nohlt' on the command line without a device tree) -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
