OpenDeviceDB: discovering INAV support by flight-controller model

[smichea]

Hi everyone,

I'm Sebastien, the creator of OpenDeviceDB, an independent open-source catalogue connecting device models to firmware, drivers and tools.

I'd like someone looking up their flight controller to find the relevant INAV documentation, with the exact board variant, firmware target, release and Configurator requirements preserved. A target present in a development branch is not necessarily an officially released build.

For example, the MATEKF405TE target definitions include separate MATEKF405TE and MATEKF405TE_SD targets. The README's F411 notice also makes release limits important. Neither a shared MCU nor a similarly named board would justify a compatibility claim.

Would this kind of discovery entry be useful? Is there a preferred maintained source mapping retail board models/revisions to targets? I would handle the downstream catalogue work and link back to the official docs. No INAV importer, new record or flight-controller test has been implemented by this proposal.

Thanks,
Sebastien

Prepared with AI assistance.

[sensei-hacker]

Hello Sebastien. You may or may not have seen the full list of supported targets available in the latest release here:

https://github.com/iNavFlight/inav/wiki/Boards,-Targets-and-PWM-allocations

There's not really a cross reference to retail branding outside of the target names that I can think of.

[smichea]

Thanks for the pointer, this is a useful starting point! The lack of a retail cross-reference is helpful context.

I'll retain the page's source branch/date and official-release caveats when referencing it. For retail mappings, I'll use explicit board documentation to confirm the model and revision. No INAV importer or hardware validation has been added yet.

Prepared with AI assistance.