<sven>
last time i had to look at the uart i used "picocom -b 115200 /dev/cu.debug-console" fwiw
aleasto has joined #asahi-dev
<FireFox317>
sjg1: i think it actually uses 2 pins in the usb-c cable and actually transmits the uart signal over that, so then setting the baudrate does make sense
<FireFox317>
but I might be incorrect tho
<sjg1>
Thank you, I suppose it was something wrong with 'screen'. picocom works:
<sven>
yeah, it uses the SBU1/2 pins for the UART signal
<sjg1>
Yes it is awesome thanks again!
<j_ey>
sjg1: and thanks for reviewing the uboot code!
<sjg1>
j_ey: :-) Interesting to do some ARM work for a change
<j_ey>
sjg1: I can't disagree ;)
<sjg1>
So how does one get one of these? - "Flexible USB-PD Debug Interface (project name TBD)"
<j_ey>
I dont think you need that if you have vdmtool?
<sven>
i don't think that was ever finished (or, well, i guess it wasn't even started). most of us just use another m1 machine and the few who have a real serial interface built something themselves
povik has quit [Quit: Page closed]
<kettenis>
openssl speed
<sjg1>
sven: OK ta. The breakout board seems to be out of stock but will see if it comes back. I would prefer USB serial as I don't generally use Mac for development. I suppose I can use ssh to help
<j_ey>
you can also run u-boot under the hypervisor, which means you can use a non-mac to conenct to the vUART
<sven>
hrm, i guess i should also look into exposing that USB PD chip to linux userspace so that we can eventually also use linux running on the m1 for this
<j_ey>
you mean connecting m1linux <-> m1linux?
<sven>
yeah. or m1linux <-> m1n1/uboot/whatever-else
<sjg1>
j_ey: Do you have instructions for the hypervisor? I'm not even quite sure what it is
<j_ey>
sjg1: are you using linux.py?
<j_ey>
sjg1: something like python3 linux.py --compression=none u-boot-nodtb.bin t8103-j274.dtb right?
<sjg1>
j_ey: It sort-of works but seems to crash somewhere
<sjg1>
j_ey: Oh, sorry, that was the mini image. It boots fine, thank you
<j_ey>
sjg1: awesome!
<j_ey>
sjg1: so now, in another terminal you can use picocom with ttyAMA1
<j_ey>
(and in the original terminal where you used run_guest you can use ctrl+c to stop it running, and type reboot to.. reboot)
<j_ey>
sorry ttyACM1
psykose has quit [Remote host closed the connection]
psykose has joined #asahi-dev
<sjg1>
j_ey: Having problems with that. Once U-Boot starts I see:
<sjg1>
[2724541.082113] usb 1-6: USB disconnect, device number 92
<sjg1>
[2724541.085569] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
<kettenis>
probably need to remove the usb controller used by the hypervisor from the device tree
<kettenis>
otherwise u-boot will try to take control and mess things up
<j_ey>
oh yes, I forgot about that. I stripped the dts of a lot of stuff
<j_ey>
all the pcie stuff, all the dwc3 stuff
<kettenis>
u-boot isn not going to be very useful if you remove all hardware devices ;)
<j_ey>
i just wanted to try get it booting at all :P
<j_ey>
https://termbin.com/q4dc is what I deleted, but as kettenis said, maybe just work out which dw3 node you need to delete
<j_ey>
kettenis: I also did a weird thing and appended my linux kernel to the uboot image, so I didnt have to use the nvme code to load the kernel lol
<kettenis>
does that work?
<j_ey>
not without some m1n1 changes
psykose has quit [Read error: No route to host]
psykose has joined #asahi-dev
<sjg1>
j_ey: kettenis: I don't get a console when I leave the USB and dart USB nodes as 'disabled'. It waits for several seconds, appears to connect, but I see no output
<kettenis>
i've not tried using the hypervisor myself
<j_ey>
Im not sure about that either, I always managed to get the serial output