-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SPI #3
Comments
"When I try to run "PlayerThread" the processor is used whole, 100%." |
Now, I never tested my lib with Rpi Zero (only Rpi 2 and 3). My guess, the SPI resets can be the result of a loss in sync with Lepton. |
Well, increasing the number of packets_per_read helped a little. But it is really only small quallity improvement. I found that Rpi Zero has problem with electric interference. Output is much better, if I disconnect usb keyboard. So I think that missing frames is not a software problem but hardware. |
That could be the case. If I put my hands on a Rpi Zero I will try to debug this behavior too. Thanks ! |
Uhh, have everything including battery power source inside a faraday cage, yet still not working properly. After a short reading of Rpi 2,3 and Zero differences I have to ask: how the spi speed is set in the program? I have only found setting the speed in Hz in LeptonCommon.h but how is this value interpreted by Rpi? How does it sets the divider? I have tried to find this reading though the program with no success. |
Searching the web, I found many problems with the SPI, since this is based on the CLK and a pre-fixed set of dividers.
I will read more on this. |
Yeah, I have read something like that on the web. However, I will try to get my hands on Rpi3 :D |
Hi, I have a problem with running the program. When "Player" is executed in terminal can be seen that it opens and closes the SPI communication to the infinity. Some frames are visible on the screen (like 1 frame per 5 sec.), rest it is looking like the camera is freezed. What can cause this issue?
I´m using Rpi Zero, Jessie, Lepton v3. The processor indicator is not even windy, shows around 40% used computing capacity.
When I try to run "PlayerThread" the processor is used whole, 100%. Almost no frames can be seen and it makes Rpi unuseable unless hard restart is done.
The text was updated successfully, but these errors were encountered: