Mvcam firmware update manual

1 Applicable Product models

MV MIPI series (e.g., MV-MIPI-IMX178M ...)
RAW MIPI series (e.g., RAW-MIPI-SC132M ...)
VEYE-MIPI-IMX335

2 How to upgrade camera firmware

Each MIPI camera module features an I2C control interface, which is used to facilitate firmware upgrades via the I2C bus.

2.1 Preparation

You can download the camera firmware upgrade package from the provided link. The default file format is ProductModel_Version_.bin, for example, MV-MIPI-IMX178M_C1.08_L1.02_upgrade.bin.

To perform the upgrade, use the veye_i2c_upgrade tool. For different platforms, we provide the corresponding toolsets, such as mv_tools_rpi, which includes veye_i2c_upgrade.

The mv_tools_rpi toolset can be found on GitHub.

For instance,

Raspberry Pi platform tools are available for download at this link.

Jetson platform tools at this link.

RK35XX platform tools at this link.

2.2 Upgrade Steps:

2.2.1 Step 1:

Place the upgrade package (e.g., MV-MIPI-IMX178M_C1.08_L1.02_upgrade.bin) in the same directory as veye_i2c_upgrade.

2.2.2 Step 2:

Ensure that the camera module is powered on.

When using the V4L2 driver, the camera will power on and probe automatically during the Linux boot process—simply power on the board.
For legacy Raspberry Pi models, you need to execute camera_i2c_config to power up the camera manually.

2.2.3 Step 3:

Refer to this article to determine which I2C bus the camera is connected to.

i2c bus number on different boards

2.2.4 Step 4:

For the mv series, execute this command to read the current version：

./mv_mipi_i2c.sh -r -f version -b [i2c bus]

For VEYE-MIPI-IMX335，execute this command to read the current version：

./veye5_mipi_i2c.sh -r -f version -b [i2c bus]

2.2.5 Step 5：

Execute the upgrade command. A progress prompt will appear during the process:

sudo ./veye_i2c_upgrade [upgrade package file name] -b [i2c bus]

If the upgrade fails, power cycle the camera and try again.

2.2.6 Step 6：

After the upgrade, the camera will restart automatically. Verify the new firmware version using the same commands as in Step 4.