Join GitHub today
Well that was quick. I guess since you have a json dump in the directory it would be good to read that in and with a self test script (and maybe call
/bin/true with it to test "flash process" rather than
Have you examined any firmware binaries to check how they're constructed? I inquire because I notice this:
If that's a common situation then this might be difficult to represent in the plugin.
I've never seen an image with more than one chunk, and I've never seen an image that had an offset that wasn't 0. If we did have to support such a thing I'd urge the vendor to ship a DfuSe binary, that can have multiple images, each with a 32bit offset, and additional metadata. This could then be parsed in the plugin and each image applied.
If you think that's a sensible thing to support out of the box (or if you know of a NVMe binary with more than one chunk) just say and I'll add it to the plugin.
If it's not common I don't think it's sensible to support. I haven't analyzed any of the binaries we use yet, so I don't know if that's something we have to worry about.