I need some help with this memory. According to datasheet it should be compatible with 25X80, so I tried to program it with 25X80 device selected. As a result - Opgui 0.9.1 gives errors at the end of verification process. Tried to select 25Q40 as target - 0.9.1 gives no errors but checksum mismatch due to half of memory was written. v0.11.0 also gives errors at the end but less then 0.9.1 (115 against 229). I was able to make a dump of original data in that chip, so I can test any combinations you will ask me to do.
Last edit: ded6moroz 2019-09-22
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is Opgui v 0.11.0. It writes ony 1% of total amount of data, then verifies it and stops. If I press read from flash - it completes the task without any problems.
Upper time - interrupted read time (about 4-5% was completed)
Lower time - writing to flash.
Because it is. It's working like this - Erasing.........Writing 0%....1%....Verifying 0%...1%...Stop.(31 seconds - max) (also sometimes opgui shows that writing process was interrupted because of huge amount of errors - 200+)
But if I press read - Reading 0%...1%...2%......and so on.............99%...100%. (118 seconds)
v0.9.1 uses double SPI mode to program it. It is supported, but memory chip has quad-mode enabled from the factory, so we need to use 25Qxx protocol and the only chip currently supported - 25Q40.
v0.11.0 can read data from 25Q80, but if I press SAVE button - HEX-file won't be created. with any name I'm trying to use.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello everyone.
I need some help with this memory. According to datasheet it should be compatible with 25X80, so I tried to program it with 25X80 device selected. As a result - Opgui 0.9.1 gives errors at the end of verification process. Tried to select 25Q40 as target - 0.9.1 gives no errors but checksum mismatch due to half of memory was written. v0.11.0 also gives errors at the end but less then 0.9.1 (115 against 229). I was able to make a dump of original data in that chip, so I can test any combinations you will ask me to do.
Last edit: ded6moroz 2019-09-22
Can you list the errors?
Can you send me the file written and the logfile?
This is what version 9.1 shows...
This is Opgui v 0.11.0. It writes ony 1% of total amount of data, then verifies it and stops. If I press read from flash - it completes the task without any problems.
Upper time - interrupted read time (about 4-5% was completed)
Lower time - writing to flash.
Also v 0.11.0 is unable to save files
Last edit: ded6moroz 2019-09-25
Why do you say it writes 1% of memory?
Unable to save files? Memory files or log files?
Because it is. It's working like this - Erasing.........Writing 0%....1%....Verifying 0%...1%...Stop.(31 seconds - max) (also sometimes opgui shows that writing process was interrupted because of huge amount of errors - 200+)
But if I press read - Reading 0%...1%...2%......and so on.............99%...100%. (118 seconds)
v0.9.1 uses double SPI mode to program it. It is supported, but memory chip has quad-mode enabled from the factory, so we need to use 25Qxx protocol and the only chip currently supported - 25Q40.
v0.11.0 can read data from 25Q80, but if I press SAVE button - HEX-file won't be created. with any name I'm trying to use.