T87A Bins to Pins - Who's In ?

E38 E92 and many others. Approximately 2007 and newer
Post Reply
kidturbo
Posts: 80
Joined: Mon Dec 21, 2015 3:15 pm
cars: Nothing With Wheels

T87A Bins to Pins - Who's In ?

Post by kidturbo »

Being that the T87A is now 10 years old, I feel it's time we dump the data for these units, so the next generation can and sort what fits what.
20250201_035442.jpg
While attempting to help out on some stand alone builds, I've discovered there are several pinout to OS differences across platforms. First off is the Range Switch. 6/8/10 speed, 3 possible range switches, 4 or 6 wire, analog or 9v PWM signal. All same T87A hardware, with multiple OS choices based on range along.

Second thing to sort, is primary OS# vs Slave MPU. Now that GM Boot Mode is documented, and can read / write the SRAM without cracking the case open, we also need to sort what OS mates with 2nd MPU OS versions. So far I have read out a half dozen different models, and started making a spreadsheet of HW to SW #'s.

A good start for this new topic? While searching the web, found a serious lack of details available for these modules,that are older than my grand kids.. Maybe we can build a library of all the OS to transmission options, and match up the physical case hardware ID's along the way.. I have about 10 OS versions to share so far. I can dump em here, or share link to my private repo. But lets move this old hardware into the E38 knowledge category.. :hmm:
hjtrbo
Posts: 227
Joined: Tue Jul 06, 2021 6:57 pm
cars: VF2 R8 LSA
FG XR6T
HJ Ute w/RB25DET

Re: T87A Bins to Pins - Who's In ?

Post by hjtrbo »

I feel like a dedicated gm gen 4 / gen 5 section (aka Global A) is warranted. We're starting to build a good knowledge pool of e38/67, t43, t87/87a modules now. Be nice to have it in 1 place. If you're reading this antus, what do you think?
kidturbo
Posts: 80
Joined: Mon Dec 21, 2015 3:15 pm
cars: Nothing With Wheels

Re: T87A Bins to Pins - Who's In ?

Post by kidturbo »

Plus 1 for the Global A header. That covers 20yrs of shared GMLAN modules and options.
User avatar
antus
Site Admin
Posts: 8999
Joined: Sat Feb 28, 2009 8:34 pm
cars: TX Gemini 2L Twincam
TX Gemini SR20 18psi
Datsun 1200 Ute
Subaru Blitzen '06 EZ30 4th gen, 3.0R Spec B
Contact:

Re: T87A Bins to Pins - Who's In ?

Post by antus »

Good idea. I feel like one for newer than vpw eg can and e38 and similar then another for global a and up. But what describes that best?
Have you read the FAQ? For lots of information and links to significant threads see here: http://pcmhacking.net/forums/viewtopic.php?f=7&t=1396
ironduke
Posts: 695
Joined: Thu Feb 13, 2020 11:32 pm
cars: Mainly GM trucks, a Cruze and an Equinox for dailys..

Re: T87A Bins to Pins - Who's In ?

Post by ironduke »

Maybe CANBUS ECU's?? That covers 2007 and up. Could make another one for global A but some ecm's are both pre and post global A so that could get confusing.

Edited.. I thought there was a gm specific section but don't see one, so the section should say GM somewhere in it..
kidturbo
Posts: 80
Joined: Mon Dec 21, 2015 3:15 pm
cars: Nothing With Wheels

Re: T87A Bins to Pins - Who's In ?

Post by kidturbo »

I like GMLAN as a header. If someone wants to go chip diving, there seems to be plenty of good headers to cover most. Forsaking the Hitachi STmicro in these TCM's.

I've found GMLAN Global A covers 04-24 depending on platform. Using the early E38 as our first noted occurrence. From best recollection..

While most will say Global B is 2020 and up, I rented a 2024 Malibu with CVT last week, and it's still squawking full Global A set on the DLC. Everything Global B is firewalled at the DLC, and won't speak unless spoken to first.. But it seems they left the low end platforms alone, until they run out of stocked up hardware I'm guessing.

