Fail if meta-product is not correct about fwup HOT 3 CLOSED

Yes, a check could be added. I'll take a look next time I make a pass on fwup maintenance - probably in the next couple weeks.

Here are some other possibilities for now:

1. Firmware metadata is stored at the very beginning of the .fw file, so you only need a little data run fwup -m. This unit test is an example: https://github.com/fhunleth/fwup/blob/master/tests/055_metadata_partial_file.test. You could still stream the whole file through fwup, but on the side, you'd have code that runs after 512 bytes (or 1K since it's not like this has to be as small as possible) is received, saves those first bytes to a file and then runs fwup -m on that file.

2. If the currently running firmware's metadata can be stored in a uboot-formated environment block. You don't need U-Boot. This is just the format, you can check it with require-uboot-variable. Here's an example: https://github.com/nerves-project/nerves_system_rpi0/blob/master/fwup.conf#L329-L330. To give a nice error message when there's a mismatch, this code was added: https://github.com/nerves-project/nerves_system_rpi0/blob/master/fwup.conf#L391-L403.

from fwup.

Thank you very much, I think solution number 1 would be good enough for me, but the optimal solution would be to use uboot require as the board runs from U-Boot. I cannot currently use it as I have redundant env on the board, so I'm writing a patch to add support for it in fwup. When it's ready and tested I will send a pull request here. And I think you can close this issue unless you think the option I proposed should be added anyway.

from fwup.

Thanks - also, thanks for looking into redundant u-boot environment support. I had been putting that off. Even if you only have the updates for https://github.com/fhunleth/fwup/blob/master/src/uboot_env.c, I'd take it to slowly push things forward.

from fwup.