From utilities->patcher original file->select bin when bin is opened you can edit tableseek from settings->tableseek Than you can add an entry just like configuring an xdf with different options. the main difference is that except absolute address it uses tableseek string. You can seek absolute or r...

Virgin gm_bosch_t87a_bench_fullbackup_full_backup_20221122165010_int_flash.rarHere are some files to look at: Virgin T87A read, Allison Trans T87A read, un lo ck ed T87A read, un lo ck ed T87A flashed with different software... Are these unlocked obd patch bins and if so do you have a before and af...

It wasn`t that hard once you know the pattern.

Found there is 2 main revisions of t43 code, not sure how to differentiate unless open in patcher, early style is labelled t43-0
later style t43

Did some changes to e38 tableseek file, and now it will find the TX and RX tables stored in OS for any e38 e67 bin. End of table is open, so user needs to figure where it ends, Usage will be for display mainly.


Extract file to XML folder overwriting previous versions.

9:BSCM,10:HBP,11:CGM,12:VDCM,13:BECM_A Here is some more to add to the list, I am sure there is correlation between number and ID on some GMW document, or they just got added on demand. No matter how long is the list last 2 are always.NumOfRxDevices and InvalidRxDevice , they always takes last 2 num...

Knackersjewels wrote: ↑Sat Apr 27, 2024 9:25 pm Bumping, as this is what I need right now

Check this link.
https://universalpatcher.net/a2l-application/

Tre-Cool, once I map some of the code and see what is needed, I can add some tableseek logic to find it on any e38 bins.

Currently you need to trace it in ghidra from start of calibration offset for CAN RX/TX settings.

If I counted correctly this is where bytes are stored from that message, r31 is the offset they get stored in numerical order. Now tracing down to individual bits will take some time, due to ppc crap code. Here is how bits are copied for first byte , r4 is the bit position, some bits might get inver...

For anyone wondering how Cal data is defined per node, there is a table in OS that defines it, similar to DTC list logic. second dword per node defines???length ??size and some other ??data. M:000755C8 TX_table_dword_755C8:.long 0xC9 # DATA XREF: TX1_main_sub_74334+104o ROM:000755C8 # TX1_main_sub_7...

Newer versions might have support for other j-tools. Which IDS version did you use with autel.