Skip to content

add a new target BLADE_F4#9904

Open
hakrc1 wants to merge 3 commits intoiNavFlight:maintenance-9.xfrom
hakrc1:hakrc1
Open

add a new target BLADE_F4#9904
hakrc1 wants to merge 3 commits intoiNavFlight:maintenance-9.xfrom
hakrc1:hakrc1

Conversation

@hakrc1
Copy link
Contributor

@hakrc1 hakrc1 commented Apr 7, 2024

add a new target BLADE_F4

@mmosca mmosca added the New target This PR adds a new target label Apr 17, 2024
@mmosca
Copy link
Collaborator

mmosca commented Apr 17, 2024

Hi @hakrc1, good to see you want to submit a target.

Are you in contact with one of the developers already?

According to the hardware policy, we need at least 2 members of the dev team to receive samples for validation, before we can merge this as an official target.

Here is the link for the policy, in case you would like to have a look:
https://github.com/iNavFlight/inav/blob/master/docs/policies/NEW_HARDWARE_POLICY.md

If you are not in touch with any devs, let me know and I can try to organize get you in touch with the right people.

@HAKRC
Copy link

HAKRC commented Jan 10, 2025

Hi @hakrc1, good to see you want to submit a target.您好,很高兴看到您要提交目标。

Are you in contact with one of the developers already?您是否已经与其中一位开发人员取得了联系?

According to the hardware policy, we need at least 2 members of the dev team to receive samples for validation, before we can merge this as an official target.根据硬件策略,我们至少需要 2 名开发团队成员接收样本进行验证,然后才能将其合并为正式目标。

Here is the link for the policy, in case you would like to have a look:以下是该政策的链接,如果您想查看: https://github.com/iNavFlight/inav/blob/master/docs/policies/NEW_HARDWARE_POLICY.md

If you are not in touch with any devs, let me know and I can try to organize get you in touch with the right people.如果您没有与任何开发人员取得联系,请告诉我,我可以尝试安排您与合适的人取得联系。

Hello, the previous software engineer resigned, so no one took over this new target submitted in April 2024, I haven't been in touch with the developers on your side for the time being, can you help arrange for the relevant developers to contact me, I entered your INAV discord community.

@sensei-hacker
Copy link
Member

Can you message me or talk on the Discord so we know who you are? I'm Sensei on the Discord as well.

@HAKRC8899
Copy link
Contributor

Can you message me or talk on the Discord so we know who you are? I'm Sensei on the Discord as well.你能给我发消息或在 Discord 上聊天,以便我们知道你是谁吗?我也是 Discord 的老师。
Hello, I am the new engineer at HAKRC, currently taking over the work of uploading the BLADE_F4 firmware. May I ask if you are one of the developers related to INAV?

@sensei-hacker
Copy link
Member

Can you message me or talk on the Discord so we know who you are? I'm Sensei on the Discord as wel

Hello, I am the new engineer at HAKRC, currently taking over the work of uploading the BLADE_F4 firmware. May I ask if you are one of the developers related to INAV?

Yes, I am

@HAKRC8899
Copy link
Contributor

Can you message me or talk on the Discord so we know who you are? I'm Sensei on the Discord as wel

Hello, I am the new engineer at HAKRC, currently taking over the work of uploading the BLADE_F4 firmware. May I ask if you are one of the developers related to INAV?

Yes, I am

Can you message me or talk on the Discord so we know who you are? I'm Sensei on the Discord as wel

Hello, I am the new engineer at HAKRC, currently taking over the work of uploading the BLADE_F4 firmware. May I ask if you are one of the developers related to INAV?

Yes, I am

I sent you a message on Discord, please check it.

@sensei-hacker sensei-hacker changed the base branch from master to maintenance-9.x February 24, 2026 13:54
@sensei-hacker sensei-hacker added this to the 9.1 milestone Feb 24, 2026
sensei-hacker added a commit to sensei-hacker/inav_unofficial_targets that referenced this pull request Mar 4, 2026
Ported from PR iNavFlight#9904 (hakrc1) with the following corrections applied:

- Fix IMU2 SPI bus: MPU6000/ICM42605/BMI270 _BUS_2 macros were BUS_SPI1,
  corrected to BUS_SPI4 (IMU2 is physically wired to SPI4 on PE11-PE14)
- Assign unique TARGET_BOARD_IDENTIFIER: "BLF4" and "BLPH" (both were "RUSH")
- Fix MAX_PWM_OUTPUT_PORTS: 15 -> 12 to match actual timerHardware[] entries
- Fix timerHardware[] comments to match actual pin order; remove dead
  commented-out duplicate timer block
- Remove FEATURE_SOFTSERIAL from BLADE_F4 DEFAULT_FEATURES (no softserial
  port defined)
- Remove unused USE_SPI_DEVICE_3 and pin definitions from BLADE_F4 (dead code)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@sensei-hacker
Copy link
Member

If someone can merge these fixes: hakrc1#1 then we can get these targets added. If someone can please press the merge button on hakrc1#1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

New target This PR adds a new target

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants