I have started working on a buildroot branch to support the UNO Q, however my device hasn't arrived yet, so it's mostly assumptions gleaned from the arduino/linux-qcom github repo and the debian image that the arduino-flasher-cli downloads.
I know that the fine folks at Arduino are working hard to get all the code ready for public release and a lot of my guesses will have definitive answers then.
Regardless, I wanted to post progress here in case anyone else is working on the same thing or has expertise in this area and advice to give.
Okay so neither mainline u-boot nor linaro’s Qualcomm fork will boot a kernel as far as I can tell. Looking at the log output for the stock u-boot it’s version string contains a sha that isn’t present in either repo so my guess is that the hard working folks at Arduino have their own u-boot fork that they’re working on which are not yet publicly available.
If anyone has any suggestions other than “hurry up and wait” I’d love to hear them.
@manchuino any chance we can get the bootloader code bumped up the priority list? I know you’re all flat out so no pressure but if you don’t ask you don’t get
@jamesharton sorry for the delay, I didn’t see the thread earlier The bootloader code is here GitHub - arduino/u-boot at qcom-mainline , we are currently in the process of upstreaming so the commit history will likely change soon, but it can safely be used.
Thank you so much! This is awesome. For my next ask, can you tell me where the prog_firehose_ddr.elf binary comes from in the debian image? I need it to make QDL work, but I've just had to copy it for now.
The bootloader code is here