Date: Fri, 30 Sep 2022 09:58:18 -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.org, Hans Petter Selasky <hps@selasky.org> Subject: Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it Message-ID: <924ED901-F9EB-4CFE-8376-1C2653FB6EBE@yahoo.com> In-Reply-To: <7A431698-1A8C-44BA-AFA2-EF5BAA69574F@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>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Sep-30, at 09:40, Klaus K=C3=BCchemann = <maciphone2@googlemail.com> wrote: >> Am 30.09.2022 um 02:27 schrieb bob prohaska <fbsd@www.zefox.net>: >> =E2=80=A6=E2=80=A6 >> . >> I just captured an example now. Because of the file=E2=80=99s >> size it's at=20 >> http://nemesis.zefox.com/~fbsd/=20 >> in a file named=20 > =E2=80=A6=E2=80=A6.. >=20 > O.K., you now have extended logs..fine... > comparing success/fail we see: >=20 > -fail--- This is for: Manufacturer=20 Product U-Boot Root Hub SerialNumber=20 bind node usb1@1 > port 1 returns 0 > pgood_delay=3D2000ms 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. > devnum=3D1 poweron: query_delay=3D2000 connect_timeout=3D3000 > usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 = length 0x4 > Port 1 Status 311 Change 1 > devnum=3D1 port=3D1: USB dev found > usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 = length 0x4 > portstatus 311, change 1, 1.5 Mb/s > ... > STAT_C_CONNECTION =3D 0 STAT_CONNECTION =3D 1 USB_PORT_STAT_ENABLE 0 > Cannot enable port 1 after 5 retries, disabling port. > Maybe the USB cable is bad? > cannot reset port 1!? >=20 > -success---- > port 1 returns 0 > pgood_delay=3D2000ms Same point again. > devnum=3D1 poweron: query_delay=3D2000 connect_timeout=3D3000 > usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 = length 0x4 > Port 1 Status 511 Change 1 > devnum=3D1 port=3D1: USB dev found > usb_control_msg: request: 0x0, requesttype: 0xA3, value 0x0 index 0x1 = length 0x4 > portstatus 511, change 1, 480 Mb/s > -- >=20 > So we now know that when it fails, the issue consists of an = underpowered port1 of the USB-Hub > ( what doesn't necessarily mean that the hub itself is the root cause) >=20 > We see the values of query_delay / connect_timeout / pgood_delay=20 > and some informative (device specific)problem descriptions ( as = comments) > in the file :=20 > common/usb_hub.c > ...many possibilities to manipulate delays / max retries / force = resets or whatever, even the log message: "Maybe the USB cable is bad?" = is interesting ;-)... >=20 > I would consider to "force" the King of USB to read this file contents = (usb_hub.c + usb.c): > So consequently I quietly step out of the discussion again=20 > and put HPS to CC :-) lol >=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?924ED901-F9EB-4CFE-8376-1C2653FB6EBE>