Radiolink AT9 as a platform for Deviation?

I just ordered an AT9. I think we'll need to do something interesting since apparently it only has a tiny EEPROM. But it does have a 512k onboard flash with 2k page size, which means we could very likely fit a small devofs filesystem on the MCU (maybe up to 256k). that would be plenty for anything except for icons.

Not the best quality, it has bearing on one side only, second side mounted on pot shaft.

Thanks to victzh, here is the hardware connectivity for the AT9:
www.deviationtx.com/wiki/hardware/radiolink_at9

The AT10 should be following soon. The FCC was nice enough to provide a schematic for it too:
www.deviationtx.com/wiki/hardware/radiolink_at10

You can find Frsky Taranis gimbals or Hitec Aurora 9 gimbals.

www.robotshop.com/en/axis-joystick-gim.html

www.banggood.com/Frsky-Taranis-X9D-Plus-...embly-p-1022093.html

I got my AT9 today and installed the test firmware that victzh put together on it right away. We can draw to the screen now, and usually that is the hardest part of porting Deviation. Then again, this transmitter has a different button configuration than the Devos do, and that could make it much more difficult since we assume 6 buttons and only actually have 5 (equivalent) buttons to use. Before I do anything else, I need to get a reliable programmer though. The Radiolink firmware upload software is terrible.

Small update:
I figured out that the problem with uploading to the Radiolink using 'dfu-util' is that the flash has a 2k page size, but the bootloader only supports a 1k transfer-size. dfu-util does an erase/write for each transfer, which means we erase the page we just wrote every other time. The fix is to do an erase pass first, and then follow it up with a write pass. I've modified my dfu_util to do this, but I'll need to update deviation_upload to support this as well to make it easy for others to use. In the interim, the radiolink software is (barely) usable.

I expect it'll wait for a 4-in-1/UniversalTx module. We may enable the stock protocol at some point, but the main benefit for Deviation would be supporting the current protocols.

The AT9 is almost exactly the same size as a Devo10.
They all have a 320x24016bit screen. I think the firmware is only setup to support 16 colors though (I'm not really sure, I haven't actually tested the stock firmware).

I think the AT10 is basically identical to the AT9 with the exception of the cursor lever and extra dial. I am not sure yet what to do with the interface on this one. we only have the equivalent of 5 buttons (Exit, Mode, Dial Press, Dial Left, Dial Right) and The entire interface is designed for 6 buttons.

I've converted our test software for the AT9 to work as a proper target for deviation. I can now build Deviation for the AT9. It doesn't actually work because I haven't figured out what to do with the filesystem, but I have verified that I can read from all of the analog inputs.

Because the AT9 has limited space for a filesystem, I don't think we'll get the full benefit of the 320x240 screen. My current plan is to build a reduced-color gui (probably just 16-color icons/buttons) to start with. Then we're thinking that we can add some SPI flash to a 4-in-1 module to give us proper file-system support with full color icons and full font support. if I can get that working, I should have a basic demo running pretty soon.