Add new target RUSHCORE7

[nyway]

Rush authorization add new target RUSHCORE7.
https://www.rushfpv.com

[nyway]

Have ome mistakes,it's use gcc-arm-none-eabi-7-2018-q2-update and mainteance compile before.
Will change to gcc-arm-none-eabi-7-2017-q4-major 3.5.x-mainteance and do some test later.

[asizon]

This is the same PR as closed #7333?what differences?
Please read:
https://github.com/betaflight/betaflight#embargo-on-new-targets-for-betaflight-40

[nyway]

@asizon
This is against Betaflight 3.5.x-maintenance.
#7333Against Betaflight 4.x.x

[asizon]

okey, the previous one was open against master

[asizon]

I think that GYRO1_CS_PIN now works on 3.5

[MJ666]

@nyway after checking more in detail @asizon is correct 3.5.x is alredy supporting thenew types of definitions for the Gyro/ACC and is on the step to transition to the new settings. So your definitions most likely working as expected.

[mikeller]

The pull request system is not intended to be used to find / fix compilation / functional errors. Before opening a pull request for a new target, please make sure that:

• your target builds;
• basic function checks succeed, i.e. the target boots, and the acc / gyro works,...

[MJ666]

@mikeller my comment was regarding MPU6500_CS_PIN vs. GYRO_1_CS_PIN definitions and related ones. They are both supported in 3.5.x in parallel. For sure generic target need a different PR for the config.

[mikeller]

@MJ666: Sorry, my comment wasn't a reply to you, it was addressed at @nyway.

[nyway]

@mikeller @MJ666
Modification complete and test good so far.Please help me check if there is anything to be modified,thanks.

[mikeller]

The rest looks good.

[mikeller]

@MJ666: Have your concerns with this been addressed?

[MJ666]

Looks all good to me.

[mikeller]

Added board description link to wiki.

[mikeller]

@nyway: Now that the format for Unified Target configurations for Betaflight 4.0 has been defined, and a process to create them established, can you please open a pull request to get this target added to the master branch? Instructions for this can be found at https://github.com/betaflight/betaflight#new-requirements-for-the-submission-of-new-and-updated-targets.

We can do this for you, but since we do not have the actual hardware, this will mean that the target will be untested and potentially broken in 4.0, so it is preferrable if you do this, and test the resulting firmware and Unified Target configuration before submitting the pull request.

[nyway]

@mikeller
Okay,i will do that.
Should i do the same thing for the other out target DALRCF405 or 722?

[mikeller]

@nyway: Those two are already in 4.0 as 'legacy' targets (in src/main/target). But if you could submit them as Universal Target configurations (in universal_targets/configs) that would be great!