Matrix Vision mvBlueFOX3

To Next Page

To Previous Page

8.4 Relationship between driver, ﬁrmware, FPGA ﬁle and user settings 49

Note

As it can be seen in the image the ﬁrmware ﬁle is NOT part of the device driver but comes as a separate

archive. It is important to notice that a ﬁrmware ﬁle that may be present on the host system will not be used

automatically but only when the user or an application explicitly updates the ﬁrmware on the device and will

only become active after power-cycling the device.

The name of the ﬁrmware update archive (∗ in the ﬁgure above) is:

• mvBlueFOX3_Update.mvu

Only during a ﬁrmware update the ﬁrmware ﬁle that has been selected from the ﬁle system of the host system will

be downloaded permanently into the device's non-volatile memory.

Warning

Each ﬁrmware archive might contain more than one speciﬁc ﬁrmware version per device thus in order to select

the one that is appropriate for the device appropriate tools such as mvDeviceConﬁgure (p. 100) should be

used.

So assume a device with a certain ﬁrmware version is connected to a host system.

During an explicit ﬁrmware update, the ﬁrmware ﬁle will be downloaded onto the device. In order to become active

the device must be power-cycled:

Figure 8: Firmware ﬁle will be downloaded during an ﬁrmware update...

This can either be done by unplugging the device and then by plugging it back in or (for devices supporting this

feature) by resetting/rebooting the device by a certain software command (DeviceControl/DeviceReset). When

using mvDeviceConﬁgure (p. 100) to update devices the latter mechanism will be used by the tool thus it is NOT

necessary to unplug the device.

When the device has completed rebooting the new ﬁrmware version will become active:

MATRIX VISION GmbH

Matrix Vision mvBlueFOX3 - Page 60