#asahi-dev · 2026-01-20 14:56
yukanow it hangs at cpuhp_setup_state#asahi-dev · 2026-01-20 14:55
yuka*parameters#asahi-dev · 2026-01-20 14:54
yukalikely fixed one mistake in my device tree's aic node parameter#asahi-dev · 2026-01-20 14:54
yukaI was able to map the uart mmio ranges in early boot and use debug_putc after enable_mmu, traced up to aic init#asahi-dev · 2026-01-20 14:53
yukamade some progress on t8123:#asahi-dev · 2026-01-18 16:31
yukaif the initial baud rate on the other side is not 1.5M, it will always fail get the iodev_whami(), and then wrongly assume it's already set to 1.5M#asahi-dev · 2026-01-18 16:31
yuka(and adjust the baudrate)#asahi-dev · 2026-01-18 16:31
yukaI still don't see any way for proxyclient to work if the initial baud rate does not match (before even attempting to check)#asahi-dev · 2026-01-18 16:21
yukathat works#asahi-dev · 2026-01-18 16:21
yukaSo, if I use a stage 1 m1n1 with usb support (no BRINGUP), I can connect via usb and set the uart baud rate to 115200, and then hardcode it to the same in bootstrap_port()#asahi-dev · 2026-01-18 16:16
yukayes, still 0xc on t8132 too#asahi-dev · 2026-01-18 16:03
yukait's already not happening#asahi-dev · 2026-01-18 16:02
yukamaybe I don't understand how baud rates work#asahi-dev · 2026-01-18 16:02
yukain my case, it does the iodev_whoami(), which fails so it sets do_baud = False and assumes 1500000. If I set this to anything else, it would mismatch the baud rate configured on the m1n1 side, no?#asahi-dev · 2026-01-18 16:01
yukaso it will never work on devices where 150000 baud rate does not work?#asahi-dev · 2026-01-18 15:57
yukaI'm not sure how it works, how does the proxyclient tell m1n1 to adjust its baudrate if the m1n1 receiving baud rate is initially wrong?#asahi-dev · 2026-01-18 15:55
yukaI don't see m1n1 configuring its local baud rate to anything by default#asahi-dev · 2026-01-18 15:54
yukawithout cpufreq#asahi-dev · 2026-01-18 15:54
yukamaybe t8132 is too slow for 1500000?#asahi-dev · 2026-01-18 15:46
yukafull output: https://termbin.com/zpil#asahi-dev · 2026-01-18 15:41
yukaNo, I just tested it with my Asahi machine, the uart works bidirectionally#asahi-dev · 2026-01-18 15:40
yukabut maybe the other direction does not work#asahi-dev · 2026-01-18 15:39
yukawith picocom#asahi-dev · 2026-01-18 15:39
yukaI do see the boot log from m1n1#asahi-dev · 2026-01-18 15:38
yukathe noop command#asahi-dev · 2026-01-18 15:36
yuka> m1n1.proxy.UartTimeout: Expected 1 bytes, got 0 bytes#asahi-dev · 2026-01-18 15:35
yukasadly, proxyclient still does not work#asahi-dev · 2026-01-18 15:35
yukamade the central scrutinizer firmware present two serial ports for control commands and the uart#asahi-dev · 2026-01-18 15:35
yukahttps://cyberchaos.dev/yuka/cs-sw/-/commit/35b9d757c9885900be00d4b98c18572c7eb72131#asahi-dev · 2026-01-17 12:44
yukabut the proxy protocol does not work over it because it also has the central scrutinizer control stuff mixed in#asahi-dev · 2026-01-17 12:43
yukaI can see the serial output from m1n1#asahi-dev · 2026-01-17 12:43
yukait does do serial passthrough#asahi-dev · 2026-01-17 12:40
yukathanks for confirming#asahi-dev · 2026-01-17 12:27
yukaFor me, I can open the ttyACM device in screen/picocom and see that it's running the proxy, but trying to run the proxyclient on it yields this: https://termbin.com/adby#asahi-dev · 2026-01-17 12:26
yukaHow do you use the m1n1 proxyclient on the central scrutinizer serial?#asahi-dev · 2026-01-17 01:30
yukaI see#asahi-dev · 2026-01-17 01:09
yukaSo possibly not available out of the box, but it should be possible to be inspired by this code to make my own debug_putc work after mmu init#asahi-dev · 2026-01-17 01:08
yukaThere is code related to it in the arm64 head.S#asahi-dev · 2026-01-17 01:07
yukaIs this stacktrace from earlycon output?#asahi-dev · 2026-01-17 00:58
yukaIt seems CONFIG_DEBUG_LL would be useful for getting even earlier uart#asahi-dev · 2026-01-17 00:55
yukaJust getting no output when starting the kernel?#asahi-dev · 2026-01-17 00:49
yuka(Or maybe enabling the mmu is preventing debug_putc from working afterwards)#asahi-dev · 2026-01-17 00:47
yukaWith the help of debug_putc, I traced it into the __enable_mmu function in head.S of the kernel#asahi-dev · 2026-01-17 00:47
yukaAs a reminder, I was not seeing any output after "Vectoring to next stage" despite having the serial console enabled in the device tree and setting earlycon#asahi-dev · 2026-01-17 00:46
yukaI debugged my minimal device tree with a single cpu core on t8132 baremetal further. Copied the debug_putc into the kernel and added debug prints in the very first code of the kernel.#asahi-dev · 2026-01-15 20:31
yukaasahi-6.18.4-1 & asahi-6.18.5-1#asahi-dev · 2026-01-15 20:31
yukaIt is tagged#asahi-dev · 2026-01-15 20:30
yuka*request an update#asahi-dev · 2026-01-15 20:30
yukaThen I would request of the alx.sh payload so that we can ship 6.18 installer isos of NixOS ;)#asahi-dev · 2026-01-15 20:29
yukadwc3-apple 702280000.usb: probe with driver dwc3-apple failed with error -22