The VTX power switch pin is defined with a default OUTPUT level in
hwdef.dat, but was never mirrored into hwdef-bl.dat. Since ChibiOS's own
unconfigured-pin default is INPUT FLOATING, the pin floated for the
entire time each of these boards sat in the bootloader (DFU / SD-card
flashing), even though the main firmware correctly drove it once it
booted. Add the matching line so the VTX power rail has a defined state
throughout.
- AEDROXH7 (PB12 VTX_SW)
- DAKEFPVF405 (PB4 VTX_PWR)
- DAKEFPVH743Pro (PE3 PINIO2)
- FlyFishRCF405 (PC5 PINIO1)
- HWH7 (PE4 VTX_POWER)
- JHEMCUF405WING (PC13 PINIO1)
- LongBowF405WING (PC13 PINIO1)
- OrqaF405Pro (PB9 VTX_SW)
- SIMPLIFLYH7 (PB2 PINIO1)
- SPEDIXH743 (PA2 VTX_SW)
- SpeedyBeeF405WING (PC13 PINIO1)
- speedybeef4v5 (PC13 VTX_PWR)
STM32F405 based board with ICM-42688-P IMU, DPS310 barometer,
MAX7456 OSD, onboard dataflash, 8 PWM outputs, hardware SBUS
inverter on USART2, and USB OTG.
Processing these hwdefs printed "<name> already in defines with same
value". In four of them the board repeats a define it has just taken
from the hwdef it includes:
DAKEFPVH743 DEFAULT_NTF_LED_TYPES from DAKEFPVH743Pro
MatekF765-Wing-bdshot DEFAULT_NTF_LED_TYPES from MatekF765-Wing
SkystarsH7HDv2 AP_MSP_VIDEOTX_ENABLED from SkystarsH7HD-bdshot
TBS_LUCID_H7_WING DEFAULT_NTF_LED_TYPES from TBS_LUCID_H7
and in the other two the same define appears twice in the one file:
sparknavi-blue HAL_WITH_RAMTRON
esp32diy HAL_LOGGING_BACKENDS_DEFAULT
The generated hwdef.h held each of these twice, as an identical
redefinition, and now holds it once; the value reaching the compiler is
unchanged. hw.dat loses the line too, so it and the ROMFS which
embeds it are one line shorter.
Parsed state - defines, intdefines, config, pins and the rest - is
unchanged for all 490 boards.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Three places looped over af_labels asking whether a label named an
alternative function, and none of them used the entry which matched.
str.startswith() takes a tuple of prefixes and does the whole test at
once, so ask it that way instead; two of the three are in
get_alt_function(), which is called for every pin line.
Processing all 443 ChibiOS hwdefs goes from 0.335s to 0.325s. The
parse state of all 490 boards is unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
valid_type() still ran nine uncompiled re.match() calls for every pin
line, cross-checking the peripheral number in a pin's type against the
one in its label. Compile them once as class members.
Processing all 443 ChibiOS hwdefs goes from 0.35s to 0.32s. The parse
state of all 490 boards is unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Every line was split into words three times over: once by
process_file() to see whether it was an include line, once by the
HAL-specific process_line(), and once again by the base
process_line() the HAL-specific one delegates to.
Have process_line() take the words the caller has already split out,
and only split in process_file() for lines which could be an include.
That takes the number of splits done to process all 443 ChibiOS hwdefs
from 140374 to 56389, and the time from 0.40s to 0.35s.
The parse state of all 490 boards, and the hwdef.h, ldscript.ld and
hw.dat generated for a sample of 14 boards and their bootloaders, are
unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
valid_type() rebuilt an 18-entry list of patterns and ran up to 18
uncompiled re.match() calls for every pin line in every hwdef. Compile
the alternation once as a class member instead.
get_mcu_lib() called importlib.import_module() every time, which is
also once per pin line; remember the module we found.
Together these take processing all 443 ChibiOS hwdefs from 0.45s to
0.40s. The parse state of all 490 boards is unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
shlex is a character-at-a-time lexer written in Python, and it
dominated the cost of processing hwdefs: 65% of the time spent parsing
all 443 ChibiOS hwdefs was inside shlex.split().
Almost no hwdef line needs it. A line containing none of shlex's
special characters, whose whitespace is only spaces and tabs, is split
identically by str.split(); 99.1% of the lines the parser sees qualify.
Take that path when it applies and fall back to shlex otherwise.
Processing all 443 ChibiOS hwdefs goes from 1.39s to 0.45s. The parse
state of all 490 boards, and the hwdef.h, ldscript.ld and hw.dat
generated for a sample of 13 boards and their bootloaders, are
unchanged.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
AP_Periph configures the ZED-F9P from its own parameters at every boot, so
the copy saved into the receiver's flash is never the source of truth. Each
save is a UBX-CFG-CFG sent with no deviceMask, which the receiver applies to
BBR and flash: an erase and program of the whole flash configuration layer.
That write lands 5s or more after startup and only while disarmed, which is
exactly when a unit is likely to be unplugged, and the receiver shares the
board supply so there is no orderly shutdown. A power cut mid-save can leave
the configuration layer corrupt.
Defaulting GPS_SAVE_CFG to 0 keeps the receiver configured from RAM on every
boot and removes the write.
The STM32L4+ port's stm32_isr.c unconditionally includes the
stm32_i2c1..4.inc ISR files, which require STM32_I2C_USE_I2Cx to be
defined. In bootloader builds HAL_USE_I2C is FALSE so hal_i2c_lld.h
(which supplies FALSE defaults) is never included, breaking the
PixFlamingo bootloader build.
Add ifndef-guarded FALSE defaults, matching the STM32G4 fix in
abffee1520.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
ALLOW_ARM_NO_COMPASS has not had the stated effect since Nov 2019; remove it from
the template output of the betaflight hwdef conversion script.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
ALLOW_ARM_NO_COMPASS was broken by commit 653fad44d4 in Nov 2019
which changed AP_Arming::compass_checks() to call use_for_yaw(0)
instead of use_for_yaw(void). The void version implicitly called
healthy() which caused compass_checks() to return true (pass) when
no compass was present. After that change, compass_checks() proceeds
to call healthy() directly and fails pre-arm even with this define set.
The define has not had the stated effect for over 5 years.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
boards coming in with stale defines. The defines are several versions old, so I don't think it's really worth adding code to enforce no-more-merging of these bad defines.
minimize_fpv_osd.inc force-enabled AP_MSP_VIDEOTX_ENABLED on the F405
FPV boards, costing ~1.5K of flash for a feature those boards rarely
use. Leave it to the default (off); 2MB boards that want it opt in via
their own hwdef.
These boards default a serial port to MSP DisplayPort or DJI FPV, so they
have the digital VTX hardware that MSP VTX control targets. Enable it
explicitly now that it no longer defaults on for >1MB boards.
Initial hwdef support for the SimpliFly H7 based on STM32H743:
- ICM42688P IMU on SPI, BMP280 barometer on I2C
- AT7456E (MAX7456) OSD on SPI2, W25Q128FV 16MB dataflash
- 5 UARTs, 4 motor outputs on TIM8 (BDshot capable)
- 4 servo outputs on TIM4 (BDshot capable), NeoPixel LED on TIM3
- 9V regulator GPIO control (RELAY2_PIN 81)
- Camera trigger output on CC pad (RELAY3_PIN 82)
- defaults.parm: SERVO9_FUNCTION=120 (NeoPixel), OSD_TYPE2=5 (MSP DisplayPort)
Reject a numeric DEFAULT_SERIALn_PROTOCOL/HAL_SERIALn_PROTOCOL/HAL_OTGn_PROTOCOL
value during hwdef processing, and convert the in-tree boards that used numbers
to the equivalent SerialProtocol_* name (value-preserving).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>