Memcal Burning Not Starting The Car

[Rhysk94]

Hey guys!

Finished up a tune this morning on a customers car using a NVRam.
I had UV Erased his factory memcal and then burnt in the .bin file. All was ID'd okay, blank checked okay, Written & verified okay.
The car wouldn't even start. NVRam back in and it fired up immediately.
I then tried it on a flash chip, same thing every thing checked out through all the steps and once again it wouldn't start the car yet as
soon as the NVRam went back in it fired right up.

Any ideas of where I went wrong or what could of happened.
Car was a VS N/A ecotec for reference.

Cheers

[pman92]

Was it a full bin you wrote to the memcal, or only the calibration section?

[Rhysk94]

Was it a full bin you wrote to the memcal, or only the calibration section?

The full bin as far as I'm aware.
Opened the .bin in the GQ programmer and then wrote it to the chip

[antus]

read bin from car with ose flashtool to get it all, or disable 'calibration only' in oseplugin, read n save. look at chip size vs file size. burn so that the end of the bin is at the top of the chip. eg 32kb padding for 32kb file on 64kb chip. stacking is easy to do this but bottom copy is filler and pcm uses top copy.

[Rhysk94]

Cheers Antus Ill try that on the next one I get through for a tune!

[Rhysk94]

For anyone reading this, it ends up being the checksum, have to manually set it to AA everytime i save the .bin ready to burn.

[heff0018]

Great to know as I haven’t been able to successfully burn a chip yet. I understand the process but I’m sure it’s just something small like that.Thanks

[immortality]

What .bin file are you using?

the enhanced tuned should all have the checksum set to AA as default but any other .bin file you will need to set manually.

[antus]

Yeah I am not sure why anything would be different between nvram and memcal. But I've only ever run an '808 on my own car, so its possible I missed something all these years that isnt talked about much. If it is the case about about needing to set AA only for memcal, then that would mean the bin has code added to detect nvram and skip checksum only when running from nvram hardware, as well as the checksum being present but not tested because of that code. I am also interested to know what bin we are talking about here.

[Rhysk94]

What .bin file are you using?

the enhanced tuned should all have the checksum set to AA as default but any other .bin file you will need to set manually.

I only use enhanced tunes.
Yeah I was under that assumption but trying it on 3 different cars/bins/tunes all to the same result.