Before I go down the rabbit hole, I figured I'd ask....
Are there any technical limitations of having a small web server running parallel to the Ethernet Audio library?
The web server example works fine on the hardware. But when I try to integrate it into my ethernet audio project, the setup works (server.begin()), but the first time it calls
the teensy crashes.
Aside from letting the EthernetAudio handle setting up the SPI, MAC and IP, my code is copied and pasted from the webserver example. I recognize the way the example is written, it's blocking so I would rewrite it to keep loop times low. But it's not getting past the first line.
Are there any technical limitations of having a small web server running parallel to the Ethernet Audio library?
The web server example works fine on the hardware. But when I try to integrate it into my ethernet audio project, the setup works (server.begin()), but the first time it calls
Code:
EthernetClient client = server.available();
Aside from letting the EthernetAudio handle setting up the SPI, MAC and IP, my code is copied and pasted from the webserver example. I recognize the way the example is written, it's blocking so I would rewrite it to keep loop times low. But it's not getting past the first line.