Add BETAFPVG473_V3 #928

liyouluo · 2025-10-17T01:55:03Z

Hi.

The schematic has been reviewed in Discord.

please check the config.

Summary by CodeRabbit

New Features
- Added full support for the BetaFPV G473 V3 flight controller: STM32G4-class MCU support, ICM42688P accel/gyro, BMP280/DPS310 barometer options, onboard flash and video OSD support, beeper, four motor outputs, addressable LED strip, multiple UART/I2C/SPI ports, ADC battery/current sensing, timer/DMA mappings, and sensible defaults for sensors, telemetry, and motor protocols.

coderabbitai · 2025-10-17T01:55:12Z

Walkthrough

Adds a new board configuration header configs/BETAFPVG473_V3/config.h that declares MCU/board identifiers, enables sensors/peripherals, and defines comprehensive GPIO, timer, DMA, SPI, I2C, ADC, and default runtime mappings and constants.

Changes

Cohort / File(s)	Summary
Board & identifiers `configs/BETAFPVG473_V3/config.h`	New board header with `FC_TARGET_MCU(STM32G47X)`, `BOARD_NAME(BETAFPVG473_V3)`, `MANUFACTURER_ID(BEFH)` and top-level feature toggles.
Sensors & feature flags `configs/BETAFPVG473_V3/config.h`	Enables accelerometer/gyro, ICM42688P SPI accel/gyro, flash (`M25P16`), MAX7456 OSD, gyro clock input, barometers (BMP280, DPS310) and related compile-time flags.
Pin mappings & peripherals `configs/BETAFPVG473_V3/config.h`	Declares pins for beeper, motors, LED strip, LEDs, UART1–4 TX/RX, SPI1–3 (SCK/SDI/SDO), I2C1 SCL/SDA, ADC channels (VBAT/CURRENT), flash & MAX7456 CS, gyro CS/EXTI/CLKIN and related CS/EXTI assignments.
Timers, DMA & timer-pin mapping `configs/BETAFPVG473_V3/config.h`	Adds `TIMER_PIN_MAPPING` macro with timer/port/channel-to-pin entries and defines `ADC1_DMA_OPT` / `ADC2_DMA_OPT`.
Instances, alignment & defaults `configs/BETAFPVG473_V3/config.h`	Sets SPI/I2C instances (`MAX7456_SPI_INSTANCE`, `FLASH_SPI_INSTANCE`, `GYRO_1_SPI_INSTANCE`, `BARO_I2C_INSTANCE`, `MAG_I2C_INSTANCE`), gyro alignment, `DEFAULT_ALIGN_BOARD_YAW`, default blackbox/DSHOT/meter sources, `BEEPER_INVERTED`, `SYSTEM_HSE_MHZ`, and conditional UART/serialrx mappings.

Sequence Diagram(s)

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Files/areas to inspect closely:

configs/BETAFPVG473_V3/config.h — verify timer-to-pin channel assignments, CS/EXTI coherence, and that SPI/I2C/UART instances match pin mappings.
Conditional blocks (OSD display UART, SERIALRX) — ensure correct UART selection when options are toggled.
DMA and peripheral instance constants — check for potential conflicts with other board configs.

Possibly related PRs

Add HGLRCF435_AIO board #884 — Adds a new board config header with overlapping peripheral and TIMER_PIN_MAPPING changes.
Add CRAZYBEE473 target #727 — Adds STM32G47X board configuration headers with similar sensor and instance macro definitions.
Fix BETAFPVH725 default config #896 — Modifies gyro clock input, timer pin mapping, and default alignment macros similar to this change.

Suggested reviewers

ot0tot
haslinghuis
nerdCopter

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description is largely incomplete and does not follow the required template structure. The description template specifies mandatory sections including hardware compliance requirements, housekeeping notes, and a detailed checklist covering schematics review, hardware testing, guidelines compliance, connector standards, flight testing, and issue resolution. The actual description is a brief informal message ("Hi. The schematic has been reviewed in Discord. please check the config.") that lacks all required sections, the mandatory checklist items, and proper formatting. While the PR label indicates "Schematics approved," the description itself does not meet the template requirements.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run `@coderabbitai generate docstrings` to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "Add BETAFPVG473_V3" directly corresponds to the primary change in the pull request, which is the addition of a new flight controller configuration file. The raw summary confirms this is a new file at configs/BETAFPVG473_V3/config.h. The title is concise, clear, and specific enough for reviewers scanning the commit history to understand that a new Betaflight target is being added. It avoids vague language and accurately reflects the main objective of the changeset.

