#
#asahi-re · 2021-01-05 11:25
marcan00000000 02 00 e0 ac is what the apple ones have :-)
#asahi-re · 2021-01-05 11:25
marcanactually just look at the first word
#asahi-re · 2021-01-05 11:24
marcando you have a sample firmware for it?
#asahi-re · 2021-01-05 11:23
rwhitbyThe TPS65987 EVM I have is somewhat expendable, so could be use for experimentation.
#asahi-re · 2021-01-05 11:23
marcanwe don't know about that one, but it well might
#asahi-re · 2021-01-05 11:23
rwhitbyMarcan probably already knows all this, but for the benefit of others, this document describes the "patch bundles" in the external SPI flash for the PD controller: https://www.ti.com/lit/an/slvae21a/slvae21a.pdf
#asahi-re · 2021-01-05 11:10
rwhitbymarcan: the CD3217B12 on the M1 and 16,1 doesn't happen to correspond to the TPS65987 does it?
#asahi-re · 2021-01-05 11:09
rwhitbyinteresting, the 65983 EVM photo in https://www.ti.com/lit/ug/slvuap1a/slvuap1a.pdf is the same board I have, and shows a 65982 mounted on it.
#asahi-re · 2021-01-05 11:06
rwhitbyI have 65982 and 65987 dev boards, but no 65983
#asahi-re · 2021-01-05 11:00
marcanthe ACE1 ones outright say TPS65983 in the firmware, so I'm pretty sure CD3215C00 == TPS65983 with different OTP/ROM code
#asahi-re · 2021-01-05 10:58
rwhitbyHmm, the 14,2 is "expendable" to me, the 15,2 is important and the 16,1 is my main laptop. I was hoping to be able to experiment on the 14,2 first so I don't damage the others :-)
#asahi-re · 2021-01-05 10:56
marcanbut still, let's see
#asahi-re · 2021-01-05 10:55
marcanACE1 seems to have a somewhat different firmware approach (config area is different)
#asahi-re · 2021-01-05 10:55
marcanso only the 16,1 has the same chip as the M1s
#asahi-re · 2021-01-05 10:55
marcan15,2/Mac-827FB448E656EC26 is ACE1, so is 14,2/Mac-CAD6701F7CEA0921. 16,1/Mac-E1008331FDC96864 is ACE2.
#asahi-re · 2021-01-05 10:51
rwhitby14,2 response to actionId 0x205 is unchanged after updating to OSX 11.1, so remains different to 15,2 response.
#asahi-re · 2021-01-05 10:49
rwhitby16,1: Mac-E1008331FDC96864 15,2: Mac-827FB448E656EC26 14,2: Mac-CAD6701F7CEA0921
#asahi-re · 2021-01-05 10:40
marcanthose will point me to the right firmware
#asahi-re · 2021-01-05 10:39
marcanioreg -l | grep -i board-id
#asahi-re · 2021-01-05 10:39
marcancan you get the board IDs?
#asahi-re · 2021-01-05 10:38
rwhitbylooking at TBT firmware versions, the Titan Ridge 16" 16,1 is at 55.3 (but it's still running OSX 10.15.17 cause I've got things that need to be updated for Big Sur), the Titan Ridge 13" 15,2 is at 47.4 (OSX 11.1) and the Alpine Ridge 13" 14,2 is at 41.4 (OSX 11.1)
#asahi-re · 2021-01-05 10:37
marcanthis ACE2 firmware speaks of "A127X" but A1278 is a 2010 macbook which *definitely* wasn't using ACE2
#asahi-re · 2021-01-05 10:37
marcandammit mac codenames are so annoying to relate
#asahi-re · 2021-01-05 10:31
marcanthe firmware grew several kilobytes
#asahi-re · 2021-01-05 10:31
marcanI think there were significant changes there, yeah
#asahi-re · 2021-01-05 10:31
rwhitbyit was on OSX 11.0.1 whereas the 15,2 is on OSX 11.1
#asahi-re · 2021-01-05 10:30
rwhitbysorry, 14,2 the 2017 alpine ridge one
#asahi-re · 2021-01-05 10:29
marcan14,2 or 14,1?
#asahi-re · 2021-01-05 10:29
rwhitbyWill also check the TBT firmware version in the system report after I update it.
#asahi-re · 2021-01-05 10:27
rwhitbyboth are Big Sur, but I just realised the 14,1 is a minor version behind, so I'll update it and see if it changes things.
#asahi-re · 2021-01-05 10:26
marcanare these devices running the same firmware? (same OSX version)
#asahi-re · 2021-01-05 10:25
rwhitbythe same actionId on different ports of the same device seemed to return the same data (for a limited subset I looked at)
#asahi-re · 2021-01-05 10:23
rwhitbygotcha
#asahi-re · 2021-01-05 10:23
marcan(it's a set)
#asahi-re · 2021-01-05 10:23
marcanso the only difference is the second adds 0x501
#asahi-re · 2021-01-05 10:23
marcanthey use 16-bit tokens, so that looks like 0x385,0x103 for the first, and 0x103,0x501,0x385 for the second
#asahi-re · 2021-01-05 10:22
rwhitbyalthough the data there looks "rotated"
#asahi-re · 2021-01-05 10:22
marcanI think that might include things like what pins it can be muxed on
#asahi-re · 2021-01-05 10:22
marcanyeah, I suspected that too
#asahi-re · 2021-01-05 10:21
rwhitbySOP"_Debug Apple Unknown VDM Command (0x11) Ack (03 01 01 05, 00 00 85 03) | 12 bytes (51 80 AC 05 03 01 01 05 00 00 85 03)
#asahi-re · 2021-01-05 10:21
rwhitbySOP"_Debug Apple Unknown VDM Command (0x11) (02 05 00 00) | 8 bytes (11 81 AC 05 02 05 00 00)
#asahi-re · 2021-01-05 10:21
rwhitbyMacBookPro15,2 (Titan Ridge):
#asahi-re · 2021-01-05 10:21
rwhitbySOP"_Debug Apple Unknown VDM Command (0x11) Ack (85 03 03 01, 00 00 00 00) | 12 bytes (51 80 AC 05 85 03 03 01 00 00 00 00)
#asahi-re · 2021-01-05 10:21
rwhitbySOP"_Debug Apple Unknown VDM Command (0x11) (02 05 00 00) | 8 bytes (11 81 AC 05 02 05 00 00)
#asahi-re · 2021-01-05 10:21
rwhitbyMacBookPro14,2 (Alpine Ridge):
#asahi-re · 2021-01-05 10:20
rwhitbyHmm, it seems the information for a certain actionId is different on different devices.
#asahi-re · 2021-01-05 09:36
marcan(if we need to I will)
#asahi-re · 2021-01-05 09:36
marcanit's not hard to dump the ROM, you can use SWD on the chip pins or just flash some firmware that dumps the ROM out, but I haven't bothered to go there yet
#asahi-re · 2021-01-05 09:35
marcanbasically the SPI code gets loaded at a (hieously unaligned) SRAM offset, called, and it overrides function pointer table entries that the ROM uses. The ROM has thunks that call through those pointers to itself (initially), and the SRAM code has more thunks that call back into the ROM functions.
#asahi-re · 2021-01-05 09:35
rwhitbyI see. Hmm.

plus ›