Cluster Dump Checksum
Re: Custer Dump Checksum
i can give you these files
but what do you want to do I still do not understand
but what do you want to do I still do not understand
- Attachments
-
- ipcholden.7z
- (329.55 KiB) Downloaded 201 times
Re: Custer Dump Checksum
Thanks for the files. They will really help. Now a disassembly can be made from the OS segment and the rest can be figured.
Interesting the other file don`t match exactly the dumps. I suspect these are written in the eeprom area and don`t have any checksums. Maybe the os apply some form of checksum when the data is updated.
Anyone knows what cpu is in this IPC or have a pic of internal board.
Interesting the other file don`t match exactly the dumps. I suspect these are written in the eeprom area and don`t have any checksums. Maybe the os apply some form of checksum when the data is updated.
Anyone knows what cpu is in this IPC or have a pic of internal board.
-
- Posts: 2882
- Joined: Sun Aug 02, 2009 9:16 pm
- Location: Bayside, Melbourne, Victoria
- Contact:
Re: Custer Dump Checksum
I'm not 100% sure what the 2 bigger files are in that attachment & then assuming the 7 other really small sections make up 1 complete file, but hopefully it will allow us to map them out further & figure out the checksum for that area too.
Re: Custer Dump Checksum
That is the OS segment, might be stored internally to the processor. I plan to do some disassembly of them but don`t know what processor is used in that IPC.VX L67 Getrag wrote:I'm not 100% sure what the 2 bigger files are in that attachment & then assuming the 7 other really small sections make up 1 complete file, but hopefully it will allow us to map them out further & figure out the checksum for that area too.
Do you have any pics of the chips and the internal pcb.
-
- Posts: 2882
- Joined: Sun Aug 02, 2009 9:16 pm
- Location: Bayside, Melbourne, Victoria
- Contact:
Re: Custer Dump Checksum
It’s been years since I pulled 1 apart & don’t think I’ve kept any photos, but I’ll check what I have.
-
- Posts: 2882
- Joined: Sun Aug 02, 2009 9:16 pm
- Location: Bayside, Melbourne, Victoria
- Contact:
Re: Custer Dump Checksum
Again thanks to car modder forum this was the only image I could find...
- Attachments
-
- VE Instrument Cluster EEPROM Location.jpg (152.83 KiB) Viewed 3458 times
Re: Custer Dump Checksum
I could read japan only. Maybe some NEC or Hitachi processor[ could be some processor used in BCMs also]. There is also the eeprom marked, where the other stuff is written.
-
- Posts: 2882
- Joined: Sun Aug 02, 2009 9:16 pm
- Location: Bayside, Melbourne, Victoria
- Contact:
Re: Custer Dump Checksum
Yeah so the eeprom is where those dumps are from.
Not sure how it correlates with mcu type, I have a feeling that picture is from a series 1 which isn’t even what the dumps I have supplied suit... so it could be completely different so I’ll have to try & get some better info!
Not sure how it correlates with mcu type, I have a feeling that picture is from a series 1 which isn’t even what the dumps I have supplied suit... so it could be completely different so I’ll have to try & get some better info!
Re: Custer Dump Checksum
Been playing around with dash's myself lately, though only after attempting to get an VY auto dash working on a manual, and not knowing it's origins, brought me undone with the SRS, seems it may be off a ute.
Had my son buy the srs diag gear from tazzi.
Then proceeded to pull chips from spare dash's to dump them.
Starting with a Gen3 Maloo dash, is the checksum calc'd in these too.
Had my son buy the srs diag gear from tazzi.
Then proceeded to pull chips from spare dash's to dump them.
Starting with a Gen3 Maloo dash, is the checksum calc'd in these too.
Re: Custer Dump Checksum
A little hint
a large file is in the processor
small ones need to be considered
as in the screenshot below
don't search the whole file
but only blocks from it
if the cluster is on the table
then you can try to read them in can
1a 22
1a 24
1a 46
1a 18
1a 48
1a 25
I think the meaning is clear
Open calibration
Skip GlobalHeaderLength bytes
Read BlockCount
While BlockCount > 0
Read BlockLength
Copy BlockLength bytes of calibration into message (first byte is Data Identifier)
Send message
If not a positive response is received
Break while
Endif
Subtract 1 from BlockCount
Loop
Endif
a large file is in the processor
small ones need to be considered
as in the screenshot below
don't search the whole file
but only blocks from it
if the cluster is on the table
then you can try to read them in can
1a 22
1a 24
1a 46
1a 18
1a 48
1a 25
I think the meaning is clear
Open calibration
Skip GlobalHeaderLength bytes
Read BlockCount
While BlockCount > 0
Read BlockLength
Copy BlockLength bytes of calibration into message (first byte is Data Identifier)
Send message
If not a positive response is received
Break while
Endif
Subtract 1 from BlockCount
Loop
Endif
- Attachments
-
- did1.JPG (39.63 KiB) Viewed 3404 times
-
- did.JPG (63.76 KiB) Viewed 3405 times