[flashrom] Re: In a bind
Try to shorten the wires between SOIC8 and CH341A and/or replace them with the copper ones, maybe that would help. On Sun, Dec 29, 2019 at 9:00 PM AL VAN DER LAAN wrote: > > I am trying to flash the HP Elitebook 850 G2 - as mentioned three went > succesful but the one I forgot to erase first did not. I have read up a lot > about this in the various forums. I tried with -f and it seems part of the > bios chip is actually locked. The laptop still boots properly and I can > install Windows on it but cannot change any of the bios settings as the TPM > is preventing me to manipulate it. I mean it is not too bad these units are > going into the resale channel but not the one with the locked bios. I will > see if there are any samples, and if I am successful I will upload my process. > > > > On Dec 29, 2019, at 12:42 PM, Mike Banon wrote: > > > > You haven't described what device you are trying to flash. Usually > > there's nothing wrong with using SOIC8 test clip, for the laptops. > > However, some routers/hdmi recorders/other devices of this type, may > > try powering its' main CPU from a test clip and interfere with your > > programming through a test clip. In example, here's a flashrom mod I > > had to do for making it possible to read a firmware of one router > > through a test clip https://review.coreboot.org/c/flashrom/+/31830 > > (because a CPU tries to power itself from a test clip and access a > > flash chip, its' only available for 30% of each second to a programmer > > behind a test clip), however - despite a similar code for read and > > write - this router becomes software bricked if a write has been > > attempted, and then a chip is inaccessible at all without a > > desoldering. > > > > So a chip itself could be fine, and such problems could be caused by > > an imperfection in your device's hardware design. Other problems could > > be i.e. too long cables between a SOIC8 test clip and a programmer, or > > their poor quality (i.e. electrical resistance of aluminium wires is > > about 1.5x times higher than of the copper ones with the same > > properties). > > > > On Sun, Dec 29, 2019 at 8:32 PM AL VAN DER LAAN wrote: > >> > >> Hi Mike, thanks for responding. I tried with Linux as well and am using > >> the SOIC8. I think I did mess up when I forgot to Erase and performed a > >> write to it (it should still erase before the write but here we are). I > >> performed the same tasks on three other units that came out of an auction > >> and successfully reprogrammed them with a bios file obtained from HP. > >> > >> I am thinking of ordering a couple clean ones from eBay and desolder the > >> defective one. > >> > >> And I know, everyone keeps telling me to stop using the SOIC8, but I > >> simply have too much volume with a huge backlog. > >> > >> > >> > >>> On Dec 29, 2019, at 11:18 AM, Mike Banon wrote: > >>> > MX25L12835F/MX25L12845E/MX25L12865E > >>> This doesn't seem to be one-time-programmable. Have you tried flashing > >>> it on Linux instead of OS X ? Are you doing ISP (In system > >>> programming, i.e. with a test clip like SOIC8 or SOIC16) ? At the > >>> moment it's unclear to me why your erase operation is failing... > >>> > >>> On Fri, Dec 27, 2019 at 10:34 PM AL VAN DER LAAN > >>> wrote: > > Happy Holidays, > > > So this happened: I forgot to Erase the EEPROM, which clearly is my > fault, but it was late and I was tired. > > Just trying to see if I can recover this EEprom at all or if I am better > getting a couple of new ones from eBay? > > > > > flashrom -p ch341a_spi -E -c MX25L12835F/MX25L12845E/MX25L12865E -f > flashrom v1.1 on Darwin 19.2.0 (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Calibrating delay loop... OK. > Found Macronix flash chip "MX25L12835F/MX25L12845E/MX25L12865E" (16384 > kB, SPI) on ch341a_spi. > Erasing and writing flash chip... FAILED at 0x! Expected=0xff, > Found=0x40, failed byte count from 0x-0x0fff: 0x1000 > ERASE FAILED! > Looking for another erase function. > FAILED at 0x! Expected=0xff, Found=0x40, failed byte count from > 0x-0x7fff: 0x8000 > ERASE FAILED! > Looking for another erase function. > FAILED at 0x! Expected=0xff, Found=0x40, failed byte count from > 0x-0x: 0x1 > ERASE FAILED! > Looking for another erase function. > ^[[B^[[B^[[B^[[BFAILED at 0x! Expected=0xff, Found=0x40, failed > byte count from 0x-0x00ff: 0x100 > ERASE FAILED! > Looking for another erase function. > FAILED at 0x! Expected=0xff, Found=0x40, failed byte count from > 0x-0x00ff: 0x100 > ERASE FAILED! > Looking for another erase function. > Looking for another erase function. > Looking
[flashrom] Thanking for the tool
Hi, I would like to thank you for development of the flashrom tool, as I was able to fix my bios via the tool. The chip I have is gigadevice GD25B128C and I was able to use the settings for GD25Q128C. The software informed me that reading or writing to this chip wasn't tested so I thought it would help to inform you that both functions worked for me. Sencirely, Omer basri ___ flashrom mailing list -- flashrom@flashrom.org To unsubscribe send an email to flashrom-le...@flashrom.org
[flashrom] Re: In a bind
You haven't described what device you are trying to flash. Usually there's nothing wrong with using SOIC8 test clip, for the laptops. However, some routers/hdmi recorders/other devices of this type, may try powering its' main CPU from a test clip and interfere with your programming through a test clip. In example, here's a flashrom mod I had to do for making it possible to read a firmware of one router through a test clip https://review.coreboot.org/c/flashrom/+/31830 (because a CPU tries to power itself from a test clip and access a flash chip, its' only available for 30% of each second to a programmer behind a test clip), however - despite a similar code for read and write - this router becomes software bricked if a write has been attempted, and then a chip is inaccessible at all without a desoldering. So a chip itself could be fine, and such problems could be caused by an imperfection in your device's hardware design. Other problems could be i.e. too long cables between a SOIC8 test clip and a programmer, or their poor quality (i.e. electrical resistance of aluminium wires is about 1.5x times higher than of the copper ones with the same properties). On Sun, Dec 29, 2019 at 8:32 PM AL VAN DER LAAN wrote: > > Hi Mike, thanks for responding. I tried with Linux as well and am using the > SOIC8. I think I did mess up when I forgot to Erase and performed a write to > it (it should still erase before the write but here we are). I performed the > same tasks on three other units that came out of an auction and successfully > reprogrammed them with a bios file obtained from HP. > > I am thinking of ordering a couple clean ones from eBay and desolder the > defective one. > > And I know, everyone keeps telling me to stop using the SOIC8, but I simply > have too much volume with a huge backlog. > > > > > On Dec 29, 2019, at 11:18 AM, Mike Banon wrote: > > > >> MX25L12835F/MX25L12845E/MX25L12865E > > This doesn't seem to be one-time-programmable. Have you tried flashing > > it on Linux instead of OS X ? Are you doing ISP (In system > > programming, i.e. with a test clip like SOIC8 or SOIC16) ? At the > > moment it's unclear to me why your erase operation is failing... > > > > On Fri, Dec 27, 2019 at 10:34 PM AL VAN DER LAAN wrote: > >> > >> Happy Holidays, > >> > >> > >> So this happened: I forgot to Erase the EEPROM, which clearly is my > >> fault, but it was late and I was tired. > >> > >> Just trying to see if I can recover this EEprom at all or if I am better > >> getting a couple of new ones from eBay? > >> > >> > >> > >> > >> flashrom -p ch341a_spi -E -c MX25L12835F/MX25L12845E/MX25L12865E -f > >> flashrom v1.1 on Darwin 19.2.0 (x86_64) > >> flashrom is free software, get the source code at https://flashrom.org > >> > >> Calibrating delay loop... OK. > >> Found Macronix flash chip "MX25L12835F/MX25L12845E/MX25L12865E" (16384 kB, > >> SPI) on ch341a_spi. > >> Erasing and writing flash chip... FAILED at 0x! Expected=0xff, > >> Found=0x40, failed byte count from 0x-0x0fff: 0x1000 > >> ERASE FAILED! > >> Looking for another erase function. > >> FAILED at 0x! Expected=0xff, Found=0x40, failed byte count from > >> 0x-0x7fff: 0x8000 > >> ERASE FAILED! > >> Looking for another erase function. > >> FAILED at 0x! Expected=0xff, Found=0x40, failed byte count from > >> 0x-0x: 0x1 > >> ERASE FAILED! > >> Looking for another erase function. > >> ^[[B^[[B^[[B^[[BFAILED at 0x! Expected=0xff, Found=0x40, failed > >> byte count from 0x-0x00ff: 0x100 > >> ERASE FAILED! > >> Looking for another erase function. > >> FAILED at 0x! Expected=0xff, Found=0x40, failed byte count from > >> 0x-0x00ff: 0x100 > >> ERASE FAILED! > >> Looking for another erase function. > >> Looking for another erase function. > >> Looking for another erase function. > >> No usable erase functions left. > >> FAILED! > >> Your flash chip is in an unknown state. > >> Please report this on IRC at chat.freenode.net (channel #flashrom) or > >> mail flashrom@flashrom.org, thanks! > >> ___ > >> flashrom mailing list -- flashrom@flashrom.org > >> To unsubscribe send an email to flashrom-le...@flashrom.org > ___ flashrom mailing list -- flashrom@flashrom.org To unsubscribe send an email to flashrom-le...@flashrom.org
[flashrom] Re: winbond w25128jvsm bios chip for asus chromebox cn65
Are you trying in-system-programming (i.e. with a test clip like SOIC8 or SOIC16) ? If yes, try to shorten the wires between a programmer and a test clip, and/or replace them by the good copper ones. On Sat, Dec 28, 2019 at 4:14 AM Eds Orioque wrote: > > try to flash this bios chip and this is the log > > ubuntu@ubuntu:~$ sudo ./flashrom -p ch341a_spi > flashrom p1.0-23-g34b0ff2f on Linux 5.0.0-23-generic (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). > Found Winbond flash chip "unknown Winbond (ex Nexcom) SPI chip" (0 kB, SPI) > on ch341a_spi. > === > This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE > The test status of this chip may have been updated in the latest development > version of flashrom. If you are running the latest development version, > please email a report to flashrom@flashrom.org if any of the above operations > work correctly for you with this flash chip. Please include the flashrom log > file for all operations you tested (see the man page for details), and mention > which mainboard or programmer you tested in the subject line. > Thanks for your help! > No operations were specified. > > another one > sudo ./flashrom -p ch341a_spi -r badflash.rom > flashrom p1.0-23-g34b0ff2f on Linux 5.0.0-23-generic (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). > Found Winbond flash chip "unknown Winbond (ex Nexcom) SPI chip" (0 kB, SPI) > on ch341a_spi. > === > This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE > The test status of this chip may have been updated in the latest development > version of flashrom. If you are running the latest development version, > please email a report to flashrom@flashrom.org if any of the above operations > work correctly for you with this flash chip. Please include the flashrom log > file for all operations you tested (see the man page for details), and mention > which mainboard or programmer you tested in the subject line. > Thanks for your help! > Read is not working on this chip. Aborting. > > hoping for your help > tnx so much in advance > > -- Forwarded message - > From: Eds Orioque > Date: Fri, Dec 27, 2019, 4:58 PM > Subject: winbond w25128jvsm bios chip for asus chromebox cn65 > To: > > > try to flash this bios chip and this is the log > > ubuntu@ubuntu:~$ sudo ./flashrom -p ch341a_spi > flashrom p1.0-23-g34b0ff2f on Linux 5.0.0-23-generic (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). > Found Winbond flash chip "unknown Winbond (ex Nexcom) SPI chip" (0 kB, SPI) > on ch341a_spi. > === > This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE > The test status of this chip may have been updated in the latest development > version of flashrom. If you are running the latest development version, > please email a report to flashrom@flashrom.org if any of the above operations > work correctly for you with this flash chip. Please include the flashrom log > file for all operations you tested (see the man page for details), and mention > which mainboard or programmer you tested in the subject line. > Thanks for your help! > No operations were specified. > > another one > sudo ./flashrom -p ch341a_spi -r badflash.rom > flashrom p1.0-23-g34b0ff2f on Linux 5.0.0-23-generic (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). > Found Winbond flash chip "unknown Winbond (ex Nexcom) SPI chip" (0 kB, SPI) > on ch341a_spi. > === > This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE > The test status of this chip may have been updated in the latest development > version of flashrom. If you are running the latest development version, > please email a report to flashrom@flashrom.org if any of the above operations > work correctly for you with this flash chip. Please include the flashrom log > file for all operations you tested (see the man page for details), and mention > which mainboard or programmer you tested in the subject line. > Thanks for your help! > Read is not working on this chip. Aborting. > > hoping for your help > tnx so much in advance > > ___ > flashrom mailing list -- flashrom@flashrom.org > To unsubscribe send an email to flashrom-le...@flashrom.org ___ flashrom mailing list -- flashrom@flashrom.org To unsubscribe send an email to flashrom-le...@flashrom.org
[flashrom] Re: In a bind
> MX25L12835F/MX25L12845E/MX25L12865E This doesn't seem to be one-time-programmable. Have you tried flashing it on Linux instead of OS X ? Are you doing ISP (In system programming, i.e. with a test clip like SOIC8 or SOIC16) ? At the moment it's unclear to me why your erase operation is failing... On Fri, Dec 27, 2019 at 10:34 PM AL VAN DER LAAN wrote: > > Happy Holidays, > > > So this happened: I forgot to Erase the EEPROM, which clearly is my fault, > but it was late and I was tired. > > Just trying to see if I can recover this EEprom at all or if I am better > getting a couple of new ones from eBay? > > > > > flashrom -p ch341a_spi -E -c MX25L12835F/MX25L12845E/MX25L12865E -f > flashrom v1.1 on Darwin 19.2.0 (x86_64) > flashrom is free software, get the source code at https://flashrom.org > > Calibrating delay loop... OK. > Found Macronix flash chip "MX25L12835F/MX25L12845E/MX25L12865E" (16384 kB, > SPI) on ch341a_spi. > Erasing and writing flash chip... FAILED at 0x! Expected=0xff, > Found=0x40, failed byte count from 0x-0x0fff: 0x1000 > ERASE FAILED! > Looking for another erase function. > FAILED at 0x! Expected=0xff, Found=0x40, failed byte count from > 0x-0x7fff: 0x8000 > ERASE FAILED! > Looking for another erase function. > FAILED at 0x! Expected=0xff, Found=0x40, failed byte count from > 0x-0x: 0x1 > ERASE FAILED! > Looking for another erase function. > ^[[B^[[B^[[B^[[BFAILED at 0x! Expected=0xff, Found=0x40, failed byte > count from 0x-0x00ff: 0x100 > ERASE FAILED! > Looking for another erase function. > FAILED at 0x! Expected=0xff, Found=0x40, failed byte count from > 0x-0x00ff: 0x100 > ERASE FAILED! > Looking for another erase function. > Looking for another erase function. > Looking for another erase function. > No usable erase functions left. > FAILED! > Your flash chip is in an unknown state. > Please report this on IRC at chat.freenode.net (channel #flashrom) or > mail flashrom@flashrom.org, thanks! > ___ > flashrom mailing list -- flashrom@flashrom.org > To unsubscribe send an email to flashrom-le...@flashrom.org ___ flashrom mailing list -- flashrom@flashrom.org To unsubscribe send an email to flashrom-le...@flashrom.org
