> Le 22 nov. 2024 à 08:24, Anastasia Klimchuk <a...@chromium.org> a écrit : > >> Technically is there a risk to not be able programming the chip which i’m >> working, why the chip is not detected with its real name, what is the >> meaning of « SFDP-capable chip» > > The chip can be handled as "SFDP-capable chip", it's not a problem. When the > chip entry is not found in our database (as you noticed), then flashrom tries > to talk to it via SFDP protocol, and if the chip supports the protocol then > it's all good. > > About programming on the chip: we did have a report earlier about segfault > when using macOS, however we didn't have a stacktrace. Later, a very similar > bug was reported for OpenBSD and that one was with stacktrace and a patch! > The latter now fixed, it is possible it was the same bug. Details here > https://ticket.coreboot.org/issues/551 > <https://ticket.coreboot.org/issues/551> and here > https://ticket.coreboot.org/issues/555 > <https://ticket.coreboot.org/issues/555> It's for programming the chip, > reading is fine. > > So there is a bug that might affect you, it is present in v1.4 and fixed in > v1.5 which is planned to be released soon, ETA 6th December.
Hello Anastasia, This morning I’ve tried to flash one ZETTA 25V04 memory with my CH341A plus grabbers with the G-flash (flash encaosulated GUI under macOS), it alll worked fine. In fact I did erase then flash then verify then read, many tests so it works fine eventhough the chip is only recognize SFDP protocol. However I did notice a condition to work, if the firmware size to be flashed does not match exactly the same physical size of the chip then G-flash (flashrom) will refuse to write. Once I added FF’s to match the sizing then it worked fantastic. It seems the v1.4 does not affect or bug with this chip but I’ll need to flash some other chips, if problem then I’ll let you know Albert
_______________________________________________ flashrom mailing list -- flashrom@flashrom.org To unsubscribe send an email to flashrom-le...@flashrom.org
