add target SEQUOIARCF405

[chao11223344]

Target details

Adds the SEQUOIARCF405 flight controller target under the existing
SEQU manufacturer ID.

• Board name: SEQUOIARCF405
• Manufacturer: Sequoia RC
• Manufacturer ID: SEQU
• Manufacturer website: http://hsairc.com
• MCU: STM32F405
• External crystal: 8 MHz
• IMU drivers: ICM42688P on SPI1
• Barometer drivers: DPS310 on I2C1
• External compass interface: I2C1
• OSD: MAX7456 on SPI2
• Blackbox: microSD via SPI3
• Motor outputs: 4
• Servo outputs: 2
• UARTs: 6
• Other features: LED strip, buzzer, voltage/current sensing,
  VTX power switching, dual-camera switching, and a user GPIO pad

Configuration notes

• PINIO1 controls VTX power and is named "VTX POWER".
• PINIO2 controls dual-camera switching and is named "CAM SWITCH".
• PINIO3 is a user-configurable output mapped to USER3.
• PID process denominator defaults to 2, providing a 4 kHz PID
  loop with an 8 kHz gyro sample rate.
• DShot bitbanging and burst DMA are disabled by default.
• Blackbox logging defaults to the SD card.
• Current-meter scale is left at the firmware default and should
  be configured for the connected ESC.

Default UART assignments

• UART2: Serial receiver
• UART3: ESC sensor telemetry
• UART5: MSP
• UART6: GPS

Checklist

• passed Betaflight team's schematics review
• passed hardware samples testing
• follows guidelines
• follows connector standards
• flight tested
• comments/issues resolved

Summary by CodeRabbit

• New Features
  • Added support for the SEQUOIARCF405 flight controller, with board-specific sensor and peripheral configuration, connectivity options, and default flight settings. The configuration includes GPS connectivity through USART6 when GPS support is enabled, along with assigned board controls and hardware settings for compatible setups.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: betaflight/config/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: bdb711b4-d079-46f1-8a37-e91d34377145

📥 Commits

Reviewing files that changed from the base of the PR and between 922b467 and f4371a6.

📒 Files selected for processing (1)

• configs/SEQU/SEQUOIARCF405/config.h

Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review.

---

Walkthrough

This change adds a configuration for the SEQUOIARCF405 STM32F405 flight controller. It specifies supported hardware, pin and timer mappings, peripheral instances, defaults, and UART assignments.

Changes

Board Configuration

Layer / File(s)	Summary
Board capabilities and configuration configs/SEQU/SEQUOIARCF405/config.h	Defines supported sensors and peripherals, pin and timer mappings, bus settings, PINIO configuration, flight-controller defaults, and UART assignments. GPS uses USART6 when USE_GPS is enabled.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Feature

Suggested reviewers: haslinghuis, ot0tot

Merge Risk: ⚪ Minimal · up to f4371

This change adds the SEQUOIARCF405 board configuration. The inspected mappings revealed no concrete merge-blocking issue, so no actionable risk remains beyond normal board validation.

Security Architecture Review

Security architecture risk: 🔵 Low · up to f4371

The change is confined to one flight-controller target, with no identified credential or remote-deployment expansion. No security defect was established, but hardware polarity and startup behavior of the controllable outputs remain unverified.

Retained concerns
No architecture-level concerns identified.

Security review details

Security Blast Radius

• inferred — The directly supported exposure is firmware selecting this target and its attached hardware interfaces. The changed configuration contains no credentials, IAM policy, network endpoint, or remote-deployment authority; downstream firmware behavior is outside the available evidence.

Trust Boundaries and Controls

• observed — MSP is assigned to a physical UART. The declaration does not establish protocol authorization, command reachability, or access through connected equipment; those controls require firmware and wiring evidence that was unavailable.

Resilience and Maintainability Implications

• inferred — Static PINIO mappings do not establish safe output levels before initialization or across reset, persisted reconfiguration, and interrupted or repeated boot. Without firmware consumers and electrical evidence, ordering, ownership, and recovery-state guarantees remain unresolved rather than verified unsafe.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the primary change: adding the SEQUOIARCF405 target.
Description check	✅ Passed	The description provides target details, configuration notes, UART assignments, and the required checklist. It also clearly identifies that hardware sample testing and comment resolution remain incomp…
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[ot0tot]

Community supported target, not tested by BF.