Hello Manfred, Thanks for posting. Looks like what happened is this: the chip (you said T25S16PQ19V1) is not directly supported, in this case flashrom tries to talk to it via SFDP and see if it might work via the protocol.
SFDP provides the information about the chip, and one of erase opcodes (0x42) was not recognised. As a note, I think usually 0x42 is opcode for OTP program, not for erase. But, from the logs you provided, apart from this one opcode, the rest of information from SFDP was recognised and that's why there is a message "All standard operations (read, verify, erase and write) should work." Given the message, there were other erase opcodes which were recognised (only that one 0x42 ignored). If none of the erase opcodes are recognised, the message would have been different. On Sun, Jun 14, 2026 at 4:34 AM Manfred H. Günzl via flashrom <[email protected]> wrote: > > Hi flashrom team, > > I got the message "Please report this at [email protected]" and here > it is: > > Revers engineering a MD81s WiFi cam module, I read out the T25S16PQ19V1 > SPI flash after desolder using an CH341A patched for 3.3V with: > > $ sudo flashrom --programmer ch341a_spi -r flash_orig.bin > flashrom v1.8.0-devel (git:v1.7.0-48-g0b14d50a) on Linux > 6.17.0-35-generic (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > spi25_get_erasefn_from_opcode: unknown erase opcode (0x42). Please > report this at [email protected] > === > SFDP has autodetected a flash chip. > All standard operations (read, verify, erase and write) should work. > Additionally, flashrom supports RPMC commands via SFDP autodetection. > We may add support for more features via SFDP in future. > If you are interested, join us on the mailing list > https://flashrom.org/contact.html#mailing-list-1 > === > Found Unknown flash chip "SFDP-capable chip" (2048 kB, SPI) on ch341a_spi. > Reading flash... done. > > * Reading two times gave the same result. > * Using binwalk gave no output, but may be normal for this type of toy, > likely running an Anyka, Jeveli, or Novatek RTOS SoC. > * Using strings gave some lines that look like successful read firmware > e.g.: > > ","android_img":"ic_continuous_shooting_off","iOS_image":"[email protected]","url":""},{"id":1,"text":"3PCS","android_img":"ic_continuous_shooting_3","iOS_image":"[email protected]","url":""},{"id":2,"text":"5PCS","android_img":"ic_continuous_shooting_5","iOS_im > age":"[email protected]","url":""},{"id":3,"text":"10PCS","android_img":"ic_continuous_shooting_10","iOS_image":"[email protected]","url":""}]},{"text":" > > Thanks for providing flashrom > > Manfred > > _______________________________________________ > flashrom mailing list -- [email protected] > To unsubscribe send an email to [email protected] -- Anastasia. _______________________________________________ flashrom mailing list -- [email protected] To unsubscribe send an email to [email protected]
