#
…

2021-09-28

00:27jhweruyuw has quit [Remote host closed the connection]
01:11riker77_ has joined #asahi-dev
01:16riker77 has quit [Ping timeout: 480 seconds]
01:16riker77_ is now known as riker77
01:30yuyichao_ has quit [Ping timeout: 480 seconds]
02:00yuyichao_ has joined #asahi-dev
02:40phiologe has joined #asahi-dev
02:44PhilippvK has quit [Ping timeout: 480 seconds]
08:28FireFox317 has joined #asahi-dev
10:57yuyichao_ has quit [Ping timeout: 480 seconds]
11:13yuyichao_ has joined #asahi-dev
11:34sjg1 has joined #asahi-dev
11:37sjg1I am new here, trying to get the UART going on a mini / air and am getting no output
11:37svenwhat cable are you using?
11:37sjg1macvdmtool seems to succeed though
11:38sjg1SS cable which I think meets the requirements
11:41svenhm.. so that looks like it successfully talked to the other side and if the cable supports usb 3.0 that should also be enough
11:41svenis the baudrate setup correctly? can't think of any other issue right now
11:42sjg1No, what is the baudrate?
11:43svenno idea what uboot uses by default. i think the default in m1n1 is 115200
11:46j_eyyou could try boot linux directly too, see if that works>
11:50sjg1Hmm so what are you using as a serial console program on MacOS?
11:51sjg1I tried: screen /dev/cu.debug-console 115200
11:51sjg1But I get invalid argument, as if it cannot set the serial rate. Also it seems odd to set that on a USB-C port which presumably goes faster
11:51sjg1Do you have the UART working in m1n1?
11:53sjg1Will try that
11:54sveni think the UART goes up to 1500000 or so
11:55svenlast time i had to look at the uart i used "picocom -b 115200 /dev/cu.debug-console" fwiw
12:01aleasto has joined #asahi-dev
12:03FireFox317sjg1: 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
12:04FireFox317but I might be incorrect tho
12:05sjg1Thank you, I suppose it was something wrong with 'screen'. picocom works:
12:05sjg1sudo picocom -q --omap crlf --imap lfcrlf -b 115200 /dev/tty.debug-console
12:05j_eysjg1: awesome
12:05svenyeah, it uses the SBU1/2 pins for the UART signal
12:06sjg1Yes it is awesome thanks again!
12:06j_eysjg1: and thanks for reviewing the uboot code!
12:14sjg1j_ey: :-) Interesting to do some ARM work for a change
12:15j_eysjg1: I can't disagree ;)
12:25sjg1So how does one get one of these? - "Flexible USB-PD Debug Interface (project name TBD)"
12:26j_eyI dont think you need that if you have vdmtool?
12:26sveni 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
12:29povik has quit [Quit: Page closed]
12:30kettenisopenssl speed
13:05sjg1sven: 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
13:06j_eyyou can also run u-boot under the hypervisor, which means you can use a non-mac to conenct to the vUART
13:14svenhrm, 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
13:15j_eyyou mean connecting m1linux <-> m1linux?
13:15svenyeah. or m1linux <-> m1n1/uboot/whatever-else
14:38sjg1j_ey: Do you have instructions for the hypervisor? I'm not even quite sure what it is
14:38j_eysjg1: are you using linux.py?
14:40j_eysjg1: something like python3 linux.py --compression=none u-boot-nodtb.bin t8103-j274.dtb right?
14:43sjg1j_ey: Ah OK yes I see. Will try it
14:44j_eylinux.py isnt using the hypervisor, but my link ^ will, and will give you uart (over a normal usb cable to a linux machine)
14:46kettenisquestion is whether the emulation of the s5l uart meets u-boot's expectations
14:46j_eyit works for me *shrug*
14:48FireFox317 has quit [Quit: Page closed]
14:50kettenisgood enough for me ;)
14:57sjg1j_ey: It sort-of works but seems to crash somewhere
14:59sjg1j_ey: Oh, sorry, that was the mini image. It boots fine, thank you
14:59j_eysjg1: awesome!
14:59j_eysjg1: so now, in another terminal you can use picocom with ttyAMA1
15:01j_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)
15:02j_eysorry ttyACM1
15:09psykose has quit [Remote host closed the connection]
15:10psykose has joined #asahi-dev
15:11sjg1j_ey: Having problems with that. Once U-Boot starts I see:
15:11sjg1[2724541.082113] usb 1-6: USB disconnect, device number 92
15:11sjg1[2724541.085569] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
15:12kettenisprobably need to remove the usb controller used by the hypervisor from the device tree
15:13kettenisotherwise u-boot will try to take control and mess things up
15:13j_eyoh yes, I forgot about that. I stripped the dts of a lot of stuff
15:14j_eyall the pcie stuff, all the dwc3 stuff
15:15kettenisu-boot isn not going to be very useful if you remove all hardware devices ;)
15:15j_eyi just wanted to try get it booting at all :P
15:16j_eyhttps://termbin.com/q4dc is what I deleted, but as kettenis said, maybe just work out which dw3 node you need to delete
15:19j_eykettenis: 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
15:20kettenisdoes that work?
15:21j_eynot without some m1n1 changes
15:22psykose has quit [Read error: No route to host]
15:22psykose has joined #asahi-dev
15:28sjg1j_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
15:29kettenisi've not tried using the hypervisor myself
15:32j_eyIm not sure about that either, I always managed to get the serial output
15:46jbowen has joined #asahi-dev
16:07aleasto has quit [Ping timeout: 480 seconds]
16:10jbowen has quit [Ping timeout: 480 seconds]
16:19nevexo has joined #asahi-dev
16:21cfleming has quit [Ping timeout: 480 seconds]
16:30aleasto has joined #asahi-dev
16:42jbowen has joined #asahi-dev
16:51jbowen has quit [Ping timeout: 480 seconds]
17:19jhweruyuw has joined #asahi-dev
17:28jbowen has joined #asahi-dev
17:43jbowen has quit [Ping timeout: 480 seconds]
18:10jbowen has joined #asahi-dev
19:56FireFox317 has joined #asahi-dev
20:00yuyichao has joined #asahi-dev
20:04yuyichao_ has quit [Ping timeout: 480 seconds]
20:16FireFox317 has left #asahi-dev [Leaving]
20:20FireFox317 has joined #asahi-dev
20:20FireFox317 has left #asahi-dev [#asahi-dev]
20:21FireFox317 has joined #asahi-dev
20:21jbowen has quit [Quit: leaving]
22:12aleasto has quit [Quit: Konversation terminated!]
22:40yuyichao_ has joined #asahi-dev
22:44yuyichao has quit [Ping timeout: 480 seconds]
22:53yuyichao_ has quit [Ping timeout: 480 seconds]
…