-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WiP: add W25N01GW and GD5F1GQ4RB9IG #29
base: main
Are you sure you want to change the base?
Conversation
And also this:
Is it possible that the flash is not exactly 128MB? |
Hi! Everything is done correctly, but the Status register (0xC0) return E_FAIL flag, this is an internal error, most likely related to the supply voltage or logic levels, your chip work on a 1.8V supply. |
Haven't oob_free_layout fields been removed? |
But the chip works normally after flashing and all other pages were written okay. What could be the problem with writing to the last 64 pages? |
Please update on new version. |
a76fcf9
to
924f96c
Compare
I've rebased to latest main, the problem is still there. |
Then I don’t understand why you have an internal error, I recently used a similar chip with a 3.3V supply, there were no problems. Is this a new chip or has it been used somewhere? Maybe it has some kind of set protection... |
It is also possible that this is not a marked BAD block. |
I tried with at least 5 pieces of the same model. Always errors at the end. |
From your posts, I see return error flags programming and erase from register 0xC0. I don't understand these reasons. |
If I specify the size like this:
there are no more errors. Do you think the flash can really be 1 page (128kB) shorter? Possibly a hardware bug? |
this is the result when I read erased flash:
But interestingly, no error at the end. |
Before writing the last block, check the state of register 0xa0, make sure that there will be 0 or the bits responsible for setting the protection are not affected. Try turning off bit the quad mode, it turns on in the highlighted area in the screenshot with the source code. |
|
Hi @McMCCRU ,
I am adding two new chips here but with one I am getting following error, can you please advice what could be wrong?