Hi Konstantin, Doh! It seems I made a cut & paste bug parsing "DC Load" identical to "DC Output".
I've updated the branch https://github.com/analogdevicesinc/fru_tools/tree/master/masterfiles with a few fixes. It works for me now, could you try it out as a sanity check? Al On Mon, 2021-02-08 at 15:26 +0300, Konstantin Aladyshev wrote: > Thanks Al! > > It helped. With this change the `ipmi-fru` utility can work on non- > IPMI systems. > > By the way, I've tried to run `ipmi-fru` on some FRU images from the > https://github.com/analogdevicesinc/fru_tools/tree/master/masterfiles > And not all things were parsed successfully. I don't know, either > these binaries have some non-standard records or `ipmi-fru` lacks > some necessary features. > But just in case here are some logs: > > aladyshev@PC10319:~/freeipmi_fru/ipmi-fru$ ./ipmi-fru --fru-file > ~/fru_tools/masterfiles/AD-FMCADC2-EBZ-FRU.bin > FRU Inventory From File: > /home/aladyshev/fru_tools/masterfiles/AD-FMCADC2-EBZ-FRU.bin > > FRU Board Manufacturing Date/Time: 10/09/14 - 16:23:00 > FRU Board Manufacturer: Analog Devices > FRU Board Product Name: AD9625 FMC Sync board > FRU Board Serial Number: 00008 > FRU Board Part Number: AD-FMCADC2-EBZ > FRU Board Custom Info: 00h 44h > FRU Board Custom Info: 01h 30h 33h 36h 30h 30h 37h > FRU Board Custom Info: 02h 30h > FRU Board Custom Info: 03h 59h > > fru/ipmi-fru-data.c: 1246: ipmi_fru_multirecord_dc_load: error 'field > not found' (7) > ipmi_fru_multirecord_dc_load: invalid parameters > api/ipmi-api.c: 2231: ipmi_ctx_close: error 'device null' (1) > api/ipmi-api.c: 2276: ipmi_ctx_destroy: error 'device null' (1) > > > aladyshev@PC10319:~/freeipmi_fru/ipmi-fru$ ./ipmi-fru --fru-file > ~/fru_tools/masterfiles/ADRV9371-W.bin > FRU Inventory From File: > /home/aladyshev/fru_tools/masterfiles/ADRV9371-W.bin > > FRU Board Manufacturing Date/Time: 11/27/12 - 11:39:00 > FRU Board Manufacturer: Analog Devices > FRU Board Product Name: Wide Tuning Range AD9371 Eval Brd > FRU Board Serial Number: 0000 > FRU Board Part Number: ADRV9371-W/PCBZ > FRU Board Custom Info: 00h 41h > FRU Board Custom Info: 01h 30h 38h 2Dh 30h 34h 32h 35h 39h 31h > FRU Board Custom Info: 02h 41h > FRU Board Custom Info: 03h 59h > > FRU DC Output Output Number: 3 > FRU DC Output Output on Standy: No > FRU DC Output Nominal Voltage: 2500 mV > FRU DC Output Maximum Negative Voltage Deviation: 0 mV > FRU DC Output Maximum Positive Voltage Deviation: 0 mV > FRU DC Output Ripple and Noise pk-pk: 50 mV > FRU DC Output Minimum Current Draw: 0 mA > FRU DC Output Maximum Current Draw: 0 mA > > FRU DC Output Output Number: 4 > FRU DC Output Output on Standy: No > FRU DC Output Nominal Voltage: 0 mV > FRU DC Output Maximum Negative Voltage Deviation: 0 mV > FRU DC Output Maximum Positive Voltage Deviation: 0 mV > FRU DC Output Ripple and Noise pk-pk: 0 mV > FRU DC Output Minimum Current Draw: 0 mA > FRU DC Output Maximum Current Draw: 0 mA > > FRU DC Output Output Number: 5 > FRU DC Output Output on Standy: No > FRU DC Output Nominal Voltage: 0 mV > FRU DC Output Maximum Negative Voltage Deviation: 0 mV > FRU DC Output Maximum Positive Voltage Deviation: 0 mV > FRU DC Output Ripple and Noise pk-pk: 0 mV > FRU DC Output Minimum Current Draw: 0 mA > FRU DC Output Maximum Current Draw: 0 mA > > fru/ipmi-fru-data.c: 1246: ipmi_fru_multirecord_dc_load: error 'field > not found' (7) > ipmi_fru_multirecord_dc_load: invalid parameters > api/ipmi-api.c: 2231: ipmi_ctx_close: error 'device null' (1) > api/ipmi-api.c: 2276: ipmi_ctx_destroy: error 'device null' (1) > > > Best regards, > Konstantin Aladyshev > > > On Sun, Feb 7, 2021 at 10:23 PM Al Chu <[email protected]> wrote: > > > > Hi Konstantin, > > > > I have a fix at this branch on github if you could give it a shot: > > > > https://github.com/chu11/freeipmi-mirror/tree/ipmi_fru_file_only > > > > after downloading, to build: > > > > ./autogen.sh > > ./configure --enable-debug --enable-trace > > make > > ipmi-fru/ipmi-fru --fru-file=... > > > > There will be extra debugging output when running this. If things > > look > > like its working, you can remove the "--enable-debug, --enable- > > trace" > > in the above to remove the debugging. > > > > Thanks, > > > > Al > > > > > > On Sat, 2021-02-06 at 09:32 -0800, Al Chu via Freeipmi-users wrote: > > > Hi Konstantin, > > > > > > Yeah, this seems to be a bug. I suppose it was always assumed > > > people > > > were on IPMI systems. I believe this was initially added b/c > > > some > > > IPMI > > > developers wanted to debug/test their binaries. > > > > > > I'll add this as a TODO for myself and get back to you with a > > > test > > > branch you can try. > > > > > > Al > > > > > > On Fri, 2021-02-05 at 12:59 +0300, Konstantin Aladyshev wrote: > > > > Is it possible to use `ipmi-fru` utility to parse local binary > > > > FRU > > > > file? > > > > I want to do it from a separate host that doesn't have any IPMI > > > > devices. > > > > I thought that `--fru-file` option was designed specifically > > > > for > > > > this > > > > case, but I can't get it working: > > > > > > > > ~/freeipmi-1.6.6/ipmi-fru$ sudo ./ipmi-fru -v > > > > --fru-file=./AD-FMCADC2-EBZ-FRU.bin > > > > could not find inband device > > > > > > > > So there seems to be a bug that assumes you are always running > > > > on > > > > an > > > > IPMI system. > > > > > > > > Best regards, > > > > Konstantin Aladyshev > > > > > > > > _______________________________________________ > > > > Freeipmi-users mailing list > > > > [email protected] > > > > https://lists.gnu.org/mailman/listinfo/freeipmi-users > > > > > > > > > _______________________________________________ > > > Freeipmi-users mailing list > > > [email protected] > > > https://lists.gnu.org/mailman/listinfo/freeipmi-users _______________________________________________ Freeipmi-users mailing list [email protected] https://lists.gnu.org/mailman/listinfo/freeipmi-users
