Updating the User Firmware

You only need to perform the operations in Installing the Runtime Package of the Programming Framework once for the initial installation or upgrade. You can refer to this section to update the firmware during subsequent development.
Do not update the user firmware during service traffic transmission. Otherwise, the update times out or fails.

Obtain the flow table configuration file configinfo generated in Developing OVS Data Plane Code and upload the file to the etc directory in the DPU environment. This file corresponds to the user code.

Obtain the firmware Hinic3_flash.bin generated in Developing OVS Data Plane Code and upload the firmware to the DPU environment. This firmware is the NPU firmware required for a cold update.

hinicadm3 updatefw -i hinic0 -f {NPU firmware} -a cold -n

The execution is successful if information similar to the following is displayed:

Please do not remove driver or network device.
Loading...
Firmware update start: 2025-07-01 08:35:38
[>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>] [100%][\]
Firmware update finish: 2025-07-01 08:36:13
Firmware update time used: 35s
Loading firmware image succeed.
Set update active cfg succeed!
Please reboot OS to take firmware effect.

On the host OS, run the reboot command to reboot the server OS so that the software package can take effect.
- Reboot the host OS. Do not reboot the DPU OS.
- By default, the DPU is rebooted in a coordinated manner when the server OS is rebooted.
  If the DPU is not rebooted, check and set the coordinated reboot status of the server and DPU.

Parent topic: OVS Deployment