This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
howto:fc_patcher_tool [2019/03/29 02:12] digdat0 [9. Run the SH script] |
howto:fc_patcher_tool [2020/01/25 23:09] (current) digdat0 path |
||
---|---|---|---|
Line 20: | Line 20: | ||
- Download [[https:// | - Download [[https:// | ||
- Download an app to allow running .SH files on Windows; i used [[https:// | - Download an app to allow running .SH files on Windows; i used [[https:// | ||
+ | - Download CYGWIN to allow running .sh on Windows [[https:// | ||
- Download and install a file extraction app like [[https:// | - Download and install a file extraction app like [[https:// | ||
- Download pcrypto by running this from a command line python -m pip install pycryptodome | - Download pcrypto by running this from a command line python -m pip install pycryptodome | ||
+ | | ||
| | ||
Line 49: | Line 51: | ||
* The file is now extracted. | * The file is now extracted. | ||
==== 4. Unsig the 0306 file ===== | ==== 4. Unsig the 0306 file ===== | ||
+ | There are two ways to unsig the 306 file: | ||
+ | |||
+ | * Use the dji_imah_fwsig.py tool | ||
+ | * Copy the 306 file to the aircraft and use djiverify | ||
+ | |||
+ | == Use the dji_imah_fwsig.py tool == | ||
+ | Download the tool from here https:// | ||
+ | Open a command line and run the tool | ||
+ | Example: python dji_imah_fwsig.py -vv -u -i wm335_0306_v03.03.04.10_20180429.pro.fw.sig | ||
+ | |||
+ | You are done, goto step #5 | ||
+ | |||
+ | == Copy the 306 file to the AC == | ||
+ | |||
Now we will unsig the 306 file, which contains the flight controller parameters. You will need to power on your aircraft and connect to PC via USB. Once you have .. | Now we will unsig the 306 file, which contains the flight controller parameters. You will need to power on your aircraft and connect to PC via USB. Once you have .. | ||
Line 137: | Line 153: | ||
^ g_config.airport_limit_cfg.cfg_disable_airport_fly_limit|1|| | ^ g_config.airport_limit_cfg.cfg_disable_airport_fly_limit|1|| | ||
^ g_config.airport_limit_cfg.cfg_limit_data|20250910|| | ^ g_config.airport_limit_cfg.cfg_limit_data|20250910|| | ||
- | ^ g_config.flying_limit.driver_license_limit_enable |0|| | + | ^ g_config.flying_limit.driver_license_limit_enable |2|| |
- | ^ g_config.flying_limit.viechle_license_limit_enable|0|| | + | ^ g_config.flying_limit.viechle_license_limit_enable|2|| |
^ g_config.flying_limit.height_limit_enabled|2|| | ^ g_config.flying_limit.height_limit_enabled|2|| | ||
^ g_config.airport_limit_cfg.cfg_search_radius|1|| | ^ g_config.airport_limit_cfg.cfg_search_radius|1|| | ||
- | ^ g_config.airport_limit_cfg.cfg_enable[FLY_LIMIT_TYPE_AIRPORT]|0|| | + | ^ g_config.airport_limit_cfg.cfg_enable[FLY_LIMIT_TYPE_AIRPORT]|1|| |
- | ^ g_config.airport_limit_cfg.cfg_enable[FLY_LIMIT_TYPE_SPECIAL]|0|| | + | ^ g_config.airport_limit_cfg.cfg_enable[FLY_LIMIT_TYPE_SPECIAL]|1|| |
- | ^ g_config.flying_limit.limit_height_rel|10000|| | + | ^ fly_limit_height|10000|| |
- | ^ g_config.flying_limit.limit_height_abs|10000|| | + | |
- | ^ g_config.flying_limit.limit_height_abs_without_gps|10000|| | + | |
^ g_config.mode_normal_cfg.tilt_atti_range|33|| | ^ g_config.mode_normal_cfg.tilt_atti_range|33|| | ||
^ g_config.mode_normal_cfg.vert_vel_up|7|| | ^ g_config.mode_normal_cfg.vert_vel_up|7|| | ||
Line 163: | Line 177: | ||
^ g_config.bat_config.level2_smart_battert_land|0|| | ^ g_config.bat_config.level2_smart_battert_land|0|| | ||
- | Note: This is a draft list as of 28-Mar-19 | + | Note: This is a draft list as of 9-Aug-19 |
+ | |||
+ | |||
+ | - I dont believe " | ||
+ | |||
+ | |||
+ | - This needs to be broken out NFZ, height, speed, battery #TODO | ||
+ | |||
+ | |||
+ | - need to include Bret883' | ||
+ | |||
+ | |||
+ | - lets create a seperate wiki page for FC Patcher params #TODO | ||
+ | |||
==== 8. Set path ==== | ==== 8. Set path ==== | ||
- | * Goto a command prompt and type | ||
+ | We need to tell the script what folder contains the firmware tools and other files. | ||
+ | |||
+ | You need to edit FC_patch_sequence_for_dummy_verify.sh and you will see the following | ||
- | | + | //if [[ -z "${PATH_TO_TOOLS}" ]]; then |
+ | echo " | ||
+ | echo " | ||
+ | exit 1 | ||
+ | // | ||
+ | Change the PATH_TO_TOOLS to be wherever you have all the files, such as C: | ||
Line 178: | Line 213: | ||
| | ||
+ | You can change Mavic to your Aircraft, such as P4P, Spark, etc. The version number is the NEW version you are setting. | ||
Note: This step requires some tool to enable running sh scripts on windows. I installed Github with bash and it had the SH included to allow running the script. | Note: This step requires some tool to enable running sh scripts on windows. I installed Github with bash and it had the SH included to allow running the script. | ||
- | The aa.bb.cc.dd string after Spark or Mavic arg is the version of the FC module you are building. It should be different from the one that is currently installed on the bird, so basically increase the number each time you build a new version... | + | This should produce a few (uncleaned) tmp files, and a *dummy_verify.bin file which is the one you will be able to flash the aircraft using dumldore |
- | + | ||
- | This should produce a few (uncleaned) tmp files, and a .bin file which is the one you will be able to flash the aircraft using dumldore | + | |
==== 9. Install the dummy_verify.sh script on your bird ==== | ==== 9. Install the dummy_verify.sh script on your bird ==== | ||
- | * Goto a command prompt and type | + | Open dumldore |
+ | Press ENABLE ADB, wait a second. Close dumldore | ||
+ | IF, during this step, adb shell fails, you do not have adb access. GO back to dumldore and press ENABLE ADB. | ||
+ | * Goto a command prompt and type | ||
+ | |||
+ | |||
+ | | ||
adb shell | adb shell | ||
mount -o remount,rw /vendor | mount -o remount,rw /vendor | ||
Line 197: | Line 237: | ||
chown root:root dummy_verify.sh | chown root:root dummy_verify.sh | ||
chmod 755 dummy_verify.sh | chmod 755 dummy_verify.sh | ||
- | cp /system/bin/dji_verify / | + | cp /sbin/dji_verify / |
sync | sync | ||
cd / | cd / | ||
mount -o remount,ro /vendor | mount -o remount,ro /vendor | ||
+ | |||
+ | Turn off the aircraft. | ||
+ | |||
==== 10. Flash the .bin file you made earlier ==== | ==== 10. Flash the .bin file you made earlier ==== | ||
+ | * Power the aircraft back on | ||
* Open a command prompt and type | * Open a command prompt and type | ||
adb shell | adb shell | ||
- | mount -o bind / | + | mount -o bind / |