Hi everyone, when I’m processing a BIOS file in FIT or MFIT, should I use a version compatible with the “Flash Image Tool” field or the “Version - Family” field of the MEA? I ask this because I’ve always used a primary and secondary version compatible with the “Flash Image Tool” field, but lately the BIOS files are coming with different secondary versions in the “Version - Family” and “Flash Image Tool” fields.
“A bios file…” that’s really a post full of information… guessing wizards now???
Sorry @MeatWar, I really was too generic, so I will try to explain my request using an example.
Below you can see an MEA output image dumped from a Dell Latitude 3410 with two EEPROMs (8 and 16MB).
Note that in yellow it has a major/minor version 14.1 for field “Version”, however in red it has a major/minor version 14.0 for field “Flash Image Tool”.
Normally I would use a Flash Image Tool major/minor version 14.1 to clean the DATA section of this engine region, but considering that image dumped has different minor versions for fields “Version” and “Flash Image Tool”, I was left with doubts.
Link for dump: Latitude_3410.7z
Sorry if I’m sending this twice
The “RED” version it’s the tool version used upon building the image at the time of output, this doesnt matter for operations (General ones on the forum).
This is also going to change when we assemble ourselves a new image from scratch, this way reporting the FIT version we used.
So, the rule is, use a higher (preferable) or same version of FIT, as the reported one in the image.
I thought you’d learn something since your 2024 posts…
Thanks MeatWar, I thought that if I used a different version of FIT than the red one I would have problems with, for example, Manifest Extension Utility, since the image was originally processed with another FIT version. To be honest, I had never picked different versions in the yellow and red fields, but I will follow your advice and start using the yellow field to select the FIT. Furthermore, the figure shows that initially the image was processed with FIT 14.0, not 14.1, and it was successful.