NVIDIA 900-9D3B4-00CC-E DPU Firmware 32.42.1000

Firmware which is added at the time of manufacturing, is used to run user programs on the device and can be thought of as the software that allows hardware to run. Embedded firmware is used to control the functions of various hardware devices and systems, much like a computer’s operating system (OS) controls the function of software applications. Firmware may be written into read-only memory (ROM), erasable programmable read-only memory (EPROM) or flash memory.

NVIDIA BlueField-3 DPU provides innovative acceleration, security, and efficiency in every host. BlueField-3 data center infrastructure combines the power of the NVIDIA ConnectX-6 Dx with programmable Arm cores and hardware offloads for software-defined storage, networking, security, and management workloads.

NVIDIA BlueField-3 also delivers superior performance, security, and reduced TCO for cloud computing platforms, enabling organizations to efficiently build and operate virtualized, containerized, and bare-metal infrastructures at massive scale.

Changes and New Features:

- Added a new command interface "Memory slow release" to enable/disable holding memory pages for a defined period of time. Once the timer expires, the firmware will return the pages to the driver.
- Increased the server's resource size for 10k data QP (connections from NVME initiator) attached to the XRQ upon 32MB, 64MB, 128MB, 256MB staging buffer.
- Added support for Hotplug Power Off for Virtio FS (hotplug_power_off).
- Added support for MVTS register via a miscellaneous driver using the access_register PRM command.
- Added support for Virtio devices' dynamic queue modification. A Virtio PF manages the available number of queues (doorbells) that can be allocated to its Virtio VFs.
- Added support for remove/plugged-in Memory Device units while the system is active. To insert/remove the device while the system is active, use the Attention Button Control or User OS Commands, press Attention Butten if exists or write SW Command if not exists.
- Added QP_INFO segment to resource dump access_register command.
- Added a new hca_cap call max_num_eqs_24b to report the number of EQs for VFs, PFs of ECPFs, and SFs.
- Firmware allocates the MSIX/VQ resources according to the function number, thus, every VF function will get the same number of MSIX/VQ.
- The user can now know the exact number of allocated MSIX by the firmware using the new added call actual_msix_number.
- Each VF can allocate all VFs' MSIX of the PF as a free pool of the PF. The new modification, increased the maximum VNET/VBLK VF MSIX number from 64 to 256. To see the new value, query the cmd_hca_cap.max_dynamic_vf_msix_table_size.
- Enabled Cache-Invalidate WQE (OPCODE=”MMO”) with OPC_MOD=”DPU_CACHE_INVALIDATE" by default for DPU GVMI. Additionally, added related capabilities to show if this capability is supported and what is the maximum supported data size to be invalidated (2MB by default.).
- MSI-X on SF can be received now through the PF's MSI-X vector.

Bug Fixes:

- Fixed the partition default value in firmware when MFT builds the bin file. Additionally, in "root certificate" partition, modified the discovery flow in case both of the "root certificate" partition are invalid by erasing them before they are used.
- Fixed an issue that caused RDE PortMetrics property Transceivers.SupplyVoltage to be reflected in incorrect units of 100uV instead of V.
- Prevented HCA_CAP from allowing rogue drivers to create more EQs than the number allowed in the HCA_CAP.max_num_eqs.
- Fixed the CMIS deactivation process for 2 lanes modules.
- Added support for unique boot configuration for Micron SSDs via ALT5 INI.
- Fixed an issue that prevented RTT response from being send thus resulting in a firmware assert with ext_synd=0x8175 in dmesg when starting the DoCA PCC NP application and the queue size is higher than 16.
- Fixed the esw scheduling rate limiter behavior to present more accurate information for virtio_net VFs and irtio_blk VFs.
- Fixed an issue that prevented CNP or RTT counters from wrapping around properly.
- Congestion Control counters such as ECN and CNP will now be the sum of both ports when in LAG mode.
- ixed an issue that prevented virtio blocked devices from being re-enabled after rebooting the server with a Virtio Block device enabled, because of a firmware internal error 7 which appears in the Host Dmesg. The following error will appear in the SNAP logs "Failed to start pci device: open BLK device for vhca_id 0×2 failed".
- Fixed an issue in systems with 64k page size, where applications opening a substantial amount of RDMA resources such as UARs, QPs, and CQs might encounter errors during the creation of these resources due to limitations in PCI BAR size.
- Fixed an issue that prevented the SFF module from accessing the EEPROM data when removing the CMIS module and inserting the SFF module instead of it.

Known Issues:

- NC-SI pass-through requires the user to allocate a MAC address to the platform BMC.
- NVIA register is not allowed for external host if any field of EXTERNAL_HOST_PRIV or EXTERNAL_HOST_PRIV_FAST TLVs is not set as the default.
- When configuring BlueField-3 Arm cores as PCIe root-complex, all non-mlx5 devices must always set the BlueField-3’s IOMMU to disabled or passthrough mode. Turning IOMMU “ON” requires special handling of interrupts in the driver or the use of polling. For further assistance, contact NVIDIA support .
- The supported DDR5 link speed in SKU B3220, is 5200 MT/s.
- SW_RESET with a pending image is currently not supported.
- Occasionally, the device may hang when there a hot plug is performed from a unknown direction.
- Some pre-OS environments may fail when sensing a hot-plug operation during their boot stage.
- The I2C clock fall time is lower than the 12ns minimum defined in the I2C-bus specification.
- When connecting to a High Speed Traffic Generator in 400G speed, the linkup time may takes up to 3 minutes.
- External flash access such as flash read using the MFT tools will fail if there is a pending image on the flash.
- On BlueField-3 devices, from DOCA 2.2.0 to 32.37.1306 (or lower), the host crashes when executing partial Arm reset (e.g., Arm reboot; BFB push; mlxfwreset).
- When unloading the network drivers on an external host, sync1 reset may be still reported as 'supported' although it is not. Thus, initiating the reset flow may result in reset failure after a few minutes.
- When connecting to a Spirent switch in 400G speed, the linkup time may takes up to 3 minutes.
- PCIe PML1 is disabled.
- Unexpected system behavior might be observed if the driver is loaded while reset is in progress.
- When performing PCIe link secondary-bus-reset, disable/enable or mlxfwreset on AMD based Genoa systems, the device takes longer then expected to link up, due to a PCIe receiver termination misconfiguration.
- The firmware rollback fails for the signature retransmit flow if the QPN field is configured in the mkey (as it only allows the given QP to use this Mkey) as the firmware rollback flow relies on an internal QP that uses the mkey.
- Socket-Direct is currently not supported.

About Wireless LAN Drivers:

Windows OSes usually apply a generic driver that allows systems to recognize the wireless component. However, in order to use all available features of this hardware, you must install the appropriate drivers.

Enabling the wireless card allows systems to read chipset information and manufacturer name, as well as connect to a network without using an Ethernet cable.

Updating the driver version can resolve different compatibility issues, fix related errors spotted throughout the product's usage, add support for new operating systems, improve transfer speed, as well as bring various other changes.

As for applying this release, the installation steps should not pose to much of a challenge since each producer intends to make the procedure as easy as possible: just download the package, run the setup, and follow the on-screen instructions.

Bear in mind that we do not recommend you install this release on OSes other than the specified ones even though other platforms might also be suitable. Also, when the update has finished, do perform a restart to ensure that all changes take effect properly.

Therefore, if you wish to apply this package, click the download button, and setup the wireless card on your system. Moreover, if you want to stay “updated one minute ago,” check with our website as often as possible.