NSFW wrote:Is there any chance that voltage is dipping during the erase?
Corruption sounds more like an electrical problem than a software problem.
I'm just guessing though.
[12:36:27:692] Battery Voltage is: 13.649
kur4o wrote:I think it is time of waiting till the erase is done, Usually 2-3 seconds per segment.
You can also check if the erase is done with reading register where 3030 is loaded, And wait for specific response.
We are reading the address where erase is commanded (0x3030) for 0x640000 iterations, but are only looking for change.
I've often wondered if we should be looking for a change to FF's ...
Intelligence is in the details!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!
My hardware arrived today and ive set it up on the bench. So far so good, Ive pulled a bin of the pcm in its virgin state. Not sure when I'll have time to get too serious with this but im keen to test and see if I can figure anything out.
My P12 diffs, they are NOT valid diff patch files, they are strictly hand patches ...
The techniques used are likely not the best way or place, they were done in the method of least path of resistance to an end goal and not intended as production code!
I use preprocessor directives to select between P12 and P01/P59 purely because it's easy, my build system handles it.
In VS it's done by adding P12 to the Conditional Compilation Symbols in the projects properties under the Build tab...
For the kernel it's done with '-D=P12' added to the gcc.exe command line.
antus wrote:My hardware arrived today and ive set it up on the bench. So far so good, Ive pulled a bin of the pcm in its virgin state. Not sure when I'll have time to get too serious with this but im keen to test and see if I can figure anything out.
Antus, what is the vin number is programmed into that P12 you have there? I am trying to look up the operating system numbers. I don't think the P12 you got came from a trailblazer or envoy.
Open the bin in a hex editor ...
Browse/goto address 0x8004, 0x8005, 0x8006, 0x8007
In the bin Antus posted you will see, 00 C0 AF AB
Convert that to decimal and you will get: 12627883
That is the Operating System ID.
The VIN is the 17 ASCII bytes starting at 0x40E8 or 0x60E8 ...
Intelligence is in the details!
It is easier not to learn bad habits, then it is to break them!
If I was here to win a popularity contest, their would be no point, so I wouldn't be here!