Release/9.1 to master#11728
Conversation
Add giantec nor flash id
ANYFC, ANYFCM7, FF_FORTINIF4, FLYCOLORF4, FLYWOOF7DUAL, FOXEERF405, FOXEERF722DUAL, and FOXEERF722V4 had no DEFAULT_FEATURES macro at all, which falls back to 0 (every optional feature off) per fc/config.c's #ifndef default. This reads like a hardware/wiring bug (VBAT, current meter, OSD, telemetry silently disabled) rather than a missing config default -- same bug class already fixed on AXISFLYINGH743PRO. Feature sets were chosen per-target based on actual hardware present (OSD chip, ADC channels, flash chip), matching the codebase-wide modal DEFAULT_FEATURES convention. FF_FORTINIF4 and ANYFCM7 deliberately omit features their hardware doesn't unconditionally support: FF_FORTINIF4 shares one SPI3 CS pin between its OSD chip and flash chip across two mutually-exclusive hardware revisions, and ANYFCM7 has no current-sense ADC channel wired at all.
taskSystem() used the sample-based load estimator's UNUSED(currentTimeUs) placement even though SITL_BUILD now uses the parameter, and lacked any note on why SITL needs a different calculation than hardware targets.
…pins-100-percent Fix SITL system load metric permanently pinned at 100%, blocking arming
…sing-8-targets Add DEFAULT_FEATURES to 8 targets with no default feature set
Update flash_w25n.c
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
Branch Targeting SuggestionYou've targeted the
If This is an automated suggestion to help route contributions to the appropriate branch. |
|
Test firmware build ready — commit Download firmware for PR #11728 243 targets built. Find your board's
|
3 participants
No description provided.