Creating a Definition File

Reply Subscribe

Thread Tools

Search this Thread

06-29-2013, 10:18 AM

camarohelp

Junior Member

Thread Starter

Join Date: Nov 2008

Posts: 27

Likes: 0

Received 0 Likes on 0 Posts

Creating a Definition File

Where does someone start in interpreting a .bin file? That's something I haven't quite found any information for yet.

Is it black magic? Do people have access to technical information from manufacturers? Is it a blind trial and error process?

Just wondering about the basics.

Reply Like

06-29-2013, 12:56 PM

RBob

Moderator

iTrader: (1)

Join Date: Mar 2002

Location: Chasing Electrons

Posts: 18,405

Likes: 0

Received 216 Likes on 202 Posts

Car: check

Engine: check

Transmission: check

Re: Creating a Definition File

It depends upon which MaskId you want to create a definition file for. Many of them have been hacked and source code created for them. Along with comments of what the calibration parameters are. There are some mistakes in them, but they are a heck of a lot better then nothing.

If there isn't a hack of the MaskId you are interested in, then it gets a lot more complicated. Need to first disassemble the BIN, break out the calibration portion and convert it to decimal. Then figure out what it all does.

Here is a portion of one that I've started a number of years ago. There is the one table that I know what it is, followed by additional data that I haven't yet formatted. But will likely be related to cranking PW:

Code:

;--------------------------------------
; 
; *Crank Mult vs CTS
;
; pw = base * N / 256
;--------------------------------------

L85B5	FCB	183	; -40
	FCB	165	; 
	FCB	117	; 
	FCB	 75	; 
	FCB	 46	; 
	FCB	 31	; 
	FCB	 27	; 
	FCB	 20	; 
	FCB	 16	; 
	FCB	 14	; 
	FCB	 12	; 
	FCB	 12	; 
	FCB	 13	; 
	FCB	 14	; 116





                     8 131 162 162 178 196 210 230   0   0   0   0   0
 05d0    0   0   0   0   0   0   0   0   0   0 251   0   0   0 251   0
 05e0    0   0 251   0   0   0 251   0   0   0 255   0   0   0 255   0
 05f0    0   0 255   0   0   0 255   0   0   0 255   0   0   0 255 255

Record 000c
 0600  255   0 255 255 255 255 255

Then what the code looks like when first disassembled:

Code:

LB6BE: 86 10		LDAA 	#16		; 
LB6C0: B7 01 69		STAA 	L0169		; 
LB6C3: 7F 01 6A		CLR  	L016A		; 
LB6C6: 15 51 34		BCLR 	L0051,#$34	; 
LB6C9: FC 3F BC		LDD  	L3FBC		; 
LB6CC: C4 FB		ANDB 	#$FB		; 
LB6CE: CA 08		ORAB 	#8		; 
LB6D0: CE 40 04		LDX  	#$4004		; 
LB6D3: 1D 00 0C		BCLR 	0,X,#$0C	; 
LB6D6: FD 3F BC		STD  	L3FBC		; 
LB6D9: CC 04 CD		LDD  	#1229		; 
LB6DC: DE C8		LDX  	L00C8		; 
LB6DE: 03		FDIV 			; 
LB6DF: FF 01 6D		STX  	L016D		;

To which it gets commented as it is figured out. Starting with the ALDL list data is a great start at what many of the RAM variables are. Which helps in figuring out what the code is doing.

RBob.