alex_sk wrote:One of often case for error p0601 is died capacitors in Vcc lines, with result of fluctuation in power voltages and errors in data exchange between chips. Or faulty voltage regulator.

Thanks.. .I try test.

alex_sk wrote:One of often case for error p0601 is died capacitors in Vcc lines, with result of fluctuation in power voltages and errors in data exchange between chips. Or faulty voltage regulator.

I Alex... I check batery of car, alternator, grounds... I change ecu and same error p0601. Car start but RPM limit at 3000...

Any other idea please?

rclassic wrote:I Alex... I check batery of car, alternator, grounds... I change ecu and same error p0601. Car start but RPM limit at 3000...

Any other idea please?

What''s the car history. It's hardware or software parity/chk issue. If error is previous to some changes, it could be ecu or some immo/bsi fault. If error is post eeprom mod it's issue with your mod or utility.

It is possible was bayed ecu with the same defect.


And nice news about 5P08C3. This chip now full supported by NeoProgrammer software and simple CH341 programmer.

NeoProgrammer can work with lots of EEPROM and Flash.

I have tried with another switchboard and there was the same problem ... Finally I have used a second hand switchboard if cloning using an emulator, and it no longer fails, so the failure was safe in the cheksum of the original eeprom. Using another eeprom I do not have the fault, but I must use emulator to start it.

VVDIprog and upa support 95p08 too.

alex_sk wrote:It is possible was bayed ecu with the same defect.


And nice news about 5P08C3. This chip now full supported by NeoProgrammer software and simple CH341 programmer.

NeoProgrammer can work with lots of EEPROM and Flash.

I can confirm the NeoProgrammer you posted seems to work beautifully with the 5P08 and CH341 (I tested with the black ch341a with selectable 3.3V/5V). Good news indeed if you just need the PIN or want to fix an immo that is acting up and don't feel like investing in more expensive hardware right off the bat.

I also tried the more recent 2.2.0.3 version, but that did not work, only wrote the first page on the chip. Too bad the dev apparently only posts on that Russian forum with the cyrillic captchas so I can't really get in touch with him.

I am the author of Neoprogrammer, can you explain what's wrong with release 2.2.0.3
Does first page means half of memory (firsts 512 bytes)?

TTAV134 wrote:I am the author of Neoprogrammer, can you explain what's wrong with release 2.2.0.3
Does first page means half of memory (firsts 512 bytes)?

Oh, hello, I honestly didn't expect for some god-like dev to seek out a puny mortal's woes like this.

The datasheet for ST95P08 says that "The 8 Kbit memory is organised as 64 pages of 16 bytes", so the first page would be the first 16 bytes, right? Version 2.2.0.3 does not automatically detect the chip (message 'SPI ID: F0FF'), and after selecting it manually it reads fine, but erasing/writing never progresses beyond 0xF and you have to cancel the operation from the program (message 'Number of written bytes not equal to IC size'). Version 2.1.0.16 works very nicely and you can easily confirm this behaviour of 2.2.0.3 with it.

Thank you for making such awesome software!

Very helpful description of the issue, thanks.
Write and erase process are very similar, only data differ.
Detection is using a particularity of this component described in STmicroelectronics Application note AN1116.
Write/erase/detection are depending of good response of status register of the chip.
Write process: When chunk of data (16 bytes at a time) is sent to the chip, the BUSY state of status register is read in a loop until it goes to 0. It seems that it never occurs for you. Pressing CANCEL button ends this loop.
My first conclusion of the possible cause is: The chip is solder on a board and data transfer is altered by other components.
If yes, remove the chip from board and make a try.
Question: Are you using version 2.1.0.16 and 2.2.0.3 at the same time in same conditions?

Nope, it is already desoldered. The conditions are the exact same, only the program that is accessing the ch341 changes. I really don't have the knowledge to make any educated guesses, but reading your answer and the AN1116 makes it seem that there might be some problem reading the status register since it is used also in the identification process, as you already said.