You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have flashed the BalenaOS RockPi Model B image onto my Rock Pi Model A just to realize it is not booting up. Upon plugging in the RockPi, there is no feedback via HDMI whatsoever (green and blue LEDs constantly on, no blinking).
Reading the Radxa FAQ, the only difference between the RockPi Model A and Model B is the lack of a Bluetooth/WiFi/PoE module on the Model A.
Would it be possible to adapt the BalenaOS build to work on the Rock Pi Model A, perhaps by disabling the Bluetooth layer in the Yocto build? Unfortunately I have no experience with Yocto to do it myself (and also do not know if that is a good suggestion). I appreciate any help!
The text was updated successfully, but these errors were encountered:
Hi,
I don't think the lack of bluetooth / wifi / poe is preventing the board from booting up.
What I suggest is that you use a serial connection to debug it. You can use a TTL USB cable, connect Ground to pin number 6 on the board's pinout header, RX to pin 8 and TX to pin 10. Then on your development machine use minicom and set the baudrate to 1500000 and try to see if you get any boot messages over this serial console
I have flashed the BalenaOS RockPi Model B image onto my Rock Pi Model A just to realize it is not booting up. Upon plugging in the RockPi, there is no feedback via HDMI whatsoever (green and blue LEDs constantly on, no blinking).
Reading the Radxa FAQ, the only difference between the RockPi Model A and Model B is the lack of a Bluetooth/WiFi/PoE module on the Model A.
Would it be possible to adapt the BalenaOS build to work on the Rock Pi Model A, perhaps by disabling the Bluetooth layer in the Yocto build? Unfortunately I have no experience with Yocto to do it myself (and also do not know if that is a good suggestion). I appreciate any help!
The text was updated successfully, but these errors were encountered: