Thank everyone for the replies, However this solution isn't working for me. I have added the files to the proper places and edited the Config.txt file, I still do not have use of the USB 2.0 ports.
Its almost like the installer img, isn't looking at the Config.txt file. Thank you again Marty -----Original Message----- From: Klaus Küchemann <macipho...@googlemail.com> Sent: Monday, June 13, 2022 7:14 PM To: Mark Kettenis <mark.kette...@xs4all.nl>; John M Trott <john.m.tr...@jci.com>; Stuart Henderson <s...@spacehopper.org>; arm@openbsd.org Subject: Re: OpenBSD and Raspberry Pi CM4 and L=keyboard issue O.K, some first impressions:-) and a quick fix for John M Trotts USB_ issue : > Am 13.06.2022 um 23:44 schrieb Mark Kettenis <mark.kette...@xs4all.nl>: > > > otg_mode=1 > that doesn’t`t work (as John M Trott told correctly , it loses the hdmi-connection short after boot and no USB-keyboard) , When pressing the mouse button(mouse connected to Apple usb-keyboard), from the uart-console I got: -- (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? uhidev0 detached uhidev0 at uhub2 port 1 configuration 1 interface 0 "SIGMACHIP Usb Mouse" rev 1.10/1.10 addr 4 uhidev0: iclass 3/1 uhid at uhidev0 not configured uhidev0 detached uhidev0 at uhub2 port 1 configuration 1 interface 0 "SIGMACHIP Usb Mouse" rev 1.10/1.10 addr 4 uhidev0: iclass 3/1 uhid at uhidev0 not configured uhidev0 detached uhidev0 at uhub2 port 1 configuration 1 interface 0 "SIGMACHIP Usb Mouse" rev 1.10/1.10 addr 4 uhidev0: iclass 3/1 uhid at uhidev0 not configured uhidev0 detached — … while, as said, hdmi disconnects to black screen… SOLUTION for John M. Trott for the first(if no uart available) : I copied dwc2.dtbo & dwc-otg.dtbo from the rpi-git firmware files (in boot folder) to msdos boot/overlays & msdos root-partiton into the openbsd boot media (just to be sure it will be initialized somewhere:- ) (yes, freshly downloaded 7.1:-) and added : dtoverlay=dwc2,dr_mode=host to config.txt - now you will have a fine USB-keyboard on hdmi to start the installation.. While I’ll continue now on the uart-console to test my main interest : pcie ;-) Regards K. >> > >> Since the CM4 itself can be used with various carrier boards I think >> you may need to do some work with device trees or overlays to tell >> the OS what hardware it has, I can't give more detail than that myself >> though. > > ...some additional configuration is indeed needed. If the carrierboard > you're using does include USB3 support (the "official" > CM4IO board does) you can enable it by adding the line: > > otg_mode=1 > Am 14.06.2022 um 00:33 schrieb Mark Kettenis <mark.kette...@xs4all.nl>: > >> From: Klaus Küchemann <macipho...@googlemail.com> >> Date: Tue, 14 Jun 2022 00:00:55 +0200 >> >>> Am 13.06.2022 um 23:44 schrieb Mark Kettenis <mark.kette...@xs4all.nl>: >>> ... >>> USB3 support (the "official" >>> CM4IO board does) …. >> >> cm4 official i/o reference board doesn’t include USB3/xhci (only >> USB2). > > Actually there is an xhci(4) controller (and it gets enabled by > otg_mode=1), but only the USB 2.0 part of the controller is exposed > and available on the CM4IO board. > >> USB3 only by pcie carrier card, while i suspect pcie will fail if >> boot is fdt(not UEFI)-driven, > > PCIe should work if you use the u-boot version on the install media > (which is also available in the u-boot-aarch64 package. > > Cheers, > > Mark
