How to get the .encrypt files for swupdate during build?

[tomdeblauwe]

Hello,
I'm using the older kirkstone R32 branch and I could use swupdate to make the .swu file. That contains my rootfs, the kernel and kernel-dtb. However, when I include the kernel and kernel-dtb in my swu file, then that does not work, it does not boot anymore. Probably because these files are not the "encrypted" type. When I flash over usb using "initrd-flash" then it starts with "signing binaries" and you see that the flash process uses these files when it flashed:

  Writing signed/boot_sigheader.img.encrypt (size=14800896) to /dev/sda3 (size=67108864)...
  Writing signed/boot_sigheader.img.encrypt (size=14800896) to /dev/sda4 (size=67108864)...
  Writing signed/kernel_tegra194-p3668-all-p3509-0000_sigheader.dtb.encrypt (size=191664) to /dev/sda5 (size=458752)...
  Writing signed/kernel_tegra194-p3668-all-p3509-0000_sigheader.dtb.encrypt (size=191664) to /dev/sda6 (size=458752)...

So I would like to somehow access the ".encrypt" versions during the build of my .swu image. Is that possible?
Best regards

[dwalkes]

I haven't experimented with r32 at all, although the original integration I referenced was on r32 I believe. Glancing at that one it doesn't look like it directly writes the kernel or kernel-dtb but rather uses tegra-bootloader-update to apply the update payload where I believe it would be included if I recall correctly.

[tomdeblauwe]

Thanks for the pointers! I don't really understand where the /opt/ota_package/bl_update_payload is coming from? it's not references in the swupdate description?