Looking to commission a new Chromium build (COMMUNITY BOUNTY)

[tophneal]

Ok, so here is the image I built, but couldn't test yet:
https://brentthierens.stackstorage.com/s...s5GI65JYBI
Probably with flashing a uboot to the SD after flashing the image, we could be fine. However, one does not know for sure untill it actually boots. I also saw issues in the past when a newer version of uboot was on the eMMC. So, if anyone wants to test and doesn't mind wiping the eMMC for the uboot part at least, go ahead!
FYI: this should have 5.8-rc5

Nice! I'll give it a try this weekend!

put it on an SD and added mrfixit's bsp uboot but it wasn't having it. i'll give it another shot from manjaro. maybe mainline uboot will get it going

[clover]

I put it on a (crappy) 16GB SD, didnt boot. I have dhivael's upstream uboot on my SPI.

[tophneal]

i guess if neither bsp or mainline will get it booting, it might be time for a serial cable, to see why

[brent.thierens]

I did some more investigation. One of the problems is that the EFI partition is empty. If you mount it and you copy over the files from e.g. a Manjaro boot partition, and change the loglevel to 6 and the console to tty1, you get some output. As we already have had before, ChromeOS believes its ROOT Partition is damaged and will do some stuff that fails and the PBP does not boot. However, if we look back at the original images by @ayufan we can see that there are a lot of hashes over there, that verify the integrity of the image (kernel image?) or whatever. I think we need to find out what these hashes mean and how to adapt them. Can @ayufan himself maybe shed some light here?

---

This might be interesting as well: https://static.googleusercontent.com/med.../42038.pdf
If anyone has some insights here, I feel we could be quite close to a working image

[tophneal]

good catch!

not sure how to get @ayufan to weigh in. He doesn't seem to be super active on the boards (i've never seen him reply to a user mention, or reply to a pm,) though you can occasionally catch him in the #pine64 and #rock64 channels (though i'm not sure what service he uses for the chat, so it may not be easy to PM him either)

[clover]

@brent.thierens ,

When you go to build the image itself, make sure  --noenable_rootfs_verification is set to bypass the verified boot. E.g., 

Code:

./build_image --board=${BOARD} --noenable_rootfs_verification test

[brent.thierens]

Thanks for the tip. I did that however, so maybe the reason it fails is something entirely different...

[clover]

Thanks for the tip. I did that however, so maybe the reason it fails is something entirely different...

are you using a custom overlay or just arm64 generic?

[brent.thierens]

I tried with arm64-generic, but I added some more options so in the end it is a custom overlay inheriting from arm64-generic.
I can post the files if you're interested

[clover]

I tried with arm64-generic, but I added some more options so in the end it is a custom overlay inheriting from arm64-generic.
I can post the files if you're interested

Please do! I tried my own arm64 custom overlay with mainline uboot + manjaro kernel, but hit a wall building the the verified boot tools package. I think this is due to the compiler toolchain being too old.