From: Nikolai Zhubr <n-a-zhubr@yandex.ru>
To: u-boot@lists.denx.de
Subject: [U-Boot] SPL debug messages (All of them!) - how?
Date: Sun, 23 Dec 2018 00:06:02 +0300 [thread overview]
Message-ID: <5C1EA73A.9000609@yandex.ru> (raw)
Hi people,
I'm struggling trying to figure how to totally enable all of those nice
debug() statements so as to debug a problem in SPL. The CONFIG_LOGLEVEL
is set to 7, have also tried to all KCFLAGS=-DDEBUG but apparently it
has all no effect for SPL. So I'm asking for advice (and I'd definitely
like to not selectively prepend "#define DEBUG" all over the place)
Background: I'm trying to perform direct nand install on an A20
olinuxino board. That is, dismissing messy boot0 and boot1 in nand.
Currently, I've succeeded to get a good greeting from u-boot SPL,
declaring that it is going to proceed to boot from nand, but then all
stops forever:
U-Boot SPL 2019.01-rc2 (Dec 22 2018 - 22:15:16 +0300)
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
DRAM: 1024 MiB
Trying to boot from NAND
I'd like to try to find the reason for this and certainly having all
those debug messages could help somewhat.
Thank you!
Regards,
Nikolai
next reply other threads:[~2018-12-22 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-22 21:06 Nikolai Zhubr [this message]
2018-12-22 22:06 ` [U-Boot] SPL debug messages (All of them!) - how? Nikolai Zhubr
2018-12-22 23:46 ` Nikolai Zhubr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5C1EA73A.9000609@yandex.ru \
--to=n-a-zhubr@yandex.ru \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox