Failed to open firmware file.

This error message could pop up due to two reasons.

1. If the software prerequisites have not been installed (VC++ redistributables in this case) it will not be possible for the program to load the DFU file.
2. If there are any characters other than A-Z a-z 0-9 in the path to the DFU file this error message could also pop up. Try to place the DFU file in a path that does not have any non supported characters.
3. The firmware file is corrupt. Try downloading the latest firmware files.

Failed to set device in configuration mode.

This error message could pop up due to two reasons.

1. Can occasionally occur when writing firmware or reading / writing parameters. Either reconnect the sensor or restart the application.
2. If this occurs every time then it is most likely to do with having wrong DFU driver installed. The program is then unable to connect to the (DFU) device in configuration mode and will therefore display the error message above. Please follow the instructions under STM32Bootloader Driver section on the Getting Started page to resolve this.

Failed to write firmware or sensor does not show up.

This can occur if the sensor gets disconnected during a write firmware, problems with drivers, faulty firmware already installed on sensor etc. Check the following:

• Check that all connectors are plugged in correctly.
• Make sure the correct driver is installed, please follow the instructions under STM32Bootloader Driver section on the Getting Started page.
• Try another USB port, preferably connected directly with the computer without any hub or docking station between.
• Unplug the sensor, press and hold the black button on the interface board while plugging the sensor back in. It should now show up as "Device In Configuration Mode" and be possible to write a new firmware to it.