Difference between revisions of "Mvcam firmware update manual"

From wiki_veye
Jump to navigation Jump to search
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
===Applicable Product models===
 
===Applicable Product models===
  
*MV MIPI series (for instance MV-MIPI-IMX178M ...)
+
* MV MIPI series (e.g., MV-MIPI-IMX178M ...)
*RAW MIPI series (for instance RAW-MIPI-SC132M ...)
+
* RAW MIPI series (e.g., RAW-MIPI-SC132M ...)
*VEYE-MIPI-IMX335
+
* VEYE-MIPI-IMX335
  
 
=== How to upgrade camera firmware ===
 
=== How to upgrade camera firmware ===
Each MIPI camera module has an i2c control interface. We use this i2c bus interface for firmware upgrades.
+
Each MIPI camera module features an I2C control interface, which is used to facilitate firmware upgrades via the I2C bus.
  
==== Prepare ====
+
==== Preparation ====
You can get the upgrade package for the camera from this [https://www.mediafire.com/folder/4tov5s500gaif/camera_firmware_upgrade_images link]. The default file name is ProductMode_Version_.bin, for instance MV-MIPI-IMX178M_C1.08_L1.02_upgrade.bin.
+
You can download the camera firmware upgrade package from the provided [https://www.mediafire.com/folder/4tov5s500gaif/camera_firmware_upgrade_images link]. The default file format is <code>ProductModel_Version_.bin</code>, for example, <code>MV-MIPI-IMX178M_C1.08_L1.02_upgrade.bin</code>.
  
Use the veye_i2c_upgrade tool to perform the upgrade operation. For different motherboards, we release the corresponding mv_tools_rpi toolset which contains veye_i2c_upgrade.
+
To perform the upgrade, use the <code>veye_i2c_upgrade</code> tool. For different platforms, we provide the corresponding toolsets, such as <code>mv_tools_rpi</code>, which includes <code>veye_i2c_upgrade</code>.
  
The mv_tools_rpi is available on GitHub, for example the tools for the Raspberry Pi platform can be downloaded from this [https://github.com/veyeimaging/mvcam_raspberrypi/tree/main/mv_tools_rpi link].
+
The <code>mv_tools_rpi</code> toolset can be found on GitHub.  
  
==== Upgrading ====
+
For instance,
  
* Step 1:  
+
Raspberry Pi platform tools are available for download at this [https://github.com/veyeimaging/mvcam_raspberrypi/tree/main/mv_tools_rpi link].
  
Put the upgrade package(MV-MIPI-IMX178M_C1.08_L1.02_upgrade.bin) into the same directory as veye_i2c_upgrade.
+
Jetson platform tools at this [https://github.com/veyeimaging/nvidia_jetson_veye_bsp/tree/master/mv_tools_jetson/veye_upgrade link].
  
* Step 2:
+
RK35XX platform tools at this [https://github.com/veyeimaging/rk35xx_firefly/tree/main/mv_tools_rockchip/veye_upgrade link].
  
Confirm that the camera module is powered up.
+
==== Upgrade Steps: ====
  
Using v4l2 driver mode, the power up and probe process will be performed during the linux boot process. Just power on the board and it should work.
+
===== Step 1: =====
 +
Place the upgrade package (e.g., <code>MV-MIPI-IMX178M_C1.08_L1.02_upgrade.bin</code>) in the same directory as <code>veye_i2c_upgrade</code>.
  
In particular, for the legacy mode of the Raspberry Pi, you need to execute camera_i2c_config to power up the camera.
+
===== Step 2: =====
 +
Ensure that the camera module is powered on.
  
* Step 3:
+
* 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 <code>camera_i2c_config</code> to power up the camera manually.
  
Please refer to the following article to determine which i2c bus this camera is connected to.
+
===== Step 3: =====
 +
Refer to this article to determine which I2C bus the camera is connected to.
  
 
[http://wiki.veye.cc/index.php/I2c_bus_number_and_video_node i2c bus number on different boards]
 
[http://wiki.veye.cc/index.php/I2c_bus_number_and_video_node i2c bus number on different boards]
  
* Step 4:  
+
===== Step 4: =====
 
 
 
For the mv series, execute this command to read the current version:
 
For the mv series, execute this command to read the current version:
  
Line 45: Line 48:
 
<code>./veye5_mipi_i2c.sh -r -f version -b [i2c bus]</code>
 
<code>./veye5_mipi_i2c.sh -r -f version -b [i2c bus]</code>
  
* Step 5:  
+
===== Step 5: =====
 +
Execute the upgrade command. A progress prompt will appear during the process:
 +
 
 +
<code>sudo ./veye_i2c_upgrade [upgrade package file name] -b [i2c bus]</code>
  
Execute this command to upgrade, and a progress prompt will be displayed during the upgrade.  
+
If the upgrade fails, power cycle the camera and try again.  
  
<code>sudo ./veye_i2c_upgrade [upgrade package file name] -b [i2c bus]</code>
+
===== Step 6: =====
 +
After the upgrade, the camera will restart automatically. Verify the new firmware version using the same commands as in Step 4.
  
* Step 6:
+
For the mv series, execute this command to read the current version:
  
After the upgrade is complete, the camera will automatically restart. You can re-read the version number to confirm.
+
<code>./mv_mipi_i2c.sh -r -f version -b [i2c bus]</code>
 +
 
 +
For VEYE-MIPI-IMX335,execute this command to read the current version:
  
 
<code>./veye5_mipi_i2c.sh -r -f version -b [i2c bus]</code>
 
<code>./veye5_mipi_i2c.sh -r -f version -b [i2c bus]</code>
  
* Step 7:
+
===== Step 7: =====
 
+
It’s recommended to restore the factory settings post-upgrade to prevent potential conflicts between the current configuration and the newly upgraded firmware:
After successful upgrade, it is recommended to restore the factory settings to avoid possible problems caused by the mismatch between the current configuration parameters and the newly upgraded program.
 
  
<code>./veye5_mipi_i2c.sh -w -f factoryparam -b [i2c bus]</code>
+
<code>./mv_mipi_i2c.sh -w -f factoryparam -b [i2c bus]</code>

Latest revision as of 17:50, 12 September 2024

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.

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.7 Step 7:

It’s recommended to restore the factory settings post-upgrade to prevent potential conflicts between the current configuration and the newly upgraded firmware:

./mv_mipi_i2c.sh -w -f factoryparam -b [i2c bus]