Calterm CM2450

[heber2192]

Had an issue happen when reading out 2 different styles of 2450 ECMS. At the end of saving the original file on either ecm, itll error out and throw the explanation of "The range of memory requested does not correspond to physical memory in the server's address space." Can anyone shed some light on this and how to correct it?

[APC]

some of the newer 2450s will not allow you to read out the program anymore, especially if you are working on the BHQ - Dodge Ram 6.7L engine...

what engine is the ECM From ?

[heber2192]

(07-22-2025 )APC Wrote:  some of the newer 2450s will not allow you to read out the program anymore, especially if you are working on the BHQ - Dodge Ram 6.7L engine...

what engine is the ECM From ?

One was a '20 BHQ RAM, the other was an early x15 cm2450. How exactly did they block the reading? First time encountering this issue and I would really like to know more about it

[APC]

the BHQs are not able to be read FULLY via calterm, or any other tool as far as im aware.

the ECM does not give up the 6th block of data, which stores some sensitive data about RSA encryption and a digital signature verification process (don't quote me on this...)

only way to read those ECM's out are with a JTAG, reading the processor directly or by finding a way to extract the 5 blocks, and attempt to rebuild the 6th block of data that it does not give you.

none of the methods mentioned above can be done with calterm, there is a 3rd party software that does give you a partial readout (wont mention the name due to forum rules but it is used frequently by diesel tuners, HP-xxxxxx) but it is useless unless converted into intel-hex format and rebuilt properly...

as far as the X15 2450, you should be able to read out the data just fine if the engine is a BKR engine code, if it is a BNN, it could possibly be the same story as the BHQs?...

[heber2192]

Thats a direction for sure. Ive swung calibrations back into intelhex from 3rd party programs and drug them into calterm. Im assuming id be able to run the CRC function in calterm once I bring it back to intelhex. The checksum has been invalid when trying to read with a 3rd party program

[APC]

the CRC function in Calterm does not properly calculate the checksum for that ECM... it is a different checksum the BHQ ECMs use, something done by Chrysler, not by Cummins...

once you convert it into intel-hex, you still need to rebuild the 6th block of data that is missing in order for it to be a complete program.

also keep in mind, you'll need to recalculate the Digital Signature of the entire file as well, both RSA/Checksum and Digital Signature need to be properly dealt with in order for the ECM to accept any modified file or anything other than completely stock file. so much as changing the speed limit and sending back in will trip out both the checksum and the digital signature, and fail the program at 100%...

FYI: Rawze has written some software that can reconstruct the missing block(s), etc. once it has been copied out and converted to binary format. It can get around some of these the check-summing issues too. If your doing that kind of ECM work, you should likely go onto his mumble server with those kinds of discussions instead.
mumble> http://rawze.com/forums/showthread.php?t...63#pid2163

[heber2192]

Super information thank you! Ill go over and check out his mumble. Have listened in a couple times in the past