-
Notifications
You must be signed in to change notification settings - Fork 427
Firmware m1700
Target
Purpose
Versions
Structure
OS and Libraries
Flashing
Interfaces
The module programs unknown VPS camera micro-controller. Location of this chip:
- in P3X, P3S and P3XW, it is on P3X VPS Module board
- in WM610, it is on WM610 VPS Module board
TODO
There are multiple versions, always unencrypted.
| Marking | Packages | Timestamp | Overview |
|---|---|---|---|
| 01.01.0004 | WM610_FC550_FW_V01.08.00.92 WM610_FW_V01.08.00.92 | 2016-03-24 | |
| 01.01.0008 | WM610_FC350Z_FW_V01.09.01.40 | 2016-11-09 | |
| 01.01.0258 | P3S_FW_V01.01.0008 P3S_FW_V01.01.0009 P3X_FW_V01.01.0006 P3X_FW_V01.01.0008 P3X_FW_V01.01.0009 P3X_FW_V01.01.1003 | 2015-04-30 ... 2015-05-12 | |
| 01.01.0262 | P3S_FW_V01.02.0007 P3S_FW_V01.02.0008 P3X_FW_V01.01.1007 P3X_FW_V01.02.0006 | 2015-06-12 ... 2015-07-10 | |
| 01.01.0263 | P3S_FW_V01.03.0020 P3S_FW_V01.04.0010 P3S_FW_V01.05.0030 P3S_FW_V01.06.0040 P3S_FW_V01.07.0060 P3S_FW_V01.08.0080 P3S_FW_V01.09.0060 P3S_FW_V01.10.0090 P3XW_FW_V01.01.0000 P3XW_FW_V01.02.0010 P3XW_FW_V01.03.0020 P3XW_FW_V01.04.0030 P3XW_FW_V01.04.0036 P3XW_FW_V01.05.0040 P3X_FW_V01.03.0020 P3X_FW_V01.04.0005 P3X_FW_V01.04.0010 P3X_FW_V01.05.0030 P3X_FW_V01.06.0040 P3X_FW_V01.07.0043_beta P3X_FW_V01.07.0060 P3X_FW_V01.08.0080 P3X_FW_V01.09.0060 P3X_FW_V01.10.0090 | 2015-07-24 ... 2016-11-07 |
TODO
TODO
Below are the known ways to re-flash the firmware. Some of the flashing methods may not be listed here.
The official way of flashing the firmware is by inserting an SD-card with firmware package file into the drone camera. The camera will extract modules from the package and distribute them to proper target components. It requires the firmware in bin form to exist in root directory of the SD-card.
In order for the firmware to be accepted:
- it cannot be compressed on the SD-card
- no newer firmware should exist on the card
- the firmware must have original file name, specific to the product
- the firmware must match the product being updated
- the new firmware needs to be newer than current, or current needs to allow rollback to the target version
- if a proper FW_DEBUG file (ie. P3X_FW_DEBUG for P3X) exists in the root directory of SD-card, the version checking rules above does not apply
After the upgrade, two logs will be created on the SD-card. The more verbose log will be in a MISC/LOG folder which has the hidden attribute set. It is best to check that log for a result information.
The camera can also upgrade specific modules of the drone if properly named files are found on the SD-card. The firmware module file needs to be unencrypted - flashing an encrypted firmware this way will cause the updated device to crash during startup, and the only way to bring it back to life will be to hook to it directly and flash it using a hardware programmer stick.
The proper file name for P3XW is "PMVOM4Fw3.bin". For P3X and current firmware lower than P3X_FW_V01.05.0030, or P3S and current firmware lower than P3S_FW_V01.04.0010 the name is "MVOM4Fw.bin". For newer current firmware version, the accepted file name in P3X and P3S is "PMVOM4Fw3.bin".
After the upgrade, log files will be created on SD-card, similar to the method with package.
TODO
This page is created by drone enthusiasts for drone enthusiasts.
If you see a mistake, or you know more about specific subject, or you see an area for improvement for the wiki - create an issue in this project and attach your patch (or describe the change you propose).