Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it
- Reply: Mark Millard : "Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it"
- Reply: bob prohaska : "Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it"
- In reply to: Klaus_Küchemann : "Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 27 Sep 2022 18:33:33 UTC
> Am 27.09.2022 um 19:58 schrieb Klaus Küchemann <maciphone2@googlemail.com>: > > >> Am 27.09.2022 um 18:03 schrieb bob prohaska <fbsd@www.zefox.net>: >> >> 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 . Regards Klaus