|
Hi guys,
I've recently puchased several OrangePi R1 Plus units and noticed that upon booting the provided image, U-Boot / dmesg logs are printing as clobbered output (as if the baud rate is incorrect) until Linux finishes booting and starts a console, at which point I can type normally.
I have found the GitHub repo: https://github.com/orangepi-xunlong/orangepi-build, which contains build scripts to build U-Boot, Kernel, and RootFS, and used it successfully to create new images. When building, it brings up the kconfig for the kernel, but not for U-Boot. If I cd into the U-Boot source directory manually and make menuconfig, I see that there are not boot arguments specifying the properties of the serial console. I have tried to modifty these to console=ttys0, 115200, but when re-building, the config gets overwritten from the default defconfig. I've tried modifying the scripts not to clean the sources before building and have also tried saving my custom defconfig over the original OrangePi one but still for the life of me can not get the customized U-Boot to stick or see any of the output before Linux starts.
Has anybody else experienced this? Does anyone have any advice?
Cheers,
stphnsmpsn
|
|