Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Sep 2022 20:33:33 +0200
From:      =?utf-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com>
To:        bob prohaska <fbsd@www.zefox.net>, freebsd-arm@freebsd.org, Mark Millard <marklmi@yahoo.com>
Subject:   Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it
Message-ID:  <4154AFCB-7428-4005-843A-4EF8C0EBCCB8@googlemail.com>
In-Reply-To: <67C09E9F-AD1D-4D0D-9E6F-9C1B046D8952@googlemail.com>
References:  <20220921154240.GA37735@www.zefox.net> <8CC2A42B-21AC-44C6-BD02-44D320CADF63@yahoo.com> <20220921175026.GA45144@www.zefox.net> <5DB9C93B-B9E1-418D-ABA3-8A0CFCE85C0F@yahoo.com> <3781CF46-C4F7-4579-8655-B7558B724C0A@yahoo.com> <20220922014500.GA46697@www.zefox.net> <20220925160531.GA63213@www.zefox.net> <DBD238AA-8C65-46D2-87CC-A9875C6959BF@yahoo.com> <20220925193415.GA63733@www.zefox.net> <3D6CF13E-261D-41D2-AC5B-923C0BF54087@yahoo.com> <20220927160328.GA71742@www.zefox.net> <67C09E9F-AD1D-4D0D-9E6F-9C1B046D8952@googlemail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

> Am 27.09.2022 um 19:58 schrieb Klaus K=C3=BCchemann =
<maciphone2@googlemail.com>:
>=20
>=20
>> Am 27.09.2022 um 18:03 schrieb bob prohaska <fbsd@www.zefox.net>:
>>=20
>> 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.
>=20
> you can add the following to common/usb.c (e.g. insert in line 44):
>=20
> #define DEBUG
>=20
> --
>=20
> that should then print out all debug functions inside the usb.c file =
to the console=20
> after recompilation of u-boot.
>=20
> Regards
>=20
> Klaus

I saw there is  /*#include <log.h>*/ available in usb.c=20
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 :=20
electrical problem(of the Pi itself)  which could perhaps be fixed by  =
manipulating the scan delay time .

Regards

Klaus





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4154AFCB-7428-4005-843A-4EF8C0EBCCB8>