FlyPlus firmware for FlySky I6X

The campaign was stopped by portal itself. But the project is still alive!

First working compilation of OpenTX. Well no much is working, but it started.

It took me some time, but I was able to isolate all components of OpenTX and shrink binary to around 90kB, and 13kB of RAM, it looks we have still space to add device specific handling.

I got in touch with OpenTX guys because there are rumors about new FlySky unit with OpenTX on board. So it look we will get protocol code instead of hacked one!

Implemented features:

• Using telemetry value SNR/RSSI/ERROR for auxiliary channels (channel 11/12) - fixed for values below 16dB 05.04.2017
• Alarm for SNR values <= 10dB
• 2 Bytes sensors added to telemetry list (without units because in case of to long text display method crashes)
• Telemetry data is working with IA6B, you can use my custom CleanFlight from:
  
  https://github.com/qba667/cleanflight/releases
  
  Or current branch of BetaFlight
  https://github.com/betaflight/betaflight/releases
  
  Selected sensors can be configured using CLI by setting array "ibus_sensor"
  If sensor id assigned to this array equals 0 it means sensor is not configured. First occurrence of 0 is preventing further sensors usage.
  
  MavlinkToIBUS can be also used in case of APM/Pixhawk
  https://github.com/qba667/MAVLinkToIbus
  
  Selected sensors can be configured using CLI by setting ibus_sensor array:

set ibus_sensor = 12,13,14,15,16,17,240,65,0,255,255,255,255,255,255

If sensor id assigned to this array equals 0 it means sensor is not configured. First occurrence of 0 is preventing further sensors usage.

1. Temperature
2. RPM
3. External Voltage
4. Avg Cell Voltage
5. Battery current
6. Remaining batt.
7. Throttle
8. Heading
9. Climb rate
10. CoG
11. GPS status
12. ACC X
13. ACC Y
14. ACC Z
15. Roll
16. Pitch
17. Yaw
18. Vertical speed
19. Ground speed
20. GPS distnace
21. Armed
22. Flight mode

Model memory details. I was searching for space in EEPROM where we can store our custom settings.

It looks promising:

0 - 639 General radio settings
640 - 7039 models 320 *20
7040 -> 7648 - 608 bytes of unrecognized yet settings (calibration etc)

The EEOROM is 16 Kbytes big - we have 8 Kbytes for us!

I have broken subtrims and breakpoints - right now I am searching for the reason, if you use this functionality please not update.

I have started work on channel assignment - meantime I have published on RCGroups version with RSSI (SNR) on channel 11.

https://github.com/qba667/FlyPlusI6X/releases/tag/...

Disassembly work in progress - injecting channel data successful - SNR on channel 11 working - but not configurable - I have to find more about menu structure.

Today I have received 2 brand new MCUs - STM32F091VCT6 - the flash size is doubled in this MCU so porting Deviation TX will be simpler in initial phase.

Meantime I was investigating possibility of installing JQ6500 Voice Sound Module - it looks that I6X can get voice.

https://www.aliexpress.com/item/NEW-JQ6500-Voice-S...

Another mod will be adding SPI flash memory - W25Q64.

https://www.aliexpress.com/item/W25Q64-64Mbit-8MBy...

Both components ordered.

Today I got at work latest IDA pro license - initial analysts is much better then before.

I have discovered more details about firmware and original implementation - it is wasting a lot of flash and memory! Good news is we get a gift from FlySky the have left for us 0x3FFF - 0x298C bytes of RAM!