On 2021/02/23 13:48, Marfaba Stewart wrote: > > On Sun, Feb 21, 2021 at 04:45:19PM +0000, marfabastewart wrote: > > > > [...] > > > > > and this is the output of sendbug -P on an APU2 > > > with the patch compiled in, after plugging in > > > the USB drive and rebooting. The USB drive is not > > > detected on the APU2 on boot, but the lines > > > from the patch are generated: > > > halted=1 > > > i=0 > > > output below: > > > > Thanks for the reports. > > > > I have tried various variants to change the halt/reset cycle slightly. > > But unfortunately nothing helps. It seems that when a certain kind > > of USB device (like the umass) is plugged in to the AMD Bolton > > controller, something goes not right with the device halt request. > > Thank you very much for looking into it. I emailed PCEngines > just now to see if they can provide any more information > about the possible differences between the USB controllers > on the APU2 and APU4. I will let you know when they reply. >
They use the same system-on-chip, the differences are in network/pcie configuration. The different firmware you are running on the two machines is much more likely to be the difference, you have: bios0: vendor coreboot version "4.0.7" date 02/28/2017 bios0: vendor coreboot version "v4.12.0.1" date 05/29/2020 Note that flashrom allows updating firmware on pcengines APU from OpenBSD. flashrom's pkg-readme file has everything you need to know.
