-
Notifications
You must be signed in to change notification settings - Fork 9
SPI output stops while XLink and the rest of the pipeline keep running #20
Comments
Here's some minimal(ish) reproducible code, meant to be run on the host, with the spatial_image_detections code running on the ESP32. The lines that are commented out are lines that make the pipeline more like the one I'm using in my real application, but I was able to still make the SPI output stop working without these lines.
|
After some offline conversation with @themarpe , we managed to find a workaround for this. The issue seems to be caused by the SPI clock speed. I changed this from 16 MHz to 4 MHz in
After this change, I was having trouble getting the ESP32 to receive any data from the Myriad X at all. The issue here ended up being that the Myriad X needs to be running before the ESP32 tries to initialize a connection. I was able to achieve this in a hacky way by adding a delay at the beginning of the ESP32 code, but it means that restarting the pipeline requires me to:
It's not ideal, but it gets the job done until a more elegant solution can be implemented. |
I'm running into a really weird issue. I've got a pipeline that sends a lot of data to the host over serial and just spatial detection data to the ESP32 over SPI. After a few minutes (2-10) of running, one of two things will happen:
I've tried checking the temperatures using the SystemLogger node, and the temps were around 80 C when the SPI output stopped working the first time, (although this isn't consistent; I've seen it work at 90 C), which is well within the 105 C limit. Any thoughts on what might be causing number 2 and how I could address this issue?
I'm working on getting a minimal example that reproduces the code. I've been able to recreate the issue by adapting the spatial-mobilenet example to use the same pipeline I'm using. Now I'm trying to figure out what I can remove while still making the problem occur.
The text was updated successfully, but these errors were encountered: