[U-Boot] SPL debug messages (All of them!) - how?

[U-Boot] SPL debug messages (All of them!) - how?

[Nikolai Zhubr]

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

[U-Boot] SPL debug messages (All of them!) - how?

[Nikolai Zhubr]

Hi again,

23.12.2018 0:06, I wrote:
> 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)

Figured hard-hacking 1 into the #define debug() in log.h does what I 
wanted. Probably not exactly elegant, but at least it lets me see the 
messages:

U-Boot SPL 2019.01-rc2 (Dec 23 2018 - 00:26:45 +0300)
CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
DRAM: 1024 MiB
 >>SPL: board_init_r()
Trying to boot from NAND
spl: nand - using hw ecc
mkimage signature not found - ih_magic = 0
Jumping to U-Boot
SPL malloc() used 0x0 bytes (0 KB)
loaded - jumping to U-Boot...
image entry point: 0x4a000000

It looks like SPL loads 0x0 bytes of u-boot and runs it! Hmm, 
interesting. Its a good start already. Now just need to insert some more 
debugging messages...


Thank you!

Regards,
Nikolai

> 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
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot

[U-Boot] SPL debug messages (All of them!) - how?

[Nikolai Zhubr]

Hi again,

23.12.2018 1:06, I wrote:
> mkimage signature not found - ih_magic = 0
> Jumping to U-Boot
> SPL malloc() used 0x0 bytes (0 KB)
> loaded - jumping to U-Boot...
> image entry point: 0x4a000000
>
> It looks like SPL loads 0x0 bytes of u-boot and runs it! Hmm,

It appears not zero size but rather zero-filled image is retrieved for 
some reason, without I/O error, but still erroneously. Uhhh, apparently 
there is no reasonably way to check if raw u-boot body image is valid or 
not so SPL simply jumps there, and of course nothing usefull happens.

Now just need to see why the image is actually zeroed.

Besides, I've got a feeling that using a raw u-boot body, as per default 
setup, is not really a good choice, since the diagnostics is essentially 
missing and it also means an emergency second copy will not necessarily 
help if the main file was e.g. erroneously overwritten.


Thank you!

Regards,
Nikolai

> interesting. Its a good start already. Now just need to insert some more
> debugging messages...
>
>
> Thank you!
>
> Regards,
> Nikolai
>
>> 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
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> https://lists.denx.de/listinfo/u-boot
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot