Add new target EASP-RRIOTF722

[ws998116]

No description provided.

[nerdCopter]

• is it possible to add the timer and dma comments similar to other existing targets? (does not affect usage/merging, just an unimportant request).
• they can be output by flashing 4.5 with the USE_TIMER_MAP_PRINT custom define, then executing timer and dma in CLI.

[ws998116]

Thanks @nerdCopter, fixed.

[nerdCopter]

@haslinghuis , does line 1 need to be a Betaflight version?

[haslinghuis]

Before merging - we need #1277

[ws998116]

Please leave this open for now, there will be some changes.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week.

[ot0tot]

Is there a typo in the config? Gyro, flash, OSD, and baro should not all be on the same SPI bus.

[ws998116]

@ot0tot we are moving the baro to I2C, but the rest will share SPI.

[ot0tot]

@ot0tot we are moving the baro to I2C, but the rest will share SPI.

Can you move flash and OSD to their own SPI bus? You cannot have all of these perepherials on the same bus.

[ws998116]

@ot0tot are you suggesting to have three separate SPI buses? One for each peripheral?

[ot0tot]

@ot0tot are you suggesting to have three separate SPI buses? One for each peripheral?

Correct. Refer to other similar target configs for examples.

[haslinghuis]

Closing as we no longer accept new unified targets. Please create a config in https://github.com/betaflight/config repo with requested SPI assignments.