#479 ekanalyzer incorrectly processes more than one custom field

[Alexander Amelkin]

If there are "additional custom mfg. fields" in a FRU information area, ekanalyzer displays them ok, but doesn't properly process the "end of fields" (0xC1) marker trying to fetch the padding space as binary data. That happens because it never re-reads the 'len' variable. This should also result in wrong processing of custom fields if there are more than one present in the file.

Here is the example of wrong output:

...
FRU File ID: Command Line
Additional Custom Mfg. length: 0x07
Additional Custom Mfg. Data: 01-02-03-04-fe-ad-1e
Additional Custom Mfg. length: 0x07
Additional Custom Mfg. Data: c1-00-00-00-00-00-00
Additional Custom Mfg. length: 0x07
No Additional Custom Mfg. 2
There is no multi record in the file 'fru.bin'

The "No Additional Custom Mfg." line appears when it thinks there must be data, but there is none, which is also wrong and looks to the user like it is not an error when in fact it is.

[Alexander Amelkin]

The fix for this is available in my merge request (commit f436acab92fbccdbfecf192ac7e31700e7e479f1)

[Zdenek Styblik]

Thank you.