NVIDIA 699210040230 DPU Firmware 24.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-2 DPU provides innovative acceleration, security, and efficiency in every host. BlueField-2 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-2 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:

- MSI-X on SF can be received now through the PF's MSI-X vector.
- 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.
- 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.

Bug Fixes:

 
- 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 an issue on the customized server with an independent power supply, that led to a non-functional virtio when power cycled the server during stressful traffic. The following error was provided: "DESTROY_GENERAL_OBJECT(0xa03) No done completion".
- 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:

- When decapsulation on a packet occurs, the FCS indication is not calculated correctly.
- PHYless Reset is currently not supported.
- Some pre-OS environments may fail when sensing a hot-plug operation during their boot stage.
- Unexpected system behavior might be observed if the driver is loaded while reset is in progress.
- When tx_port_ts is set to "true", due to a compensation mechanism in the Tx timestamp available in some hardware Rx timestamp errors, a symmetrical error and no clock offset occur when using the timestamps to synchronize the device clock. This might also cause an error while using timestamps for delay measurements (e,g., delay measurements reported by a PTP daemon) and even negative delay measurements in some cases.
- 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.
- Disabling the Relaxed Ordered (RO) capability (relaxed_ordering_read_pci_enabled=0) using the vhca_resource_manager is currently not functional.
- fwreset is currently supported on PCI Gen 4 devices only.
- 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.
- MFS1S50-H003E cable supports only HDR rate when used as a split cable.
- CRC is included in the traffic byte counters as a port byte counter.
- The "max_shaper_rate" configuration query via QEEC mlxreg returns a value translated to hardware granularity.
- GTP encapsulation (flex parser profile 3) is limited to the NIC domain. Encapsulating in the FDB domain will render a 0-size length in GTP header.
- Some pre-OS environments may fail when sensing a hot plug operation during their boot stage.
- Servers do not recover after configuring PCI_SWITCH_EMULATION_NUM_PORT to 32 followed by power cycle.
- When working with 3rd party device (e.g., Paragon) in 25GbE speed, the 25GbE speed must be configured in force mode.
- Occasionally, when rising a logical link, the link recovery counter is increase by 1.
- Forward action for IPoIB is not supported on RX RDMA Flow Table.

About Network Adapter Drivers:

When connected, the operating system usually installs a generic driver that helps the computer to recognize the newly attached device.

However, proper software must be applied if you want to make use of all features that the network adapter has available. This task also allows computers to properly recognize all device characteristics such as manufacturer, chipset, technology, and others.

Updating the adapter's drivers and utilities version might improve overall performance and stability, increase transfer speeds, fix different compatibility problems and several network-related errors, as well as bring various other changes.

To install this release, simply get the package, extract it if necessary, run the setup, and follow the instructions displayed on-screen. When done, don't forget to perform a system restart and reconnect the network adapter to make sure that all changes take effect properly.

Without further ado, if you intend to apply this version, click the download button and install the package. Moreover, check with our website as often as possible so that you don't miss a single new release.