AlexCrux Posted Tuesday at 08:21 PM Posted Tuesday at 08:21 PM (edited) Hi all, Is there any working way to enable detailed logs from uboot? I am using fresh main branch (latest commit is 4648add1450c1b26bb29bf412ef054b0e978947d) . I have created following config inside userpatches/config-test.conf.sh file BOARD="orangepizero" BRANCH="current" RELEASE="jammy" BUILD_MINIMAL="yes" PREFER_DOCKER="yes" DOCKER_ARMBIAN_BASE_IMAGE="ubuntu:jammy" BOOTDELAY=2 UBOOT_DEBUGGING="yes" My command to build image is ./compile test. As I understand from source code UBOOT_DEBUGGING variable should enable such detailed uboot logs, but it seems like build framework ignored this option, I did not get detailed logs from uboot, also build logs do not contain info messages related with enabled UBOOT_DEBUGGING, etc. P.S. Just for context - I have board wukongpih3zero (clone of orangepi zeor) and booting is hanging at unexpected mcc1 slot instead of microsd mcc0 - that's why I need detailed boot logs. Edited Tuesday at 08:24 PM by AlexCrux 0 Quote
Werner Posted 22 hours ago Posted 22 hours ago 10 hours ago, AlexCrux said: UBOOT_DEBUGGING never heard of that one before. Serial console is enabled by default on all boards (lookup your board manual on where to connect) which also outputs uboot logs while on early boot stage. For increased kernel verbosity set verbositoy to 7 in /boot/armbianEnv.txt 0 Quote
AlexCrux Posted 21 hours ago Author Posted 21 hours ago (edited) I have took this variable from Here. Actually the first thing I tried to observe is uart logs. But they are very minimalistic like that: U-Boot SPL 2024.01-armbian-2024.01-S866c-P6b16-Ha5c2-V367a-Bb703-R448a (Apr 29 2025 - 02:50:09 +0000) DRAM: 512 MiB Trying to boot from MMC1 It's from offial image from website, but the compiled image on my side has the same logs and effect Edited 21 hours ago by AlexCrux 0 Quote
Werner Posted 21 hours ago Posted 21 hours ago Hm interesting. Didn't know this exists. But if it doesn't work I suggest to run a build with also DEBUG=yes set and then share the whole log using the curl command provided at the end. May give some clues if this fails to apply or works as intended. 0 Quote
AlexCrux Posted 18 hours ago Author Posted 18 hours ago Thank you for hints. Curl approach is not working, too big file for request. Here is log file of build which was adviertised to push into pastbin (debug=yes option was passed) log-build-8431ff32-1cf8-4fe6-9eeb-6f46f683c875.log.zip 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.