Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it
Mark Millard <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Message-ID | <[email protected]> |
On 2022-Sep-27, at 11:33, Klaus Küchemann <[email protected]> wrote: >> Am 27.09.2022 um 19:58 schrieb Klaus Küchemann <[email protected]>: >> >> >>> Am 27.09.2022 um 18:03 schrieb bob prohaska <[email protected]>: >>> >>> I did look at common/usb.c but it's far from obvious how one >>> can turn on the logging feature so as to report more errors >>> to the console. >> >> you can add the following to common/usb.c (e.g. insert in line 44): >> >> #define DEBUG >> >> -- >> >> that should then print out all debug functions inside the usb.c file to the console >> after recompilation of u-boot. >> >> Regards >> >> Klaus > > I saw there is /*#include <log.h>*/ available in usb.c > so you could also try to add : > > #define LOG_DEBUG > > to the common/usb.c file which should also then enable the debug functions > which then would be output in logging style. > > You will need the debug output to to narrow down the issue. > > just a guess : > electrical problem(of the Pi itself) which could perhaps be fixed by manipulating the scan delay time . Looks to me like: https://github.com/u-boot/u-boot/blob/master/common/usb_hub.c might be relevant, not just: https://github.com/u-boot/u-boot/blob/master/common/usb.c For example, usb_hub.c is where usb_pgood_delay is involved. (My patch to enable my boot media assigns that, not that such helped Bob.) But I've not been able to uniquely identify all the specific identifiers for all the (relevant) "usb boot scan delays", although I'd expect that pgood_delay (and its usb_pgood_delay) would be considered an example. === Mark Millard marklmi at yahoo.com