The weak performance of the bundled antenna is an issue, but I’m also looking for a way to connect the uConsole to a network in an environment that doesn’t provide WiFi.
One of the ways is to share the internet on macOS via a USB-C cable, which I did as shown below, but in the end I was unable to make any connections on macOS.
If someone could point out where I went wrong, I would greatly appreciate it.
modified /boot/config.txt from dtoverlay=dwc2,dr_mode=host to dtoverlay=dwc2
@Petrakis Thank you for your reply.
The latest version of driver is outdated and does not work on macOS 13.
And I built kext my own without signining & turned off system guard using csrutil in Safe Mode of macOS. BUT eventually I had to delete the kext because the whole macOS system stopped in networking. After delete the kext and reboot, everything work again.
@barry99705 Thank you for your suggestion. But I have only one Ethernet line for my macbook and I am trying to share its internet connection with uConsole. I’ll keep trying to make connection using USB-C.
The USB C port has data lines connected to it, which go directly to the SODIMM port for the core.
From what I can tell, it’s listed as “power only” because not all cores connect that line. From what I can tell, data should connect on the R01 core, but not the CM4 core, but I don’t know if there’s any official statement or anybody’s who’s tested them across the board. It could also not be USB 3 speeds.
If you want to check for yourself, you can follow the USB0_DP and USB0_DM wires from the USB section of the Mainboard schematic through to the specific core you’re using.
I saw somewhere in the forum, the usb-c does have some data lines with the pi4 but are missing some others… something about a CC1/CC2 pin to switch modes between host or device… and the default PiOS doesn’t do auto switching just in device mode…
On the CM4 adapter, for the J1 (DDR2 SODIMM), there are:
Pin 160: USB0_DP
Pin 162: USB0_DM
Pin 165: USB_DP
Pin 167: USB_DM
Pin 168: USB_OTGID
On the actual Compute Module, there are:
Pin 101: USB_OTGID
Pin 103: USB_DM
Pin 105: USB_DP
No matches for USB0_DP or USB0_DM
On the Mainboard for J1 (the other side of the DDR2 SODIMM):
Pin 168: USB_OTGID is wired to ground through a 1K resistor.
On the Mainboard for US01 (the internal USB hub), there are:
USB_DP and USB_DM enter the USB hub labeled as DP0 and DM0, respectively.
Output as DP1/DM1 through DP4/DM4.
On the Mainboard for JS01 (the Type-c port), there are:
Pin B6: USB0_DP
Pin B7: USB0_DM
From what I can tell, this means it’s physically impossible to change the USB_OTGID value (which seems to be associated with the internal hub, anyways), or for the USB-C port data connection to reach the CM4.