Raphael Coeffic

> @raphaelcoeffic You can do it through the bootloader isn't it, read instead of write ? Not sure I understand that right. Can you please give me some context? 😅

Now I see: the MPM stores the binding information I to its own flash space, thus reading the full chip will produce a full backup including all bindings stored, correct?

> what is the purpose of `PROTOCOL_TELEMETRY_FRSKY_D_SECONDARY` ? And what is `PROTOCOL_TELEMETRY_FRSKY_D` instead? AFAIK, it was to be able to support some DIY Multiplex module which was outputting its telemetry...

> My use case was connecting a small attiny1614 based board, that encodes 4 stick-switches into some telemetry-value and this was read via AUX2. The attiny gets its supply also...

> Do you have something special in mind? Well, something that would be closer to the hardware, and thus allowing us to integrate at lower level, and thus be usable...

> Do you mean also another physical layer, e.g. I2C? But that isn't available at AUX1/2 I think. Well, something similar, where the device would send the values/positions of it's...

@philmoz there are many SPI displays in this format with own graphic memory. It would be awesome, paired with a modern MCU with a bit more internal RAM. That could...

Please note that you could do something like that today with small code changes, which you would have to maintain yourself though. You could for instance modify the `_external_ports` array...

> Or maybe there is better to change that option from "SBUS Trainer" to something like "Inverted SBUS Trainer" It is definitely a good idea to document (at least for...

This sounds cool! I should try it out!