Hello Sakthipriya, Sorry it took me a while to get to this. Thanks for the logs, I looked into them.
First thing that I noticed, your working vs not working scenarios are running on different environments (different flashrom and linux versions), working > flashrom v1.6.0-devel (git:v1.5.0-49-g1516420f) on Linux 6.12.0-rc4 (x86_64) not working > flashrom v1.5.1 on Linux 6.14.0 (x86_64) Is this always like this, working vs non working scenarios in different environments? Have you ever had both happening on the same environment? Also about the logs, the log for failed scenario is very short because the output is redirected to a file, and you haven't attached that file. You can see in the logs, line 3 says "Command line (7 args)" and file name is the last. Is it possible you can share that verbose log file? On Fri, Jun 6, 2025 at 4:19 PM Sakthipriya M <[email protected]> wrote: > > Hi, > Please find attached the logs for working as well as for non-working > scenarios. > It fails occasionally, but once it fails "Flashrom" command fails continuous > from there with same error and we need to flash with "Dediprog" > Can you please help on this? > Thanks, > Sakthipriya M > > -----Original Message----- > From: Anastasia Klimchuk <[email protected]> > Sent: 28 April 2025 17:34 > To: Sakthipriya M <[email protected]> > Cc: [email protected]; Manimehalai Selvaraj <[email protected]> > Subject: Re: [flashrom] Re: Erase fails with flashrom using mtd > > Hello Sakthipriya, > > One thing that I thought about, maybe some regions on your chip are > write-protected (which would prevent erase too). As you are saying, > > > Chip size is 16MB, Flashrom erases successfully till 6MB and fails > > then > > Maybe the first 6MB are not protected. > > WIll you be able to provide verbose logs? To have verbose logs, you need to > add -VV to the command line (or -VVV for even more). > If you will be able to create verbose logs, also look at them yourself first > - maybe there are details of the error that can help you. But you can also > send logs to this thread. > > It is possible to specify exact regions of the chip memory to perform an > operation, see info on manpage https://flashrom.org/classic_cli_manpage.html > relevant options would be: > > -l, –layout <file> > –ifd > -i, –include <region>[:<file>] > > and check the examples > > Also check the docs about write-protection, some of this can be useful > https://flashrom.org/user_docs/example_partial_wp.html > https://flashrom.org/user_docs/fw_updates_vs_spi_wp.html > > On Fri, Apr 25, 2025 at 8:35 PM Sakthipriya M via flashrom > <[email protected]> wrote: > > > > Hi, > > > > Any update on this. We tried using the source from master repo and tried > > still facing same issue. > > > > Let us know if you need more info on this. > > > > Thanks, > > > > Sakthipriya M > > > > > > > > From: Sakthipriya M > > Sent: 15 April 2025 14:26 > > To: [email protected] > > Cc: Manimehalai Selvaraj <[email protected]> > > Subject: Erase fails with flashrom using mtd > > > > > > > > Hi, > > > > We are using customised Elkhart lake board, when we tried to update > > BIOS using flashrom, following error is reported, “linux_mtd_erase: > > MEMERASE ioctl call returned -1, error: Input/output error”. But > > sometimes we could update BIOS successfully. Chip size is 16MB, > > Flashrom erases successfully till 6MB and fails then > > > > Flashchip: Macronix MX25L12835F > > > > OS: GNU/LINUX > > > > Kernel: Tried in 6.12.5 and 6.14.2. > > > > Ensured that MTD kernel configurations are enabled. > > > > Flash chip is detected as “BIOS” in /dev/mtd0. > > > > > > > > Thanks, > > > > Sakthipriya M > > > > _______________________________________________ > > flashrom mailing list -- [email protected] To unsubscribe send an > > email to [email protected] > > > > -- > Anastasia. -- Anastasia. _______________________________________________ flashrom mailing list -- [email protected] To unsubscribe send an email to [email protected]
