Open evildave666 opened 3 years ago
If I can make time I'll try to work on this over the weekend.
Didn't I change my mind on this because the pins are broken out on pin headers?
Does CircuitPython need to have exclusive use of the pins and the SPI bus for the flash chip, or could it share them with other SPI devices as long as they use a different CS pin? It seems a shame to lose use of the pins even when the flash isn't being read/written to.
Does CircuitPython need to have exclusive use of the pins and the SPI bus for the flash chip, or could it share them with other SPI devices as long as they use a different CS pin? It seems a shame to lose use of the pins even when the flash isn't being read/written to.
At this point yes. CircuitPython does have locking around a SPI bus but we haven't made sure it works ok to share a SPI bus between USB generated SPI flash accesses and user code accesses.
I think it'd be a lot of work to get right for little payoff. This is the only board out of 250+ that I know of with this issue.
Fair enough. I had suspected as much.
The flash is optional on this board (its basically a haxpress) and the pins are meant to be usable when the flash is not populated (the non-"with_flash" board). I still think that having board pins defined which probably don't work would cause more support issues than people wondering why they're not there if they're removed. The board does have multiple additional SPI ports available in any case.
CircuitPython version
Code/REPL
Behavior