Raphael Coeffic
Raphael Coeffic
@netmute Could you please rebase this PR on top of current `main`? As we're transitioning to defining keys in targets by means of a JSON hardware definition file, this PR...
@pfeerick I do have a X9-lite, so I should be able to test things as well. @r41065 I'd need a picture of the inputs, and pinout if you have.
Just looked up the datasheet (see [here](https://www.st.com/resource/en/datasheet/stm32f207vg.pdf)) | Pin | Alternate function | RC function | |-------|-------------|-----------| |`PD14`|`TIM4_CH3`| Switch `SG` | |`PC2`|`ADC123_IN12`| Slider `LS` | |`PC3`|`ADC123_IN13`| Slider `RS` |
@r41065 as it seems, `PC2` & `PC3` can be used as analog inputs, while `PD14` could be used as an additional `2-pos` switch.
@r41065 right, I think we could easily do it now. Anyone who would be able to test?
> Possibly... but if you don't drop the profiles, you can't drop simulator library builds, without getting numerous runtime errors because the hwdef files aren't present for those targets. Thus...
> However I do not agree with retaining Companion support for unsupported firmware. I'm with you, no problem! That means you cannot convert from a radio that is not supported...
> With no hwdef then no board thus Companion will parse the yaml and report unsupported radio and go no further. #6437 adds the JSON hardware definitions directly in the...
@pfeerick is it still a thing?
> Will it increase memory demand? Something is ringing in my head that 5.3 has 32bit numbers so it takes more mem. The current LUA version we are using only...