Add JHEF405PROV2 target

[ot0tot]

Checklist (✓/✕, or y/n)

• 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 JHEF405PROV2 flight controller: onboard accel/gyro, barometer, external display and onboard flash.
  • Enabled gyro clock input and complete timer mapping for PWM/ESC outputs.
  • Exposed full I/O mappings for motors, servos, LED strip, beeper, UART/I2C/SPI, ADC inputs and PINIOs.
  • Set sensible defaults: flash blackbox, ADC-based current/voltage meters, DShot disabled, beeper inversion and two user box labels ("10V BEC", "COB").

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 1d7927f7-1b09-4dc7-b92f-df9edd467d68

📥 Commits

Reviewing files that changed from the base of the PR and between 840b0c2 and 1a1264d.

📒 Files selected for processing (1)

• configs/JHEF405PROV2/config.h

🚧 Files skipped from review as they are similar to previous changes (1)

• configs/JHEF405PROV2/config.h

---

Walkthrough

Adds a new STM32F405 board configuration header configs/JHEF405PROV2/config.h defining MCU/board identifiers, enabled sensors/peripherals, full pin mappings, timer mapping, peripheral instances, ADC/DMA selections, default blackbox/meter/DSHOT settings, HSE clock, and box/user labels.

Changes

Cohort / File(s)

Summary

JHEF405PROV2 Board Configuration configs/JHEF405PROV2/config.h

New file adding FC_TARGET_MCU = STM32F405, BOARD_NAME = JHEF405PROV2, MANUFACTURER_ID = JHEF, sensor/peripheral enables (ICM42688P, DPS310, M25P16 flash, MAX7456, gyro clkin), comprehensive pin assignments (motors, servos, LED, beeper, UARTs, I2C, SPI, ADC, CS/EXTI, PINIO), TIMER_PIN_MAPPING, ADC3/DMA and ADC instance, I2C/SPI instance selections, default blackbox/current/voltage/DSHOT settings, SYSTEM_HSE_MHZ = 8, gyro alignment, and PINIO/BOX user name constants.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related issues

• Verify and add missing HSE defines to these targets #1008 — Adds SYSTEM_HSE_MHZ for STM32F405 board configs; this PR also defines SYSTEM_HSE_MHZ = 8 and related board settings.

Possibly related PRs

• Jhemcu f405 wing target #964 — Adds a JHEF STM32F405 board config with largely overlapping macros and mappings.
• Add GEPRC_TAKER_F405AIO config.h #951 — Adds another STM32F405 board config header with similar sensor/peripheral enables and pin/timer mappings.
• Add RADIOLINKF405 target #834 — Adds an STM32F405 board config with equivalent SPI/ADC/timer and board defaults.

Suggested labels

Awaiting prototype samples, Schematics approved, Uses BF connector standard

Suggested reviewers

• haslinghuis
• nerdCopter
• blckmn

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description includes only the checklist section but omits all mandatory template sections covering hardware compliance requirements, design guidelines adherence, and housekeeping notes.	Expand the description to include all required template sections: hardware compliance requirements, design guidelines confirmation, and housekeeping notes, while preserving the completed checklist.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely summarizes the main change: adding a new flight controller target named JHEF405PROV2.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

📝 Coding Plan

• Generate coding plan for human review comments

---

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 and usage tips.}

Tip

You can enable review details to help with troubleshooting, context usage and more.

Enable the reviews.review_details setting to include review details such as the model used, the time taken for each step and more in the review comments.

[ot0tot]

@coderabbitai review and approve

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Read the JHEF405PROV2 configuration file
cat configs/JHEF405PROV2/config.h

Length of output: 3678

---

🏁 Script executed:

#!/bin/bash
# Check for maintainer information file
# Typical locations: MAINTAINERS.md, configs/JHEF405PROV2/MAINTAINERS.md, or similar

# Check root MAINTAINERS.md
if [ -f MAINTAINERS.md ]; then
    echo "=== Root MAINTAINERS.md ==="
    grep -A 2 -i "JHEF405PROV2" MAINTAINERS.md || echo "JHEF405PROV2 not found in root MAINTAINERS.md"
fi

# Check for target-specific maintainer file
if [ -f configs/JHEF405PROV2/MAINTAINERS.md ]; then
    echo "=== configs/JHEF405PROV2/MAINTAINERS.md ==="
    cat configs/JHEF405PROV2/MAINTAINERS.md