And we can't forget our Holden / Vette GMLAN protocol tucked in there. 04-12 years in the Vette, and still going strong across the pond. They all share some version of the J2534 pass thru OBDII protocol. For those interested in 2015 split, here's a good read.
https://kvaser.com/developer-blog/sae-j ... on-part-1/
kidturbo
Posts: 80
Joined: Mon Dec 21, 2015 3:15 pm
cars: Nothing With Wheels

Re: T87A Bins to Pins - Who's In ?

Post by kidturbo »

10L RPO starter listed supplied by a buddy. Matches up good with what I find listed on other forums, so a decent start.
Now to cross ref to known OS #'s..

MI4 = 2nd Gen Camaro 10L90 transmission (LT4)
MI2 = 2nd Gen Camaro 10L80 Transmission (LT1)
MQB - 2nd Gen Global A Truck transmission (2019+ Silverado/Sierra and select 2021 SUV's)
MGL = 1st Gen 10L90 Camaro transmission (LT4 2017-2019)
MF6 = 1st Gen Camaro 10L80 transmission and 1st Gen truck 10L80's (2019 camaro, 2018-2020 SUV's, 2018 Trucks)
kidturbo
Posts: 80
Joined: Mon Dec 21, 2015 3:15 pm
cars: Nothing With Wheels

Re: T87A Bins to Pins - Who's In ?

Post by kidturbo »

Starting to put together the list of known OS version details to RPO # based off bin file details. But wanted to clarify which values we should focus on collecting first.

I'm much better at moving GM data than sifting thru bin files. Besides the unlock keys and checksum structure, not much I'm looking to gain from there. But from the A2l data I do have, at least we can locate all the main OS segments, and byte positions that define each. Found a helpful doc on naming structure used by ASAM or ASAP-2 as previously know. https://www.asam.net/standards/detail/mcd-2-mc/wiki/

So for our list, here is where I'm currently focused. Using these known positions, have several different platforms saved now, and comparing these areas for our reference. The first image is from a raw/virgin 6spd Allison OS bin. Second is a 2019 10spd.
Screenshot 2025-02-20 130738.png
Screenshot 2025-02-20 130738.png (97.45 KiB) Viewed 5421 times
Screenshot 2025-02-20 130905.png
Screenshot 2025-02-20 130905.png (105.53 KiB) Viewed 5421 times
For now lets skip past the 0x00080000 address where it looks like our main keys preside, and focus in OS identification for now.

0x00080020
RL_VALUE_UB
255
CM_BYTE
0
255
/begin ANNOTATION
ANNOTATION_LABEL "Calibration Note"
/begin ANNOTATION_TEXT
" Transmission Calibration FNA 6502QA "
/end ANNOTATION_TEXT
/end ANNOTATION

What does our "Transmission Calibration FNA" identify, and is that the primary OS # we should focus on??

Or should we be using the EPK value to track these differences?

ADDR_EPK 0x00080050
EPK "t87A_1617119AW******************"
/end MOD_PAR

EPK MOD_PAR String that describes the EPROM. Anything special to take note of here?

Last up, 2 lines down we find.

/begin CHARACTERISTIC KaADLY_CIN[x]
"KaADLY_CIN[0]"
CURVE
0x00080070
RL_VALUE_UB
255
CM_BYTE
0
255
/begin ANNOTATION
ANNOTATION_LABEL "Calibration Note"
/begin ANNOTATION_TEXT
" ASCII Calibration Identifier "
/end ANNOTATION_TEXT
/end ANNOTATION

Feel free to fill in the details on that one, and how it relates to our sorting list. When a T87A is factory virgin, this value always shown as DEFAULT. Once programmed, that changes. So if someone with better knowledge on the segments would like to verify relativity of these values to our sort, I'll start building a spreadsheet. Haven't located anything A2l related to our Slave chip yet either, and since it's seems important to match up that OS# to our main MPU OS#, can use a little help mapping that out.
MPC001
Posts: 39
Joined: Sat May 05, 2018 9:41 pm

