#asahi-re · 2026-07-02 17:05
mischa85starcatmeow: is nvme-secure-bar present in your ADT?#asahi-re · 2026-07-02 16:33
mischa85right. that makes sense. might be worth tracing ans bringup from xnu on t6040/t6041#asahi-re · 2026-07-02 16:22
mischa85should SART also cover the low range the firmware DMA's to?#asahi-re · 2026-07-02 16:22
mischa85yeah, before any command, no identify sent.#asahi-re · 2026-07-02 16:16
mischa85so the million dollar question is: what programs the coastguard?#asahi-re · 2026-07-02 16:15
mischa85*iommu#asahi-re · 2026-07-02 16:15
mischa85looks like the coastguard uimmu translation for the fw's FTL DMA never gets set up#asahi-re · 2026-07-02 16:14
mischa85StanfordAppliedCyber[m]: got PCIe up on t6041, back on NVMe now. admin queue works from el2 via the +0x40000000 alias, but the fw's cold-boot FTL gives NVME_PERM_ERR before any host command #asahi-re · 2026-07-01 17:42
mischa85hmmm. maybe i need to apply the tunables for things to work out#asahi-re · 2026-07-01 16:39
mischa85now onto ans3 firmware shenanigans#asahi-re · 2026-07-01 16:39
mischa85i was trying to write to the admin-queue registers directly, the alias +0x40000000 works#asahi-re · 2026-07-01 10:18
mischa85StanfordAppliedCyber[m]: so i can't tell if there's a fabric/dart setup that opens the reg for plain el2 or if it's strictly the guarded attribute#asahi-re · 2026-07-01 10:17
mischa85StanfordAppliedCyber[m]: a plain el2 str to bar+0x24 faults here (L2C_ERR 0x80)#asahi-re · 2026-07-01 10:17
mischa85StanfordAppliedCyber[m]: when you write the admin-queue regs from el2, is guarded/gxf state actually active during the store, or is it a genuinely plain el2 str?#asahi-re · 2026-06-30 22:34
mischa85exit#asahi-re · 2026-06-30 22:30
mischa85yes i feel close to figuring it out. i know what to try next#asahi-re · 2026-06-30 22:26
mischa85hmmm. the plot thickens#asahi-re · 2026-06-30 22:20
mischa85are those the standard offsets or did they move on ans3?#asahi-re · 2026-06-30 22:12
mischa85on m4, are the nvme admin-queue regs writable from el2, or only from gl2?#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:12
mischa85you mean this one? misc-cores-offset = 557056 -> 0x88000 (same as m3)#asahi-re · 2025-04-06 13:07
mischa85nickchan: no for sure not. just the shell on bringup m1n1#asahi-re · 2025-04-06 12:57
mischa85m1n1 base: 0x10005d68000#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:31
mischa85correct#asahi-re · 2025-04-06 12:31
mischa85yes these are the same for EL2#asahi-re · 2025-04-06 12:29
mischa85uh#asahi-re · 2025-04-06 12:29
mischa85CTRR_B_LWR_EL1 = 0x10000000000, CTRR_B_UPR_EL1 = 0x1000181f000#asahi-re · 2025-04-06 12:28
mischa85CTRR_A_LWR_EL2 = 0x1000000c000, CTRR_A_UPR_EL2 = 0x100002af000#asahi-re · 2025-04-06 12:25
mischa85all 0#asahi-re · 2025-04-06 12:25
mischa85no these are correct#asahi-re · 2025-04-06 12:24
mischa85derp#asahi-re · 2025-04-06 12:24
mischa85oh wait#asahi-re · 2025-04-06 12:24
mischa85CTRR_A_LWR_EL12 = 0x0, CTRR_A_UPR_EL12 = 0x0, CTRR_B_LWR_EL12 = 0x0, CTRR_B_UPR_EL12 = 0x0#asahi-re · 2025-04-06 12:19
mischa85CTRR_C_LWR_EL2 = 0x10004e1c000, CTRR_C_UPR_EL2 = 0x10004e27000, CTRR_D_LWR_EL2 = 0x0, CTRR_D_LWR_EL2 = 0x0#asahi-re · 2025-04-06 12:17
mischa85excuse me, on it#asahi-re · 2025-04-06 12:17
mischa85oh i expected some complicated logic behind it again#asahi-re · 2025-04-06 12:15
mischa85x is 1, 2, 3 and 4 for A and B#asahi-re · 2025-04-06 12:14
mischa85chaoss_princess: currently A and B are defined in apple_regs, how do i translate s3_0_c11_c6_6 to "enc": [3, 4, 15, 9, x ]