<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Hi Alex,<div><br></div><div>I expected it to be kernel-fitimage.bbclass’s responsibility to deploy the fitImage.</div><div><br></div><div>Regards, Leon</div><div><br></div><div><br><div><div style="text-align: -webkit-auto; font-variant-ligatures: normal; font-variant-position: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; line-height: normal;"><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div></div><div><br>On 16 Sep 2018, at 16:22, Alex Kiernan &lt;<a href="mailto:alex.kiernan@gmail.com">alex.kiernan@gmail.com</a>&gt; wrote:<br><br></div><blockquote type="cite"><div><span>On Sun, Sep 16, 2018 at 11:41 AM Alex Kiernan &lt;<a href="mailto:alex.kiernan@gmail.com">alex.kiernan@gmail.com</a>&gt; wrote:</span><br><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Hi Leon</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>On Sun, Sep 16, 2018 at 10:18 AM Leon Woestenberg &lt;<a href="mailto:leon@sidebranch.com">leon@sidebranch.com</a>&gt; wrote:</span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Hi Alex,</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>On 15 Sep 2018, at 19:45, Alex Kiernan &lt;<a href="mailto:alex.kiernan@gmail.com">alex.kiernan@gmail.com</a>&gt; wrote:</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>On Mon, Sep 10, 2018 at 10:57 PM Leon Woestenberg &lt;<a href="mailto:leon@sidebranch.com">leon@sidebranch.com</a>&gt; wrote:</span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>kernel-fitimage.bbclass replaces an occurance of "fitImage" in</span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>KERNEL_IMAGETYPE_FOR_MAKE by an image type that is buildable for the</span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>architecture (such as zImage). The kernel-fitimage.bbclass packs that</span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>image as sub-image in a flattened image tree image (fitImage) and</span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>deploys this fitImage along with the image tree source file (.its).</span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>kernel-fitimage.bbclass does not alter KERNEL_IMAGETYPES, which thus</span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>also contains "fitImage", which kernel.bbclass will also deploy</span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>redundantly with different naming.</span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>The result is a dual deployment with slightly different naming,</span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>each with a set of symlinks.</span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>The solution chosen is to have fitImage deployment be handled by</span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>kernel-fitimage.bbclass, and have kernel.bbclass ignore fitImage</span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>types during deployment.</span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Signed-off-by: Leon Woestenberg &lt;<a href="mailto:leon@sidebranch.com">leon@sidebranch.com</a>&gt;</span><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>This looks completely plausible, but the two "FIT" images that are</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>installed aren't identical... after this I end up with no FIT image</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>and only a bare image in the deploy dir.</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>What was in your KERNEL_IMAGETYPES? Did it at least contain “fitImage”??</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Yes, in fact only fitImage (and no initramfs).</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Digging into it, the logic between the two classes is a bit odd... in</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>the case of a non initramfs build, the fitImage is actually installed</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>here.</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>If ‘here’ means kernel-fitimage, then I’ld say ALL versions of a FIT image containing AT LEAST a Linux kernel are installed by kernel-fitimage.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>The one that's installed in kernel-fitimage is the bare</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>linux.bin, but named fitImage-...</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>which is totally broken. If you want the bare kernel binary (which naming depends on architecture, so it should NOT be hard-coded to linux.bin anyway), you would need to specify that type *also* in KERNEL_IMAGETYPES, next to “fitImage”.</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Totally agree...</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>I'll send a patch reverting this and removing the other one as I'd</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>agree that it appears to have no purpose (and if you did want it, I</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>guess you could list it in KERNEL_IMAGETYPES).</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>I’m sorry I cannot follow what this and the other one is, and it. Let’s first understand all cases correctly.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Sorry I've not described it well... the code in</span><br></blockquote><blockquote type="cite"><span>kernel-fitimage.bbclass that inserts the kernel into the its happens</span><br></blockquote><blockquote type="cite"><span>here <a href="http://git.openembedded.org/openembedded-core/tree/meta/classes/kernel-fitimage.bbclass#n371">http://git.openembedded.org/openembedded-core/tree/meta/classes/kernel-fitimage.bbclass#n371</a></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>fitimage_emit_section_kernel ${1} "${kernelcount}" linux.bin "${linux_comp}"</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>inside fitimage_emit_section_kernel we create a kernel section which</span><br></blockquote><blockquote type="cite"><span>has `data = /incbin/("${3}");` so linux.bin is our bare image.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Then we have the installation of fitImage-linux-bin that happens here</span><br></blockquote><blockquote type="cite"><span><a href="http://git.openembedded.org/openembedded-core/tree/meta/classes/kernel-fitimage.bbclass#n495">http://git.openembedded.org/openembedded-core/tree/meta/classes/kernel-fitimage.bbclass#n495</a></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>echo "Copying linux.bin file..."</span><br></blockquote><blockquote type="cite"><span>install -m 0644 ${B}/linux.bin</span><br></blockquote><blockquote type="cite"><span>${DEPLOYDIR}/fitImage-linux.bin-${KERNEL_FIT_NAME}.bin</span><br></blockquote><blockquote type="cite"><span>ln -snf fitImage-linux.bin-${KERNEL_FIT_NAME}.bin</span><br></blockquote><blockquote type="cite"><span>${DEPLOYDIR}/fitImage-linux.bin-${KERNEL_FIT_LINK_NAME}</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>i.e. the bare linux.bin file which we used to pack into the FIT image,</span><br></blockquote><blockquote type="cite"><span>not a fitImage.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>The output FIT image from kernel-fitimage.bbclass is created here</span><br></blockquote><blockquote type="cite"><span><a href="http://git.openembedded.org/openembedded-core/tree/meta/classes/kernel-fitimage.bbclass#n450">http://git.openembedded.org/openembedded-core/tree/meta/classes/kernel-fitimage.bbclass#n450</a></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>uboot-mkimage \</span><br></blockquote><blockquote type="cite"><span>${@'-D "${UBOOT_MKIMAGE_DTCOPTS}"' if len('${UBOOT_MKIMAGE_DTCOPTS}') else ''} \</span><br></blockquote><blockquote type="cite"><span> &nbsp;-f ${1} \</span><br></blockquote><blockquote type="cite"><span> &nbsp;arch/${ARCH}/boot/${2}</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>i.e. in arch/${ARCH}/boot/${2}</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>It's that image which is then picked up by kernel.bbclass to install</span><br></blockquote><blockquote type="cite"><span>into deploydir (because KERNEL_OUTPUT_DIR ?= "arch/${ARCH}/boot"):</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>for imageType in ${KERNEL_IMAGETYPES} ; do</span><br></blockquote><blockquote type="cite"><span> &nbsp;# kernel-fitimage class deploys fitImages, skip here</span><br></blockquote><blockquote type="cite"><span> &nbsp;if [ "$imageType" != "fitImage" ]; then</span><br></blockquote><blockquote type="cite"><span> &nbsp;&nbsp;&nbsp;base_name=${imageType}-${KERNEL_IMAGE_NAME}</span><br></blockquote><blockquote type="cite"><span> &nbsp;&nbsp;&nbsp;install -m 0644 ${KERNEL_OUTPUT_DIR}/${imageType}</span><br></blockquote><blockquote type="cite"><span>$deployDir/${base_name}.bin</span><br></blockquote><blockquote type="cite"><span> &nbsp;fi</span><br></blockquote><blockquote type="cite"><span>done</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Only it's doesn't because of the filter against fitImage.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><span></span><br><span>To check I'm not seeing some strange artefact of our BSP or</span><br><span>linux-ti-staging (or any other layer we're using):</span><br><span></span><br><span>$ git clone git://git.yoctoproject.org/poky</span><br><span>$ cd poky</span><br><span>$ . oe-init-build-env</span><br><span>$ cat &lt;&lt; EOF &gt;&gt; conf/local.conf</span><br><span>MACHINE = "beaglebone-yocto"</span><br><span>KERNEL_CLASSES += " kernel-fitimage"</span><br><span>KERNEL_IMAGETYPES = "fitImage"</span><br><span>EOF</span><br><span>$ bitbake linux-yocto</span><br><span></span><br><span>The FIT images we then have:</span><br><span></span><br><span>$ find tmp/deploy/images/beaglebone-yocto -name 'fit*.bin' -type f</span><br><span>tmp/deploy/images/beaglebone-yocto/fitImage-linux.bin--4.18.3+git0+7341720391_eba03655e8-r0-beaglebone-yocto-20180916134100.bin</span><br><span></span><br><span>And what is:</span><br><span></span><br><span>$ bitbake u-boot-mkimage-native -caddto_recipe_sysroot</span><br><span>$ oe-run-native u-boot-mkimage-native mkimage -l</span><br><span>tmp/deploy/images/beaglebone-yocto/fitImage-linux.bin--4.18.3+git0+7341720391_eba03655e8-r0-beaglebone-yocto-20180916134100.bin</span><br><span>Running bitbake -e u-boot-mkimage-native</span><br><span>GP Header: Size a0e1 LoadAddr a0e1</span><br><span></span><br><span>Revert c2d00e2f83cdf3d2923660448756ed29296a06a6 and try again:</span><br><span></span><br><span>$ git revert c2d00e2f83cdf3d2923660448756ed29296a06a6</span><br><span>$ bitbake linux-yocto</span><br><span></span><br><span>This time there's two images:</span><br><span></span><br><span>$ find tmp/deploy/images/beaglebone-yocto -name 'fit*.bin' -type f</span><br><span>tmp/deploy/images/beaglebone-yocto/fitImage--4.18.3+git0+7341720391_eba03655e8-r0-beaglebone-yocto-20180916141923.bin</span><br><span>tmp/deploy/images/beaglebone-yocto/fitImage-linux.bin--4.18.3+git0+7341720391_eba03655e8-r0-beaglebone-yocto-20180916141923.bin</span><br><span></span><br><span>And what they are:</span><br><span></span><br><span>$ oe-run-native u-boot-mkimage-native mkimage -l</span><br><span>tmp/deploy/images/beaglebone-yocto/fitImage--4.18.3+git0+7341720391_eba03655e8-r0-beaglebone-yocto-20180916141923.bin</span><br><span>Running bitbake -e u-boot-mkimage-native</span><br><span>FIT description: U-Boot fitImage for Poky (Yocto Project Reference</span><br><span>Distro)/4.18.3+gitAUTOINC+7341720391_eba03655e8/beaglebone-yocto</span><br><span>Created: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Sun Sep 16 14:14:47 2018</span><br><span> Image 0 (kernel@1)</span><br><span> &nbsp;Description: &nbsp;Linux kernel</span><br><span> &nbsp;Created: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Sun Sep 16 14:14:47 2018</span><br><span> &nbsp;Type: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Kernel Image</span><br><span> &nbsp;Compression: &nbsp;uncompressed</span><br><span> &nbsp;Data Size: &nbsp;&nbsp;&nbsp;6381368 Bytes = 6231.80 KiB = 6.09 MiB</span><br><span> &nbsp;Architecture: ARM</span><br><span> &nbsp;OS: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Linux</span><br><span> &nbsp;Load Address: 0x80008000</span><br><span> &nbsp;Entry Point: &nbsp;0x80008000</span><br><span> &nbsp;Hash algo: &nbsp;&nbsp;&nbsp;sha1</span><br><span> &nbsp;Hash value: &nbsp;&nbsp;909137524ffd28b5b0ac51ea39c648b09902dc18</span><br><span> Image 1 (<a href="mailto:fdt@am335x-bone.dtb">fdt@am335x-bone.dtb</a>)</span><br><span> &nbsp;Description: &nbsp;Flattened Device Tree blob</span><br><span> &nbsp;Created: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Sun Sep 16 14:14:47 2018</span><br><span> &nbsp;Type: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Flat Device Tree</span><br><span> &nbsp;Compression: &nbsp;uncompressed</span><br><span> &nbsp;Data Size: &nbsp;&nbsp;&nbsp;33030 Bytes = 32.26 KiB = 0.03 MiB</span><br><span> &nbsp;Architecture: ARM</span><br><span> &nbsp;Hash algo: &nbsp;&nbsp;&nbsp;sha1</span><br><span> &nbsp;Hash value: &nbsp;&nbsp;0fece12f15fc5ac6c452d9308cd374c2c0cfea47</span><br><span> Image 2 (<a href="mailto:fdt@am335x-boneblack.dtb">fdt@am335x-boneblack.dtb</a>)</span><br><span> &nbsp;Description: &nbsp;Flattened Device Tree blob</span><br><span> &nbsp;Created: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Sun Sep 16 14:14:47 2018</span><br><span> &nbsp;Type: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Flat Device Tree</span><br><span> &nbsp;Compression: &nbsp;uncompressed</span><br><span> &nbsp;Data Size: &nbsp;&nbsp;&nbsp;34782 Bytes = 33.97 KiB = 0.03 MiB</span><br><span> &nbsp;Architecture: ARM</span><br><span> &nbsp;Hash algo: &nbsp;&nbsp;&nbsp;sha1</span><br><span> &nbsp;Hash value: &nbsp;&nbsp;337f6843020cb8fbaf119b43fd748222d32e72df</span><br><span> Image 3 (<a href="mailto:fdt@am335x-bonegreen.dtb">fdt@am335x-bonegreen.dtb</a>)</span><br><span> &nbsp;Description: &nbsp;Flattened Device Tree blob</span><br><span> &nbsp;Created: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Sun Sep 16 14:14:47 2018</span><br><span> &nbsp;Type: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Flat Device Tree</span><br><span> &nbsp;Compression: &nbsp;uncompressed</span><br><span> &nbsp;Data Size: &nbsp;&nbsp;&nbsp;33286 Bytes = 32.51 KiB = 0.03 MiB</span><br><span> &nbsp;Architecture: ARM</span><br><span> &nbsp;Hash algo: &nbsp;&nbsp;&nbsp;sha1</span><br><span> &nbsp;Hash value: &nbsp;&nbsp;4974e8b1656cd7f52829ac3c01f6747bece87cbc</span><br><span> Default Configuration: '<a href="mailto:conf@am335x-bone.dtb">conf@am335x-bone.dtb</a>'</span><br><span> Configuration 0 (<a href="mailto:conf@am335x-bone.dtb">conf@am335x-bone.dtb</a>)</span><br><span> &nbsp;Description: &nbsp;1 Linux kernel, FDT blob</span><br><span> &nbsp;Kernel: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;kernel@1</span><br><span> &nbsp;FDT: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="mailto:fdt@am335x-bone.dtb">fdt@am335x-bone.dtb</a></span><br><span> &nbsp;Hash algo: &nbsp;&nbsp;&nbsp;sha1</span><br><span> &nbsp;Hash value: &nbsp;&nbsp;unavailable</span><br><span> Configuration 1 (<a href="mailto:conf@am335x-boneblack.dtb">conf@am335x-boneblack.dtb</a>)</span><br><span> &nbsp;Description: &nbsp;0 Linux kernel, FDT blob</span><br><span> &nbsp;Kernel: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;kernel@1</span><br><span> &nbsp;FDT: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="mailto:fdt@am335x-boneblack.dtb">fdt@am335x-boneblack.dtb</a></span><br><span> &nbsp;Hash algo: &nbsp;&nbsp;&nbsp;sha1</span><br><span> &nbsp;Hash value: &nbsp;&nbsp;unavailable</span><br><span> Configuration 2 (<a href="mailto:conf@am335x-bonegreen.dtb">conf@am335x-bonegreen.dtb</a>)</span><br><span> &nbsp;Description: &nbsp;0 Linux kernel, FDT blob</span><br><span> &nbsp;Kernel: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;kernel@1</span><br><span> &nbsp;FDT: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href="mailto:fdt@am335x-bonegreen.dtb">fdt@am335x-bonegreen.dtb</a></span><br><span> &nbsp;Hash algo: &nbsp;&nbsp;&nbsp;sha1</span><br><span> &nbsp;Hash value: &nbsp;&nbsp;unavailable</span><br><span>$ oe-run-native u-boot-mkimage-native mkimage -l</span><br><span>tmp/deploy/images/beaglebone-yocto/fitImage-linux.bin--4.18.3+git0+7341720391_eba03655e8-r0-beaglebone-yocto-20180916141923.bin</span><br><span>Running bitbake -e u-boot-mkimage-native</span><br><span>GP Header: Size a0e1 LoadAddr a0e1</span><br><span></span><br><span>-- </span><br><span>Alex Kiernan</span><br></div></blockquote></div></body></html>