The following is a comprehensive list of the supported parameters to customize
bf.cfg during BFB installation:
BlueField target is stuck inside UEFI menu
Upgrade to the latest stable boot partition images, see "How to upgrade the boot partition (ATF & UEFI) without re-installation".
BFB does not recognize the BlueField board type
If the .bfb file cannot recognize the BlueField board type, it reverts to low core operation. The following message will be printed on your screen:
Please contact NVIDIA Support if this occurs.
Unable to load BL2, BL2R, or PSC image
The following errors appear in console if images are corrupted or not signed properly:
CentOS fails into "dracut" mode during installation
This is most likely configuration related.
- If installing through the RShim interface, check whether /var/pxe/centos7 is mounted or not. If not, either manually mount it or re-run the setup.sh script.
- Check the Linux boot message to see whether eMMC is found or not. If not, the BlueField driver patch is missing. For local installation via RShim, run the setup.sh script with the absolute path and check if there are any errors. For a corporate PXE server, make sure the BlueField and ConnectX driver disk are patched into the initrd image.
How to find the software versions of the running system
Run the following:
Also, the version information is printed to the console.
For ATF, a version string is printed as the system boots.
For UEFI, a version string is printed as the system boots.
For Yocto, run:
How to upgrade the host RShim driver
See the readme at
How to upgrade the boot partition (ATF & UEFI) without re-installation
Boot the target through the RShim interface from a host machine:
Log into the BlueField target:
How to upgrade ConnectX firmware from Arm side
flint tools can be used to update firmware.
For Ubuntu, CentOS and Debian, run the following command from the Arm side:
How to configure ConnectX firmware
Configuring ConnectX firmware can be done using the mlxconfig tool.
It is possible to configure privileges of both the internal (Arm) and the external host (for DPUs) from a privileged host. According to the configured privilege, a host may or may not perform certain operations related to the NIC (e.g. determine if a certain host is allowed to read port counters).
For more information and examples please refer to the MFT User Manual which can be found at the following link.
How to use the UEFI boot menu
Press the "Esc" key when prompted after booting (before the countdown timer runs out) to enter the UEFI boot menu and use the arrows to select the menu option.
It could take 1-2 minutes to enter the Boot Manager depending on how many devices are installed or whether the EXPROM is programmed or not.
Once in the boot manager:
- "EFI Network xxx" entries with device path "PciRoot..." are ConnectX interface
- "EFI Network xxx" entries with device path "MAC(..." are for the RShim interface and the BlueField OOB Ethernet interface
Select the interface and press ENTER will start PXE boot.
The following are several useful commands under UEFI shell:
How to Use the Kernel Debugger (KGDB)
The default Yocto kernel has
CONFIG_KGDB_SERIAL_CONSOLE enabled. This allows the Linux kernel on BlueField to be debugged over the serial port. A single serial port cannot be used both as a console and by KGDB at the same time. It is recommended to use the RShim for console access (
/dev/rshim0/console) and the UART port (
/dev/ttyAMA0 or /dev/ttyAMA1) for KGDB. Kernel GDB over console (KGDBOC) does not work over the RShim console. If the RShim console is not available, there are open source packages such as KGDB demux and agent-proxy which allow a single serial port to be shared.
There are two ways to configure KGDBOC. If the OS is already booted, then write the name of the serial device to the KGDBOC module parameter. For example:
To attach GDB to the kernel, it must be stopped first. One way to do that is to send a "g" to
To debug incidents that occur at boot time, kernel boot parameters must be configured. Add "
kgdboc=ttyAMA1,115200 kgdwait" to the boot arguments to use UART1 for debugging and force it to wait for GDB to attach before booting.
Once the KGDBOC module is configured and the kernel stopped, run the Arm64 GDB on the host machine connected to the serial port, then set the remote target to the serial device on the host side.
<BF_INST_DIR> is the directory where the BlueField software is installed. It is assumed that the SDK has been unpacked in the same directory.
How to enable/disable SMMU
SMMU could affect performance for certain applications. It is disabled by default and can be modified in different ways.
- Enable/disable SMMU in the UEFI System Configuration
- Set it in
bf.cfgand push it together with the
install.bfb(see section "Installing Popular Linux Distributions on BlueField")
- In BlueField Linux, create a file with one line with
SYS_ENABLE_SMMU=TRUE, then run
The configuration change will take effect after reboot. The configuration value is stored in a persistent UEFI variable. It is not modified by OS installation.
See section "UEFI System Configuration" for information on how to access the UEFI System Configuration menu.
How to change the default console of the install image
How to change the default network configuration during BFB installation
On Ubuntu OS, the default network configuration for
oob_net0 interfaces is set by the cloud-init service upon first boot after BFB installation.
The default content of
/var/lib/cloud/seed/nocloud-net/network-config as follows:
This content can be modified during BFB installation using
bf.cfg. For example:
Using the same technique, any configuration file on the BlueField DPU side can be updated during the BFB installation process.