Date: Tue, 27 Sep 2022 18:59:29 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: Klaus K??chemann <maciphone2@googlemail.com>, freebsd-arm@freebsd.org Subject: Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it Message-ID: <D5C7C2D4-53A8-405F-B1B3-6E367D630725@yahoo.com> In-Reply-To: <20220927232930.GC72077@www.zefox.net> References: <3D6CF13E-261D-41D2-AC5B-923C0BF54087@yahoo.com> <20220927160328.GA71742@www.zefox.net> <67C09E9F-AD1D-4D0D-9E6F-9C1B046D8952@googlemail.com> <4154AFCB-7428-4005-843A-4EF8C0EBCCB8@googlemail.com> <D8708275-D396-4D2F-9461-B305E522BCCE@yahoo.com> <9A3609DF-D873-4712-A61D-C351C162EF2A@googlemail.com> <61CFA9D4-8DFD-41C5-A2B4-E5B3CD78C327@yahoo.com> <650FD030-783D-46C4-8CC9-50D608569898@yahoo.com> <81C8A094-8492-41DC-A74E-486A9225A2A3@googlemail.com> <760FE9D5-7A1D-40C2-B4CC-E90B300F5B3B@yahoo.com> <20220927232930.GC72077@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Sep-27, at 16:29, bob prohaska <fbsd@www.zefox.net> wrote: > On Tue, Sep 27, 2022 at 03:27:10PM -0700, Mark Millard wrote: >> >> Until the following are changed to have appropriate >> values at the overall configuration level, it does >> not appear that LOG_DEBUG and/or DEBUG will do >> anything: >> >> QUOTE >> The following options are used to enable logging >> at compile time: >> >> CONFIG_LOG - Enables the logging system >> CONFIG_LOG_MAX_LEVEL - Max log level to >> build (anything higher is compiled out) >> CONFIG_LOG_CONSOLE - Enable writing log >> records to the console >> END QUOTE >> >> I expect that means having them set appropriately >> in rpi_arm64_defconfig for the experiments. >> > At long last I did it correctly and got a u-boot.bin > that's just under 600kB. After issuing shutdown -r now > part of the output includes > > Uptime: 1h38m7s > Resetting system ... Note the lack of output from the RPi* firmware at the point in the sequence. This answered an earlier question: you can not tell a full RPi* reset with the RPi* firmware starting over before U-Boot starts over vs. just U-Boot starting over. I expect that when you have said/shown U-Boot as starting over that in fact the RPi* reset and the RPi* firmware also started over (before it starts U-Boot again). It would help to enable getting some output from the RPi* firmware as well so that you have evidence for when it is (re)running. > U-Boot 2022.04 (Sep 27 2022 - 15:47:57 -0700) > > DRAM: 948 MiB > RPI 3 Model B (0xa02082) === Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D5C7C2D4-53A8-405F-B1B3-6E367D630725>