darkman5001 wrote:Many have worked hard on this in many ways, not just you, and not just me. Its about team work and pulling our resources together and doing it as a team. I have always seen this as a team effort as I know it can't be accomplished by one person without taking an extreme amount of time and resources of the one person. I look at it this way... We are all helping the world and this community. Not about you or me.
Shows your newness around here ... You're preaching to the choir!
Not that there is anything wrong with being new ... We all have to start someplace!
Whatever that means. Not sure what you are trying to say there. I may be new here, but you don't know my capabilities... Nobody does. So keep judgement to yourself. Regardless, this thread is about P12 development. Rant Over! Let's get back to work.
Lets stay on topic and stay technical please. Any further non-technical posts will be deleted. Its a 49 page thread and we dont need to lower the signal to noise ratio.
Thanks gampy for the latest p12 branch and darkman5001 for testing some more we have found the 2007 P12s are the P12b variant with the 2Mb flash, and the image is larger and with slightly different checksums. We'll need to add code to know these OSIDs and add support for the 2Mb image and update the checksum code, then the P12b support should be good.
@kur4o your right we could use the logic of when hardware type is P12 and flash size is 2Mb use that, but it'll be tidyer to keep all the image size information in the same place in pcminfo.cs, and I think we can find a list of OSIDs. Otherwise we end up with more logic in more places for different hardware types, since P10 needs to do the opposite thing and only read half the chip when a 1Mb chip is detected and we solved that by adding imagesize to pcminfo by OSID.
I have a few bins from different OSs I can post, hoping someone can help disassemble them for modifying, and hopefully I can help progress/research on these quirky computers. P12 and P12b I have been able to successfully upload the primary, slave, and shadow programming (with some help of course) as I am primarily doing this for the ecotec LSJ platform (04-07 saturn ion redline, 05-07 chevy cobalt ss 2.0) In my research I was able to get ahold of 2 different trailblazer p12s as well, 06 trailblazer is p12 where 07 trailblazer is p12b. ALL LSJ ones 04-07 are p12. I have pulled tune repository from 07 hummer as well and see that it is a p12b.
Now: with HPT and the other programs I have used the p12b takes twice as long to pull tunes/binaries out of. it appears so far I can write successfully those to regular p12 boards but I have not tested if they work yet. I hope some of this helps!
last bin dump of tonight, I have plenty more from different OSs, mostly from the platform I am interested in. If for some reason there is more to the p12b and it is in fact 2mb chips I will need to get another in my hands and do some more testing with it.
Really hoping someone can help hack these files for some much needed tuning support
Thanks thats very helpful. At the moment we dont know how to read or write the slave and the theory is that they are all the same and it doesnt need to be updated, but your slave bins give us something to investigate. We also did yet realise there was a slave and a shadow, so that is interesting too.