Don't enable all flash chips by default on EXST targets.

[hydra]

EXST targets generally ship with a specific flash chip, so there is no point including flash chip drivers that are never intended to be on the PCB.

e.g. there's no point including other flash chip drivers for the SPRacingH7NANO/ZERO which always have the W25N01G.

[github-actions]

Do you want to test this code? Here you have an automated build:
Assets
WARNING: It may be unstable. Use only for testing! See: https://www.youtube.com/watch?v=I1uN9CN30gw for instructions for unified targets!

[blckmn]

AUTOMERGE: (FAIL)

• github identifies PR as mergeable -> FAIL
• assigned to a milestone -> PASS
• cooling off period lapsed -> PASS
• commit count less or equal to three -> PASS
• Don't merge label NOT found -> PASS
• at least one RN: label found -> PASS
• Tested label found -> FAIL
• assigned to an approver -> FAIL
• approver count at least three -> FAIL

[haslinghuis]

How does this work if another H7 implementation decides to use another flash chip?

[hydra]

How does this work if another H7 implementation decides to use another flash chip?

Not sure I fully understand your question; Any cloud build target should be able to now be built with only the flash chip drivers required for the target using the appropriate gating defines. As opposed to all the flash chip drivers which is appropriate for the large-flash, non-EXST targets like the STM32H743 target.

If a new flash chip driver is required it should be added to the list as required, and also in any target definition for EXST targets.

[blckmn]

The issue I think @haslinghuis is raising is that the core build should load all flash drivers.

So that the actual detected flash can be determined.

Without me checking, I'm assuming this is outside of a cloud build.