-
Volunteering positions
-
Test Automation Engineer
Position: Software integration test engineerNumber of places: 16Applicants: 8
-
-
Chat | Social Media
#armbian at
irc.libera.chat or irc.oftc.net
Matrix or Discord
Mastodon | 𝕏 -
Popular Now
-
Activity Stream
-
4
How to enable uboot_debugging option via userpatches?
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 -
8
MYD-lt527m-16e2d-180-e-sx
I managed to get a device tree from Android. The veil has been lifted))) android-dtbo_MYD-lt527m-16e2d-180-e-sx.dts -
4
How to enable uboot_debugging option via userpatches?
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. -
4
How to enable uboot_debugging option via userpatches?
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 -
4
How to enable uboot_debugging option via userpatches?
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
-
-
Member Statistics
