village_idiot
Senior Heliman
Location: Land of confusion
| There is some kind of bootloader running as the servo connections that are using for programmer comms are not the same as listed on the data sheet, so they moved them with software. As far as what data I can get out, that's all shown over at RCGroups, so far they only allowed the GUID that the receiver is bound to, and I suspect the power condition and channel number for Quick Connect and LED blink (yet to be verified), so not much as the real meat is locked.
And if you brick it, then you might get to send it back where there should be a method of restoring it. Actually if you really brick it then the servo connectors should default back to their programming functions and you should still be able to push the full 8k "image" back into the device after changing IO pins. If I had the 8K worth of hex file, I would try to brick mine on purpose just to make sure it could be recovered and to document how to do it. An intentional brick would be easy to cause and should be part of the testing.
Yes there are a lot of shoulds in the above, and there would need to be some testing done before committing to offering this. I have 3 receivers that need their firmware upgraded, and I would be more than happy to upgrade them and send them back to Horizon for evaulation as part of the testing. The exception might be my AR6200 as I may want to get it installed without tying it up for the entire Summer. But the AR6100e that I've been using can remain a test device from now 'til I need it or want to sell it (with no plans for the future).
I would definitely rather work with Horizon/Spektrum than against them, but I do feel that we should be able to do this simple task at home (it really should be a simple task). Cracking this may be beyond my knowledge and it may never be done, but now that some connections are known, someone else may be able to finish the task. |
