There is a webcam model that we have which works well on a rpi3 running raspbian with kernel 4.19.118-v7+ but doesn’t work in kernel 4.19.75 of balenaOS 2.51 for fin. I was wondering when a development version of balenaOS 2.53 will be out for balenafin since that contains kernel 4.19.118
Thank you balenaFin Gods for downgrading the image for Rasbpberry Pi as well. Having that we could at least continue our work. Now you took it away without a notice and we have to find another way.
balenaOS 2.56 is currently being tested in the staging environment for both Fin and RPi3 devices, and will be released in the near future. We will keep you updated.
We’re working on updating the image to Buster (you can follow up our progress here). The current blocker is building the WiFi driver on the new kernel required for Buster, but we’re making progress there and it should be resolved soon.
Apart from running the latest version, are you experiencing any particular issue with the current version or Raspbian?
Sure. I don’t know why my email reply didn’t went through. But I will try to paste here my comments…in general:
Documentation seems bit old/inaccurate. Or even very few for certain developers.
Examples:
No pinout description on PDF. No pinout direction. Just location. At least pin1 should be there somewhere.
On page balenaFin - Docs > Controlling the RGB LED > Its not ok: its not /sys/class/led/pca963x:$COLOR should be: /sys/class/leds/pca963x:$COLOR/brightness (led should be plural)
Most of the implementations are using dockers (because of balena.io … I know) …but since I want to implement a X11 / Electron fast boot solution…it’s been very hard to convince my team to go for this board.
Most important: Not a single script on raspian (or sample of code) to use the i2c to power-off. There is very very few documentation about how to flash the firmware not using the docker. Dev’s must reverse eng the docker to create code for that…but would be good/easier to have a lean step-by-step guide. I try to watch your video about firmware update and at the end…was just a nice conversation but nothing that could document the process. And the power on/power off (or sleep…) …is a show-stopper for my team.
Our project will require 700 boards / year. So is important for us to select the right board. Suggestion: focus on better documentation
Thanks a lot for your valuable feedback! Let me address your items one by one and hopefully get you unblocked:
1.1 and 1.2 Thanks for pointing this out. I’ve already filed an issue to fix the leds typo and to include the first pin indication on the datasheet. You can take a look at the physical balenaFin for reference on the pin position in the meantime
1.3 What issue are you having with turning the HDMI off? Do you mean that shutting down port4 of the USB also shuts down the HDMI? I’ll test this tomorrow and get back to you, but I don’t why this would be happening.
Installing the 3G modem in Raspbian should work the same way as if you’d be adding one on a RaspberryPi. I’m not sure which modem you’re using, but the easiest path would be to install ModemManager and NetworkManager to do so. I’ve personally installed a few modems that way. There’s a quick guide here that should get you up and running, do let me know if you face any issues with this.
This shouldn’t be a problem with balenaOS, but in any case, I’ve asked a few colleagues to chime in.
This is a good point, most of our customers have been using the coprocessor within balenaOS and that’s what our docs are focused on. I’ll discuss this internally and get back to you with more information.
Let me know if there’s anything else I can help with.
Cheers,
Nico.
1.3 To turn the HDMI off, I try the commands available on dev documentation. But they have no effect on HDMI port. So what I did was to use the USB that powers the screen and turn it on/off using the git code presented.
The 3G modem I try the one included on balenafin. It doesn’t show in neither modemmanager neither networkmanager. But I will look at the guide! THANKS!