Around a month ago, my Rock 3A arrived and I got to playing with it. I noticed that there was a community build configuration for it, so I set up an Armbian build environment and got to building it. The image built without error and before I knew it my device had booted.
However, since then, a few changes have been made to the Rock 3A (including receiving a proper Armbian maintainer), and now it seems to be completely broken. This issue seems to be reproducible, with people both being able to boot the board with old images as well as not being able to boot with fresh images.
There seems to be some work happening towards fixing u-boot (which seems to be the issue) on GitHub, but it has been completely silent for almost two weeks.
I realize that stuff like this takes time, as well as the fact that all of this work is community-driven. My main goal for asking this is so that I can contribute to the development for this board myself. I can't tell why booting this board isn't working from boot logs (available throughout this thread on the Radxa forum), so I'm largely at the mercy of those more knowledgeable about this part of Armbian and Linux than I am.
Any and all info would be greatly appreciated.