FuriousFPV has recently released a V2 firmware for their True-D diversity module for the Fatshark Dominator FPV Goggles. In this post we will talk about how I flash new firmware on my old module.
What’s New In the New V2 Firmware?
Here is my review of the True-D module with previous firmware.
Improved “Working Channel” mode
- Ability to move channels
- Ability to delete channels
New feature – Smart Search
It scans through all channels, and return the frequencies that are broadcasting, in the order of priority based on signal strength. Then you are allowed to also scroll through these channels.
Improved Receiver Switching Algorithm
- More precise antenna selection, and faster video switching speed
- Reduced noise
- Ability to show RSSI value
Boot-Up Screen Logo Customization
A logo of your choice will appear on the screen at start-up. However it looks to me that it’s not user customizable yet. There are limited options available, which are available on the firmware download page.
If you want to change logo, you will need to re-upload the firmware.
Here is our “IntoFPV” logo, firmware is available for download.
How To Update True-D Firmware
First of all, can old/existing True-D module update to new firmware (V2)? The answer is yes by using a FTDI cable. New module you buy in the future should already come with the new V2 firmware. However if you already own the module and wish the update the firmware yourself, this guide might help you. (Warning: I take no responsibility for damaged module during firmware flashing)
There are many Youtube videos out there showing you how to update True-D diversity firmware, so here is basically just a sum up. There are more than 1 way of flashing, one way is using XLoader.exe (this guide), another is the using OSD_Config.exe by FuriousFPV.
You will need this FTDI232 adapter (only $3!). And in this guide we are using Windows 10.
1. Download Firmware
2. Open Xloader.exe
Xloader.exe is located in:
3. Load Hex File, and Xloader Settings
Find the .hex file “True_D_REV_2.0” inside the folder FIRMWARE_TRUE_D_REV_2.0
Set Device to ATmega328, and Baud Rate to 57600. Make sure you choose the COM port of your FTDI adapter.
4. Connect FTDI Module with your True-D module
Remove the white plastic piece from the module, and you should see the 6 pins next to the antenna connectors.
Pinout is DTR,TX,RX,VCC,CTS,GND (from left to right). TX and RX should match on the FTDI and True-D, i.e., TX to TX, and RX to RX.
On the FTDI module you can select 3.3V or 5V. I use 5V because when I chose 3.3V, it doesn’t power up the module.
When you plug in your FTDI module to your computer, a new COM port should appear in Windows, if this is the first time you use this FTDI module, make sure you install the necessary drivers first.
When FTDI and True-D are connected correctly, you should see a solid green LED on the true-D and it should power up like normal.
On Xloader, select the COM Port of the FTDI, and press Upload.
FTDI lights will start blinking rapidly indicating that it’s talking to the True-D. Flashing will take a minute, when it’s finished, it will say “done” at the bottom of Xloader.
Note: Do not remove connection, or power down devices during firmware upload, it might damage your True-D. If it get stuck at uploading it could mean your TX and RX connection are reversed, or these pins are loose. Double check and try again.
Update (16/Nov/2016): I’m having trouble flashing one of my units, when using XLoader, it simply gets stuck at uploading, and FTDI adapter LED doesn’t flash (no data activity). When using OSD_config, it returns an error saying “Failed to talk to bootalder”. I am looking for a solution and when I manage to fix it I will come back and update on this page.
Update (20/Nov/2016): Some people having issues of “failed to talk to bootloader”, or stuck uploading error, was able to flash their modules by performing “timing trick). Basically, if you are using XLoader, you should hit upload as soon as you power up the module, and if you use OSD_Config, you should load the firmware file as soon as you power up the module.
However so far only modules of Rev01 and Rev02 confirmed they were successfully flashed their module with timing trick, Rev00 are still having this issue. You can find the Rev version under the screen, it’s printed on the PCB. See comments here for detail.