Add CCRCF435FC

[ASDosjani]

20x20 ICM42688 gyro FC with AT32F435 MCU, analog osd, 5/10V 3A BEC, 16MB blackbox, DPS310 baro.

[haslinghuis]

Another board sharing SPI :(

[ASDosjani]

Another board sharing SPI :(

Unfortunatelly there are not enough pins on the 48 pin package...

[ASDosjani]

Should I change something on the target?

[sugaarK]

Another board sharing SPI :(

Unfortunatelly there are not enough pins on the 48 pin package...

plenty of room on the board for a more suitable version of the at chipset after 1 July we won't accept new designs that share resources

[nerdCopter]

@ASDosjani , please recommend CCRC pay close attention to design spec recommendations on the .com as they may change frequently.
https://betaflight.com/docs/development/manufacturer/requirements-for-submission-of-targets https://betaflight.com/docs/development/manufacturer/manufacturer-design-guidelines#32-resource-selection-considerations will be changing very shorty. see https://github.com/betaflight/betaflight.com/pull/434

if this FC is already in production, please tell the BF team so that a merge decision can be made.

[ASDosjani]

@sugaarK @nerdCopter @haslinghuis will this target be merged?

[sugaarK]

not sure we should frankly.. other companies are complying with the new rules.. we don't need more sub par hardware in the market.. I see a lot of these companies trying to grab some of the $$$ going to the Ukraine conflict and frankly thats not our problem.. if your gonna put an OSD chip on an fc you can design the fc so its supported properly. I personally don't see a reason to let this slide as it in the hands of the hobbyists, the people we do this for, this is a sub standard product.

@ot0tot @haslinghuis @blckmn what are you thoughts

[haslinghuis]

Agree with the assessment. Bad designs will no longer be accepted as users will blame the firmware for issues resulting in support burden. Qualified hardware will result in a better user experience.

We no longer accept unified targets and have a partner program in place, manufacturers will again be responsible for submitting new targets, maintaining revisions and need to work with us as outlined in the documentation in the manufacturer section of development for qualification and evaluation. User supplied targets should no longer be accepted.

[ASDosjani]

I see and I can understand why. I tell this to the manufacturer

[haslinghuis]

Closing as design does not comply with the target submission policy: https://betaflight.com/docs/development/manufacturer/requirements-for-submission-of-targets