pcmhacking.net

kojab wrote:Hi malser. If you want to read from 0 to FFFF (64k) this program will work. You won't be able to read from 10,000 to 1FFFF

Cheers
Richard

Thanks for the answer. I will ask a question on another. Memory am29f010 It is had two banks on 64к. 1 - from 0000 to ffff and 2 from 10000 to 1ffff. Switching between banks occurs to the senior А16 address (2 pin of a microcircuit). If on it Logic 0 - 1 bank, if Logic unit - 2 bank is readable. Switching this address I can read at first 1 bank, and then 2 bank?

Assuming you are using a 128 k bin , if you were to alter the address pins it would probably stop the ecm from booting up and then you couldnt connect to it with flash tool.

Ok a quick question I might be missing something here but in Flash tools there is a Migrate function for Cal files only. As I've been working with bin files is there a way to get the cal file from a bin beside putting into the ecu and reading the chip or even a way to migrate a bin file to the new version?

if you don't have realtime gear to do it yourself post the bin file up, one of us will load it into our test bench and suck the cal out for you.

I have the capable gear to do it I was just wondering if there was and easy way to upgrade the bin to the latest version that's all without going to the hassle of uploading and downloading all the time. Means connecting to the car uploading the Cal file, reprogramming the NVRAM to the latest version migrating the Cal file downloading to the NVRAM then uploading the bin to burn to the EEPROM for the car.

But if that is the steps then that is what I'll do.

Jason

well depending what version your running you should be able to upload the new bin file without removing the nvram .... so in that case my normal process...

* extract current cal file from 808
* upload latestly release of 12P bin file to 808
* migrate step 1 cal file to suit new bin
* upload to 808

Hello I beg your assistance. My car is exactly as in this topic https://pcmhacking.net/forums/viewtopi ... 95&start=0. In the block from me is a flash memory am29010 (not ROM M27512). Read the firmware I can, but written in the block does not work. Attachments, which I thought from the car, BinaryDefinitions 300410.xml and log file records calibrations. What does this line: Please Submit This Code For Vehicle Support: 57a4e992b0991297171e5a28676. Where is my mistake?

Hi, supporting vehicles with flash memory based PCMs is very time consuming and difficult and as such will only be supported for aussie based PCMs that I have access to. The reason being is a program needs to be developed that can be uploaded to the PCM to do the erasing and writing functions. Getting the entire bin out of the 128k flash memory over ALDL presents the same issue as GM only use a 16 bit address in the normal mode 2 ALDL function, so a program also needs to be written to do this.

Tell me if I'm wrong here.
I was looking at the bin file in a hex editor and it looks like the Cal file is made up from $0000 to $1AFF so I've cheated and used a hex editor to generate a Cal file then migrated from V1.00 to V1.04 it using Flash tools then stuck in in front of the V1.04 bin in a hex editor. Burn/Flashed eeprom with the new bin. Will this work or am I barking up the wrong tree here.

Jason

Your spot on