Attn: Anyone With Comp Prog Or Ee Talent

[Zac]

already got it (was hosted on vs infact i think)

4.4 is quite different looking although I haven't really played enough with it yet because I had no use for it because it wouldnt run on my car.

[Guest Guest]

So is this topic dead? I'm looking into lh2.4 chipping (seems to be easier, but i'm not terribly deep into it yet), but a lot of tools favor newer stuff, but at a price. Someone mentioned WinOLS, a license for it runs a cool $2k, and does not include the checksum generators one would need to "fix" new images.

And they dont sell to individuals either, but they've got some really cool stuff :)

[Slater]

So is this topic dead? I'm looking into lh2.4 chipping (seems to be easier, but i'm not terribly deep into it yet), but a lot of tools favor newer stuff, but at a price. Someone mentioned WinOLS, a license for it runs a cool $2k, and does not include the checksum generators one would need to "fix" new images.

And they dont sell to individuals either, but they've got some really cool stuff

I actually acquired a slightly older version of WINOLS and was not impressed with it at all. You have no way of knowing if the "maps" it "thinks" it finds are real, or what they are to. They could be limp home mode maps for all you know. I don't know. I just don't think a generic swiss army knife is the answer. A custom developed Volvo Motronic-specific program is the only REAL solution.

I've read and disassembled the PES ECU I bought for my 96R but I believe the other chip they added (Programmable logic chip sorta deal) keeps it from returning any valid results for some map data (or maybe it is valid stuff-some of their maps were just maxed out almost everywhere...either way the car still ran on a copy of their chip but seemed weird and eventually started to throw a p605 code)

Yeah, that is a PIC chip - most of the tuning companies use it. It's basically an "encryption" or scrambling chip that could contain god knows what memory scrambling code. The data on the ROM chip itself can be read if removed from the PIC board, but it will be "scrambled". And if you try and read the ROM while it is attached to the PIC board (like The ECU has to), the PIC chip will deny sequential read functions from a chip reader (but allows the ECU to read the chip normally because it just looks up data ramdomly i.e. some data here, some there. It doesn't try and start with the first memory location and read the whole chip sequentially).

What you would need is to decrypt the PIC chip, or find some burner that has a random read function. But most burners do not do that because they know people will be reading encrypted chips that way (it's the only possible reason why you would want a random read) and don't want to get caught in the middle of a huge lawsuit.

Also, to add fuel to the fire most of the tuning companies sand off or deface the top of the PIC chip, so you don't even know the specs or maker of the PIC chip to even find a datasheet on it.

[Zac]

This wasn't a PIC series mcu but was a generic array logic chip by Lattice - but either way it did the exact same thing...luckly only returning a few bad numbers for parts after the main code so it still ran :-P

Who else is playing with these ECUs? There's a list of all of the map addresses after a few (assumed) constant values after the code ends.

Still playing with this but I'm waiting until I can build a few hardware tools to get more into this - not to mention I'm lazy