add a new target BLADE_F4#9904
Conversation
|
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: 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. |
|
Can you message me or talk on the Discord so we know who you are? I'm Sensei on the Discord as well. |
|
Yes, I am |
I sent you a message on Discord, please check it. |
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>
add a new target BLADE_F4