Chibios for wideband on stm32f103 - #19
Merged
Merged
Conversation
|
@dron0gus the gd32f103 reference is confusing. is this just a stm32f103 issue with gd32f103 behaving exactly same as stm32f103 or do we observe any differences between stm32f103 and gd32f103 here? we need to bring this up/create ticket with ChibiOS to get their take on the problem |
dron0gus
force-pushed
the
chibios-for-wideband
branch
from
March 21, 2022 19:03
17ebdae to
a318ff4
Compare
Member
Author
|
Description fixed. |
dron0gus
force-pushed
the
chibios-for-wideband
branch
from
March 21, 2022 19:36
a318ff4 to
f7d1374
Compare
dron0gus
pushed a commit
to dron0gus/ChibiOS
that referenced
this pull request
Sep 4, 2026
rusefi#32) 🤖 This PR was prepared by the ChibiOS sheriff (assistant-operated account) on the maintainer's direction. It is for **human review and merge** — the sheriff does not review, approve or merge its own PRs. Backport of the post-21.11.5 HAL ecosystem work from `main` onto the `stable-21.11.x` LTS, targeting **21.11.6**. XHAL (the OOP HAL) is intentionally out of scope; only the `os/hal` halves of the shared fixes are applied. 1. **STM32 HAL: assorted port fixes** — RTC EXTI-clear sysHalt on H5 (rusefi#15) and U0 (rusefi#16); STM32U3 RTC APB-clock boot-hang + bogus RTC EXTI removal (rusefi#31, U3 only — U5 has no RTC-EXTI framework on 21.11.x); L4+/L4R `CLK_POINT_NAMES` comma (rusefi#21); STM32C0xx SPI2 RCC/DMAMUX (rusefi#12); ADCv6/v7 `ADC2_IRQ_HOOK` (rusefi#11); SYSTICKv1 `STM32_ST_FREQUENCY_TOLERANCE` (rusefi#17). 2. **FTL templates + mcuconf regen** — `tools/ftl` bumped to the chibios-ftl `stable-21.11.x` line (3 mcuconf template fixes); all 244 templated mcuconf.h regenerated. Net: 496 insertions / 0 deletions — tolerance on every config (0; 0.5% on U0/U3), F303 I2S section, C071 SPI2 (rusefi#17/rusefi#18/rusefi#19). 3. **OOP: oop_random_stream** base class (regenerated; required by VFS). 4. **tools/style: stylecheck.py** Python checker + wrappers + rusefi#28 FP fixes (Perl checker left in place). 5. **VFS: current generation + ROMFS driver** — file nodes expose a random-access stream; new read-only ROMFS driver (default off); pulls in `os/common/utils/packbits`. Codegen is idempotent on this branch (regen reproduces these files byte-for-byte). 6. **style:** deterministic whitespace/comment cleanups (HAL/common/various/lib, rusefi#20/rusefi#27/rusefi#29/rusefi#30), no functional change. - **No new HAL ports introduced** — only ports already present in 21.11.5 are touched; the main-only `*_TEST` port dirs are excluded. - `os/vfs/various/syscalls.c` is **left as-is**; main's newlib_bindings reorg is out of scope for the backport. - The cosmetic style pass is **partial** where 21.11.x sources have diverged from main (51 files applied, 7 diverged/absent skipped). - Compile-surface checked against the 21.11.x kernel-7 OSAL (no kernel-8 API). Per maintainer, hardware/build verification is done on `main`. - Submodule `tools/ftl` points at chibios-ftl `stable-21.11.x` @ 170e75b. --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
rusefillc
pushed a commit
that referenced
this pull request
Sep 21, 2026
#32) 🤖 This PR was prepared by the ChibiOS sheriff (assistant-operated account) on the maintainer's direction. It is for **human review and merge** — the sheriff does not review, approve or merge its own PRs. Backport of the post-21.11.5 HAL ecosystem work from `main` onto the `stable-21.11.x` LTS, targeting **21.11.6**. XHAL (the OOP HAL) is intentionally out of scope; only the `os/hal` halves of the shared fixes are applied. 1. **STM32 HAL: assorted port fixes** — RTC EXTI-clear sysHalt on H5 (#15) and U0 (#16); STM32U3 RTC APB-clock boot-hang + bogus RTC EXTI removal (#31, U3 only — U5 has no RTC-EXTI framework on 21.11.x); L4+/L4R `CLK_POINT_NAMES` comma (#21); STM32C0xx SPI2 RCC/DMAMUX (#12); ADCv6/v7 `ADC2_IRQ_HOOK` (#11); SYSTICKv1 `STM32_ST_FREQUENCY_TOLERANCE` (#17). 2. **FTL templates + mcuconf regen** — `tools/ftl` bumped to the chibios-ftl `stable-21.11.x` line (3 mcuconf template fixes); all 244 templated mcuconf.h regenerated. Net: 496 insertions / 0 deletions — tolerance on every config (0; 0.5% on U0/U3), F303 I2S section, C071 SPI2 (#17/#18/#19). 3. **OOP: oop_random_stream** base class (regenerated; required by VFS). 4. **tools/style: stylecheck.py** Python checker + wrappers + #28 FP fixes (Perl checker left in place). 5. **VFS: current generation + ROMFS driver** — file nodes expose a random-access stream; new read-only ROMFS driver (default off); pulls in `os/common/utils/packbits`. Codegen is idempotent on this branch (regen reproduces these files byte-for-byte). 6. **style:** deterministic whitespace/comment cleanups (HAL/common/various/lib, #20/#27/#29/#30), no functional change. - **No new HAL ports introduced** — only ports already present in 21.11.5 are touched; the main-only `*_TEST` port dirs are excluded. - `os/vfs/various/syscalls.c` is **left as-is**; main's newlib_bindings reorg is out of scope for the backport. - The cosmetic style pass is **partial** where 21.11.x sources have diverged from main (51 files applied, 7 diverged/absent skipped). - Compile-surface checked against the 21.11.x kernel-7 OSAL (no kernel-8 API). Per maintainer, hardware/build verification is done on `main`. - Submodule `tools/ftl` points at chibios-ftl `stable-21.11.x` @ 170e75b. --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This fixes overrun issue when using ADC on high sample rates.