Old Custom Tune from here

[VX L67 Getrag]

How the hell do you figure that sort of stuff out & what would the original file look like?

On another not for the new memcal id tool one of the files in data m BJMF is 60Kb & in $11 RFI VR V8 not sure whether thats right?

Another good feature for the memcal id tool maybe an extra line when looking at the bin files for the size? but no big deal!

[VL400]

I looked at the reset vector address (it had 80 06 instead of 90 06) and then at the reset the first few instructions should be 8E 01 FF CE 3F C0 but were 8E 01 CF CE 0F C0. If you had address lines B4 and B5 all would be happy But in this case they are always zero.

[Doctor Bob]

hahahaha beaten by an old bloke hey Ryan..lol
i couldnt tell what pins but ive seen it before.

Cheers Rob

[antus]

You can spot it when you look at a bin as binary. For example, this is from a good read of a $54 N13 pulsar bin:

Code: Select all

  Address  |    00      +01      +02      +03    |     HEX     | ASC 
-----------+-------------------------------------+-------------+-----
0x00000000 | 00001001 01011110 00000010 10111001 | 09 5E 02 B9 | .^..
0x00000004 | 00000000 00111111 01111000 10010110 | 00 3F 78 96 | .?x.
0x00000008 | 01010100 00010001 00010001 00000100 | 54 11 11 04 | T...
0x0000000C | 00011001 10011010 00000001 11111111 | 19 9A 01 FF | ....
0x00000010 | 11111111 10111101 01100100 01011100 | FF BD 64 5C | ..d\
0x00000014 | 00011011 00000000 00000101 00000011 | 1B 00 05 03 | ....
0x00000018 | 11111111 01101100 01001101 00000011 | FF 6C 4D 03 | .lM.
0x0000001C | 00000000 00001101 00011011 00101100 | 00 0D 1B 2C | ...,

If a position was always 1 or always 0 for each and every byte then there is a data line problem. In this case you can see at a glance that some bytes are 00000000 and some are 11111111 so you know pretty quickly the data pins are good. An address line problem is harder to see as the data is scrambled (at regular intervals, of differing sizes depending on whats wrong with what address lines), but anyway...

Heres the same bin, missing two data lines:

Code: Select all

  Address  |    00      +01      +02      +03    |     HEX     | ASC 
-----------+-------------------------------------+-------------+-----
0x00000000 | 00001001 01001100 00000000 10101001 | 09 4C 00 A9 | .L..
0x00000004 | 00000000 00101101 01101000 10000100 | 00 2D 68 84 | .-h.
0x00000008 | 01000100 00000001 00000001 00000100 | 44 01 01 04 | D...
0x0000000C | 00001001 10001000 00000001 11101101 | 09 88 01 ED | ....
0x00000010 | 11101101 10101101 01100100 01001100 | ED AD 64 4C | ..dL
0x00000014 | 00001001 00000000 00000101 00000001 | 09 00 05 01 | ....
0x00000018 | 11101101 01101100 01001101 00000001 | ED 6C 4D 01 | .lM.
0x0000001C | 00000000 00001101 00001001 00101100 | 00 0D 09 2C | ...,

even without the original file you can look at it bit by bit and and when you to the 4th position you see every byte has a 0 there (for the entire bin). So you know its a bad read.

[antus]

the crane bin is clean up till 5000hex, it does look like it has reminents of vr v8 $11 onwards, maybe it was a test/custom ecu code, i dunno.

Yeah, its a $58 HSV tune..

0x00005000 | 05 BC FF FF FF FF 4F 9E 58 00 00 28 0F 00 79 0D | ......O.X..(..y.

According to Dr Bobs memcal list, under VS:
$58 = Like VR's $11 release but VS Theft Deter Implemented. (0x6008)

Im not sure why its at 0x5008, though..

[The1]

cool mate

no worries, goneski's!~

[The1]

How the hell do you figure that sort of stuff out & what would the original file look like?

On another not for the new memcal id tool one of the files in data m BJMF is 60Kb & in $11 RFI VR V8 not sure whether thats right?

Another good feature for the memcal id tool maybe an extra line when looking at the bin files for the size? but no big deal!

Ive fixed that up, got the correct bin now, i originally got it from the bin section here, so it's the wrong bin in there as well, i had so many conflicts of information when writing this program, i hope it's as accurate as possible, new version coming soon hopefully. Yeh ill include filesize