Tazzi wrote:Isnt the CVN the CRC16? Or have I gotten that wrong?

If the CVN is the CRC, then what/where is the SUM?

Absolutely correct. CVN is custom CRC16.
checksum is simple add/sum.

I checked against an old file I have of the same programming, might have been a differerent ECM though? Anyways everything was the exact same from 0xF17A and down, but there were differences before that here and there.. That section isn't calibration or operating system area, eeprom? registers? etc...

Yep, thats supposed to be the correct path. You did right, im curious what you got? And a little satisfied that it worked :D I found some registry file for the GM MDI. Turns out that also the Registry entry of the Volvo Dice is non standard :roll: I fixed that, now it should enter the passthru devic...

Thanks, ill have a deeper look at the Zip tonight. You should just choose in the left dropdown box "J2534 PassThru". If everything works as it should, in the middle should be dispayed something like "GM MDI" and in the right box should be a valid path to a Passthrou DLL im your S...

Im in Germany, Europe. Usually :) Yes, what Tazzi does is already done for my tool. Did not saw he made good progress before i started before a few weeks. Thank you for fast testing. I changed some library linking options. Maybe thatswhy it is working now. When it works for you, we leave it this way...

So after some long long nights i updated to 0.0.0.3 Major change is integration of PassThru DLLs from tool supplier with standard PassThru API. It looks up the registry for the DLL path. For GM MDI it is: BVTX4J32.dll You are very welcome to test. Im not surprised if it is not working on non Volvo D...

The Dice Tools behavior regarding J2534 is strange. If you just follow the Passthru API, it won't connect. It needs special treatment of the passed arguments. Always wanted to patch the DLL, but never had the time. Then there are flaws in all the Parameters - to get it working as it should you alway...

I had no Luck reading any address in the 16MB space up to 1000000. If i remember correct, the MPC5xx devices with internal flash can have them disabled. Or it is blended out and if it needs to be read it has to be blended in adress space before. Which is not done by flashloaders of us. Further inves...

Ok, so far i integrated both seed&key algos. I think there will be more around, but testing will show... Then i had a quick view how PCMHammer does the loading of PassThru Devices. It searches the Registry for registered J2534 Devices and their native DLL locations, passes both to Tazzis Wrapper...

Yes, mixing address space is very common and has been done before with MPC5xx architecture. Common automotive approach would be putting all calibration on one flash and leave software where it is in system without internal flash. But bootcode must be in flash since it is mapped to 0x000000. We know ...