So I got a IMX 462 from Arducam which works when installed on Raspbian Legacy. When I run the BlueOS install script it breaks. I have already tried the --skip-board-config flag without any luck. I’m not sure why it’s breaking but it seems that the installer is writing the the /boot/config file even though it shouldn’t It also overwrites any changes I make to the file on reboot.
I’m at a loss as to why these two supposedly native systems break when used together. I’ve tried using the BlueOS image without any luck.
I just reinstalled everything from scratch again. The camera works great… right up until the restart at the end of the install script. I’m guessing it has something to do with BlueOS continuously trying to take over the i2c interface in /boot/config.txt which is also used by the camera. Is there any way to stop it from doing that?
I found the issue. Uart 1 conflicts with the camera. However, I found it by loading Rpanion-server and commenting out Uart1 in the /boot/config.txt. I prefer to use BlueOS as my class has been using it up to this point, and Cockpit is very interesting for my use case with students. BlueOS still overwrites any changes I make that alter its configuration in /boot/config.txt. Short of making it immutable I can’t seem to stop it from changing the file back.
Does it work to turn on legacy camera support in the Video Streams page in BlueOS (via the settings button in the bottom right corner)?
If that doesn’t help I can ask our software team for recommendations on managing the configuration. There might be some settings that BlueOS loads when it starts up.
Nope, I continued to troubleshoot it, and turning off uart1 fixed it but I had to be on a newer kernel. However, I also looked through the pivareity kernel driver and couldn’t find any place where there might be a conflict. I’m fairly certain this is on Arducam’s end. What I couldn’t figure out how to do was stop the config file from replacing any lines I commented out or removed. Something was just putting them back, which I expect is the bootstrap doing its thing?
OK, I got it working by upgrading the kernel to 6.1.21-v8+ and disabling Bluetooth in config.txt. However, the camera still won’t show in BlueOS despite being able to trigger it manually and having it work in Rpanion-server.
It looks like enabling UART 1 forces it to go into the highspeed mode to support the Bluetooth radio’s high-speed functions. My fix sort of cludged it into submission by forcing the BT radio to the mini uart. Adding the code below to the config.txt should fix it cleaner.
dtparam=i2c_vc=on,i2c_vc_baudrate=50000
I’m still unable to get it visible in BlueOS, though it works in Rpanion-Server. I’m considering just writing a script to force it to stream to the default topside address but I’m not familiar with how to write a simple Docker.