Date: Fri, 30 Sep 2022 11:36:54 -0700 From: Mark Millard <marklmi@yahoo.com> To: =?utf-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com> Cc: bob prohaska <fbsd@www.zefox.net>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it Message-ID: <8CE490A2-B512-4170-95BC-D0584F2B254A@yahoo.com> In-Reply-To: <5F180C78-BC07-4605-A042-0BEC8A6FD185@googlemail.com> References: <A8C2BA4E-4520-4B34-9614-DDC4D8BEB097@yahoo.com> <6AA65AE6-41F1-405F-A592-7D641EA4C9CF@yahoo.com> <E3A1C678-8C47-4283-9F9F-4C9011DB8A2B@yahoo.com> <20220929054120.GA77803@www.zefox.net> <D7A62820-4928-49F0-8387-C1E6D998B121@yahoo.com> <ABFBD0E6-8A9B-4C99-84DF-BF398F23678A@yahoo.com> <20220929151926.GA80020@www.zefox.net> <F316420B-C7AF-4131-9734-06117FFE212D@yahoo.com> <20220929170927.GB80020@www.zefox.net> <6C5019EC-B4A8-448F-9A85-4A98BC46F7DD@yahoo.com> <20220930002742.GA81169@www.zefox.net> <7A431698-1A8C-44BA-AFA2-EF5BAA69574F@googlemail.com> <924ED901-F9EB-4CFE-8376-1C2653FB6EBE@yahoo.com> <97AB11F6-2F4D-4026-8A96-50FC68B6EF8C@googlemail.com> <ED81813C-6F25-4751-BBCA-BC711684B219@yahoo.com> <5F180C78-BC07-4605-A042-0BEC8A6FD185@googlemail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Sep-30, at 10:25, Klaus K=C3=BCchemann = <maciphone2@googlemail.com> wrote: > Am 30.09.2022 um 19:13 schrieb Mark Millard <marklmi@yahoo.com>: >>=20 >> On 2022-Sep-30, at 10:07, Klaus K=C3=BCchemann = <maciphone2@googlemail.com> wrote: >>=20 >>>=20 >>>> Am 30.09.2022 um 18:58 schrieb Mark Millard <marklmi@yahoo.com>: >>>> =E2=80=A6 >>>> . >>>> The 2000ms is from the U-Boot build setting usb_pgood_delay >>>> explicitly: Bob is using the part of the patch that I use to >>>> get my every different devices to boot. >>>>=20 >>>>> =E2=80=A6 >>> Ah, O.K., no clue if giving e.g. 3000 instead of 2000 or so will = help, >>> But if Bob got improvements by setting your values ,=20 >>> I would consider continuing to manipulate that values. >>>=20 >>=20 >> It is more like they made no differences so we have not been >> bothering to eliminate them. That way I can build and test >> the build in my context, still with a bootable environment >> for my media. >>=20 >> =3D=3D=3D >> Mark Millard >> marklmi at yahoo.com >=20 >=20 > O.K., thanks for info=E2=80=A6 > what we know now is that port1 of the Hub Which "the"? The Hub in question is internal to the RPi3B. It also shows up on my RPi3B with no external hubs involved. (But I've never had the failure mode occur.) Manufacturer=20 Product U-Boot Root Hub SerialNumber=20 bind node usb1@1 It is a hub with 5 ports, one associated with the EtherNet port and 4 for plugging things in. Or, that is my understanding. I've little clue what would interfere with its operation in this specific way. > is (sometimes) underpowered ( 1,5MB), has to be 480MB instead.. > While even a broken USB cable can of course trigger this issue , > I guess this is not the first time that an USB hub-port fails by = underpower on those dev boards or elsewhere, > So `ring ring` HPS,... how to force inject more power to port1 in = /common/usb_hub.c ? :-) Ha Ha=20 =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8CE490A2-B512-4170-95BC-D0584F2B254A>