9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Mack Wallace <mackbw@mapinternet.com>
To: 9front@9front.org
Subject: Re: [9front] CM4 and USB ports
Date: Tue, 11 Jul 2023 01:55:48 +0000	[thread overview]
Message-ID: <0100018942a971ef-d3f903e0-d45a-486a-b945-67c0a3fbf718-000000@email.amazonses.com> (raw)
In-Reply-To: <01000189424eb99d-971534eb-a1fc-44dc-9bad-4873a31c8448-000000@email.amazonses.com>

Followed my hunch and added usbdwc into the pi4 config - both excluding and including usbxhcipci. However, all I got was the kernel to hang after CPU 2, 3 and 4 are detected. I’m probably missing something, as I vaguely remember having to change another file / device table when I added uartpl011 two years ago.. but don’t know… will dig into it tomorrow - and maybe someone will have some advice.

Regards,

mackbw



> On Jul 10, 2023, at 8:16 PM, Mack Wallace <mackbw@mapinternet.com> wrote:
> 
> I have a Super6c Pi cluster board and am trying to get 9front and the CM4 working with the two USB 2.0 ports that are on the board. They work fine with Raspberry Pi OS, but are unrecognized when booting 9front. I read that the CM4 USB port are disabled by default and require either dtoverlay=dwc2,dr_mode=host or otgmode=1 statements in config.txt.  I copied the CM4 device blobs, fixup and start files into the boot directory of 9front, with no luck. Since the Raspberry Pi OS worked, and wondering if this was an issue occurring before the kernel load, I copied the 9pi4 kernel onto my Raspberry Pi OS boot and explicitly called for it to be loaded instead of the linux kernel. Still no luck.
> 
> After looking through kmesg and dmesg, I realized that the USB host controller in this case is not on the PCI bus. I am wondering if that is the snag - and I’m not loading an appropriate driver for it.
> 
> Below is the kmesg from 9front and an excerpt from RPiOS dmesg
> Hoping someone else had run into this and it is an easy fix. 
> 
> mackbw
> 
> -KMESG-
> 127 holes free
> 0x004c0000 0x3b300000 988020736
> 988020736 bytes free
> 
> Plan 9
> Cpu0: 1500MHz ARM Cortex-A72 r0p3
> 8051M memory: 947M kernel data, 7104M user 31242M swap
> *pciwin: 0x600000000 0x640000000
> *pcidmawin: 0x400000000 0x600000000
> Pcireset: why link is down
> #l0: genet: 1000Mbps port 0xFFFFFFFFBD580000 irq 189 ea d83add090ba5
> Cpu2: 1500Mhz ARM Cortex-A72 r0p3
> Cpu3: 1500Mhz ARM Cortex-A72 r0p3
> Cpu4: 1500Mhz ARM Cortex-A72 r0p3
> bootfs: Sun Jun 25 15:14:05 GMT 2023
> fingerprint: a0cbdb2b4ebdcbc855d746ff06eb79ebfd01d97c
> #l0: phy0 id 600d84a2 oui 80361
> usb/usbd: no hubs
> 
> /dev/sdM0: BCM SD Host Controller 02 Version 10
> /dev/sdM0/data
> /dev/sdM0/ntfs
> /dev/sdM1: BCM SD Host Controller 02 Version 10
> /dev/sdM2: BCM SD Host Controller 02 Version 10
> Bootargs is (tcp, pls, il, local!device)[]
> 
> 
> -DMESG-
> [    1.353831] brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges:
> [    1.353868] brcm-pcie fd500000.pcie:   No bus range found for /scb/pcie@7d500000, using [bus 00-ff]
> [    1.353957] brcm-pcie fd500000.pcie:      MEM 0x0600000000..0x063fffffff -> 0x00c0000000
> [    1.354050] brcm-pcie fd500000.pcie:   IB MEM 0x0000000000..0x01ffffffff -> 0x0400000000
> [    1.355097] brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00
> [    1.355119] pci_bus 0000:00: root bus resource [bus 00-ff]
> [    1.355137] pci_bus 0000:00: root bus resource [mem 0x600000000-0x63fffffff] (bus address [0xc0000000-0xffffffff])
> [    1.355216] pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400
> [    1.355485] pci 0000:00:00.0: PME# supported from D0 D3hot
> [    1.359322] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
> [    1.359593] pci_bus 0000:01: supply vpcie3v3 not found, using dummy regulator
> [    1.359786] pci_bus 0000:01: supply vpcie3v3aux not found, using dummy regulator
> [    1.359907] pci_bus 0000:01: supply vpcie12v not found, using dummy regulator
> [    1.677581] brcm-pcie fd500000.pcie: link down
> [    1.677750] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
> [    1.677788] pci 0000:00:00.0: PCI bridge to [bus 01]
> [    1.677891] pci_bus 0000:01: busn_res: [bus 01] is released
> [    1.678762] pci_bus 0000:00: busn_res: [bus 00-ff] is released
> …
> [    1.794939] usbcore: registered new interface driver r8152
> [    1.795041] usbcore: registered new interface driver lan78xx
> [    1.795105] usbcore: registered new interface driver smsc95xx
> [    1.821348] xhci-hcd fe9c0000.xhci: xHCI Host Controller
> [    1.821387] xhci-hcd fe9c0000.xhci: new USB bus registered, assigned bus number 1
> [    1.821836] xhci-hcd fe9c0000.xhci: USB3 root hub has no ports
> [    1.821856] xhci-hcd fe9c0000.xhci: hcc params 0x0220fe65 hci version 0x110 quirks 0x0000000000010010
> [    1.821965] xhci-hcd fe9c0000.xhci: irq 33, io mem 0xfe9c0000
> [    1.822588] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
> [    1.822610] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
> [    1.822625] usb usb1: Product: xHCI Host Controller
> [    1.822638] usb usb1: Manufacturer: Linux 6.1.21-v8+ xhci-hcd
> [    1.822651] usb usb1: SerialNumber: fe9c0000.xhci
> [    1.823381] hub 1-0:1.0: USB hub found
> [    1.823451] hub 1-0:1.0: 1 port detected
> [    1.824217] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
> [    1.824602] dwc_otg: FIQ enabled
> [    1.824613] dwc_otg: NAK holdoff enabled
> [    1.824624] dwc_otg: FIQ split-transaction FSM enabled
> [    1.824642] Module dwc_common_port init
> [    1.825284] usbcore: registered new interface driver uas
> [    1.825376] usbcore: registered new interface driver usb-storage
> 


      reply	other threads:[~2023-07-11  2:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11  0:16 Mack Wallace
2023-07-11  1:55 ` Mack Wallace [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0100018942a971ef-d3f903e0-d45a-486a-b945-67c0a3fbf718-000000@email.amazonses.com \
    --to=mackbw@mapinternet.com \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).