Sharing SPI with ETHERNET module in new AT custom command
Posted: Fri Aug 23, 2024 4:08 pm
I have a question for the ESP-AT developers.
I would to perform the following:
1) activate support for a SPI ethernet module to ESP-AT (assigning 5 pins: SI,SO,CK,CS1,INT)
2) share the same SPI with another chip, driven by my custom AT commands (assigning 5 pins: SI,SO,CK,CS2,INT)
As you can see, SI,SO,CK and INT are shared between the ethernet module and the other chip, using two different CS to address the SPI bus without hardware conflict.
Now, thinking software-wise I'm wondering:
1) can the ethernet module source code support sharing the SPI port shared lines (i.e. check if they are busy before using)?
2) can the ethernet module source code support sharing the SPI interrupt (i.e. check the source of the interrupt, to ignore it if not ethernet-related)?
Thanks in advance.
I would to perform the following:
1) activate support for a SPI ethernet module to ESP-AT (assigning 5 pins: SI,SO,CK,CS1,INT)
2) share the same SPI with another chip, driven by my custom AT commands (assigning 5 pins: SI,SO,CK,CS2,INT)
As you can see, SI,SO,CK and INT are shared between the ethernet module and the other chip, using two different CS to address the SPI bus without hardware conflict.
Now, thinking software-wise I'm wondering:
1) can the ethernet module source code support sharing the SPI port shared lines (i.e. check if they are busy before using)?
2) can the ethernet module source code support sharing the SPI interrupt (i.e. check the source of the interrupt, to ignore it if not ethernet-related)?
Thanks in advance.