MBF2H332A-AEEOT - bundled firmware manager does not include firmware for this board

Using SDKManager to try to install DOCA 2.0.2 on a MBF2H332A-AEEOT Bluefield2 the install failed at “Burn Target Firmware” with this error:

WARNING: The bundled firmware manager does not include firmware for this board. Recommended firmware version cannot be determined.

The board PSID is MT_0000000540 which, as far as I know, is current and fully supported.

I need a pointer or some assistance to resolve this in order to complete the DOCA install.

Thanks
-J

Here is some diagnostic info that maybe helpful:

root@localhost:~# bfvcheck
Beginning version check…

-RECOMMENDED VERSIONS-
ATF: v2.2(release):4.0.3-25-g4e9af27
UEFI: 4.0.3-10-gb8abccc
FW: N/A

-INSTALLED VERSIONS-
ATF: v2.2(release):4.0.3-25-g4e9af27
UEFI: 4.0.3-10-gb8abccc
FW: 24.37.1300

WARNING: The bundled firmware manager does not include firmware for
this board. Recommended firmware version cannot be determined.

Firmware Manager Path: /opt/mellanox/mlnx-fw-updater/firmware/mlxfwmanager_sriov_dis_aarch64_41686
Part Number: MBF2H332A-AEEOT

Version check complete.
root@localhost:~#


root@localhost:~# ./mlxup
Querying Mellanox devices firmware …

Device #1:

Device Type: BlueField2
Part Number: MBF2H332A-AEEO_Ax_Bx
Description: BlueField-2 P-Series DPU 25GbE Dual-Port SFP56; PCIe Gen4 x8; Crypto Enabled; 16GB on-board DDR; 1GbE OOB management; HHHL
PSID: MT_0000000540
PCI Device Name: /dev/mst/mt41686_pciconf0
Base GUID: b8cef60300677860
Base MAC: b8cef6677860
Versions: Current Available
FW 24.37.1300 24.37.1300
NVMe N/A 20.4.0001
PXE 3.7.0102 3.7.0102
UEFI 14.30.0013 14.30.0013
UEFI Virtio blk 22.4.0010 22.4.0010
UEFI Virtio net 21.4.0010 21.4.0010

Status: Up to date

root@localhost:~#

This is a bug in the sdkmanager - the firmware is not included in the bundle.

Workaround is to manually install firmware. Then patch the sdkmanager to not attempt to check/install firmware, then install completes fine and works.

We have enterprise support, they have a ticket on this along with my workaround patch. Hopefully they can produce a proper fix that can help others.

  • J
1 Like