[b3lha]

Originally Posted by longassname

No, that's the 94 usdm rom. Most if not all obd1 USDM awd SVXii use the e23aa11p or e23aa12p roms. That's the e23aa12p rom--the latter model obd1 rom. I used the Dewtronics M6811Dis v1.0 code seeking dissassembler back when I did it. Maybe you didn't notice it's sitting in a 32k ROM and your control file is loading it complete with padding to c000? May also need to edit some entry points?

I noticed the 16K of FF on the front. I am loading this image at 8000. I guess the bigger rom gives much more space for TCU mods.

Now that I have looked at it properly, I can see that the image you sent me is corrupt. Bit 1 of every single byte is set to 1. This obviously results in incorrect disassembly. I thought I was using the wrong disassember.

Compare the following:

This is the 705402

f33e 8e 01 ff    lds 0x01FF
f341 86 a0       ldaa 0xA0
f343 b7 10 39    staa (0x1039)
f346 86 04       ldaa 0x04
f348 b7 10 3f    staa (0x103F)
f34b 86 01       ldaa 0x01
f34d b7 10 38    staa (0x1038)

This is the 725606

f35c 8e 03 ff    lds 0x03FF
f35f 86 a2       ldaa 0xA2
f361 b7 12 3b    staa (0x123B)
f364 86 06       ldaa 0x06
f366 b7 12 3f    staa (0x123F)
f369 86 03       ldaa 0x03
f36b b7 12 3a    staa (0x123A)

You can see it better in binary:

705402: 10001110 00000001 11111111 10000110 10100000 10110111 00010000 00111001
725606: 10001110 00000011 11111111 10000110 10100010 10110111 00010010 00111011

The whole image is corrupted like that, every single byte has that bit set to a 1. I can't imagine how it could have happened.