Date: Sat, 18 Dec 2021 17:19:49 -0800 From: Mark Millard via freebsd-arm <freebsd-arm@freebsd.org> To: bob prohaska <fbsd@www.zefox.net> Cc: Free BSD <freebsd-arm@freebsd.org> Subject: Re: Dealing with slow USB disks, was: Re: Saving environment variables in u-boot Message-ID: <772E3794-B762-429F-B2A5-F504EA293C59@yahoo.com> In-Reply-To: <20211218223543.GA9484@www.zefox.net> References: <20211216180704.GA4173@www.zefox.net> <214132DD-A095-4349-BB81-B79CB8CF6B0C@yahoo.com> <20211217013613.GA4452@www.zefox.net> <E2F6D50B-694A-4108-BD84-C85BC96AD832@yahoo.com> <20211218005946.GA7670@www.zefox.net> <5C44D0E6-2FF1-4EEB-B21A-83333D6FCF46@yahoo.com> <9D416106-660F-40BB-98D2-1354B53D2FEF@yahoo.com> <EC6CC83C-BC0A-4A12-866A-9FA24083FF7E@yahoo.com> <20211218223543.GA9484@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Dec-18, at 14:35, bob prohaska <fbsd@www.zefox.net> wrote: > . . . > I'm becoming sceptical that usb_pgood_delay is relevant, > after many reboots this morning. Indeed, I can't detect > that the delays have a useful (or harmful) effect. > They do seem to be active, in that pauses in serial console > output change roughly in proportion to values set. > I even tried putting usb_pgood_delay=20000 in config.txt, Wrong place: usb_pgood_delay is only for U-Boot, not the RPi* firwmare. It does nothing useful in config.txt on an RPi* . As stands the only ways I know to supply usb_pgood_delay to U-Boot are: A) Type its assignment into the U-Boot prompt. B) Build the *u-boot*.bin in question with the value assigned at build time. To my knowledge (B) has yet to be tried. Any test of usb_pgood_delay that did not involve (A) was a wrong-context test and does not apply. That includes any testing about seconds vs. milliseconds. I expect that usb_pgood_delay is in milliseconds in U-Boot. > hoping that the firmware might pass on the value. No luck. > > Usb reset finds the disk after one to about six tries, seemingly > at random, regardless of > usb_pgood_delay > bootcode.bin_delay ".bin"? Wrong name. use: bootcode_delay= > or > boot_delay > So far, the disk has never been recognized as a mass storage device > on the first try. > > I also tried putting > program_usb_boot_timeout=1 in config.txt, to no avail. The line seemed > to help on a Pi3 with a different usb-sata adapter and the same kind of > disk. It will probably be a while before I look at http://www.zefox.net/~fbsd/slow_usb_notes but it may be that some experiments need to be replaced/re-run based on usb_pgood_delay being provided in the wrong place and the bootcode.bin_delay wrong name being used. === Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?772E3794-B762-429F-B2A5-F504EA293C59>