#
#asahi-dev · 2026-07-20 23:03
JamesCalligeros[m]https://asahilinux.org/copyright/ study this thoroughly
#asahi-dev · 2026-07-20 23:02
JamesCalligeros[m]you can do so but keep the chat to #asahi-re and know that you wont be able to contribute m1n1 or kernel code directly if you do so
#asahi-dev · 2026-07-20 23:01
djyeah that’s what I was looking at so I can check the soc specific code
#asahi-dev · 2026-07-20 22:58
JamesCalligeros[m]but i think youll need to look at iboot and/or sptm for your machine too
#asahi-dev · 2026-07-20 22:58
JamesCalligeros[m]xnu is source-available
#asahi-dev · 2026-07-20 22:57
djquick question is it ok to disassemble the kernel to see how its handling the cpu init
#asahi-dev · 2026-07-20 22:31
djm4 pro cores load all fine right?
#asahi-dev · 2026-07-20 22:29
djit seems highly likely that it’s just the chickens preset which is botched for m5 pro/max
#asahi-dev · 2026-07-20 22:22
djlemme look into that
#asahi-dev · 2026-07-20 22:21
djooh okay perfect - thank you
#asahi-dev · 2026-07-20 22:21
yukachickens
#asahi-dev · 2026-07-20 22:21
yukayes
#asahi-dev · 2026-07-20 22:20
djsomething related to per-core execution/memory ownership state - is there anything like that which rings a bell?
#asahi-dev · 2026-07-20 22:16
djok, what if it doesn’t execute anything at all because the fetch is failing and it faults
#asahi-dev · 2026-07-20 22:05
djok the replacement def lands - verified it via read back but it just ends up at +0x200. tried to update held bit from +0 but it just seems like core never executes it and the pc read hack just reports +0x200 on the third sample. so loop and nop both didn’t work
#asahi-dev · 2026-07-20 21:42
djI had tried to replace +0 before but it still ended up at 0x200 as if the replacement didn’t work is it cause it’s chain loaded?
#asahi-dev · 2026-07-20 21:40
djI can’t get to read the pc first few cycles before it’s at +0x200, initial read was completely 0 but starting at rvbar+0 (reset) it ends up at exception vector. I’ll try making it an endless loop
#asahi-dev · 2026-07-20 21:38
yukayes but it seems 0x200 is indeed already something else, I don't know if that can be relocated just like that
#asahi-dev · 2026-07-20 21:37
chaos_princessor nop slide the entire suspected area?
#asahi-dev · 2026-07-20 21:37
yukathen observe if the pc still goes to the exception
#asahi-dev · 2026-07-20 21:37
yukaplace it at the expected entrypoint
#asahi-dev · 2026-07-20 21:37
yukayou could try to make an endless loop
#asahi-dev · 2026-07-20 21:35
djI think it’s the reset routine which faults -> ends up in exception
#asahi-dev · 2026-07-20 21:35
djwait can we just place something else there like that
#asahi-dev · 2026-07-20 21:35
yukaor maybe it's just borked and will always go into exception
#asahi-dev · 2026-07-20 21:35
yukaor what happens if we place something at 0x200
#asahi-dev · 2026-07-20 21:34
yukaso the question is where it does initially start
#asahi-dev · 2026-07-20 21:34
dj0x800 is expected indeed, that would be _start
#asahi-dev · 2026-07-20 21:34
djit’s the exception vector slot where it stops at
#asahi-dev · 2026-07-20 21:32
yukaI I thought it was 0x800
#asahi-dev · 2026-07-20 21:32
yukais +0x200 what we expect though?
#asahi-dev · 2026-07-20 21:31
djmy guess was it was getting into an exception state soon as you start it but I’m losing progress on that end, doesn’t seem to hold up..
#asahi-dev · 2026-07-20 21:31
yukahuh, amazing
#asahi-dev · 2026-07-20 21:30
djdid same for cpu0 to verify and it is a reliable way to get stable pc
#asahi-dev · 2026-07-20 21:29
djI’m reading the per-core uttdebug. read32(cpu-uttdbg-reg + 0x90). Sampling both halves I got the exact pc. I’m decently new to this, could be very off lol
#asahi-dev · 2026-07-20 21:29
core[m]yuka: core
#asahi-dev · 2026-07-20 21:24
yukacan you observe the pc of the secondary from the boot core?
#asahi-dev · 2026-07-20 21:15
yukadj: I don't really understand this: "I did see the pc it was just stuck at start" <- how do you see this?
#asahi-dev · 2026-07-20 21:13
yukawhoops
#asahi-dev · 2026-07-20 21:13
yukai
#asahi-dev · 2026-07-20 21:13
JamesCalligeros[m]yuka: docs kinda fell by the wayside by the time we got to t6020 unfortunately. Contributions welcome :3
#asahi-dev · 2026-07-20 20:36
djso maybe theyre not stuck in the reset start only?
#asahi-dev · 2026-07-20 20:35
djthe cores are released and pc changes from 0 to rvbar+0x200. 32 bit utt read exposes the real low pc. 64 bit read for some reason says 0
#asahi-dev · 2026-07-20 20:26
yukayou mean you put something directly _at_ rvbar which you can detect?
#asahi-dev · 2026-07-20 20:25
djinteresting, so cores do start on t6050 but pc doesn’t change but when I did a half read at pc I did see the pc it was just stuck at start
#asahi-dev · 2026-07-20 17:09
yukabesides the code
#asahi-dev · 2026-07-20 17:09
yukathere are no t602x pcie docs are there?
#asahi-dev · 2026-07-20 17:08
yukaAh fair
#asahi-dev · 2026-07-20 17:00
chaos_princessyours + my fixes + i intend to change regmap_spmi more
#asahi-dev · 2026-07-20 16:58
yukaare you using the patches from mildsunrise and me as a base or did you start from scratch?

plus ›