Multiprotocol firmware is compiled using the Arduino IDE. The guide below will walk you through all the steps to compile and upload your customized firmware.
These instructions are for the STM32 version of the Multiprotocol module. If you are Compling for the Arduino ATmega328p version of the Multiprotocol Module please go to the dedicated ATmega328 page.
- Tools Required
- Preparation
- Configure the firmware
- Verify the firmware
- Preparing to upload the firmware
- Uploading the firmware
- Precompiled Binaries
- Troubleshooting
| 3.3V USB-TTL Adapter | 4-pin Serial Programming Header |
|---|---|
 |
 |
| (example ebay link) | (example ebay link) |
The USB-TTL adapter can be either FTDI or CH340G, as long as it works. It should have a switch or jumper to select 3.3V or 5V, which must be set to 3.3V.
The 4-pin header needs to be soldered onto the board as indicated by the red rectangle:
| DIY Multiprotocol Module | Banggood 4-in-1 Module | iRangeX IRX4 Plus Module |
|---|---|---|
 |
 |
 |
Note: The Banggood STM32 module most likely already has the header pin in place.
- Download and install the Arduino IDE. The currently supported Arduino version is 1.8.5, available for Windows and Mac OSX
- It is recommended to upgrade Java to the latest version
- Either
- Download the zip file with the Multiprotocol module source code from here and unzip and copy the source code folder Multiprotocol to a location of your choosing, or
- Clone the project using Git or Github Desktop, then
- Double-click the Multiprotocol.ino file in the Multiprotocol folder to open the project in the Arduino IDE
- Follow these instructions to install the Multi 4-in-1 STM32 Board in the Arduino IDE
- Under Tools -> Board select Multi 4-in-1 (STM32FC103)
- Under Tools -> Programmer select stm32flash (FTDI)
The STM32 module has more than enough flash space for all the available protocols so, unlike the Atmega328p-based module, it is not necessary to disable unused protocols.
You can still disable protocols if you wish, and you may also enable or disable other optional Multiprotocol features.
To check that the program will compile correctly and fit in the Atmega click Sketch -> Verify/Compile, or press Ctrl+R.
If there are errors, carefully read it, go to the line number indicated and correct your typo.
If there are no errors and you see output like this:
Sketch uses 68564 bytes (52%) of program storage space. Maximum is 131072 bytes.
Global variables use 4064 bytes (19%) of dynamic memory, leaving 16416 bytes for local variables. Maximum is 20480 bytes.
You can proceed to the next step.
If you have already burned the bootloader, and are simply recompiling firmware to re-flash using your TX or USB cable, you can skip this step and go straight to Flash from TX or Upload via USB.
There are three methods to upload firmware to an STM32 module:
- Flash from TX - highly recommended, uses maintenance mode in radios running ersky9x to upload the firmware
- Upload via USB - uses the USB port on the module
- Upload via Serial (FTDI) - uses the serial interface on the module via a USB-to-TTL adapter
Note: 'Flash from TX' is only available with radios running ersky9x r221e2 or newer
Flash from TX is highly recommended if your transmitter supports it, Upload via USB is recommended for all others. Upload via Serial can be used if your module does not have a working USB port and your transmitter does not run ersky9x.
- Under Tools -> Upload Method select an upload method
The rest of this process will vary depending on the upload method you selected.
It is strongly recommended that you power your module from the transmitter when flashing it. This ensures that the module cannot be inadvertently supplied with 5V, which will damage the RF modules. This guide assumes that you will follow that advice, and instructs you to leave the V+ pin on the USB-to-TTL adapter disconnected. You may choose to ignore that advice at your own risk!
- Put the module in the transmitter
- Connect the USB-to-TTL adapter to the module's 4-pin serial header as follows:
- USB-to-TTL TX pin <-> Module RX pin
- USB-to-TTL RX pin <-> Module TX pin
- USB-to-TTL GND pin <-> Module GND pin
- Plug the USB-to-TTL adapter into the PC
- In the Arduino IDE click Tools -> Port and choose the COM port which matches the USB-to-TTL adapter
If you are using Upload via Serial you can skip this step and proceed to Upload via Serial.
If you have selected either Flash from TX or Upload via USB the module will need to install the appropriate bootloader. The bootloader only needs to be installed once unless you decide to switch from one upload method to the other.
In order to flash the bootloader the BOOT0 jumper must be installed.
- Install the BOOT0 jumper
- Switch on the transmitter
- Verify that you have selected the correct upload method under Tools -> Upload Method
- Verify that you have selected stm32flash (FTDI) as the programmer under Tools -> Programmer
- Verify that the USB-to-TTL adapter is correctly connected to your module and you have selected the correct port under Tools -> Port
- Click on Tools -> Burn Bootloader
Output will look similar to this:
C:\Users\blye\AppData\Local\Arduino15\packages\multi4in1\hardware\STM32F1\1.0.0/tools/win/serial_upload.bat COM4 0x0 C:\Users\blye\AppData\Local\Arduino15\packages\multi4in1\hardware\STM32F1\1.0.0/bootloaders/Multi4in1/StmMultiUSB.bin
stm32flash -v -g 0x0 -b 57600 -w C:\Users\blye\AppData\Local\Arduino15\packages\multi4in1\hardware\STM32F1\1.0.0\bootloaders\Multi4in1\StmMultiUSB.bin COM4
stm32flash 0.4
http://stm32flash.googlecode.com/
Using Parser : Raw BINARY
Interface serial_w32: 57600 8E1
Version : 0x22
Option 1 : 0x00
Option 2 : 0x00
Device ID : 0x0410 (Medium-density)
- RAM : 20KiB (512b reserved by bootloader)
- Flash : 128KiB (sector size: 4x1024)
- Option RAM : 16b
- System RAM : 2KiB
Write to memory
Erasing memory
Wrote and verified address 0x08000100 (3.56%)
Wrote and verified address 0x08000200 (7.13%)
...
Wrote and verified address 0x08001c00 (99.78%)
Wrote and verified address 0x08001c10 (100.00%) Done.
Starting execution at address 0x08000000... done.
Assuming the process is successful:
- Power off the transmitter
- Remove the BOOT0 jumper
- Disconnect the USB-to-TTL adapter
Follow the instructions which apply to the Upload method you previously selected.
- Click Sketch -> Export compiled Binary, or press Ctrl+Alt+S
- Locate the file named multifw.bin in the Multiprotocol folder
- Follow the instructions here to upload the firmware using your radio
The Upload via USB bootloader enables your PC to detect the Multiprotocol module as a Maple DFU device. It will not be detected as a USB serial device until the firmware is uploaded to it, when it will be detected as a Maple Serial device.
In order for these devices to be correctly identified in Windows it is necessary to install drivers. This only needs to be done once.
- Open the folder where you unzipped or cloned the Multiprotocol project
- Browse to \BootLoaders\Boards\stm32\drivers
- Run install-drivers.bat
- Follow the prompts to install the two drivers
- Download and install the legacy Windows XP drivers from here
Note: Power to the module will be supplied via the USB cable. If the module is installed in a transmitter, the transmitter should be switched off.
- Connect the USB cable to the Multiprotocol module
- Verify that a Maple device appears in Device Manager (Maple DFU for a module with only a bootloader, Maple Serial for a module with a bootloader and firmware)
- In the Arduino IDE click Sketch -> Upload, or press Ctrl+U
You should see output similar to this:
Sketch uses 68564 bytes (52%) of program storage space. Maximum is 131072 bytes.
Global variables use 4064 bytes (19%) of dynamic memory, leaving 16416 bytes for local variables. Maximum is 20480 bytes.
C:\Users\blye\AppData\Local\Arduino15\packages\multi4in1\hardware\STM32F1\1.0.0/tools/win/maple_upload.bat COM4 2 1EAF:0003 C:\Users\blye\AppData\Local\Temp\arduino_build_933551/Multiprotocol.ino.bin
maple_loader v0.1
Resetting to bootloader via DTR pulse
Reset via USB Serial Failed! Did you select the right serial port?
Searching for DFU device [1EAF:0003]...
Assuming the board is in perpetual bootloader mode and continuing to attempt dfu programming...
Found it!
Opening USB Device 0x1eaf:0x0003...
Found Runtime: [0x1eaf:0x0003] devnum=1, cfg=0, intf=0, alt=2, name="STM32duino bootloader v1.0 Upload to Flash 0x8002000"
Setting Configuration 1...
Claiming USB DFU Interface...
Setting Alternate Setting ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
Transfer Size = 0x0400
bytes_per_hash=1371
Starting download: [##################################################] finished!
state(8) = dfuMANIFEST-WAIT-RESET, status(0) = No error condition is present
Done!
Resetting USB to switch back to runtime mode
error resetting after download: usb_reset: could not reset device, win error: The system cannot find the file specified.
Note: The line Reset via USB Serial Failed! Did you select the right serial port? is expected because the uploader initially looks for a Maple Serial device, which isn't yet available, before failing back to Maple DFU. The final line warning, stating that the device could not be reset, is also expected.
For subsequent firmware uploads you need only repeat steps 1-3 above, ensuring that you first select the correct COM port, which should be labelled COMx (Multi 4-in-1 (STM32F103CB)).
If the module is installed in a transmitter, disconnect the USB cable before powering on the transmitter.
Upload via Serial follows the same process as burning the bootloader and uses the same USB-to-TTL adapter.
- Ensure you USB-to-TTL adapter is connected as described in Connect the programmer
- Install the BOOT0 jumper
- Turn on the transmitter
- Click Sketch -> Upload
You should see output similar to this:
Sketch uses 62772 bytes (47%) of program storage space. Maximum is 131072 bytes.
Global variables use 3216 bytes (15%) of dynamic memory, leaving 17264 bytes for local variables. Maximum is 20480 bytes.
C:\Users\blye\AppData\Local\Arduino15\packages\multi4in1\hardware\STM32F1\1.0.0/tools/win/serial_upload.bat COM4 0x8000000 C:\Users\blye\AppData\Local\Temp\arduino_build_868436/Multiprotocol.ino.bin
stm32flash -v -g 0x8000000 -b 57600 -w C:\Users\blye\AppData\Local\Temp\arduino_build_868436\Multiprotocol.ino.bin COM4
stm32flash 0.4
http://stm32flash.googlecode.com/
Using Parser : Raw BINARY
Interface serial_w32: 57600 8E1
Version : 0x22
Option 1 : 0x00
Option 2 : 0x00
Device ID : 0x0410 (Medium-density)
- RAM : 20KiB (512b reserved by bootloader)
- Flash : 128KiB (sector size: 4x1024)
- Option RAM : 16b
- System RAM : 2KiB
Write to memory
Erasing memory
Wrote and verified address 0x08000100 (0.41%)
Wrote and verified address 0x08000200 (0.82%)
...
Wrote and verified address 0x0800f500 (99.92%)
Wrote and verified address 0x0800f534 (100.00%) Done.
Starting execution at address 0x08000000... done.
Once the firmware has uploaded, remove the BOOT0 jumper and disconnect the USB-to-TTL adapter.
Pre-compiled binaries are availale here.
- Multiprotocol_V1.X.X_STM32.bin files are for transmitters with support for hardware telemetry inversion, such as Turnigy 9X, 9XR, 9X+.
- Multiprotocol_V1.X.X_STM32_INV.bin files are for tranismitters which require telemetry inverted in the module firmware, such as Taranis.
If you want to flash a pre-compiled binary file (like the Release .bin files) you will use the same USB-to-TTL adapter as above.
You will also need to download the ST Flash Loader Demonstrator from here
Run the ST Flash Loader Demonstrator program. There are many tutorials on the web on how to use this program, for example here.
You can report your problem using the GitHub issue system or go to the Main thread on RCGROUPS to ask your question. Please provide the following information:
- Multiprotocol code version
- STM32 version
- TX type
- Using PPM or Serial, if using er9x or ersky9x the version in use
- Different led status (multimodule and model)
- Explanation of the behavior and reproduction steps