Re: T87A Bins to Pins - Who's In ?

Post by MPC001 »

Any background on what the T87A/T87a slave does?
kidturbo
Posts: 80
Joined: Mon Dec 21, 2015 3:15 pm
cars: Nothing With Wheels

Re: T87A Bins to Pins - Who's In ?

Post by kidturbo »

I was about to ask the same.. For a reverse engineering topic, sure been a lot of crickets bounce thru here... :shock:

Topic says "Pins", so lets move to that side for a moment. I've sorted the offsets questions above, and will update those shortly. For now, have a look at our different Range Switch pinouts possibilities. Best I have noted so far, there are 4 possible range switch hardware options used by GM as of posting. Luckily have only found 2 wiring and operational differences, based on 4 or 6 pins. The 6 pins models seems to share hardware characteristics with older GM range switches. Using a single dedicated ground switched P/N safety wire going back to our ECM/PCM in belows first 2019 E92 ECM example. 2014+ 6-spd Allison also share the 6 pin range layout with our 8L45 models. However our 6 and 4 pin switches, now both share 9v Ref lines with our from our new style speed sensors that we will address later.

In this 2019 8L45 M5T Pinout example. The ground pin is provided by the TCM to the internal switch, and signal is passed to ECM.
2019-8L45-6Pin-Range.jpg
Next up is our cable shifted Ford 10R80 and GM 10L80/90 models that share the same internal range switch hardware. Along with all other sensors and actuators. But where they split off, is how they wire the range sensors, and the PWM variable duty cycle signals generated. No more single ground wire P/N Safety outputs. Now it's all about CANbus messages, and for GM models that still use a shifter cable, a 5v PWM is telling the ECM and TCM what position that shifter is in. No old 0-5v sweeps, the new sensors produce 2x opposed sweeping 0-100% duty cycle values. Called Sensor A and Sensor B, if you add these two signals together, you should always get 100%.

In the Ford 10R world, they took this as designed and feed both of the range signals to the TCM Only. TCM is then tasked with telling all other nodes what shifter position is over CANbus. Very simple design, where the range switch gets it's Power from the TCM 9v Ref Lines shared with other sensors.
10R80-Range-9vPWM.jpg

Of-course that OEM hardware and Ford design couldn't fit in GM platfoms,, so they jacked it all up. On the T87A's at least.. GM felt they needed a way to give the ECM's their old style direct P/N signal, not trusting CANbus I guess. So they split the Sensor A and Sensor B signal lines between the ECM and TCM. Then they check the ECM against TCM position using CANbus, to come to a Correlation.. Haven't dove super deep into this correlation deal, but know it will set a MIL if they don't pair up after a couple minutes. Car still shifts, so moving on...

In image below, note how GM chose to power the range switch from an ECM 5v Ref Line rather than the same 9v lines they use in for the 8L models.. Which tells us two things. First, the E92 ECM isn't hardware equipped to handle a 9v signal on any ports. And second, the T87A will obviously read a 5v or 9v PWM signal on it's inputs, so long as the HZ and duty cycles values line up with the tune. I have verified this input emulated on the bench with a 3$ PWM board.
2019-10L80-4Pin-Range.jpg

Now that we know our range switch power and pins, this should help anyone trying to up mix and match platform hardware. 6 or 4 pin range, also determines which ECM will fit the build. But for our next point of interest, will need checked using an actual range switch, which I currently don't have on the bench. But while reviewing this data, I quickly noticed that our Ford 10R units PWM duty values don't exactly line up with our GM 10L values. Same sensor, but different supply voltages. Is the cables longer in a Ford, or does that 5v / 9v Ref change our output values?? Time will tell. But it sure would make a cleaner 10L stand-alone option if we can power that range switch from the TCM 9v Ref like Ford, and it line up with map in our tune files without modifications...
10L80-Range-5vPWM.jpg

Ok crickets, chirp..
Post Reply