ECUFlash - Getting close!

[Td-d]

Originally Posted by endrswrd

I have flashed both a stock image with the 0 padding issue and one of the shiv roms with the bad checksum (I believe its the calculation that is having issues). Both cars were perfectly fine after the flash.

Ah, interesting - so you didn't correct the checksum error? I believe Skullworks did, might be the issue.

[vgi]

Originally Posted by jamesm

yeah i wouldn't go flashing anything not based on the rom that came off of your own car until more is understood. personally i've flashed roms based on my pulled image as well as another (stock image) dozens of times with no issues. i suspect the guy flashed the wrong rom for his car or had some other sort of hardware issue.

maybe you're right, I hope it's not a beta soft.

[Td-d]

I can tell you that using the various older version of Ecuflash, I've used it literally hundreds of times on my STI, without any problems.

[vgi]

Originally Posted by Td-d

I can tell you that using the various older version of Ecuflash, I've used it literally hundreds of times on my STI, without any problems.

just like many other folks i have faith in Ecuflash but it's still a beta
PS for brz i mean

[SkullWorks]

Originally Posted by Td-d

That's what I'm thinking as well - he flashed an OFT stage 2 rom I think. At this stage, I would edit whatever rom was pulled off the car to flash, the architecture (i.e. CAL ids) of the various roms is only just being identified.

I hope he managed to get hold of Skullworks, they should be able to take him through the SHBoot process.

Per MikeyPSF: He understood that Colby had worked out the recovery method for this ECU, BUT he was under the impression that there was an AUTO recovery feature, that appears to be not working ***IN MY CASE*** I have full faith that it will work, However Colby is getting married this weekend, Mike offered to try and steal some time from him to help me solve my issue, I insisted that he not think about my utter stupidity until after he has taken care of getting hitched.

Again I have full faith that my issue will be handled early next week and that we will find the issue is my stupidity.

[Td-d]

I'm sure you'll come right - don't be too hard on yourself - I've also nearly fried the ECU.

I didn't realise that when I got into the car, I had kicked the OP2 extension cable just enough to have it half in half out... I was lucky that I picked it up after a couple of failed attempts, and with the ignition on, and the cable firmly in place, I managed to flash.

I remember having a couple of stiff whiskeys that night

[ztan]

Originally Posted by endrswrd

I have flashed both a stock image with the 0 padding issue and one of the shiv roms with the bad checksum (I believe its the calculation that is having issues). Both cars were perfectly fine after the flash.

How does EcuFlash behave when writing the padded ROM files to our ECU? Does it write all the 00s or does it write from 8000 on?

Asking because my ROM pull was padded and I have not yet tried to write with this beta.

[Ralph Spoilsport]

Originally Posted by Td-d

I'm sure you'll come right - don't be too hard on yourself - I've also nearly fried the ECU.

I didn't realise that when I got into the car, I had kicked the OP2 extension cable just enough to have it half in half out... I was lucky that I picked it up after a couple of failed attempts, and with the ignition on, and the cable firmly in place, I managed to flash.

I remember having a couple of stiff whiskeys that night

Along those lines... the only thing I absolutely detest about my BRZ... is the location of the OBDII port. It's like they designed it to put the OP2 in harm's way.

[vgi]

Originally Posted by ztan

How does EcuFlash behave when writing the padded ROM files to our ECU? Does it write all the 00s or does it write from 8000 on?.

well, based on this

Originally Posted by endrswrd

I have flashed both a stock image with the 0 padding issue and one of the shiv roms with the bad checksum (I believe its the calculation that is having issues). Both cars were perfectly fine after the flash.

if i had to guess, looks like the EcuFlash just writes block 8000-13FEFF and thus the padding difference between oft (FF) vs ecuflash (00) for the first 32768 bytes and last 256 bytes doesn't matter as long as checksum correction is not applied

[Td-d]

Originally Posted by ztan

How does EcuFlash behave when writing the padded ROM files to our ECU? Does it write all the 00s or does it write from 8000 on?

Asking because my ROM pull was padded and I have not yet tried to write with this beta.

To answer that:

Originally Posted by cboles

Here is a full ROM for ZA1JA00C to get you started. I'll be posting up a beta for and EcuFlash version that does the "OEM style" 0x8000-0x13FEFF reads and writes in the next day or so, just to get you started while I work on finishing up a kernel based reflash which will be quicker and more flexible, along with being able to read out the full ROM. Since there is no longer a kernel loader in the stock ROM, I will be adding a patch to allow for this. I'm also working on another patch to add fast and complete logging capability.

[ft_sjo]

Is the boot loader part of that address range?

[Td-d]

I assume so - my understanding is that Colby is also coding a new kernel based reflash alongside the logging capability.

[Td-d]

I have started on the Ecuflash definition, it's a work in progress and requires an updated 32bitbase.xml - check out the original definition thread for the new links.

[utekineir]

is this viable for the unwashed masses yet?

tactrix cable waiting,

very computer literate, but 100% programming retarded.


thanks,