#asahi-dev · 2025-03-22 23:25
mischa850x6dd0000#asahi-dev · 2025-03-22 23:25
chaos_princessout of?#asahi-dev · 2025-03-22 23:24
mischa85again, 0x2187450#asahi-dev · 2025-03-22 23:22
mischa85first try stopped at 0x2187450, going to try a second time to check if it's consistent#asahi-dev · 2025-03-22 23:12
chaos_princesscan you modify the upload code to give you percentage process, to see when exactly it goes wrong#asahi-dev · 2025-03-22 23:11
chaos_princessamx problably no longer exists on m4, since they have sme#asahi-dev · 2025-03-22 23:11
mischa85but now i'm getting a serialexception from serialposix.py#asahi-dev · 2025-03-22 23:10
mischa85had to disable amx and guest ap keys part tho#asahi-dev · 2025-03-22 23:10
mischa85alright progress. i can get to to the Loading kernel image (0x6dd0000 bytes)... part#asahi-dev · 2025-03-22 22:55
mischa85ack, on it#asahi-dev · 2025-03-22 22:55
chaos_princessit will most likely blow up, but hopefully you will be able to capture msr write traces before it does#asahi-dev · 2025-03-22 22:55
chaos_princessimo, skip memory mapping too, and launch xnu as-is#asahi-dev · 2025-03-22 22:53
mischa85i just gotta accept my m1n1 branch is a total mess for now#asahi-dev · 2025-03-22 22:49
mischa85that's a nifty idea#asahi-dev · 2025-03-22 22:49
PaulFertserGood old strace can give a quick hint about the differences between minicom and pyserial, sometimes it's faster to view the log of syscalls to see what exactly happens there.#asahi-dev · 2025-03-22 22:49
fl0_idout of context waterfalling sounds nice haha#asahi-dev · 2025-03-22 22:49
fl0_idsounds good :)#asahi-dev · 2025-03-22 22:48
mischa85at least now i can run it on 1.5 mbaud again which will come in handy once we're actually goint to transfer that xnu blob#asahi-dev · 2025-03-22 22:48
mischa85still waterfalls after Mapping MMIO range so let's see what's causing that#asahi-dev · 2025-03-22 22:47
mischa85it's consistenly booting on cpu4#asahi-dev · 2025-03-22 22:46
mischa85at least i can now get to disabling enough m1n1 so i can run xnu kernel on hv#asahi-dev · 2025-03-22 22:46
mischa85yes i am back on my trusty macbook which consistently gave me errors on the cleaned up m1n1 i had. only wanted to work on 115200 kbps. now back on the mess i made which is working fine. probably still not on my main rig on linux but i can't have too many variables right now#asahi-dev · 2025-03-22 22:44
fl0_idhttps://pyserial.readthedocs.io/en/latest/pyserial_api.html#asahi-dev · 2025-03-22 22:44
fl0_idmischa85 prob you are a bit further now, but pyserial docs say "The port is immediately opened on object creation, when a port is given. It is not opened when port is None and a successive call to open() is required." so the open() is in pyserial presuambly#asahi-dev · 2025-03-22 22:36
fl0_idmischa85 there is this... https://www.mypy-lang.org/ - it's like static types based on python type hints#asahi-dev · 2025-03-22 18:25
mischa85so confused#asahi-dev · 2025-03-22 18:25
mischa85where is the pyserial open() call then#asahi-dev · 2025-03-22 18:25
mischa85how does that syntax even make sense#asahi-dev · 2025-03-22 18:25
mischa85it sets a "device =" as a environment variable but then goes on to say device = Serial(serial.devpath, baud)#asahi-dev · 2025-03-22 18:22
mischa85i cannot stand python sometimes#asahi-dev · 2025-03-22 18:22
mischa85every 4 tries it receives some data but the checksum is wrong#asahi-dev · 2025-03-22 18:21
mischa85minicom works totally fine#asahi-dev · 2025-03-22 18:21
mischa85yeah it's probably an rtscts or dsrdtr thing, but i just cannot get my head around the python code in proxy.py, where does it even open the port and how are the settings parsed#asahi-dev · 2025-03-22 18:20
fl0_idmischa85 which thing are you having trouble with? the pyserial that the proxyclient uses with picocom or which part? Pretty sure I used it from Linux and it worked, maybe I can check it there#asahi-dev · 2025-03-22 18:15
dylantayloroh, cool to see that's up already. I guess it's just staticly published to github pages. Pretty clean design.#asahi-dev · 2025-03-22 17:28
mischa85so i can actually use the cs on my main rig and test to see if hv works#asahi-dev · 2025-03-22 17:27
nicolas17I was going to submit the newest devices but I waited until we actually knew details on M3 Ultra, then I forgot >.>#asahi-dev · 2025-03-22 17:27
mischa85just trying to fix this stupid pyserial thing which somehow doesn't work on linux but does on macos#asahi-dev · 2025-03-22 17:26
nicolas17dylantaylor: https://asahilinux.org/docs/hw/devices/device-list/#asahi-dev · 2025-03-22 17:22
mischa85yep, cpu4. everest core#asahi-dev · 2025-03-22 17:18
jannaushould be visible from the device adt. the running core has 'status = "running"';#asahi-dev · 2025-03-22 17:08
mischa85if i'm interpreting this correctly: https://esr.arm64.dev/midr.html?#0x611f0591#asahi-dev · 2025-03-22 17:08
mischa85but i think i has e and p cores swapped earlier, MIDR is 0x611f0591 which i think suggest the e-cores are 0x59 and p-cores are 0x60#asahi-dev · 2025-03-22 17:05
mischa85i think i've seen it having core 0.4 started up#asahi-dev · 2025-03-22 17:04
jannaudoesn't m4* start on a performance core like m3?#asahi-dev · 2025-03-22 16:43
sventhe chicken setup happens fairly early inside xnu so you don’t even need many thing to work #asahi-dev · 2025-03-22 16:41
mischa85just using the core we got powered on for free is not something i tried yet#asahi-dev · 2025-03-22 16:40
mischa85ok i'll take out smp_start_secondaries() completely#asahi-dev · 2025-03-22 16:36
chaos_princessnot like you can, but in the sense that you should skip that code#asahi-dev · 2025-03-22 16:36
chaos_princessjust make sure you are not starting other ones