So, regarding my old patchset. Thanks to the generous support of Simon, I have been able to use a google servo board to obtain an output log of my boot failure. Whereas Simon got the following:
U-Boot SPL 2017.11-rc2-00017-g6cda208-dirty (Oct 19 2017 - 17:20:26) Trying to boot from SPI U-Boot 2017.11-rc2-00017-g6cda208-dirty (Oct 19 2017 - 17:20:26 -0600) Model: Google Speedy DRAM: 2 GiB MMC: dwmmc@ff0c0000: 1, dwmmc@ff0d0000: 2, dwmmc@ff0f0000: 0 Using default environment In: cros-ec-keyb Out: vidconsole Err: vidconsole Model: Google Speedy Net: Net Initialization Skipped No ethernet found. Hit any key to stop autoboot: 0 => On his 2 GiB Asus C201, I only get the following: U-Boot SPL 2017.11-rc2-00017-g6cda208-dirty (Oct 19 2017 - 17:20:26) Trying to boot from SPI U-Boot 2017.11-rc2-00017-g6cda208-dirty (Oct 19 2017 - 17:20:26 -0600) Model: Google Speedy DRAM: 0 Bytes Further, after rebasing my patch against master to commit ec1754f091c3c06d76592a3f9fecf6184f27e4c9 I don't get any output at all, except for one of those unicode mojibake <?> characters everytime I hit the servo reset button. It seems somewhere along the lines between 0def58f7fd (upstream/master) Merge git://git.denx.de/u-boot-x86 and ec1754f091 (upstream/master) Prepare v2018.05-rc3 something went funky. If someone with one of the supported rockchip chromebooks could dry the above commit I would greatly appreciate it. Regards, Marty _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
