ConnectX-9 Firmware Release Notes

Changes and New Features

To generate PLDM packages for firmware updates, users must install and use the MFT version that corresponds with the respective firmware release.

Feature/Change

Description

82.49.1014

PCC/ZTR-RTT Congestion-Control Histogram Collection

Added support for Congestion-Control histogram collection in the PCC/ZTR-RTT algorithm. After enabling this capability, customers can read RATE and RTT histogram counters for PCC-managed flows.

Precoded Data Reception Support

Added support for receiving precoded data on the NVIDIA Rx side to ensure signal integrity performance.

Note: To support this capability, the Tx connected to the NVIDIA Rx must transmit precoded data.

PCC TopoAware PLB (probe_metadata Behavior)

PCC_CONFIG.probe_metadata is now supported as a global setting that applies uniformly across all probe slots. Updates made via CREATE/MODIFY (regardless of probe_type_slot) propagate to all slots.

ZTR_RTTCC Tunable Probe Timeout

Added a new parameter to the ZTR_RTTCC algorithm to define the probe-packet timeout threshold.

PTP/PPS/SyncE over I2C DC‑TCXO

Firmware now enables full timing functionality on ConnectX‑9: PTP (Precision Time Protocol, IEEE 1588) time synchronization, PPS (Pulse Per Second) input/output, and SyncE (Synchronous Ethernet) frequency synchronization on platforms that use an external DC‑TCXO. This is done by adding I2C-based control of the DC‑TCXO so the NIC can steer/discipline its reference clock for accurate and stable timing.

Link up/Down dmesg Messages

When powering down the OSFP port, the link up/down dmesg messages were previously sent only to the primary ASIC, they are now sent to the secondary ASIC as well.

PSP Transport Packet Reformat

Added support for a new packet reformat type for PSP transport packets. This reformat removes the PSP trailer and the UDP + PSP transport headers, and updates the IP Protocol field based on the PSP next_header value.

Persistent CRDT Token

CRDT token behavior has changed and is now persistent.

Previously, debug firmware was allowed only if a CRDT token was applied temporarily, meaning it was erased after reset, or if another debug firmware was already running. Once a user moved to production firmware, a new token was required to switch back to debug firmware.

With the new behavior, the token is saved to flash, meaning it remains readable via MDSR even after reset. Once installed, the token allows the user to move between debug and production firmware until it is explicitly revoked using the MDSR set command.

Bug Fixes

See Bug Fixes section.

For the list of changes and bug fixes in earlier versions, see Release Notes History section.


Last updated: