User Tools

Site Tools


howto:fc_patcher_tool

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
howto:fc_patcher_tool [2019/08/09 19:14]
digdat0 [7. Modify flight controller parameters]
howto:fc_patcher_tool [2020/01/25 23:09] (current)
digdat0 path
Line 51: 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://​github.com/​o-gs/​dji-firmware-tools/​raw/​master/​dji_imah_fwsig.py
 +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 179: Line 193:
  
 ==== 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.
  
-   set PATH_TO_TOOLS=C:​\fcpatcher+You need to edit FC_patch_sequence_for_dummy_verify.sh and you will see the following
  
 +//if [[ -z "​${PATH_TO_TOOLS}"​ ]]; then
 +  echo "​Define PATH_TO_TOOLS variable to use this script! eg:"
 +  echo "​PATH_TO_TOOLS=/​tmp/​tools/​ ./​FC_patch_sequence_for_dummy_verify.sh"​
 +  exit 1
 +//
 +
 +Change the PATH_TO_TOOLS to be wherever you have all the files, such as C:​\fcpatcher
  
  
Line 192: Line 213:
    ​FC_patch_sequence_for_dummy_verify.sh Mavic 03.02.44.08    ​FC_patch_sequence_for_dummy_verify.sh Mavic 03.02.44.08
  
 +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
  
  
 +   ​cd\fcpatcher
    adb shell    adb shell
    mount -o remount,rw /vendor    mount -o remount,rw /vendor
howto/fc_patcher_tool.txt · Last modified: 2020/01/25 23:09 by digdat0