#
#asahi-re · 2025-04-06 13:18
mischa85there's also cluster-ctl-offset = 131072
#asahi-re · 2025-04-06 13:18
mischa85yeah there are quite some new values compared to t6031
#asahi-re · 2025-04-06 13:14
nickchanback then we bruteforce
#asahi-re · 2025-04-06 13:14
nickchanso it's in the adt these days interesting
#asahi-re · 2025-04-06 13:13
nickchanmischa85: yeah
#asahi-re · 2025-04-06 13:12
mischa85you mean this one? misc-cores-offset = 557056 -> 0x88000 (same as m3)
#asahi-re · 2025-04-06 13:11
nickchanhave you tried every 0x4000 from pmgr base to a max of 0x100000?
#asahi-re · 2025-04-06 13:10
nickchanmischa85: maybe start offset is wrong?
#asahi-re · 2025-04-06 13:07
nickchanokay so it's iboot that did that
#asahi-re · 2025-04-06 13:07
mischa85nickchan: no for sure not. just the shell on bringup m1n1
#asahi-re · 2025-04-06 13:06
nickchanmischa85: you have not attempted to start secondaries in the same boot right
#asahi-re · 2025-04-06 13:04
svenor does it lock automatically after writing to it these days?
#asahi-re · 2025-04-06 13:03
sventhe only weird part is that the reg is locked
#asahi-re · 2025-04-06 13:03
svenyeah
#asahi-re · 2025-04-06 13:03
nickchansven: yep and it is secondary entry point as well
#asahi-re · 2025-04-06 13:02
svenm1n1's entrypoint is 0x800 from its base
#asahi-re · 2025-04-06 13:01
nickchanbut on older socs bit 11 can be configured
#asahi-re · 2025-04-06 13:01
svenbut i don't think we lock that reg down
#asahi-re · 2025-04-06 13:01
nickchanit might be because of alignment requirements on that reg
#asahi-re · 2025-04-06 13:00
svendoesn't m1n1 set that to its reset vectors as well?
#asahi-re · 2025-04-06 12:59
nickchanah wait
#asahi-re · 2025-04-06 12:59
nickchanit's almost as if it's designed for m1n1
#asahi-re · 2025-04-06 12:58
nickchanbecause entry point is +0x800
#asahi-re · 2025-04-06 12:58
nickchanokay so that's right at m1n1 base and apple goes out of the way to make sure it's not the entry point *either*
#asahi-re · 2025-04-06 12:57
mischa85m1n1 base: 0x10005d68000
#asahi-re · 2025-04-06 12:57
svenyeah, could be that it was just locked by m1n1
#asahi-re · 2025-04-06 12:57
svenalso, where is m1n1 located?
#asahi-re · 2025-04-06 12:57
nickchanmischa85: hmmm... is that inside m1n1?
#asahi-re · 2025-04-06 12:56
nickchanokay so supposed put code at 0x10005d68000 and supposedly all other cores would end up there
#asahi-re · 2025-04-06 12:56
svenbut that explains why you had issues bringing up the other cores
#asahi-re · 2025-04-06 12:56
svennot inside CTRR though
#asahi-re · 2025-04-06 12:55
svenhah
#asahi-re · 2025-04-06 12:55
nickchansven: it's all locked!
#asahi-re · 2025-04-06 12:55
mischa85cpu0-9: 0x110010005d68001, cpu 10-16: 0x210010005d68001
#asahi-re · 2025-04-06 12:53
mischa85i'll check
#asahi-re · 2025-04-06 12:53
mischa85cpu4
#asahi-re · 2025-04-06 12:52
nickchannot sure which core m4 boots on but check that as well
#asahi-re · 2025-04-06 12:52
nickchanmischa85: maybe do read64(u.adt["/cpus/cpu1"].cpu_impl_reg[0]) following sven's advice
#asahi-re · 2025-04-06 12:35
svenespecially for the secondary cores
#asahi-re · 2025-04-06 12:35
sveni'd take a look at that value and see if it happens to point into one of these CTRR regions
#asahi-re · 2025-04-06 12:35
nickchanthat should be the IORVBAR
#asahi-re · 2025-04-06 12:35
nickchansven: /cpus/cpu<n>/cpu-impl-reg
#asahi-re · 2025-04-06 12:34
svenalso dump that cpu start region and look for the IORVBAR value or however that's called
#asahi-re · 2025-04-06 12:33
svenif this was my machine I'd dump these regions and take a look at them, but since they contain apple code we shouldn't share them unfortunately . they seem to all be rather large though.
#asahi-re · 2025-04-06 12:32
nickchansven: what do you think
#asahi-re · 2025-04-06 12:31
nickchanapple used 3 CTRR regions for it but previous chips can only do 2
#asahi-re · 2025-04-06 12:31
nickchanso like
#asahi-re · 2025-04-06 12:31
nickchananyways
#asahi-re · 2025-04-06 12:31
mischa85correct
#asahi-re · 2025-04-06 12:31
mischa85yes these are the same for EL2

plus ›