I took the 258005 chip from the motherboard. I read the chip and saved the dump. Changed the initial bytes "Asustek" to "OpenProg"
Chip writing via opgui_11.2 failed. In my opinion, it has not even been erased. The "Erasing..." message was less than a second.
Recording via opgui_9.1 - Ok.
Maybe this is important. On the SPI-LV adapter, I used LM317 instead of LD1086.
If necessary, I can measure the voltage.
As you correctly noted the difference is in the erase part.
After issuing the erase command (0xC7), the status register is checked every 100ms to see if the device is still busy.
In one case 0x3 stays for ~5.2s, in the other for just 200ms.
The erase code is exactly the same as the previous releases, but the latest version of opgui has less waiting time for every USB transfer.
Still this difference is unexplainable.
If you put a manual delay of 5 or 6 seconds it should work; not pretty but practical.
In progEEPROM.c, line 1136, insert:
msDelay(5500);
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I took the 258005 chip from the motherboard. I read the chip and saved the dump. Changed the initial bytes "Asustek" to "OpenProg"
Chip writing via opgui_11.2 failed. In my opinion, it has not even been erased. The "Erasing..." message was less than a second.
Recording via opgui_9.1 - Ok.
Maybe this is important. On the SPI-LV adapter, I used LM317 instead of LD1086.
If necessary, I can measure the voltage.
Tried writing a chip using opgui_0.10.1, opgui_0.11.1 - Ok.
Only the latest version has problems with writing the chip.
Can you log with 11.1? Unfortunately 9.1 has a slightly different fomat that makes comparison a bit inconvenient.
You can write as much as you like to the chip, but all old data will be retained. The chip is not erased.
With 11.2
Last edit: Oleg S. 2021-02-15
As you correctly noted the difference is in the erase part.
After issuing the erase command (0xC7), the status register is checked every 100ms to see if the device is still busy.
In one case 0x3 stays for ~5.2s, in the other for just 200ms.
The erase code is exactly the same as the previous releases, but the latest version of opgui has less waiting time for every USB transfer.
Still this difference is unexplainable.
If you put a manual delay of 5 or 6 seconds it should work; not pretty but practical.
In progEEPROM.c, line 1136, insert:
msDelay(5500);
I'm using a compiled version of opgui and I'm fine with 9.1 and others.
I needed to restore the satellite receiver. He works! ))
Thank!