Torsten Kurbad

Oh, and I like the idea of being able to configure the slave through the master by I2C. :-) Of course, the general/initial parameters can be set up in advance,...

Thanks @keirf. I'll try and code it in my private fork first and send a PR when I deem it ready for inclusion. As mentioned, I've got a setup that's...

One (hopefully) last thing before I start coding: I've had a look at the pinout and found that if I want to activate I2C2 for master-to-slave communication, I need B10...

I misunderstood the purpose of A15. Thought it was an input to enable/disable the OSD, not the display... What other 5V tolerant spare pin do you see? I don't want...

Hmm, A12 seems a good candidate...

@keirf Just a request for comments: https://gist.github.com/tkurbad/1bdedc8757e1fb1730230057b1ea061a holds a patch that implements the video switch functionality as described. There's also a start of master-slave communication, namely a op(eration)_mode, configurable as...

On a side note, I just realized two things: The I2C communication to the slave blue pill is just a very simplified version of what FF does towards FF_OSD. This...

Thanks for the comment. I'm d'accord with this stuff living in a branch. Besides the relocation of U2, driving I2C2 makes the code a bit convoluted and adds unnecessary complexity...

> Mode switches have so far required a full Blue Pill reset, so doing the switches without reset is sure to require some reinitialization which has not so far been...

I investigated further: When manually (i.e. by external jumper/switch) switching to RTG mode and back, nothing bad happens. The OSD runs on and on unimpressed. The issue only surfaces if...