It isn't a good idea to share the WiFi SPI interface with another device.
Hardware-wise the problem is that the SPI clock is set to a really high speed (around 50 MHz IIRC), which means the connections must be really short; if you try to set a lower speed, the SDK throws out errors.
Software-wise, it isn't a good idea to lock out the networking software for a period of time, while the interface is being used for something else. You'll probably create all sorts of problems; for example, TCP keeps track of the round-trip time of its datagrams, and uses this to determine the timing of retries. If you increase the round-trip time, then every time there is an error the code will wait an inordinately large time before retrying, which isn't good for throughput.
If you want to experiment with some CYW43439 driver code, take a look at my PicoWi project, https://iosoft.blog/picowi
Hardware-wise the problem is that the SPI clock is set to a really high speed (around 50 MHz IIRC), which means the connections must be really short; if you try to set a lower speed, the SDK throws out errors.
Software-wise, it isn't a good idea to lock out the networking software for a period of time, while the interface is being used for something else. You'll probably create all sorts of problems; for example, TCP keeps track of the round-trip time of its datagrams, and uses this to determine the timing of retries. If you increase the round-trip time, then every time there is an error the code will wait an inordinately large time before retrying, which isn't good for throughput.
If you want to experiment with some CYW43439 driver code, take a look at my PicoWi project, https://iosoft.blog/picowi
Statistics: Posted by jayben — Wed Jul 30, 2025 5:23 pm