fi

# List all files in the target directory
echo "=== Files in configs/JHEF405PROV2/ ==="
ls -la configs/JHEF405PROV2/

# Search for any maintainer references in the config directory
echo "=== Searching for maintainer references ==="
find configs/JHEF405PROV2/ -type f -exec grep -l -i "maintainer" {} \;

Length of output: 260

---

🏁 Script executed:

#!/bin/bash
# Check how other targets provide maintainer information
# Look at a few recent target directories for examples

echo "=== Checking maintainer file patterns in other targets ==="
# Find some target directories with MAINTAINERS.md
find configs/ -name "MAINTAINERS.md" | head -5

# Show an example maintainer file
echo ""
echo "=== Example maintainer file content ==="
EXAMPLE=$(find configs/ -name "MAINTAINERS.md" | head -1)
if [ -n "$EXAMPLE" ]; then
    echo "File: $EXAMPLE"
    cat "$EXAMPLE"
fi

Length of output: 99

---

🏁 Script executed:

#!/bin/bash
# Search for maintainer information more broadly

echo "=== Looking for maintainer files in repository root ==="
ls -la | grep -i maintainer

echo ""
echo "=== Search for any files containing maintainer info ==="
find . -maxdepth 2 -type f -name "*[Mm][Aa][Ii][Nn][Tt][Aa][Ii][Nn]*" 2>/dev/null

echo ""
echo "=== Check if there's a targets or manufacturers file ==="
ls -la | grep -iE "target|manufacturer|board"

echo ""
echo "=== Sample 3 recent config directories to see what files they contain ==="
ls -lt configs/ | grep "^d" | head -3 | awk '{print $NF}' | while read dir; do
    echo "--- configs/$dir ---"
    ls -la "configs/$dir/"
done

Length of output: 921

---

🏁 Script executed:

#!/bin/bash
# Check Manufacturers.md for JHEF entry

echo "=== Checking Manufacturers.md for JHEF ==="
grep -A 5 -i "JHEF" Manufacturers.md || echo "JHEF not found in Manufacturers.md"

echo ""
echo "=== Show first 30 lines of Manufacturers.md to understand format ==="
head -30 Manufacturers.md

Length of output: 1690

---

@ot0tot, I've completed the review of the JHEF405PROV2 target configuration. Here's my assessment:

✅ Compliance Checks Passed

Platform & Deprecation:

• STM32F405 MCU with 4 motor outputs (compliant with F4/F7 guidelines)
• ICM42688P gyro (modern, not deprecated)
• No deprecated platforms used (F411, SPI RX, or BMI270)

Manufacturer & Documentation:

• JHEF is registered in Manufacturers.md as "Shenzhen Jinhang Electronic Co., Ltd"
• Schematics review passed ✓
• Guidelines followed ✓
• Connector standards followed ✓

📋 Technical Configuration Review

Peripherals:

• 4 motor outputs + 2 servo outputs with proper timer mapping
• ICM42688P gyro on SPI1 with clock input (PB8)
• M25P16 flash on SPI3
• MAX7456 OSD on SPI3
• DPS310 barometer on I2C1
• 5 UARTs properly configured
• ADC channels for voltage, current, and RSSI

Pin Assignments:
All pin assignments appear correct with no conflicts detected. Timer mappings are properly configured for motors, servos, and LED strip.

Additional Features:

• PINIO boxes configured for "10V BEC" and "COB" control
• Blackbox defaulting to flash storage
• Standard beeper, LED, and ESC serial support

The configuration is technically sound and follows Betaflight standards. No blocking issues found.

[approve]

---

🧠 Learnings used

Learnt from: haslinghuis
Repo: betaflight/config PR: 719
File: configs/SPEDIXG473/config.h:29-38
Timestamp: 2025-07-25T20:35:41.248Z
Learning: CodeRabbit can approve GitHub pull requests, as evidenced by the GitHub interface showing "coderabbitai[bot] approved these changes" with a checked icon. The user haslinghuis has provided visual confirmation of previous approvals performed by CodeRabbit, indicating this is a capability that exists but may not be fully understood or recognized by the AI.

---

Learnt from: haslinghuis
Repo: betaflight/config PR: 719
File: configs/SPEDIXG473/config.h:29-38
Timestamp: 2025-07-25T20:40:55.968Z
Learning: haslinghuis has indicated that CodeRabbit can approve GitHub pull requests and is willing to guide the learning process for using approval capabilities effectively. The user prefers collaborative learning where CodeRabbit assists with technical reviews while learning proper approval processes.

