I have a Boson 640 core plugged into a USB 3.0 hub, with a Flir USB 2.0 VPC. I'm running on a linux based embedded computing platform based on the aarch64 Linux 5.10 kernel (it is very similar to Debian).
I've successfully compiled the BosonUSB application for my platform, and am running the application as follows:
./Boson_USB y SB
So it is running in 8 bit YUV mode as Boson640 defaulting to video0.
After the application runs for ~45 seconds, the application freezes and there are no more frames being redisplayed or consumed from the camera.
The processor is not locked up and I am able to continue operations on the board itself.
While the application is running, dmesg is getting spammed with errors as follows:
uvcvideo: Non-zero status (-75) in video completion handler.
Device is still listed under lsusb and in /dev/video0 & 1 while the USB app is frozen.
I see this same behavior with another Boson camera on a different embedded board, so I do not believe its a specific hardware failure.
I have a Boson 640 core plugged into a USB 3.0 hub, with a Flir USB 2.0 VPC. I'm running on a linux based embedded computing platform based on the aarch64 Linux 5.10 kernel (it is very similar to Debian).
I've successfully compiled the BosonUSB application for my platform, and am running the application as follows: ./Boson_USB y SB
So it is running in 8 bit YUV mode as Boson640 defaulting to video0.
After the application runs for ~45 seconds, the application freezes and there are no more frames being redisplayed or consumed from the camera. The processor is not locked up and I am able to continue operations on the board itself. While the application is running, dmesg is getting spammed with errors as follows: uvcvideo: Non-zero status (-75) in video completion handler.
Device is still listed under lsusb and in /dev/video0 & 1 while the USB app is frozen.
I see this same behavior with another Boson camera on a different embedded board, so I do not believe its a specific hardware failure.