BA Falcon Instrument Cluster EEPROM Programming

[TazzI]

Ok, after looking over your dump, and doing a little analysis,

0x10-0x13 looks to be the serial number in some manner,

Places to look for autolight, and high/low series, switch
0x19
0x1D-1F
0x55-57
0xA8
0xD6

The 4 error codes i think are at
0xBA-BB + BD
0xC2-C3 + C5
0xCA-CB + CD
0xD2-D3 + D5

Lets see what we can dig up,

Ill pull up IDS this arvo and see what "identification" stuff it shows. Should be able to try search from there as well.

[TazzI]

So the LCD controller takes messages in the format of:

Device ID : Command: Data: checksum (i think its a checksum?)

Taking these two frames as an example:
[0x38+0xC0-0x21-0x80+0x00+0x00+0x00+0x00+0x7E+0x00+0x00+0x00+0x00+0x00+0x00+0x00+0x00+0x00+0x18-]
[0x38+0x03+0x87-0x00+0x00+0x00+0x00+0x00+0xF8+0x00+0x00+0x00+0x00+0x00+0x00+0x00+0x00+0x00+0x31+]

So breaking down the first command:
0x38 = Send to LCD driver
0xC0 = 1100 0000 = Commands continue (1) + (constant 10) + 0 (Normal power mode) + 0 (display status disabled) + 0 (LCS bias config 1/3) + 00 (1:4 multiplex; BP0, BP1, BP2, BP3)
0x21 = Load data point command = 0010 0001 = Last Command (0) + (Constant 0) + Pointer(100001)
0x80 = Device Select Command =1000 0000 = Commands continue (1) + 0000000

[TazzI]

Success! Iv got random digits and parts lighting up with custom commands! Woop woop!

The BusPirate has done its job.. now to get the microcontroller involved.. hold the I2C line hostage and send only our custom messages.

*I know this is completely off course off eeprom hacking... but at least its BA/BF cluster related!

*Edit
So its more than possible to display custom digits. But, custom text isnt really possible!. But you can make it display whatever numbers you want.

Also, to get a perfect screen refresh, you would need to lift the SDA and SCL lines so that only the micro controller communicates with everything.
I reckon its a good way of being able to flick between engine temp, digital RPM or speedo, ect.

[aumatt]

Ok, after looking over your dump, and doing a little analysis,

0x10-0x13 looks to be the serial number in some manner,

Places to look for autolight, and high/low series, switch
0x19
0x1D-1F
0x55-57
0xA8
0xD6

The 4 error codes i think are at
0xBA-BB + BD
0xC2-C3 + C5
0xCA-CB + CD
0xD2-D3 + D5

Lets see what we can dig up,

0x10-0x11 Trip A
0x12-0x13 Trip B

All other assumptions are incorrect

Matt

[TazzI]

0x10-0x11 Trip A
0x12-0x13 Trip B

All other assumptions are incorrect

Matt

What differences are there between high/low?

Does anything else display on the screen? Or is it just a way of identifying the cluster type?

[aumatt]

High Series has a different left have LCD, where it shows door ajar info. Trip info is displayed on the ICC

Low series shows trip info etc on the left LCD as the ICC doesnt display it.

Matt

[TazzI]

Ahh ok, so thats an easy way of identifying high/low series. High will have that little car on the left lcd.

[TazzI]

Bugger, I did have another read of the eeprom after programming just for another kms reading. But instread of clicking verify, I hit Erase!

Daaammmmnnn. Least I had the good bin to write back.

Will attempt this again later on.

[yoda67]

what software are you using to read and right eeprom thanks

[TazzI]

The default software that comes with a gq4


Things been a bit slow on the Ford front, kept getting stuck due to the IDS looking for an ecu response... But, a BA ECU rocked up today to be hooked up to the cluster

Will hopefully be able to fully control all inputs to the cluster after seeing the chatter from the ecu.