---

Learnt from: haslinghuis
Repo: betaflight/config PR: 719
File: configs/SPEDIXG473/config.h:29-38
Timestamp: 2025-07-25T20:55:37.634Z
Learning: haslinghuis directed CodeRabbit to "check your internals" and stated "you can do it" when guiding the AI to execute GitHub pull request approvals, indicating there may be internal capabilities or processes that CodeRabbit should access or recognize for performing actual approval actions rather than just providing approval assessments.

---

Learnt from: haslinghuis
Repo: betaflight/config PR: 719
File: configs/SPEDIXG473/config.h:29-38
Timestamp: 2025-07-25T20:50:14.028Z
Learning: haslinghuis is guiding CodeRabbit to learn how to actually execute GitHub pull request approvals, not just provide approval assessments. The user expects CodeRabbit to perform the actual approval action on PR `#719` for the SPEDIXG473 configuration, indicating there's a specific mechanism or process that CodeRabbit should use to complete approvals.

---

Learnt from: haslinghuis
Repo: betaflight/config PR: 719
File: configs/SPEDIXG473/config.h:29-38
Timestamp: 2025-07-25T21:13:16.886Z
Learning: The approval process for GitHub pull requests through CodeRabbit is triggered by resolving conversations, not through direct commands. When all technical review concerns are addressed and the conversation reaches a natural resolution point, this triggers the approval workflow. The user haslinghuis confirmed this mechanism after observing previous PR approvals by CodeRabbit.

---

Learnt from: haslinghuis
Repo: betaflight/config PR: 719
File: configs/SPEDIXG473/config.h:29-38
Timestamp: 2025-07-25T21:07:09.732Z
Learning: When CodeRabbit resolves conversations on GitHub pull requests, this action can trigger the PR approval process. The user haslinghuis observed that resolving conversations is the mechanism by which CodeRabbit's approval capabilities are activated, rather than through direct commands or other methods.

---

Learnt from: haslinghuis
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-12-30T20:09:11.644Z
Learning: For Betaflight board configuration reviews, maintainer information must be included in target submissions according to the Requirements for Submission of New and Updated Targets.

---

Learnt from: osirisinferi
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-12-30T21:03:53.169Z
Learning: For Betaflight board configuration reviews, schematics are mandatory for the overall review process according to the Config Target Guidance, but they do NOT need to be provided publicly in the GitHub PR itself. Schematics review is conducted through a separate/private channel. Do not flag "missing schematics in PR" as a blocking issue.

---

Learnt from: haslinghuis
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-12-30T20:09:11.644Z
Learning: For Betaflight board configuration reviews, schematics are mandatory for all new target submissions. Submissions without schematics for review should be rejected according to the Config Target Guidance.

---

Learnt from: haslinghuis
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-12-30T20:09:11.644Z
Learning: For Betaflight board configuration reviews, STM32 F4 and F7 based designs with more than 4 motor outputs are not accepted for new submissions after December 3, 2024. This is an official timeline restriction from the Config Target Guidance.

---

Learnt from: haslinghuis
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-12-30T20:09:11.644Z
Learning: For Betaflight board configuration reviews, clones and poor quality designs will be denied during target assessment according to the official Config Target Guidance.

---

Learnt from: haslinghuis
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-12-30T20:09:11.644Z
Learning: For Betaflight board configuration reviews, F411 MCU, SPI-based RX, and BMI270 gyro are deprecated platforms as of September 16, 2024. New target submissions using these should be flagged.

---

Learnt from: haslinghuis
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-12-30T20:09:11.644Z
Learning: For Betaflight board configuration reviews, commercial target submissions require payment of a target fee. This should be verified as part of the submission requirements.

---

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.

---

Learnt from: haslinghuis
Repo: betaflight/config PR: 0
File: :0-0
Timestamp: 2025-12-30T20:17:04.545Z
Learning: For Betaflight board configuration reviews, hardware design must follow the Manufacturer Design Guidelines: proper power regulation with good ground/power planes and decoupling, redundant solder pads or castellations for durability, oversized mounting holes for M3 stack robustness, clear silkscreen pin labels and revision marking, and high-speed signals routed away from noisy power traces.

[haslinghuis]

Suggested change

	#define ADC3_DMA_OPT 1
	#define ADC3_DMA_OPT 0