xusb firmare loading fails after kernel payload update about tegra-demo-distro HOT 6 CLOSED

Hi,
you are right of course, I just followed my line of thinking and skipped what you meant with the recipe. The kernel-bup-payload recipe is all I need. It is working now. I just need to adapt a couple of recipes on my project.
Thanks a lot.
Alvaro.

from tegra-demo-distro.

This is the kernel trying to load the firmware from the file /lib/firmware/tegra19x_usb_firmware. Is that file missing from your rootfs? If you use an initramfs (as we do in this demo distro), is that firmware file installed in the initramfs's rootfs filesystem? The driver may need that firmware early on in the boot process, so you need to make sure it's included in your initramfs.

from tegra-demo-distro.

Hi,
first of all thank you for your quick answer.
Actually your question triggered some deeper recheck on our recipes. We are building as you do in the demo distro, with initramfs, but we generate the update payloads adding to IMAGE_FSTYPES = cpio.gz.cboot.bup-payload. (Is this the right way to generate update payloads for an image based on this demo distro?)
When we update, I am not sure if initramfs is included in any of the automatically generated payloads or how to separately generate a payload for it.
It is anyway strange that after this partial updates, the system boots everything (except usb firmware) if there is no initramfs, right?

Regards.

from tegra-demo-distro.

The mechanism for generating the BUP payload depends on whether you've got INITRAMFS_IMAGE_BUNDLE set to 1 or 0. By default, we have it set to 1, so bitbake kernel-bup-payload should generate the correct payloads for you. If it's set to 0 (separating the initrd from the kernel build), you need that IMAGE_FSTYPES addition (and we do that automatically in the tegra-minimal-initrams recipe).

from tegra-demo-distro.

Hello,
we were actually using the default value, but somehow setting extra the IMAGE_FSTYPES generated the wrong payloads. We saw that inside the tegraflash container there is a script to generate the payloads and manually used it. With that manually generated payloads our update is working fine.

Is there a proper predefined way to automatically generate these update payloads during the yocto build process without explicitly unpacking the tegraflash container afterwards?

Thanks in advance,
Alvaro.

from tegra-demo-distro.

As I mentioned above, the kernel-bup-payload will do that for you. But even simpler is to use the tegra-bup-payload recipe, which installs a BUP payload into the /opt/ota_package directory in your rootfs; it calculates its dependencies based on the initramfs bundling setting automatically.

By default it installs the full bl_update_payload; if you need to use one of the subset payloads instead, you can do that via a bbappend.

from tegra-demo-distro.