Thomas Watson
Thomas Watson
Which Asahi installer did you use and when? That is the same machine I have and tested that installer with.
> > Which Asahi installer did you use and when? That is the same machine I have and tested that installer with. > > release-2025-11-18 yesterday To clarify I mean...
I would still like to work with you on PARAM_SET expansion and ideas (item 2).
from pymavlink PR 1143: julian oes " I want to do param v3, but ArduPilot doesn't want it, from what I hear."
Do you remember the justification for the Methodic Configurator recommending 800Hz? AFAIK it's still marked as experimental.
Those tests are just flaky, you can ignore them. Do you have a cite from ST on these numbers?
That document says But [this](https://www.st.com/resource/en/errata_sheet/es0206-stm32f427437-and-stm32f429439-device-errata-stmicroelectronics.pdf) document (for F427/F437) says So we must need to expand the table to also have the CPU ID. That explains the discrepancies in the ID...
> > Does this really cause something to get stuck? Where? > > In `support.cpp:276`, `get_mcu_desc()` traverses through `silicon_revs` that does not contain valid `revid`. As a result returns some...
#31138 should fix the need for the extra set, but there is some more cleanup to do. Are you interested in further work on this?
If you rebase this PR on top of master now that PR will be included. The changes in my mind: * The variables are already set up in https://github.com/ArduPilot/ardupilot/blob/1e8180d2d257983c94fd5f2d68dad465821a02d5/libraries/AP_Scheduler/AP_Scheduler.cpp#L116 so...