RPi4B: modern firmware vs. Device tree loaded to 0x4000 (size 0xbe0c) [fails] vs. to 0x1f0000 (size 0xbd90) [works]?
Robert Crowston
crowston at protonmail.com
Sun Oct 11 17:02:04 UTC 2020
> mmel@ has mentioned that it may not be terribly hard to implement this
> with spin tables instead. This would also let us undo a config
> fragment in U-Boot, as we won't need to reserve any more than the
> first page if we're following the standardish procedure.
Well, maybe that is the way to go.
I upgraded to the latest (head) version of u-boot. Now when I try to boot, I get stuck in malloc(). Anyone else see this?
Snipped...
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
(System hangs, so let's see what's going on ...)
(gdb) bt
#0 malloc (bytes=<optimized out>) at common/dlmalloc.c:1433
#1 0x000000003b369d68 in xrealloc (ptr=<optimized out>, size=<optimized out>) at common/cli_hush.c:3348
#2 0x000000003b369dd8 in done_command (ctx=ctx at entry=0x3af46d20) at common/cli_hush.c:2566
#3 0x000000003b369e60 in done_pipe (ctx=0x3af46d20, ctx at entry=0x3af46d90, type=PIPE_SEQ) at common/cli_hush.c:2601
#4 0x000000003b36b854 in parse_stream (end_trigger=0, input=0x3af46d90, ctx=0x3af46d90, dest=0x3af46d78) at common/cli_hush.c:3092
#5 parse_stream_outer (inp=0x3af46d90, inp at entry=0x3af46dc0, flag=flag at entry=11) at common/cli_hush.c:3199
#6 0x000000003b36ab04 in parse_string_outer (
s=0x3af64740 "echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done;run scan_dev
_for_efi;", flag=11) at common/cli_hush.c:3274
#7 0x000000003b376610 in do_run (cmdtp=<optimized out>, flag=<optimized out>, argc=<optimized out>, argv=<optimized out>) at common/cli.c:148
#8 0x000000003b3772e8 in cmd_call (repeatable=0x3af46e7c, argv=0x3af67920, argc=2, flag=0, cmdtp=0x3b3d59b8) at common/command.c:581
#9 cmd_process (flag=0, argc=2, argv=0x3af67920, repeatable=0x3b3e4e94, ticks=0x0) at common/command.c:636
...
Reminds me of going back to step 1 in July 2019. :-)
— RHC.
More information about the freebsd-arm
mailing list