I have been working on a project that uses a Rpi B3+ running BlueOs, and have been running into some issues getting it working. I don’t know exactly what or where the issue is, as I think I am only seeing symptoms of it. Specifically, right now when I look at the System Infromation page and go to firmware it fails to get the firmware of the PI or the Bootloader with the error messages:
COMMANDER_GET operation appears to be the problem right now at least as I see it. Which base on my understanding could be an issue in the Bootstrap or Core. However, I have tried 3 times reflashing the SD card with both the stable and beta versions and they have all had this issue.
At this point I am kind of lost on what is the issue so some help would be appreciated.
Thanks
It might be a hardware issue or BlueOS configuration. Check connections, try another SD card or RPi, and review system logs. If the issue persists, consult Blue Robotics support or forums.
I don’t believe we’ve done much (if any) testing on RPi 3B+ boards (our old vehicles used RPi 3B and our new ones use RPi 4B), but it is at least expected to work.
Are you running into any other issues, or just viewing those values? And is the problem consistent, or just when the system has recently started up?[1]
If that’s the only problem then there’s likely just a bug with fetching those values on the 3B+ that we’re not yet aware of, in which case it would be great if you could create a bug report by raising an Issue in GitHub.
If there are other problems then it would be helpful if you can describe them as well, and also provide a system log file, which can be downloaded from the cog icon at the bottom of the sidebar
Some services can take a while to become available ↩︎
I do see some more odd things like the kernel mostly being orange after the first 120 Ish seconds from start up. Screenshot of a portion but it goes on from line 402 to at least 2896:
I also see in video settings it throws an error saying that it can’t fetch the legacy camera settings, however my Raspberry pi hq cam works just fine and is displayed normally both in Blueos and qgroundcontrol. Also, when I go to turn on legacy camera through the cog, Raspi-config and through terminal. After a restart they all seem to go back to off, and I know for a fact the cog does (goes form selected to unselected). Screenshot of that:
While exporting the Syslogs I also realized it is not able to report certain file sizes or what units they should be in like:
Syslog (no file size):
Memory (In Gb not Mb), but disk space is correct:
I also have noticed that it throws an error when I go to shutdown or reboot the system, but it does appear to shutdown as I can no longer access it through blueos.local and the ACT led stops blinking. Screenshot:
These problems have been consistent from startup to running for a while like an hour or two. Like I said they have also persisted through multiple images with stable and beta branches on different Sd cards. Including the file size issue, I realized it was wrong but never thought about it too much.
Hi @ShootingStars76
The Raspberry pi camera has not been tested much, and from what we’ve found can make things quite unstable… Using another USB camera may be your best solution!
I don’t believe the issues I have been experiencing are related to the Raspberry pi hq camera for 2 reasons:
1: The camera has been 100% stable with 0 issues using it.
2: On a fresh install without ever plugging in an hq camera (or camera in general) it throws those errors, by just opening the video stream page.
I believe the issue is with the way blueOs requests information while running on a Raspberry pi b3+. It could be related to the vcgencmd issues, but I am not experienced enough to know if those two are related.
I have updated blueos to 1.3.1 d47b4b32 and the RAM size has fixed itself. It went from displaying in Gb to Mb like it is supposed to. However, nothing else has changed, and there is still no file size displayed on the system log file or MAVLink log file export buttons.