✨ Finishing touches

📝 Generate docstrings

🧪 Generate unit tests (beta)

Create PR with unit tests
Post copyable unit tests in a comment

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d9907bf and dd8c5d2.

📒 Files selected for processing (1)

configs/BETAFPVG473_V3/config.h (1 hunks)

🧰 Additional context used

🧠 Learnings (20)

📓 Common learnings

Learnt from: haslinghuis
Repo: betaflight/config PR: 835
File: configs/HDZERO_HALO_MPU6000/config.h:44-56
Timestamp: 2025-07-14T16:16:56.822Z
Learning: For Betaflight board configurations of boards already in production, pin assignments in config.h files reflect the actual hardware design and cannot be changed, even if they present potential conflicts with debug interfaces. The configuration must match the physical board layout, not ideal software design preferences.

Learnt from: ot0tot
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-07-03T04:33:57.480Z
Learning: Always verify that the BOARD_NAME define in each config.h matches the directory name it resides in (e.g., configs/AXISFLYINGF7AIO/config.h must have #define BOARD_NAME AXISFLYINGF7AIO). This check is required for all Betaflight board configuration reviews.

Learnt from: ot0tot
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-07-03T04:33:57.480Z
Learning: Always verify that the `BOARD_NAME` define in config.h files exactly matches the directory name where the config file is located. For example, if the config file is in configs/AXISFLYINGF7AIO/config.h, then the BOARD_NAME should be defined as "AXISFLYINGF7AIO". This ensures proper board identification and configuration loading in Betaflight.

Learnt from: haslinghuis
Repo: betaflight/config PR: 879
File: configs/AIRBOTSUPERF4V2/config.h:42-45
Timestamp: 2025-08-22T17:08:23.283Z
Learning: In Betaflight board configurations, OSD feature flags like USE_OSD_SD (analog/MAX7456) and USE_OSD_HD (digital/MSP DisplayPort) are typically defined at build time by the build system, not in the individual board config.h files. Board configs can conditionally define OSD-related settings based on these build-time flags.

Learnt from: haslinghuis
Repo: betaflight/config PR: 792
File: configs/BEEROTORF4/config.h:30-30
Timestamp: 2025-05-28T15:42:05.402Z
Learning: The DEFAULT_GYRO_ENABLED macro with both gyros enabled (GYRO_MASK(0) | GYRO_MASK(1)) should only be added to board configurations that have DEFAULT_GYRO_TO_USE set to GYRO_CONFIG_USE_GYRO_BOTH. Boards without this setting should only get the GYRO_COUNT definition to specify the number of available gyros.

Learnt from: haslinghuis
Repo: betaflight/config PR: 656
File: configs/IFLIGHT_F745_AIO/config.h:31-35
Timestamp: 2025-07-28T16:44:59.686Z
Learning: In Betaflight board configurations, when a board design uses the same physical gyro socket but different sensor variants across production batches (e.g., MPU6000 in older batches, ICM42688P in newer batches), the correct approach is to enable both sensor drivers (USE_GYRO_SPI_MPU6000 and USE_GYRO_SPI_ICM42688P) in the same configuration. This allows runtime auto-detection of which sensor is actually present without requiring separate board configurations for each hardware variant.

Learnt from: haslinghuis
Repo: betaflight/config PR: 792
File: configs/BEEROTORF4/config.h:30-30
Timestamp: 2025-05-28T15:42:05.402Z
Learning: The DEFAULT_GYRO_ENABLED macro with both gyros enabled (GYRO_MASK(0) | GYRO_MASK(1)) should only be added to board configurations that have DEFAULT_GYRO_TO_USE set to GYRO_CONFIG_USE_GYRO_BOTH. Boards without this setting should only get the GYRO_COUNT definition.

Learnt from: haslinghuis
Repo: betaflight/config PR: 822
File: configs/AXISFLYINGH7MINI/config.h:29-37
Timestamp: 2025-06-23T18:43:31.746Z
Learning: In Betaflight configuration files, feature enablement macros like USE_MAG are build options that can be controlled at compile time, while hardware instance definitions like MAG_I2C_INSTANCE are predefined in board configurations to assist with hardware mapping when those features are enabled at build time.

📚 Learning: 2025-07-14T16:16:56.822Z

Learnt from: haslinghuis
Repo: betaflight/config PR: 835
File: configs/HDZERO_HALO_MPU6000/config.h:44-56
Timestamp: 2025-07-14T16:16:56.822Z
Learning: For Betaflight board configurations of boards already in production, pin assignments in config.h files reflect the actual hardware design and cannot be changed, even if they present potential conflicts with debug interfaces. The configuration must match the physical board layout, not ideal software design preferences.

Applied to files:

configs/BETAFPVG473_V3/config.h

📚 Learning: 2025-07-03T04:33:57.480Z

Learnt from: ot0tot
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-07-03T04:33:57.480Z
Learning: Always verify that the BOARD_NAME define in each config.h matches the directory name it resides in (e.g., configs/AXISFLYINGF7AIO/config.h must have #define BOARD_NAME AXISFLYINGF7AIO). This check is required for all Betaflight board configuration reviews.

Applied to files:

configs/BETAFPVG473_V3/config.h

📚 Learning: 2025-07-03T04:33:57.480Z

Learnt from: ot0tot
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-07-03T04:33:57.480Z
Learning: Always verify that the `BOARD_NAME` define in config.h files exactly matches the directory name where the config file is located. For example, if the config file is in configs/AXISFLYINGF7AIO/config.h, then the BOARD_NAME should be defined as "AXISFLYINGF7AIO". This ensures proper board identification and configuration loading in Betaflight.

Applied to files:

configs/BETAFPVG473_V3/config.h

📚 Learning: 2025-08-22T17:08:23.283Z

Learnt from: haslinghuis
Repo: betaflight/config PR: 879
File: configs/AIRBOTSUPERF4V2/config.h:42-45
Timestamp: 2025-08-22T17:08:23.283Z
Learning: In Betaflight board configurations, OSD feature flags like USE_OSD_SD (analog/MAX7456) and USE_OSD_HD (digital/MSP DisplayPort) are typically defined at build time by the build system, not in the individual board config.h files. Board configs can conditionally define OSD-related settings based on these build-time flags.

Applied to files:

configs/BETAFPVG473_V3/config.h

📚 Learning: 2025-09-26T16:32:46.694Z

Learnt from: osirisinferi
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-09-26T16:32:46.694Z
Learning: When reviewing hardware configuration files like Betaflight configs, always check for pin assignment conflicts by verifying that no physical pins (like PB10, PB11, etc.) are assigned to multiple peripheral functions simultaneously.

Applied to files:

configs/BETAFPVG473_V3/config.h

📚 Learning: 2025-06-23T18:43:31.746Z

Learnt from: haslinghuis
Repo: betaflight/config PR: 822
File: configs/AXISFLYINGH7MINI/config.h:29-37
Timestamp: 2025-06-23T18:43:31.746Z
Learning: In Betaflight configuration files, feature enablement macros like USE_MAG are build options that can be controlled at compile time, while hardware instance definitions like MAG_I2C_INSTANCE are predefined in board configurations to assist with hardware mapping when those features are enabled at build time.

Applied to files:

configs/BETAFPVG473_V3/config.h

📚 Learning: 2025-07-23T13:43:50.456Z

Learnt from: ot0tot
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-07-23T13:43:50.456Z
Learning: For Betaflight board configuration reviews, always verify that serial port defines (like ESC_SENSOR_UART, MSP_UART, GPS_UART, etc.) use valid SERIAL_PORT identifiers that match those defined in the Betaflight codebase at src/main/io/serial.h. Common valid identifiers include SERIAL_PORT_USART1, SERIAL_PORT_USART2, SERIAL_PORT_USART3, SERIAL_PORT_UART4, SERIAL_PORT_UART5, etc. Invalid identifiers like SERIAL_PORT_UART3 (should be SERIAL_PORT_USART3) will cause build failures.

Applied to files:

configs/BETAFPVG473_V3/config.h

📚 Learning: 2025-07-03T15:17:30.040Z

Learnt from: haslinghuis
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-07-03T15:17:30.040Z
Learning: In Betaflight configurations, when a target name suggests dual IMUs (like JHEF7DUAL) but specific hardware variants only have one gyro available, the preferred solution is to use DEFAULT_GYRO_TO_USE macro to specify which gyro to use by default rather than pruning gyro defines or creating redundant configurations. This approach maintains compatibility when the same target is used by multiple hardware variants from the same manufacturer.

Applied to files:

configs/BETAFPVG473_V3/config.h

📚 Learning: 2025-07-23T13:43:50.456Z

Learnt from: ot0tot
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-07-23T13:43:50.456Z
Learning: For Betaflight board configuration reviews, always verify that serial port defines use valid identifiers from the serialPortIdentifier_e enum in src/main/io/serial.h. Valid identifiers include: SERIAL_PORT_USB_VCP (20), SERIAL_PORT_SOFTSERIAL1 (30), SERIAL_PORT_SOFTSERIAL2 (31), SERIAL_PORT_LPUART1 (40), SERIAL_PORT_UART0 (50, if SERIAL_UART_FIRST_INDEX == 0), SERIAL_PORT_USART1 (51 or 50), SERIAL_PORT_USART2, SERIAL_PORT_USART3, SERIAL_PORT_UART4, SERIAL_PORT_UART5, SERIAL_PORT_USART6, SERIAL_PORT_USART7, SERIAL_PORT_USART8, SERIAL_PORT_UART9, SERIAL_PORT_USART10. While some aliases exist (like SERIAL_PORT_UART3 = SERIAL_PORT_USART3), prefer using the primary identifiers as referenced in the serialPortIdentifiers array to avoid build failures.

Applied to files:

configs/BETAFPVG473_V3/config.h

📚 Learning: 2025-08-20T02:54:58.596Z

Learnt from: ot0tot
Repo: betaflight/config PR: 872
File: configs/HGLRCH743/config.h:82-83
Timestamp: 2025-08-20T02:54:58.596Z
Learning: For Betaflight board configuration reviews, the definitive source for validating UART pin assignments is the serial_uart_{platform}.c file in the Betaflight codebase (e.g., serial_uart_stm32h7xx.c for STM32H7xx platforms), not generic MCU datasheets. These files contain the exact pin mappings that Betaflight supports for each UART peripheral.

Applied to files:

configs/BETAFPVG473_V3/config.h

📚 Learning: 2025-06-02T16:16:20.197Z

Learnt from: haslinghuis
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-06-02T16:16:20.197Z
Learning: In STM32F405-based flight controller configurations, timer pin mappings must be carefully analyzed for DMA stream conflicts, especially between motor timers, LED strip timers, and SPI DMA assignments. Changes to TIMER_PIN_MAPPING should include verification that all required peripherals (motors, LED strip, blackbox SPI) can coexist without DMA conflicts.

Applied to files:

configs/BETAFPVG473_V3/config.h

📚 Learning: 2025-07-14T15:41:14.364Z

Learnt from: ot0tot
Repo: betaflight/config PR: 834
File: configs/RADIOLINKF405/config.h:79-88
Timestamp: 2025-07-14T15:41:14.364Z
Learning: In STM32F405 configurations, PB1 typically maps to TIM3_CH4 and PC9 typically maps to TIM8_CH4. These are different timers and do not share DMA resources, so there is no conflict when both pins are used simultaneously (e.g., PB1 for LED_STRIP and PC9 for MOTOR4).

Applied to files:

configs/BETAFPVG473_V3/config.h

📚 Learning: 2025-05-31T17:01:39.423Z

Learnt from: haslinghuis
Repo: betaflight/config PR: 798
File: configs/FURYF4OSD/config.h:88-88
Timestamp: 2025-05-31T17:01:39.423Z
Learning: For STM32F4xx platforms, PB1 pin timer definitions are:
1 = DEF_TIM(TIM1, CH3N, PB1, 0, 0)
2 = DEF_TIM(TIM3, CH4, PB1, 0, 0) 
3 = DEF_TIM(TIM8, CH3N, PB1, 0, 0)
Timer instance 2 (TIM3, CH4) is the correct mapping for PB1 motor control on STM32F4xx platforms as defined in src/platform/STM32/timer_stm32f4xx.c

Applied to files:

configs/BETAFPVG473_V3/config.h

📚 Learning: 2025-08-28T20:45:36.652Z

Learnt from: haslinghuis
Repo: betaflight/config PR: 888
File: configs/ZEX_ATHENA_MINI/config.h:0-0
Timestamp: 2025-08-28T20:45:36.652Z
Learning: In STM32H743 Betaflight configurations, PA15 maps to TIM2_CH1 (timer index 2) as defined in timer_stm32h7xx.c. When used for GYRO_CLKIN functionality, it's recommended to use the macro name GYRO_1_CLKIN_PIN in TIMER_PIN_MAPPING for consistency with other pin definitions.

Applied to files:

configs/BETAFPVG473_V3/config.h

📚 Learning: 2025-08-28T20:45:36.652Z

Learnt from: haslinghuis
Repo: betaflight/config PR: 888
File: configs/ZEX_ATHENA_MINI/config.h:0-0
Timestamp: 2025-08-28T20:45:36.652Z
Learning: In STM32H743 Betaflight configurations, PB0 can use multiple timer options including TIM1_CH2N, TIM3_CH3, and TIM8_CH2N as defined in timer_stm32h7xx.c. For CAMERA_CONTROL_PIN assignments, TIM3_CH3 (timer index 3) is the appropriate choice.

Applied to files:

configs/BETAFPVG473_V3/config.h

📚 Learning: 2025-09-01T19:58:52.049Z

Learnt from: haslinghuis
Repo: betaflight/config PR: 881
File: configs/GEPRC_TAKER_H743MINI/config.h:86-99
Timestamp: 2025-09-01T19:58:52.049Z
Learning: For STM32H743 PB0 in Betaflight, there are three timer options: TIM1_CH2N, TIM3_CH3, and TIM8_CH2N. Only TIM3_CH3 (timer index 2) is suitable for GYRO_CLKIN as the other two are complementary (N) channels. This is confirmed in timer_stm32h7xx.c.

Applied to files:

configs/BETAFPVG473_V3/config.h

📚 Learning: 2025-09-01T19:58:52.049Z

Learnt from: haslinghuis
Repo: betaflight/config PR: 881
File: configs/GEPRC_TAKER_H743MINI/config.h:86-99
Timestamp: 2025-09-01T19:58:52.049Z
Learning: For STM32H743 in Betaflight, PB0 has multiple timer options but only timer index 2 provides a non-complementary output suitable for GYRO_CLKIN functionality. The other timer options for PB0 are N channels (complementary outputs) which are not appropriate for CLKIN usage.

Applied to files:

configs/BETAFPVG473_V3/config.h

📚 Learning: 2025-06-23T18:44:59.162Z

Learnt from: haslinghuis
Repo: betaflight/config PR: 822
File: configs/AXISFLYINGH7MINI/config.h:121-129
Timestamp: 2025-06-23T18:44:59.162Z
Learning: In Betaflight configuration files, USE_OSD_HD and USE_MAX7456 are for different OSD systems: USE_MAX7456 enables the MAX7456 analog OSD chip, while USE_OSD_HD enables HD/digital OSD via MSP. MSP_DISPLAYPORT_UART should be guarded by USE_OSD_HD, not USE_MAX7456, as they serve different OSD implementations.

Applied to files:

configs/BETAFPVG473_V3/config.h

📚 Learning: 2025-05-28T15:45:15.608Z

Learnt from: haslinghuis
Repo: betaflight/config PR: 792
File: configs/MERAKRCF722/config.h:32-32
Timestamp: 2025-05-28T15:45:15.608Z
Learning: The presence of GYRO_2_SPI_INSTANCE definition in a board config does not necessarily mean the board uses dual gyros. Some boards have GYRO_2_SPI_INSTANCE defined but it's not actually used, so they should not receive GYRO_COUNT or other dual-gyro related definitions. Only boards that actually utilize dual gyros should get these definitions.

Applied to files:

configs/BETAFPVG473_V3/config.h

🔇 Additional comments (7)

configs/BETAFPVG473_V3/config.h (7)

24-27: Board identification is correct.

The BOARD_NAME matches the directory name, and MCU target is properly defined.

Based on learnings.

29-39: Feature flags are properly configured.

Standard sensor and peripheral flags for a modern flight controller with ICM42688P gyro/accelerometer, M25P16 flash, and dual barometer support.

41-76: Pin definitions are conflict-free.

All pin assignments are valid with no conflicts. Each physical pin is assigned to only one peripheral function, and SPI pin groupings are logically consistent.

Based on learnings.

77-83: Timer mappings are correctly configured.

The timer pin mappings match the correction provided in previous review comments, with appropriate timer and DMA channel assignments for motors, LED strip, and gyro CLKIN.

85-86: ADC DMA configuration is appropriate.

DMA options for ADC1 and ADC2 are properly specified.

88-97: Serial port configurations are valid.

Serial port identifiers (SERIAL_PORT_UART4, SERIAL_PORT_USART1, SERIAL_PORT_USART3) are all valid. MSP_DISPLAYPORT_UART is correctly guarded by USE_OSD_HD for HD OSD support.

Based on learnings.

99-114: Peripheral instances and defaults are correctly configured.

All SPI instance assignments match their respective CS pins and SPI bus configurations. I2C, ADC, blackbox, and motor protocol defaults are properly set. Gyro alignment and board yaw offset are specified appropriately.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

configs/BETAFPVG473_V3/config.h

Co-authored-by: Mark Haslinghuis <[email protected]>

configs/BETAFPVG473_V3/config.h

Co-authored-by: ot0tot <[email protected]>

haslinghuis · 2025-11-02T22:29:32Z

configs/BETAFPVG473_V3/config.h

 #define BEEPER_INVERTED
 #define SYSTEM_HSE_MHZ 8
+#define PINIO1_BOX          40
+#define PINIO1_CONFIG       1


Suggested change

#define PINIO1_CONFIG 1

#define PINIO1_CONFIG 129

#define BOX_USER1_NAME "VTX PWR"

sugaarK · 2025-11-03T12:29:33Z

@liyouluo can you check the buzzer works ? had a spate of boards where it hasn't been checked and they don't work

Add BETAFPVG473_V3

d14f03f

haslinghuis added the Schematics approved label Oct 17, 2025

haslinghuis assigned liyouluo Oct 17, 2025

haslinghuis requested changes Oct 17, 2025

View reviewed changes

configs/BETAFPVG473_V3/config.h Outdated Show resolved Hide resolved

configs/BETAFPVG473_V3/config.h Outdated Show resolved Hide resolved

Update configs/BETAFPVG473_V3/config.h

9990ff2

Co-authored-by: Mark Haslinghuis <[email protected]>

coderabbitai bot approved these changes Oct 20, 2025

View reviewed changes

Update BETAFPVG473_V3 Timer

8739aab

Co-authored-by: Mark Haslinghuis <[email protected]>

haslinghuis approved these changes Oct 20, 2025

View reviewed changes

ot0tot reviewed Oct 22, 2025

View reviewed changes

configs/BETAFPVG473_V3/config.h Show resolved Hide resolved

Set the SYSTEM_HSE_MHZ of BETAPPVG473_V3 target to 8

d9907bf

Co-authored-by: ot0tot <[email protected]>

haslinghuis requested a review from ot0tot November 2, 2025 01:28

Configure PINIO1 to 9V BEC enable

dd8c5d2

haslinghuis reviewed Nov 2, 2025

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Add BETAFPVG473_V3 #928

Add BETAFPVG473_V3 #928

liyouluo commented Oct 17, 2025 •

edited by coderabbitai bot

Loading

Uh oh!

coderabbitai bot commented Oct 17, 2025 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

Uh oh!

haslinghuis Nov 2, 2025 •

edited

Loading

Uh oh!

sugaarK commented Nov 3, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

	#define PINIO1_CONFIG 1
	#define PINIO1_CONFIG 129
	#define BOX_USER1_NAME "VTX PWR"

Add BETAFPVG473_V3 #928

Are you sure you want to change the base?

Add BETAFPVG473_V3 #928

Conversation

liyouluo commented Oct 17, 2025 • edited by coderabbitai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

coderabbitai bot commented Oct 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Sequence Diagram(s)

Estimated code review effort

Possibly related PRs

Suggested reviewers

Pre-merge checks and finishing touches

Uh oh!

Uh oh!

Uh oh!

Uh oh!

haslinghuis Nov 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

sugaarK commented Nov 3, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

liyouluo commented Oct 17, 2025 •

edited by coderabbitai bot

Loading

coderabbitai bot commented Oct 17, 2025 •

edited

Loading

haslinghuis Nov 2, 2025 •

edited

Loading