- VRef and Temperature sensor calibration constants defined in "stm32h7xx_ll_adc.h" are now included via “stm32h7xx_hal_adc.h”.
- Boostmode is now handled by HAL_ADC_Init using clock configuration parameters to cope with Rev.V.
- Channel specifier (ADC_CHANNEL_x) was a simple integer with V1.3.0, is now an bit field encoded value.
adcTagMap had this value, but adcChannel field in adcOperationConfig was not big enough to store it.
The adcChannel field is modified to hold 32-bit value.
- Rank for channel configuration was a integer, now a bit field encoded value (ADC_RANK_x).
adcRegularRankMap array was added to translate rank number to rank value.
- Other Rev.V changes also seem to be handled within HAL.
Fix compilation when USE_DMA and USE_DMA_SPEC are not defined.
Cleanup calling code of `isMotorProtocolDshot`.
Fix 'unused' warning when USE_PWM_OUTPUT is not defined.
Undo isMotoroProtocolDshot change.
Disable USE_SERIAL_4WAY_BLHELI_INTERFACE when USE_PWM_OUTPUT is not
enabled.
Style cleanup.
BMP388 - Move the static assert.
BMP388 - Build faster when the baro driver is not enabled.
BMP388 - Fix spi init due to changes in master.
BMP388 - Add missing bmp388 unit test files.
BMP388 - Remove debug code.
BMP388 - Prepare EXTI/EOC handling for unified targets.
BMP388 - enable on unified targets.
BMP388 - Add support to NUCLEOF722.
BMP388 - Add support to NUCLEOH743.
BMP388 - Add BMP388 (via SPI) support to NUCLEOF7
* For some CI visibility on the conditional baro SPI code.
NUCLEOH743 - Add LPS baro for more CI visibility.
Remove whitespace, as requested.
Move barometer `#defines` into the implementations.
Cleanup style of method names in baro drivers.
Abs control accidentally was defaulted up from 0 to 5 in #7907. It is still experimental and still can cause oscillations even with these changes. Should be off by default until fully tested.
Protection against previous Configurator versions allowing higher cutoff values than the parameter limits in the firmware and causing out-of-range corrupted config errors.
* HAL_Delay() was being used before HAL_Init() was called.
* Brings it in-line with ST examples which follow this call order:
CubeMX generated code goes startup_xxx.s (asm) -> SystemInit(), then
main(), HAL_Init(), SystemClock_Config()
Boot-tested on:
* SPRacingF4NEO
* SPRacingF7DUAL
* SPRacingH7ZERO
