#asahi-re · 2026-07-18 19:09
chaos_princessi guess yes, those specific instructions can be marked with labels or sth, and if it is there - bump the elr#asahi-re · 2026-07-18 19:07
amarioguyor is there a better way where m1n1 doesn't keep looping the serror#asahi-re · 2026-07-18 19:07
amarioguynot saying that those registers do exist, more trying to figure out...is doing elr += 4 a good idea for the read8/read16/read32/read64 case specifically?#asahi-re · 2026-07-18 19:05
amarioguyi did try 32-bit access width on this same addr, lower nibble became 3 but otherwise not much different)#asahi-re · 2026-07-18 19:04
amarioguythe INF lower bit values seem to be consistent as well#asahi-re · 2026-07-18 19:04
amarioguyfor example 0x210F80040 (from iBoot disasm) exists and returns a good value but 0x2110400D0 does not#asahi-re · 2026-07-18 19:03
amarioguythat's an example but most things that aren't IORVBAR or very specific addresses which are known to exist seem to throw these#asahi-re · 2026-07-18 19:03
amarioguyESR: 0xbe000000 (SError)#asahi-re · 2026-07-18 19:03
amarioguyL2C_ERR_INF: 0x1400100007#asahi-re · 2026-07-18 19:03
amarioguyL2C_ERR_ADR: 0x1a80000211010000#asahi-re · 2026-07-18 19:03
amarioguyL2C_ERR_STS: 0x200#asahi-re · 2026-07-18 19:02
chaos_princesscan you figure it out from that register that has extra error info?#asahi-re · 2026-07-18 19:01
amarioguybut yes, in the general case you're correct#asahi-re · 2026-07-18 19:01
amarioguysee it turns out on apple platforms (some previous experience with some m1n1 testing a few years ago gave me similar issues too) accessing some memory addresses wrong basically throws an serror that's synchronous with the instruction#asahi-re · 2026-07-18 19:00
amarioguyyea..............if only it were that simple#asahi-re · 2026-07-18 18:59
yukaso the instruction which caused it already passed#asahi-re · 2026-07-18 18:59
yukait's asynchronous#asahi-re · 2026-07-18 18:59
yukaSError does not usually occur at the instruction that caused it#asahi-re · 2026-07-18 18:57
amarioguyso every time it was doing the ERET, it was returning to the exact same instruction that was SError'ing#asahi-re · 2026-07-18 18:56
amarioguyi can PR that small addition if upstream wants it though#asahi-re · 2026-07-18 18:56
amarioguyi say "in quote marks" because i'm sure there's probably a good reason serror handling doesn't have the exception guard code#asahi-re · 2026-07-18 18:55
amarioguymy "fix" in quote marks is basically just to add the logic from sync exceptions for the purposes of dumping these registers#asahi-re · 2026-07-18 18:55
amarioguyyuka: tl;dr is that serrors don't have the exception guard code that the synchronous exception path does#asahi-re · 2026-07-18 18:53
yukaI haven't seen this issue before#asahi-re · 2026-07-18 18:52
yukaI'm interested in what was the problem#asahi-re · 2026-07-18 18:51
amarioguyah i see why simple local fix should do it#asahi-re · 2026-07-18 17:47
amarioguy(the problem isn't necessarily the serrors themselves, more that m1n1 seems to be struggling to recover from them...)#asahi-re · 2026-07-18 17:44
amarioguyi'm trying to dump some of that area for context#asahi-re · 2026-07-18 17:44
amarioguyok definitely not the iorvbar region...but seems like trying to just read other stuff outside of that can result in an serror loop#asahi-re · 2026-07-18 17:43
amarioguynow why tf when i try to read from cpu-impl-reg (IORVBAR region) does it cause an serror loop...#asahi-re · 2026-07-18 17:42
amarioguyyep, now the proxy shell works#asahi-re · 2026-07-18 17:42
amarioguyacked#asahi-re · 2026-07-18 17:18
yuka(the proxyclient side is enough to fix your issue, no need to re-install m1n1)#asahi-re · 2026-07-18 17:17
yukasorry, I forgot I always used to comment this out when working with M5#asahi-re · 2026-07-18 17:17
yukayou need https://github.com/AsahiLinux/m1n1/pull/626#asahi-re · 2026-07-18 17:17
amarioguythis is on t8142, j704ap#asahi-re · 2026-07-18 17:17
amarioguyyuka: erm....seems like when i try to connect to the uartproxy the shell just spams '> 0'#asahi-re · 2026-07-17 19:03
yukabooting and proxy worked out of the box iirc, but the usb cdc-acm proxy needed this: https://github.com/AsahiLinux/m1n1/pull/578#asahi-re · 2026-07-17 19:02
amarioguyyuka: acked, that's good, all i really need is to read/write memory regions here#asahi-re · 2026-07-17 19:01
yukaAnd on M5 Pro for sure#asahi-re · 2026-07-17 19:01
yukaapparently, because someone just ran my m1n1 experiment on it#asahi-re · 2026-07-17 19:00
amarioguybtw just to ask, is m1n1 able to boot to the proxyconsole uart on m5?#asahi-re · 2026-07-16 01:34
amarioguymy hypothesis here is that these are "tunables" like mentioned before that are applied in the fuOS case, as the same functions seem to also apply other things too that are unrelated to cpu lockouts#asahi-re · 2026-07-16 01:33
amarioguyfor j616c/25G5043d, the base address is loaded from 0x10081D9A290, the tables are 0x10081D12728, 0x10081D126F0, 0x10081D12080 (last one i think is dependent on that flag)#asahi-re · 2026-07-16 01:29
amarioguyi *think* one of these might be conditioned on another flag that seemed lpol related too?#asahi-re · 2026-07-16 01:29
amarioguythe whole routine seems to be applying some values from the tables across the board like chaos_princess implied, critically these specific tables *only* seem to be accessed in the case where an fuos is being booted#asahi-re · 2026-07-16 01:28
amarioguythe actual tables i'm noting as "of interest" are 0x10081D116D8, 0x10081D11388, 0x10081D119F8#asahi-re · 2026-07-16 01:27
amarioguyfor j616c/25G5028f of note, before the functions that use these tables access them, it seems it loads the value 0x211000000 from 0x10081D9A290 (this is why i have the gut feeling these might be related as the effects of the lockout primarily affect cpu features and msrs and such, the CPU-local address being loaded here seems a bit important as it might imply it's a "base" address of sorts)#asahi-re · 2026-07-16 01:23
amarioguyif anyone wants to follow along, (the specific iBoots i'm diffing are 25G5043d and 25G5028f) will post some addresses below of some of the things i found, if someone wants to act as verifier but i have a bit of a gut feeling these might be it#asahi-re · 2026-07-16 01:19
amarioguy(as in might've stumbled across the table...)