#136 veyron speedy uboot fails to boot

So I built a veyron speedy uboot payload rom for my C201 the other day, and it shows no indication of booting. I can see a black screen and a flash of white line. I don't think linux is booting because I can't ssh into it and I don't have a UART debugger or pads apparently. I'm also not sure if uboot is crashing or if coreboot crashed before that. Good thing I have an external flasher.

So has anyone else had success in flashing libreboot+uboot to veyron-speedy? Any failures? Anyone have their backups at hand? What about veyron boards? What I'm looking for are volunteers who would be willing to backup their factory roms and post their fmap dumps. Then we can look at commonalities and differences.

The flashmap utility is now a part of futility, and can be installed with sudo apt install vboot-utils. From there we can run futility dump_fmap /path/to/c201.rom

This is the dump from what I built: https://paste.debian.net/1265625/

This is the dump from my factory image: https://paste.debian.net/1265626/

For what it's worth, my C201 has 4GB of ram and a usqwerty keyboard, intended for North American consumers. It's an AZUREWAVE/AW-CM195F C201PA-DS02 manufactured 2017-03.

EDIT: I've done another build, this time with alpernebbi's PR: https://notabug.org/libreboot/lbmk/pulls/137

I've also built for both C201PA and C101P. I'm not seeing an elf file in the veyron board.

Veyron Console output: https://paste.debian.net/1265852/

Gru Console output: https://paste.debian.net/1265853/

Also about the missing uboot warning... Is that a fake warning or a real warning?

Also about the missing uboot warning... Is that a fake warning or a real warning?

That's a "fake" warning. Coreboot images are built without any payload. lbmk then injects the payload manually. So, nothing to worry about.

You should get a UART debugger though. If you don't want to or can't afford one, coreboot can also write logs to the flash chip (if I recall correctly). Enable the option and rebuild.

Hello, I have a c201 in which I can get serial logs from. Here are the logs after building with log level set to 7. The boot process hangs after it displays the memory size.

https://paste.debian.net/1272538/

hi

according to alpernebbi on irc, the last known working version of u-boot on veyron machines is the 2021.01 version

so, with alpernebbi's patches applied for each try, a git-bisect is probably the best way to find what broke, to then know what fix is needed. and then veyrons can work nicely

i removed the veyron roms from the december 2022 release, while keeping it in the build system. i'm not sure whether i should simply delete it while this is broken (moving it to a branch, and documenting such a move on the website)

Just use 2021.01.

Hello. I could reproduce u-boot black screen on my C201 and with bisect I found that these two commits are causing the problem here:

• rockchip: video: vop: Add reset support 9749d2ea29
• rockchip: video: edp: Add missing reset support cd529f7ad6

u-boot works before those two, but with some commits it takes a while until something appears on screen (a different problem)

And I think this doesn't apply to all Veyron models, because it doesn't happen in a Veyron Jerry where I also did some testing.