emard
commented
5 years ago HI
I had seen similar issues before with various chips and other programming methods, not only ujprog. Not only reading status register but also pulsing CS line while clocking and similar forces reading WIP to actually return correct value...
I'll test your patch on ULX3S and ULX2S, if they still work, I'll merge :)
On 3/28/19, Ben Wolsieffer notifications@github.com wrote:
Adds support for Lattice's official ECP5 evaluation board. This board does not have an LED connected to the FTDI, so
cbus_ledis assigned to an unused pin.I ran into an issue where the WIP and WEL status bits would never clear after performing an erase (even with a very long wait), but I was able to work around this by reading the status register before performing the erase, which somehow prevents the issue from happening. You can view, comment on, or merge this pull request online at:
https://github.com/f32c/tools/pull/15
-- Commit Summary --
- Add support for ECP5 evaluation board.
-- File Changes --
M ujprog/ujprog.c (18)-- Patch Links --
https://github.com/f32c/tools/pull/15.patch https://github.com/f32c/tools/pull/15.diff
-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/f32c/tools/pull/15
Adds support for Lattice's official ECP5 evaluation board. This board does not have an LED connected to the FTDI, so
cbus_ledis assigned to an unused pin.I ran into an issue where the WIP and WEL status bits would never clear after performing an erase (even with a very long wait), but I was able to work around this by reading the status register before performing the erase, which somehow prevents the issue from happening.