[flashrom] Re: Ch341a support on 1.3

[Mike Banon]

Luckily, it seems that the popular ch341a programmer is still
supported ;-) I just got flashrom-v1.3.0.tar.bz2 , saw that it still
has ch341a_spi.c, and when built and launched with --help - it tells
that "ch341a_spi" is one of the supported programmers [1]. Maybe I
haven't tested v1.3.0 in practice yet - but it should work.

Another great thing is that ENE KB9012 flashing (original patches by
Paul Kocialkowski, I only helped to merge it 5 years ago) - is still
supported! ;-) It is the only opensource way of flashing the EC KB9012
(i.e. found in a coreboot-supported AMD no-PSP G505S laptop which is a
libreboot candidate), and the only way of flashing KB9012 without
getting the expensive special programmer tools: thanks to flashrom and
Paul's original work, this could be done even with the above mentioned
ch341a which costs like $2

[1]  -p | --programmer [:] specify the programmer device.
One of internal, dummy, nic3com, nicrealtek, gfxnvidia,
raiden_debug_spi, drkaiser, satasii, atavia, it8212, serprog,
buspirate_spi, dediprog, developerbox, rayer_spi, pony_spi, nicintel,
nicintel_spi, nicintel_eeprom, ogp_spi, satamv, linux_mtd, linux_spi,
pickit2_spi, ch341a_spi, digilent_spi, stlinkv3_spi

On Fri, Mar 17, 2023 at 10:01 AM Joe h via flashrom
 wrote:
>
> Hello I was wondering if support dropped for the ch341a on flashrom version 
> 1.3 ?
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org



--
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: flashrom Verifying FAILED

[Mike Banon]

What is your flashing connection & setup in general? Please check if
it is good enough

On Tue, Jan 31, 2023 at 9:59 PM Servus  wrote:
>
> Hi!
>
>
>
> I get this error very often:
>
>
>
> flashrom v1.2 on Linux 5.10.78-7-osmc (armv7l)
> flashrom is free software, get the source code at https://flashrom.org
>
> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> Found GigaDevice flash chip "GD25Q64(B)" (8192 kB, SPI) on ch341a_spi.
> Reading old flash chip contents... done.
> Erasing and writing flash chip... Erase/write done.
> Verifying flash... FAILED at 0x8790! Expected=0x44, Found=0xff, failed 
> byte count from 0x-0x007f: 0xcc60
> 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!
>
>
>
> Any ideas?
>
>
>
> Regards, Servus.
>
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: flashrom for windows build/download

[Mike Banon]

Good day, John! You can easily find these prebuilt binaries by
Googling. However, for the best (and secure) user experience it is
really recommended to use a Linux version of flashrom. You can use
some Linux LiveDVD / LiveUSB to use flashrom without installing Linux
to a target PC's HDD - and such a secure & stable flashing environment
could be set up in just a few minutes. Hope this will change your
mind... If not, then you could use something like this -
https://winraid.level1techs.com/t/tool-flashrom-v1-2-win10/35907 , but
I've warned you of the possible downsides.

On Tue, Jun 14, 2022 at 1:22 PM JOHN WESTMORELAND via flashrom
 wrote:
>
> Hello,
>
> I was wondering if someone could point me in the right direction to find 
> prebuilt binaries for windows.
>
> Thanks In Advance,
> John W.
>
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: issue

[Mike Banon]

1) Try the shorter cables between a test clip and a programmer. See my
notes here at
http://dangerousprototypes.com/docs/Flashing_a_BIOS_chip_with_Bus_Pirate#Standard_SOIC8_clip

2) Make sure that your ch341a programmer is good enough. I had to
repair a couple of dead-on-arrival ch341a:
https://www.reddit.com/r/coreboot/comments/bjygqz/green_ch341a_didnt_work_turned_out_its_a_badly/
https://www.reddit.com/r/coreboot/comments/defkim/green_ch341a_didnt_work_because_of_a_missing/

On Sat, Jan 29, 2022 at 6:06 PM John Evacristo  wrote:
>
> ch341a_spi and yes In-System Programming with a test clip
>
> On Sat, Jan 29, 2022, 11:05 PM Mike Banon  wrote:
>>
>> Please describe your flashing setup in more details. We don't even
>> know which programmer you're trying to use, and in what mode?
>> (In-System Programming with a test clip?)
>>
>> On Mon, Jan 24, 2022 at 12:55 AM John Evacristo  
>> wrote:
>> >
>> > flashrom v1.2 on Linux 5.11.0-27-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 Macronix flash chip "MX25L3206E/MX25L3208E" (4096 kB, SPI) on 
>> > ch341a_spi.
>> > Erasing and writing flash chip... FAILED at 0x0001347f! Expected=0xff, 
>> > Found=0xef, failed byte count from 0x00013000-0x00013fff: 0x7
>> > ERASE FAILED!
>> > Looking for another erase function.
>> > FAILED at 0x0098! Expected=0xff, Found=0xfe, failed byte count from 
>> > 0x-0x: 0x4a7f
>> > ERASE FAILED!
>> > Looking for another erase function.
>> > FAILED at 0x! Expected=0xff, Found=0x02, failed byte count from 
>> > 0x-0x: 0x544f
>> > ERASE FAILED!
>> > Looking for another erase function.
>> > FAILED at 0x! Expected=0xff, Found=0xbd, failed byte count from 
>> > 0x-0x003f: 0x3e0c19
>> > ERASE FAILED!
>> > Looking for another erase function.
>> > FAILED at 0x! Expected=0xff, Found=0xbb, failed byte count from 
>> > 0x-0x003f: 0x3fffea
>> > 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
>>
>>
>>
>> --
>> Best regards, Mike Banon
>> Open Source Community Manager of 3mdeb - https://3mdeb.com/



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: issue

[Mike Banon]

Please describe your flashing setup in more details. We don't even
know which programmer you're trying to use, and in what mode?
(In-System Programming with a test clip?)

On Mon, Jan 24, 2022 at 12:55 AM John Evacristo  wrote:
>
> flashrom v1.2 on Linux 5.11.0-27-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 Macronix flash chip "MX25L3206E/MX25L3208E" (4096 kB, SPI) on 
> ch341a_spi.
> Erasing and writing flash chip... FAILED at 0x0001347f! Expected=0xff, 
> Found=0xef, failed byte count from 0x00013000-0x00013fff: 0x7
> ERASE FAILED!
> Looking for another erase function.
> FAILED at 0x0098! Expected=0xff, Found=0xfe, failed byte count from 
> 0x-0x: 0x4a7f
> ERASE FAILED!
> Looking for another erase function.
> FAILED at 0x! Expected=0xff, Found=0x02, failed byte count from 
> 0x-0x: 0x544f
> ERASE FAILED!
> Looking for another erase function.
> FAILED at 0x! Expected=0xff, Found=0xbd, failed byte count from 
> 0x-0x003f: 0x3e0c19
> ERASE FAILED!
> Looking for another erase function.
> FAILED at 0x! Expected=0xff, Found=0xbb, failed byte count from 
> 0x-0x003f: 0x3fffea
> 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



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: How to obtain a BIOS image from another computer use flashrom？

[Mike Banon]

Hi there Angel, thank you for your reply and clarification! Please
tell, is this command

> sudo flashrom -p internal:laptop=force_I_want_a_brick,amd_imc_force=yes -r 
> ./build/coreflop.rom

- dangerous to run, even if it's only trying to read (-r) and not
write? (aside from "irritating the EC" possibly causing a sudden
power-off). As for "amd_imc_force=yes", sorry was my mistake

On Mon, Jan 24, 2022 at 3:28 PM Angel Pons  wrote:
>
> Hi,
>
> On Sun, Jan 23, 2022 at 9:49 AM Mike Banon  wrote:
> >
> > Good day! The flashrom software has the "internal" mode - using which,
> > you may be able to access the BIOS chip directly from your OS, if your
> > hardware is supported. In example:
> >
> > sudo flashrom -p
> > internal:laptop=force_I_want_a_brick,amd_imc_force=yes -r
> > ./build/coreflop.rom
>
> Mike, can you please explain why you've suggested using such a
> dangerous command without even knowing which system it's going to be
> run on? The `force_I_want_a_brick` name is intentional, as flashrom
> can cause problems on certain laptops (most laptops from the last
> decade should be fine, though), c.f. https://www.flashrom.org/Laptops
> for a detailed explanation. And you've suggested using `amd_imc_force`
> even though it only applies to AMD southbridges using SPI.
>
> I know you're just trying to help, but I'm afraid that suggesting
> people to run dangerous commands on unknown hardware without
> mentioning the risks is not helpful.
>
> > I think this mode is available only on Linux (may have to boot with
> > "iomem=relaxed" kernel flag) - however, you may boot a Linux LiveUSB
> > on your target PC to use Linux without the installation in a live
> > mode.
>
> On x86, the internal programmer should also work on most BSDs and
> Darwin (macOS). It might even work on Solaris.
>
> On Linux, the `iomem=relaxed` kernel parameter can be used when a
> kernel module conflicts with the resources flashrom wants to use, but
> it reduces the system's security. On Intel systems, unloading the
> `lpc_ich` kernel module should allow using flashrom's internal
> programmer without having to boot with `iomem=relaxed`.
>
> > As for "how do I remotely obtain a BIOS image from another computer
> > using flashrom" - if this internal mode is available to you, and a
> > target PC is running Linux, you can remotely connect to this PC using
> > a SSH (or VPN + SSH), run the flashrom command to read a BIOS image
> > from a chip, and then - using scp - copy the obtained BIOS image to
> > your own PC
> >
> >
> > On Fri, Jan 21, 2022 at 3:26 AM zy <2018111...@bupt.cn> wrote:
> > >
> > > Hi，
> > >I'm a student from China and I've been learning flashrom，So I would 
> > > like to know whether the flashrom can support extracting BIOS firmware 
> > > images under Windows 7/10.
> > >If I don't have the Internet（Just LAN），how do I remotely obtain a BIOS 
> > > image from another computer use flashrom？
> > >Maybe my English not very well. Thank you very much.
>
> On Windows, flashrom's internal programmer is unusable. It requires
> libpci and raw memory access; libpci is not available on Windows as
> far as I know, and I think Windows restricts raw memory access from
> userspace code for security reasons. One could try to implement the
> required functionality in a driver, but one would also need to
> convince Microsoft to sign the driver. It could be done, but it's not
> easy. No one is working on this, as far as I know.
>
> > >Looking forward to your reply.
> > >
> > >
> > > ___
> > > flashrom mailing list -- flashrom@flashrom.org
> > > To unsubscribe send an email to flashrom-le...@flashrom.org
> >
> >
> >
> > --
> > Best regards, Mike Banon
> > Open Source Community Manager of 3mdeb - https://3mdeb.com/
> > ___
> > flashrom mailing list -- flashrom@flashrom.org
> > To unsubscribe send an email to flashrom-le...@flashrom.org
>
> Best regards,
> Angel



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: How to obtain a BIOS image from another computer use flashrom？

[Mike Banon]

Good day! The flashrom software has the "internal" mode - using which,
you may be able to access the BIOS chip directly from your OS, if your
hardware is supported. In example:

sudo flashrom -p
internal:laptop=force_I_want_a_brick,amd_imc_force=yes -r
./build/coreflop.rom

I think this mode is available only on Linux (may have to boot with
"iomem=relaxed" kernel flag) - however, you may boot a Linux LiveUSB
on your target PC to use Linux without the installation in a live
mode.

As for "how do I remotely obtain a BIOS image from another computer
using flashrom" - if this internal mode is available to you, and a
target PC is running Linux, you can remotely connect to this PC using
a SSH (or VPN + SSH), run the flashrom command to read a BIOS image
from a chip, and then - using scp - copy the obtained BIOS image to
your own PC


On Fri, Jan 21, 2022 at 3:26 AM zy <2018111...@bupt.cn> wrote:
>
> Hi，
>I'm a student from China and I've been learning flashrom，So I would like 
> to know whether the flashrom can support extracting BIOS firmware images 
> under Windows 7/10.
>If I don't have the Internet（Just LAN），how do I remotely obtain a BIOS 
> image from another computer use flashrom？
>Maybe my English not very well. Thank you very much.
>
>
>Looking forward to your reply.
>
>
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: failed write to an erased chip

[Mike Banon]

Your log looks right to me, like a file has been programmed into your
chip successfully. How did you check that the writing operation was a
failure instead?

P.S. I hope that your 1.8V chip wasn't partially damaged by a
temporary usage of 3.3V on it

On Tue, Nov 23, 2021 at 11:23 PM Сергей Янович
 wrote:
>
> Hi.
>
> This chip is a 1.8V one. I tried to flash it with RPi 3.3V spi, but
> failed. Reads were unstable. Now I can reliably read it by having a TI
> ALVC164245 between RPi and the chip. The chip seems erased, but I
> cannot write anything to it. Attaching a log of
>
> # flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=5000 -VVV -w 8.bin
>
> Thanks!
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: report can't write fw with hp 8200 ssf

[Mike Banon]

If there's a write protection in place which blocks the internal
programmer, then you could get the external programmer like a USB CH341A
(preferably a green PCB) to access a chip with a BIOS firmware - directly.
If your BIOS chip is inside the DIP8 socket, then you'd need a DIP8 / PLCC
remover to safely extract it from a socket; if it's SOIC8 soldered on the
motherboard, you'd need a SOIC8 test clip to connect a programmer directly
to this chip without desoldering it.

On Sun, Oct 31, 2021 at 8:48 PM Nico Huber  wrote:

> Hi,
>
> your email got mangled or was from the beginning, so I can't reply
> inline. Better *don't* use HTML when copying program output, or better
> don't use HTML for emails at all.
>
> This was the interesting part (it would have been easier to spot with
> less verbosity):
>
> > BIOS_CNTL = 0x02: BIOS Lock Enable: enabled, BIOS Write Enable: disabled
> > Warning: Setting Bios Control at 0xdc from 0x02 to 0x01 failed.
> > New value is 0x02.
>
> This means that your currently running firmware doesn't allow you to
> write to the flash chip. Sometimes there's an option in the BIOS setup,
> but IIRC chances are low for this machine.
>
> Nico
>
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org
>


-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Chrome OS Flash

[Mike Banon]

Perhaps to disable the write protection you need to remove the write
protection screw? (depending on your chromebook model) Or you can try
flashing a firmware using the external programmer supported by flashrom
like a USB CH341A.

On Sat, Oct 23, 2021 at 8:39 PM Jacobb Faucher 
wrote:

> I was wondering if I could get assistance on how to disable Write
> Protection (WP) on Chrome OS. My Chromebook is the Acer Chromebook 311
> (CB311-9H).
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org
>


-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: FAILED: asus p5n-e sli

[Mike Banon]

What is the size of this 1406.BIN file? If it's a power of 2 (1MB, 2MB,
4MB, etc.) - then most likely it's a raw image for the BIOS chip, which
could be flashed using the hardware method (programmer), or the software:
either flashrom internal mode if it's supported, or ASUS USB utility like
AFUDOS.

On Wed, Sep 29, 2021 at 5:36 PM John Beck  wrote:

> I am trying to use the 1406.BIN file I got from ASUS
>
> Help, please?
>
> Thanks! John
>
> --
> If you forward this correspondence, PLEASE delete the forwarding history
> which includes my email address. It is a courtesy to me and others who may
> not wish to have their email addresses sent all over the world. Deleting
> the history helps prevent Spammers from mining addresses and also prevents
> viruses from being propagated. Thank you.
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org
>


-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Difficulty installing libreboot with flashrom v.1.2 on a green ch341a programmer.

[Mike Banon]

It looks like you may have a broken libusb installation. Please try to
re-install libusb, re-build a flashrom against it and try again.

On Tue, Jun 1, 2021 at 10:06 AM keizerrijk via flashrom <
flashrom@flashrom.org> wrote:

> Hi, I'm attempting to install libreboot on my thinkpad x200 (soic16) with
> a green ch341a programmer. The reading of the flash chip works fine, but
> when attempting to write to the flash chip, it fails and spits out these
> errors: https://pastebin.com/G17JWGfQ
>
> Hoping for any help on what's going wrong. I've checked the connections
> are right.
>
> Thanks in advance!
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org
>


-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Dell 3100 Chromebook

[Mike Banon]

Are you doing the ISP (In-System Programming) ? Maybe there are
problems with the reliability of your flashing setup (i.e. too long
wires between a programmer and test clip)

On Thu, May 13, 2021 at 2:39 AM Tim Tech  wrote:
>
> Are you able to help with the following issue? Thank you
>
> Calibrating delay loop... OK.
> 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.
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: xmc-qh128ahig

[Mike Banon]

The only reliable way to "remove all of the spyware" from your
firmware - is to switch to the opensource coreboot BIOS with as few
binary blobs as possible. (By simply removing some UEFI modules you
could't guarantee the security, I hope you understand this). If your
PC isn't supported by coreboot: either try to port a coreboot to it if
it's possible, or sell it and buy a supported PC with that money.

On Thu, Apr 8, 2021 at 10:53 PM Patryk P  wrote:
>
> For me read/write works fine I just send output to You for further 
> development purposes.
>
> Regards
>
> On Thu, Apr 8, 2021 at 8:07 PM Winfried Kybelka 
>  wrote:
>>
>> Hi Mike
>>
>> i have compile last git source an make a read -test
>>
>> yesterday have i testet it with old version . this has "Found Unknown flash 
>> chip "SFDP-capablechip" (8192 kB, SPI) on ch341a_spi.
>> and data was also read out.
>> then I had to repeat the read process to a new file and check with diff 
>> command that recognized differences.
>>
>> today with aktual git source "flashrom v1.2-230-gc193fbd"
>> the unknown Unknown flash chip "SFDP-capablechip" also appears.
>> but the reading tests showed that no more differences were recognized.
>>
>> I found a post in another forum:
>> >
>> I've de-soldered chip  XMC QH64AHIG (XM25QH64AHIG)
>> In attachment you can find dump from flashrom
>> Also I've found that, this chip is equals to :
>> XM25QH64AHIG GD25Q64CSIG MX25L6406EN2I-12G EN25QH64A-104HIP W25Q64JVSSIQ
>> <
>>
>> an make  test 'flashrom --programmer ch341a_spi -f -c "GD25Q64(B)" -r 
>> XMC_XM25QH64AHIG.bin'
>> with the same result. flashrom can read chip.
>> I couldn't write test yet because I have to revise the flash first and 
>> remove all of the China spyware from the firmware.
>>
>> greetings Winfried
>>
>>  schrieb Mike Banon
>> :
>>
>> > It could be that XMC chips aren't officially supported yet, but there
>> > are some unofficial flashrom patches for XMC support available online.
>> > Please try them.
>> >
>> > On Wed, Apr 7, 2021 at 9:10 PM Patryk P 
>> > wrote:
>> > >
>> > >
>> > > ___
>> > > flashrom mailing list -- flashrom@flashrom.org
>> > > To unsubscribe send an email to flashrom-le...@flashrom.org
>> >
>> >
>> >
>>


-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: xmc-qh128ahig

[Mike Banon]

It could be that XMC chips aren't officially supported yet, but there
are some unofficial flashrom patches for XMC support available online.
Please try them.

On Wed, Apr 7, 2021 at 9:10 PM Patryk P  wrote:
>
>
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: info log for unknown chip XMC_QH64AH16

[Mike Banon]

Please build the more recent version of flashrom directly from the
source code, and try again.

On Wed, Apr 7, 2021 at 9:10 PM Winfried Kybelka
 wrote:
>
> hi programmer
> i have att log.
>
> Thanks for your work
>
> W. Kybelka
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: (Re)Unsuccessful Read with FlashRom

[Mike Banon]

If you suspect that your BIOS is infected (BadBIOS?), I could only
suggest doing a hardware ISP flashing with one of the
flashrom-supported programmers (i.e. green PCB ch341a) and a test clip
like SOIC8 (to be able to attach to a chip without any soldering)
while the board is turned off of course. This should be the most
reliable. Before flashing a new known good BIOS image that you might
obtain i.e. by extracting from a manufacturer's update utility, please
dump the previous contents with a programmer: so that you'll be able
to recover from it just in case, and maybe even look through it for
any hard evidence of a BIOS virus to share it with the community (if
that's really true, could be quite interesting for research purposes).
Also I copy this message to a flashrom mailing list, in case someone
else could also advise you.

On Wed, Apr 7, 2021 at 2:05 PM Rahngue NGARIERA  wrote:
>>
>> Hi Mike. I didn't mention it in my previous email, but I used also flashrom 
>> 0.9.6 on Ubuntu 14.4 Which failed on both Probe and Read with "Hardware 
>> sequencing was requested but the flash descriptor is not valid. Aborting". 
>> While using version 0.9.4 (on DOS) I did both Probe and Read. As You said, 
>> the 2 chips FlashRom 0.9.4 found (AT25DF081A and AT26DF081A) are the same 
>> and one chip. And checking on the main board I did see that chip. It's 
>> AT26DF081A. I did try to read on FlashRom 0.9.4 (on DOS) using the -c 
>> parameter with AT26DF081A first (as in -c AT26DF081A) but that failed. Then 
>> just to see, I tried to read with -c AT25DF081A ( since 0.9.4 was seeing two 
>> chips). But it also failed. I'm sending you again the Probe log and the Read 
>> logs using FlashRom 0.9.4 : READ1.TXT (AT25DF081A)
>
> and  READ2.TXT (AT26DF081A).
>
>  FlashRom 0.9.6 (Ubuntu14.4) and FlashRom 1.2 (on DOS) both failed whether 
> reading or probing even with -c AT26DF081A ( -c AT25DF081A) with the same 
> message at the end saying that flash descriptor is invalid.
>This Dell system I want to read from, I think, has its bios infected. When 
> It comes to bios, I prefer to operate from DOS: I think it's safer and maybe 
> help avoid any action from the virus.
>   Please Mike, what do I do for FlashRom to successfully read this chip?
>  I need  to confirm if this bios chip is infected.
>  Thanks for your help,
> Etonam.



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Unsuccessful Read using FlashRom

[Mike Banon]

Seeing from your PROBE.TXT log that AT25DF081A and AT26DF081A are at
the same 0xfff0 physical address, I think it's the same chip which
got detected twice. Do you have the opportunity to physically see the
markings on your chip to confirm its' model? Then, maybe with directly
specifying the chip's model using a "-c" option there could be more
success (of course with a new version of flashrom).

Also, I see that you are trying to use flashrom on MS-DOS. Please
could you try some LiveCD with Linux? (you may have to add the
"iomem=relaxed" option to Linux kernel flags after pressing e while at
GRUB for the default boot entry)

On Sat, Apr 3, 2021 at 2:52 PM Rahngue NGARIERA  wrote:
>
> Hi there. I tried to probe for/read the bios chip in my Dell T3400 (desktop 
> pc) using Flashrom 0.9.4 and 1.2  It detected chipset is Intel ICH9R and then 
> failed. FlashRom 0.9.4 found 2 flash chips AT25DF081A and AT26DF081A then 
> failed to read. But I could see on the mobo only one chip AT26DF081A FlashRom 
> 1.2 failed on Probe/Read while trying Hardware Sequencing. I've attached the 
> logs to this email. Looking at the list of supported chips, I saw that 
> success with this Intel chipset was "config-dependent". So what corrections 
> to get FlashRom to work for my Dell? or What flash utility do you advise so I 
> can get a copy of the bios chip?
> Thanks for your help, Etonam.
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: [HowardHo2021 DOS Port] RE: Changes made for FlashRom DOS port

[Mike Banon]

Very interesting port. Does it work with a FreeDOS too?

On Sun, Apr 4, 2021 at 7:52 AM  wrote:
>
> Hi,
>
>
>
> Thanks for your email. Unfortunately, I did not specifically write down the 
> changes I made in a document. However, you may check the commit history at my 
> “flashrom for DOS” port repository here. If you wish, you can clone that 
> repository and follow the instructions I wrote in “README_DOS” to compile 
> your own copy.
>
>
>
> For future correspondence, please use howardho2...@gmail.com instead.
>
>
>
> Thanks.
>
>
>
> From: Rahngue NGARIERA 
> Sent: Saturday, April 3, 2021 11:58 PM
> Subject: Changes made for FlashRom DOS port
>
>
>
> Hi HowardHo. I haven't seen your list of changes to the original FlashRom (to 
> get a working DOS port) on your Git pages. Could you please post them there 
> or email it to me? I'd very much like to know. 'Cause I wasn't able to get it 
> done with the original FlashRom.
>
> Thanks for your help,
>
> Etonam.
>
>
>
> PS:  As you advised me, I sent my Read/Probe failure email to FlashRom.org  
> And I'm waiting for their answer.
>
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Fail flashing

[Mike Banon]

Hi there GN, any news regarding your progress? btw please CC flashrom
mailing list for your future replies, so that someone else could be
able to help you as well

On Sun, Mar 28, 2021 at 7:49 PM GN  wrote:
>
> Dear MIke,
>
> Thank you for you detailed answer, very much appreciated.
>
> Thank you for the clarification about the chips, I was getting crazy finding 
> the right information about it. I will report the difference across all the 
> posts I wrote on the issue :)
>
> The procedure in [1] is for a BBB. I will try to understand what can be 
> transferred to the CH341a that I am using. For it, I found this interesting 
> DIY, although according to the author the outputted voltage cannot be 
> carefully controlled.
>
> I have tried to connect the power supplier to the naked motherboard while 
> reading the Winbond chip. As predicted, the power LED on the CH341a lights on 
> dimmed and it gets full-on when connected to the USB 3 port. Less obviously,  
> flashrom cannot recognize the chip when the power supplier is connected. As I 
> disconnect the power supplier, flashrom correctly recognizes the chip again, 
> but the writing problems persist.
>
>
> Bests regards,
>
> GN
>
>
> On 25.03.21 14:39, Mike Banon wrote:
>
> I think the only way to prevent the current leaking to the surrounding
> elements of a chip - is desoldering. So, if we are trying to avoid the
> desoldering - yes, you could try reducing the length of wires between
> a programmer and a test clip - i.e. to 10cm. That certainly wouldn't
> hurt, and sometimes it really helps to achieve the successful flashing
> by ISP (in-system programming) method.
>
> Please note: while there are some successful examples of using the
> external PSU for an ISP flashing (i.e. this [1] BBB example at
> libreboot wiki), depending on a motherboard design this could be
> dangerous according to Angel Pons comments under [2] - so using the
> external PSU should be avoided unless all the other options have been
> tried and you still don't want to solder/desolder.
>
> While looking for the examples of L530 flashing I found a thread with
> your comments [3]. To answer your question why the other people were
> also targeting a ps08a chip: this is CMOS, and clearing a CMOS memory
> sometimes is also important to ensure the successful boot of a
> proprietary BIOS - but we haven't reached this stage yet, since we're
> just trying to flash a BIOS into a SPI flash chip.
>
> Have you ever tested your CH341A before in other setups? If not, do
> you have a spare CH341A to try it with a different one? And could you
> try a higher powered USB port to ensure that your CH341A itself is
> sufficiently powered? (i.e. you may be using a USB extender for your
> convenience, which is fine - but that extender also shouldn't be too
> long)
>
> [1] https://libreboot.org/docs/install/bbb_setup.html
> [2] https://review.coreboot.org/c/flashrom/+/31830
> (this was my patch for the older version of flashrom useful in a
> unreliable flashing setup, but I only successfully read with it and
> never successfully wrote).
> [3] https://www.badcaps.net/forum/showthread.php?t=61517
>
> P.S. I'm not sure how you can measure the leakage with a multimeter,
> and in any case knowing the exact values isn't necessary - when we
> already know the cause of unsuccessful flashing and just need to find
> out how to resolve it.
>
>
> On Wed, Mar 24, 2021 at 8:46 PM G. Nalin  wrote:
>
> HI,
>
> I have been recommended to desolder the BIOS chip to use the CH341a reliably, 
> but I would like to avoid it and use the clip instead! Should I simply cut 
> shorter the clip wires? Is there something I can do to ground the motherboard 
> or avoid the leaking? How can I measure it (I have just a multimeter here 
> atm).
>
> I don´t know how to supply the power externally while the EEPROM is connected 
> to the USB. Could you indicate me a reference?
>
> I tried to verify the dumo, but if fails because there is some writing 
> involved.
> $ sudo flashrom -V -p ch341a_spi -v bios1b.img
>
> I don´t have a reference so I can´t say if the HEX or BIN dump is actually at 
> least partially valid. It is not all FF and 00.
>
> Cheers,
>
> Giammarco Nalin
>
> Handy: +4915252667614
> Adresse: Hausener Weg 96, 60489, Frankfurt am Main
>
>
> 
> From: Mike Banon 
> Sent: 24 March 2021 13:40
> To: G. Nalin 
> Cc: flashrom@flashrom.org 
> Subject: Re: [flashrom] Fail flashing
>
> Could you please verify that at least a part of the binary file got
> flashed correctly? If yes, these reliability problems could be caused
> by your setup - i.e. too long wires or the surrounding elements 

[flashrom] Re: Fail flashing

[Mike Banon]

read-write.
> Not all flash regions are freely accessible by flashrom. This is most likely
> due to an active ME. Please see https://flashrom.org/ME for details.
> 0x74: 0x8aaf0800 PR0: Warning: 0x0080-0x00aa is read-only.
> 0x78: 0x8ab00ab0 PR1: Warning: 0x00ab-0x00ab0fff is read-only.
> 0x7C: 0x8adf0ab1 PR2: Warning: 0x00ab1000-0x00ad is read-only.
> 0x80: 0x8bff0b40 PR3: Warning: 0x00b4-0x00bf is read-only.
> At least some flash regions are read protected. You have to use a flash
> layout and include only accessible regions. For write operations, you'll
> additionally need the --noverify-all switch. See manpage for more details.
> 0x90: 0xc0 (SSFS)
> SSFS: SCIP=0, FDONE=0, FCERR=0, AEL=0
> 0x91: 0xf94000 (SSFC)
> SSFC: SCGO=0, ACS=0, SPOP=0, COP=0, DBC=0, SME=0, SCF=1
> 0x94: 0x0606 (PREOP)
> 0x96: 0x3f90 (OPTYPE)
> 0x98: 0x03003505 (OPMENU)
> 0x9c: 0x9f20d802 (OPMENU+4)
> 0xa0: 0x (BBAR)
> 0xc4: 0x80802025 (LVSCC)
> LVSCC: BES=0x1, WG=1, WSR=0, WEWS=0, EO=0x20, VCL=1
> 0xc8: 0x8000 (UVSCC)
> UVSCC: BES=0x0, WG=0, WSR=0, WEWS=0, EO=0x0
> 0xd0: 0x50444653 (FPB)
> Enabling hardware sequencing due to multiple flash chips detected.
> OK.
> The following protocols are supported: Programmer-specific.
> Probing for Programmer Opaque flash chip, 0 kB: Hardware sequencing reports 2 
> attached SPI flash chips with a combined density of 12288 kB.
> The first partition ranges from 0x00 to 0x652fff.
> In that range are 1619 erase blocks with 4096 B each.
> The second partition ranges from 0x653000 to 0xbf.
> In that range are 1453 erase blocks with 4096 B each.
> Found Programmer flash chip "Opaque flash chip" (12288 kB, 
> Programmer-specific) mapped at physical address 0x.
> Found Programmer flash chip "Opaque flash chip" (12288 kB, 
> Programmer-specific).
> No operations were specified.
> Restoring MMIO space at 0x7f0d5db958a0
> Restoring PCI config space for 00:1f:0 reg 0xdc
>
> ///
>
> $ sudo flashrom -V -p ch341a_spi
> flashrom v1.2 on Linux 5.8.0-45-generic (x86_64)
> flashrom is free software, get the source code at https://flashrom.org
>
> flashrom was built with libpci 3.6.4, GCC 9.2.1 20200304, little endian
> Command line (3 args): flashrom -V -p ch341a_spi
> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> Initializing ch341a_spi programmer
> Device revision is 3.0.4
> The following protocols are supported: SPI.
>
> ..
>
> Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on ch341a_spi.
> Chip status register is 0x00.
>
> This chip may contain one-time programmable memory. flashrom cannot read
> and may never be able to write it, hence it may not be able to completely
> clone the contents of this chip (see man page for details).
>
>
>
> Cheers,
>
> GN
>
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: About bios flash

[Mike Banon]

Flashing BIOS chip is relatively easy, the end of this article shows
how to do this with a cheap USB CH341A adapter supported by the
opensource flashrom tool -
http://dangerousprototypes.com/docs/Flashing_a_BIOS_chip_with_Bus_Pirate
. However, hardware flashing a EC is more difficult -
http://dangerousprototypes.com/docs/Flashing_KB9012_with_Bus_Pirate -
especially if your EC isn't supported by flashrom. So it's preferable
to update EC by a proprietary UEFI tool if you can't hardware flash
it, but this could be done only if your laptop is already working. If
your laptop reacts to a power button, chances are you don't have to
touch your EC. Before flashing a BIOS image extracted from ASUS update
utility, make sure you cut the correct 4MB (correct offset, looking at
headers, and correct size). And in some cases you may need to populate
some areas with IDs (i.e. MAC address of a laptop's Ethernet
controller). You can learn more platform-specific info by looking them
up online.

On Fri, Mar 19, 2021 at 10:28 AM Aurelijus Gogas  wrote:
>
> I downloaded from asus. And there is EC firmware update. I extracted. Size is 
> 2MB. Flash chip  size is 4MB. Are there some tricks for flashing like this 
> files?
>
> Thanks
> With Best Regards
> Aurimas
>
> Get BlueMail for Android
> On Mar 18, 2021, at 22:06, Mike Banon  wrote:
>>
>> Hi there, 20cm wires is a bit long in my opinion - should be 10cm, but
>> still - if your board is "hungry" - there may be a voltage drop and
>> the resulting voltage level is insufficient for the successful
>> flashing. As for "desoldered & flashed & soldered and nothing happens"
>> - if you're confident your hardware is OK, then there may be an issue
>> with a proprietary BIOS image that you are flashing, and I could only
>> suggest searching for a good BIOS online or trying to extract it from
>> a manufacturer's UEFI update utility if nothing helps.
>>
>>
>> On Thu, Mar 18, 2021 at 7:45 PM Aurelijus Gogas  
>> wrote:
>>>
>>>
>>>  Hallo again. I flashed winbond bios on asus x54h only when desoldered. But 
>>> when I soldered back, there was nothing. Even light on laptop not lighting. 
>>> I flashed smaller bios file by adding in begin file difference ( coppied 
>>> from bricked bios).
>>>  Are there some solutions?
>>>  Thanks for answer.
>>>
>>>  With Best Regards
>>>  Aurimas
>>>
>>>  Get BlueMail for Android
>>>  On Mar 2, 2021, at 18:47, Aurelijus Gogas  wrote:
>>>>
>>>>
>>>>  I wired like schema. Resistors used like resistor divider signal-200 
>>>> Om-to flash-200 Om-200 Om-GND. Wires are about 20cm. Wp, hold, vcc 
>>>> connected to 3.3v. when connected to external power supply, then flashrom 
>>>> wrote that is promblem with erase read or something. I wired SPI also as 
>>>> default pins (50-53)… and as schema (31-34).
>>>>
>>>>  Thanks
>>>>
>>>>  With Best Regards
>>>>  Aurimas
>>>>
>>>>  Get BlueMail for Android
>>>>  On Mar 2, 2021, at 18:27, Mike Banon < mikeb...@gmail.com> wrote:
>>>>>
>>>>>
>>>>>  BV should also work fine. Please could you describe your flashing
>>>>>  setup, length of wires etc.
>>>>>
>>>>>  On Sun, Feb 28, 2021 at 10:41 PM Aurelijus Gogas 
>>>>>  wrote:
>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>>   Hallow,
>>>>>>
>>>>>>   Thanks for your work (flashrom). In hardware list there is w25q32, but 
>>>>>> mine is BV. Flashrom can not detect my chip. Is it not supported or i am 
>>>>>> doing something wrong? I wired like example in tutorial. I have  arduino 
>>>>>> mega2560.
>>>>>>
>>>>>>   What i can do?
>>>>>>
>>>>>>   Thanks for help.
>>>>>>
>>>>>>
>>>>>>
>>>>>>   With Best Regards
>>>>>>
>>>>>>   Aurimas
>>>>>>
>>>>>>
>>>>>>
>>>>>>   Get BlueMail for Android
>>>>>>
>>>>>>
>>>>>>
>>>>>> 
>>>>>>
>>>>>>
>>>>>>   flashrom mailing list -- flashrom@flashrom.org
>>>>>>
>>>>>>   To unsubscribe send an email to flashrom-le...@flashrom.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>


-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: About bios flash

[Mike Banon]

Hi there, 20cm wires is a bit long in my opinion - should be 10cm, but
still - if your board is "hungry" - there may be a voltage drop and
the resulting voltage level is insufficient for the successful
flashing. As for "desoldered & flashed & soldered and nothing happens"
- if you're confident your hardware is OK, then there may be an issue
with a proprietary BIOS image that you are flashing, and I could only
suggest searching for a good BIOS online or trying to extract it from
a manufacturer's UEFI update utility if nothing helps.


On Thu, Mar 18, 2021 at 7:45 PM Aurelijus Gogas  wrote:
>
> Hallo again. I flashed winbond bios on asus x54h only when desoldered. But 
> when I soldered back, there was nothing. Even light on laptop not lighting. I 
> flashed smaller bios file by adding in begin file difference ( coppied from 
> bricked bios).
> Are there some solutions?
> Thanks for answer.
>
> With Best Regards
> Aurimas
>
> Get BlueMail for Android
> On Mar 2, 2021, at 18:47, Aurelijus Gogas  wrote:
>>
>> I wired like schema. Resistors used like resistor divider signal-200 Om-to 
>> flash-200 Om-200 Om-GND. Wires are about 20cm. Wp, hold, vcc connected to 
>> 3.3v. when connected to external power supply, then flashrom wrote that is 
>> promblem with erase read or something. I wired SPI also as default pins 
>> (50-53)… and as schema (31-34).
>>
>> Thanks
>>
>> With Best Regards
>> Aurimas
>>
>> Get BlueMail for Android
>> On Mar 2, 2021, at 18:27, Mike Banon < mikeb...@gmail.com> wrote:
>>>
>>> BV should also work fine. Please could you describe your flashing
>>> setup, length of wires etc.
>>>
>>> On Sun, Feb 28, 2021 at 10:41 PM Aurelijus Gogas  
>>> wrote:
>>>
>>>
>>>>
>>>>
>>>>  Hallow,
>>>>
>>>>  Thanks for your work (flashrom). In hardware list there is w25q32, but 
>>>> mine is BV. Flashrom can not detect my chip. Is it not supported or i am 
>>>> doing something wrong? I wired like example in tutorial. I have  arduino 
>>>> mega2560.
>>>>
>>>>  What i can do?
>>>>
>>>>  Thanks for help.
>>>>
>>>>
>>>>
>>>>  With Best Regards
>>>>
>>>>  Aurimas
>>>>
>>>>
>>>>
>>>>  Get BlueMail for Android
>>>>
>>>>
>>>>
>>>> 
>>>>
>>>>  flashrom mailing list -- flashrom@flashrom.org
>>>>
>>>>  To unsubscribe send an email to flashrom-le...@flashrom.org
>>>>
>>>>
>>>>
>>>
>>>
>>>


-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: HP chromebook 11 g4 - dead

[Mike Banon]

It looks like you have some reliability problems with your flashing
setup. Please verify that the wires are short enough, etc.

On Thu, Mar 4, 2021 at 12:23 PM Blah Mbah  wrote:
>
> sudo ./flashrom -p ch341a_spi -w
> backup_folder/coreboot_tiano-kip-mrchromebox_20200604.rom
> [sudo] šifra za eeepc:
> flashrom v1.2-99-gfbb2b25f61 on Linux 5.4.0-65-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 "W25Q64.W" (8192 kB, SPI) on ch341a_spi.
> Reading old flash chip contents... done.
> Erasing and writing flash chip... FAILED at 0x08f4! Expected=0xff,
> Found=0xfe, failed byte count from 0x-0x0fff: 0x2
> ERASE FAILED!
> Reading current flash chip contents... done. Looking for another erase 
> function.
> FAILED at 0x020b! Expected=0xff, Found=0xdf, failed byte count
> from 0x-0x7fff: 0x3
> ERASE FAILED!
> Reading current flash chip contents... done. Looking for another erase 
> function.
> FAILED at 0x020b! Expected=0xff, Found=0xdf, failed byte count
> from 0x-0x: 0x6
> ERASE FAILED!
> Reading current flash chip contents... done. Looking for another erase 
> function.
> FAILED at 0x05c5! Expected=0xff, Found=0xfd, failed byte count
> from 0x-0x007f: 0x360
> ERASE FAILED!
> Reading current flash chip contents... done. Looking for another erase 
> function.
> FAILED at 0x09cd! Expected=0xff, Found=0xfd, failed byte count
> from 0x-0x007f: 0x37b
> ERASE FAILED!
> Reading current flash chip contents... done. Looking for another erase 
> function.
> Looking for another erase function.
> Looking for another erase function.
> No usable erase functions left.
> FAILED!
> Uh oh. Erase/write failed. Checking if anything has changed.
> Reading current flash chip contents... done.
> Apparently at least some data has changed.
> 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!
> eeepc@eeepc-1005:~/ressurect$ sudo ./flashrom -p ch341a_spi
> [sudo] šifra za eeepc:
> flashrom v1.2-99-gfbb2b25f61 on Linux 5.4.0-65-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 "W25Q64.W" (8192 kB, SPI) on ch341a_spi.
> No operations were specified.
> eeepc@eeepc-1005:~/ressurect$
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Flashrom & Serprog Question

[Mike Banon]

Please try out the latest flashrom version, maybe with a Linux LiveCD
- it has more parameters which should be all accessible after reading
about them at -help.

On Sun, Feb 28, 2021 at 8:13 PM  wrote:
>
> Hello again. Posted this question in irc, but had to disconnect, thats why i 
> ask here. I build Urja Rannikko's atmega644 programmer and used it with 
> flashrom 0.9.9 on windows. If i do not connect a flash chip (only parallel 
> flash chips here to test) to the programmer i get the messages that bus mode 
> parallel and spi are on (lpc and hw off). When i connect a SST39VF040 to the 
> programmer and execute flashrom the parallel mode is changed to off, so only 
> spi is on.
> Can i force the programmer / flashrom to check only for flash chips in 
> parallel mode (with a parameter e.g.)?
>
> I did notice, that i had the wrong jumper position set for the flash chip (5V 
> instead of 3,3V). Is it possible that this is the reason why flashrom 
> switches to spi? I'm pretty sure that the flash chip is dead now, but i have 
> two more of this type :).
>
> Hope someone can help.
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: About bios flash

[Mike Banon]

BV should also work fine. Please could you describe your flashing
setup, length of wires etc.

On Sun, Feb 28, 2021 at 10:41 PM Aurelijus Gogas  wrote:
>
> Hallow,
> Thanks for your work (flashrom). In hardware list there is w25q32, but mine 
> is BV. Flashrom can not detect my chip. Is it not supported or i am doing 
> something wrong? I wired like example in tutorial. I have  arduino mega2560.
> What i can do?
> Thanks for help.
>
> With Best Regards
> Aurimas
>
> Get BlueMail for Android
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: error bios

[Mike Banon]

Well, it looks like your flashing has failed. Why? Maybe your flashing
setup wasn't reliable enough: long wires etc. Until we'll learn more
of it, we can't help you

On Fri, Feb 26, 2021 at 10:55 PM edvaldo silva via flashrom
 wrote:
>
> Found GigaDevice flash chip "GD25Q64(B)" (8192 kB, SPI) on ch341a_spi.
> Reading old flash chip contents... done.
> Erasing and writing flash chip... Erase/write done.
> Verifying flash... FAILED at 0x4500! Expected=0x45, Found=0xff, failed 
> byte count from 0x-0x007f: 0x156b2
> Your flash chip is in an unknown state.
>
> Att,
>
> Edvaldo Silva
> edvaldo.si...@zohomail.com
> +55 12 9 8209 6114
>
>
>
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Verifying flash failed

[Mike Banon]

There's no way to know you've successfully wrote the chip until the
verification - which failed in your case. As usual, please make sure
that your wires are short enough etc. - your flashing setup should be
reliable

On Wed, Feb 17, 2021 at 5:17 PM Nathaniel King  wrote:
>
> Hi,
>
> I have successfully erased and write the chip but it cannot verify it. When I 
> try to boot it it doesn't even boot, fan spin on for a second and then off.
>
> I am flashing my t440p.
>
> I hope I have given you enough information.
>
> Thanks,
> Nathaniel
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Error on Yuna

[Mike Banon]

It seems the write command failed since the start, so doing a reboot
should be safe.

On Mon, Feb 15, 2021 at 3:04 PM Flynn Price  wrote:
>
> Hi, can you please see the error below? Am i safe to reboot?
> Previously it said the flash was in an unknown state and to not reboot. 
> Thanks!
>
> Erasing and writing flash chip... 0x42-0x427fff: EInvalid OPCODE 0x06, 
> will not execute.
> spi_write_cmd failed during command execution at address 0x42
>  ERASE_FAILED
> FAILED!
> Uh oh. Erase/write failed. Checking if anything changed.
> Reading current flash chip contents... 00-0x7f:R done.
> Good, writing to the flash chip apparently didn't do anything.
> This means we have to add special support for your board, programmer or flash
> chip. 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



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: how dump FL128SAIH30, manufactured by Alvarion Technologies

[Mike Banon]

Looking at "Reading flash... done.", I think you've dumped it successfully

On Thu, Feb 4, 2021 at 5:02 PM beba beba via flashrom
 wrote:
>
> i probly like
> _030221_1_MHZ.bin -c S25FL128S..1
> flashrom v1.0 on Linux 4.4.71+ (armv7l)
> flashrom is free software, get the source code at https://flashrom.org
>
> flashrom was built with libpci 3.5.2, GCC 6.3.0 20170516, little endian
> Command line (9 args): ./flashrom -p 
> linux_spi:dev=/dev/spidev2.0,spispeed=1000 -V -o FILE_030221_1MHZ.log -r 
> FLASH_CI_modul_030221_1_MHZ.bin -c S25FL128S..1
> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> Initializing linux_spi programmer
> Using device /dev/spidev2.0
> Using 1000 kHz clock
> The following protocols are supported: SPI.
> Probing for Spansion S25FL128S..1, 16384 kB: probe_spi_rdid_generic: id1 
> 0x01, id2 0x2018
> Found Spansion flash chip "S25FL128S..1" (16384 kB, SPI) on linux_spi.
> Chip status register is 0x00.
> Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not 
> set
> Chip status register: Program Fail Flag (P_FAIL) is not set
> Chip status register: Erase Fail Flag (E_FAIL) is not set
> Chip status register: Block Protect 2 (BP2) is not set
> Chip status register: Block Protect 1 (BP1) is not set
> Chip status register: Block Protect 0 (BP0) is not set
> Chip status register: Write Enable Latch (WEL) is not set
> Chip status register: Write In Progress (WIP/BUSY) is not set
> This chip may contain one-time programmable memory. flashrom cannot read
> and may never be able to write it, hence it may not be able to completely
> clone the contents of this chip (see man page for details).
> ===
> This flash part has status UNTESTED 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!
> Reading flash... done.
> linaro@tinkerboard:~/flashrom_ci_modul$
>
>
>
> _______
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Question about flashrom GD25Q64(B)

[Mike Banon]

OP's question got resolved at
https://mail.coreboot.org/hyperkitty/list/coreb...@coreboot.org/thread/HVTJJHBU4TBDKFMHDTDMMUM2THKT5Y3H/
, for those who are searching.

On Thu, Jan 28, 2021 at 8:36 PM magiccat1 via flashrom
 wrote:
>
> Hi,
>
> How are you?
>
> I am trying to coreboot an Asus A88XM-E.  The chip on that motherboard is 
> GD25Q64(B), which I execute sudo flashrom --programmer ch341a_spi -w 
> coreboot.rom, I got this error:
> flashrom v1.2 on Linux 5.9.14-rockchip64 (aarch64)
> flashrom is free software, get the source code at https://flashrom.org
>
> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> Found GigaDevice flash chip "GD25Q64(B)" (8192 kB, SPI) on ch341a_spi.
> Reading old flash chip contents... done.
> Erasing and writing flash chip... Erase/write done.
> Verifying flash... FAILED at 0x! Expected=0x5f, Found=0xff, failed 
> byte count from 0x-0x007f: 0x168
> 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!
>
> I got new GD25Q64 chips from aliexpress.  The verbose version is like this:
>
> Found GigaDevice flash chip "GD25Q64(B)" (8192 kB, SPI).
> This chip may contain one-time programmable memory. flashrom cannot read
> and may never be able to write it, hence it may not be able to completely
> clone the contents of this chip (see man page for details).
> Reading old flash chip contents... done.
> Erasing and writing flash chip... Trying erase function 0... 
> 0x00-0x000fff:EFAILED at 0x! Expected=0xff, Found=0x00, failed 
> byte count from 0x-0x0fff: 0xd28
> ERASE FAILED!
> Reading current flash chip contents... done. Looking for another erase 
> function.
> Trying erase function 1... 0x00-0x007fff:EFAILED at 0x! 
> Expected=0xff, Found=0x00, failed byte count from 0x-0x7fff: 
> 0x7a0b
> ERASE FAILED!
> Reading current flash chip contents... done. Looking for another erase 
> function.
> Trying erase function 2... 0x00-0x00:EFAILED at 0x! 
> Expected=0xff, Found=0x00, failed byte count from 0x-0x: 
> 0xf342
> ERASE FAILED!
> Reading current flash chip contents... done. Looking for another erase 
> function.
> Trying erase function 3... 0x00-0x7f:EFAILED at 0x! 
> Expected=0xff, Found=0x00, failed byte count from 0x-0x007f: 
> 0x9dfd4
> ERASE FAILED!
> Reading current flash chip contents... done. Looking for another erase 
> function.
>
> I have also made a post on reddit asking for answers.
> https://www.reddit.com/r/coreboot/comments/krfjsn/question_about_how_to_coreboot_an_asus_a88xme/
>
> Can you please let me know what I did wrong?
>
> Thanks,
>
>
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org



-- 
Best regards, Mike Banon
Open Source Community Manager of 3mdeb - https://3mdeb.com/
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: flashrom on my laptop

[Mike Banon]

In any case the internal mode is a bit risky especially on the
laptops, and - if you can't use the official update utility - maybe
just get a flashrom-supported programmer like CH341A (ideally a green
PCB one, and make sure to check its' voltage before using) and a SOIC8
or SOIC16 test clip depending on your BIOS chip shape, to be able to
flash your BIOS chip without desoldering it.

On Fri, Jan 8, 2021 at 1:35 AM ShadowAce1 via flashrom
 wrote:
>
> Hello,
>
> I am rying to update the BIOS on my 10-yr-old laptop.  Per the output of the 
> flashrom command, I am including the output I received:
>
> [root@Dilbert ~]# flashrom -p internal -V
> flashrom v1.2 on Linux 5.8.18-350.vanilla.knurd.1.fc33.x86_64 (x86_64)
> flashrom is free software, get the source code at https://flashrom.org
>
> flashrom was built with libpci 3.6.4, GCC 10.2.1 20201125 (Red Hat 10.2.1-9), 
> little endian
> Command line (3 args): flashrom -p internal -V
> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> Initializing internal programmer
> /sys/class/mtd/mtd0 does not exist
> No coreboot table found.
> Using Internal DMI decoder.
> DMI string chassis-type: "Notebook"
> Laptop detected via DMI.
> DMI string system-manufacturer: "Micro-Star International"
> DMI string system-product-name: "GT680R/GX680R"
> DMI string system-version: "To be filled by O.E.M."
> DMI string baseboard-manufacturer: "Micro-Star International"
> DMI string baseboard-product-name: "MS-16F2"
> DMI string baseboard-version: "To be filled by O.E.M."
> W836xx enter config mode worked or we were already in config mode. W836xx 
> leave config mode had no effect.
> Active config mode, unknown reg 0x20 ID: 00.
> Found chipset "Intel HM67" with PCI ID 8086:1c4b.
> This chipset is marked as untested. If you are using an up-to-date version
> of flashrom *and* were (not) able to successfully update your firmware with 
> it,
> then please email a report to flashrom@flashrom.org including a verbose (-V) 
> log.
> Thank you!
> Enabling flash write... Root Complex Register Block address = 0xfed1c000
> Error accessing ICH RCRB, 0x4000 bytes at 0xfed1c000
> /dev/mem mmap failed: Operation not permitted
> FAILED!
> FATAL ERROR!
> Error: Programmer
>
> Can you help?  Can I use this utility to flash my BIOS (I have the BIOS file 
> from MSI)?
>
> Mike
>
>
> Sent with ProtonMail Secure Email.
>
> ___
> 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: Dell XPS 15 9550

[Mike Banon]

Perhaps you're having the connection quality problems, make sure that
your wires are short enough etc. Also, regarding " when checking to
see if the checksum of the reads I do are identical, they always come
up as different values. " - to slightly clarify this situation you
could try doing " xxd ./dump1.bin > ./dump1.txt ", " xxd ./dump2.bin >
./dump2.txt " and then compare these dumps with some diff utility to
see if there's any pattern at the read errors.

On Fri, Jan 8, 2021 at 1:34 AM Andrew Warhol via flashrom
 wrote:
>
> Hello, I was wondering if anyone would mind helping me with an issue I'm 
> running into with flashrom on a dell xps 15 9550. The dell has a 16 mbyte 
> Winbond W25Q128.V bios chip on it. I'm using flash rom on a raspberry pi 4 
> but when I read this chip with a soic8 test clip, it seems to read 
> successfully. However, when checking to see if the checksum of the reads I do 
> are identical, they always come up as different values. The other two bios 
> chips however read with the same checksums every time. I am attempting to use 
> intel me cleaner to set the hap bit and disable intel me without 
> repartitioning or cleaning anything on the chip as intel boot guard is 
> enabled. ME Cleaner is able to read the file and say the hap bit has been 
> successfully set. However, when writing the modified image, I get the error 
> through flash rom verifying flash...failed, your flash chip is in an unknown 
> state. The laptop will no longer boot and the power light comes on for a 
> moment before turning on. I suspect eith
 er flash rom is not compatible with this chip or something about this chip 
prevents it from being read by flash rom. Using this guide: 
darajnish/dell5577medisable it seems as though a select few people have been 
able to set the hap bit by using the command soft-disable-only. Even when I try 
re-flashing the original read bios image however, the laptop still does not 
boot. I read somewhere that my chip has flash descriptors locked, but since 
other people have had success I'm not sure why I can't get it to work properly. 
Any advice would be much appreciated!
> ___
> 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: Ch341a

[Mike Banon]

Looking at https://github.com/flashrom/flashrom/blob/master/flashchips.h
file, line ~600, I see there's an ID for PMC_PM25LQ020 but no ID for
PMC_PM25LQ010 (which is probably 0x41 but you should check a chip
datasheet), you'll need to add this. In addition, there's a
flashchips.c file which contains a data structure for a PMC_PM25LQ020
chip around ~12370 line - you'll need to copy-paste it for
PMC_PM25LQ010 and change a couple of values (name and chip size) to
match it. Then try to rebuild a flashrom with these modifications and
run it.

On Sun, Jan 17, 2021 at 3:38 AM Chuck Wilson  wrote:
>
> Received the following message:  "Read is not working on this chip. 
> Aborting." while trying to read a "PM25LQ010"
>
> Here is the exact programmer I have:
> SOIC8 SOP8 Flash Chip/IC Test Clip with Adapters and CH341A 24 25 Series 
> EEPROM Flash BIOS USB Programmer
>
> Amazon Link:
> https://www.amazon.com/gp/product/B08CDCPPTZ/ref=ppx_yo_dt_b_asin_title_o07_s02?ie=UTF8=1
>
> The PM25LQ010 I would like to read/write is on a Nvidia GTS 450 Video Card.  
> Flashrom Version 1.2 has detected my CH341A USB device but unable to detect 
> the Bios Chip.  Included a picture of the physical Bios.  If there is more 
> information I can provide please let me know.
>
> Chuck
> ___
> 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: reading is ok but writing fails

[Mike Banon]

Please tell me more about your connection setup. Is it done by ISP (in
system programming), i.e. a test clip? If your connection seems to be
reliable and the wires are short enough (ideally less than 10cm) :
some devices aren't working well with ISP, i.e. if the surrounding
circuits are too power hungry and as result there's a voltage drop.

On Thu, Dec 10, 2020 at 2:05 PM Cédric Vuillet  wrote:
>
> Hi,
>
>
> thanks for working on flashrom which seems to be great!
>
>
> I tried to use it in order to flash an NVidia GTX780M to put it in a iMac 
> 2010 which has graphic issue today.
>
>
> I tried to flash it using a CH341A module.
>
>
> I was able to save rom in a file using flashrom on MacOS X.
>
>
> But I have a problem trying to write a new rom on that card.
>
>
> This is the result I got... Do you know if I must change jumpers or something 
> on my CH341A controller. Or do you think this can be a plug issue on the chip 
> ?
>
>
> Tell me if you want a more verbose log maybe...
>
>
> Thanks à lot!
>
>
> Ced
>
>
>
> flashrom -p ch341a_spi -w ~/Downloads/780M_BR2.rom
>
> flashrom v1.2 on Darwin 19.6.0 (x86_64)
>
> flashrom is free software, get the source code at https://flashrom.org
>
>
> Calibrating delay loop... OK.
>
> Found PMC flash chip "Pm25LD020(C)" (256 kB, SPI) on ch341a_spi.
>
> Reading old flash chip contents... done.
>
> Erasing and writing flash chip... FAILED at 0x! Expected=0xff, 
> Found=0x4e, failed byte count from 0x-0x0fff: 0xf85
>
> ERASE FAILED!
>
> Reading current flash chip contents... done. Looking for another erase 
> function.
>
> FAILED at 0x! Expected=0xff, Found=0x4e, failed byte count from 
> 0x-0x0fff: 0xf85
>
> ERASE FAILED!
>
> Reading current flash chip contents... done. Looking for another erase 
> function.
>
> FAILED at 0x! Expected=0xff, Found=0x4e, failed byte count from 
> 0x-0x: 0xf6c3
>
> ERASE FAILED!
>
> Reading current flash chip contents... done. Looking for another erase 
> function.
>
> libusb: warning [darwin_transfer_status] transfer error: timed out
>
>
> cb_in: error: LIBUSB_TRANSFER_TIMED_OUT
>
> ch341a_spi_spi_send_command: Failed to read 4100 bytes
>
> libusb: warning [darwin_abort_transfers] aborting all transactions on 
> interface 0 pipe 1
>
> Verification impossible because read failed at 0x0 (len 0x4)
>
> ERASE FAILED!
>
> Reading current flash chip contents... done. Looking for another erase 
> function.
>
> FAILED at 0x! Expected=0xff, Found=0x4e, failed byte count from 
> 0x-0x0003: 0x27c8d
>
> ERASE FAILED!
>
> Reading current flash chip contents... libusb: warning 
> [darwin_transfer_status] transfer error: timed out
>
>
> cb_in: error: LIBUSB_TRANSFER_TIMED_OUT
>
> ch341a_spi_spi_send_command: Failed to read 4100 bytes
>
> libusb: warning [darwin_abort_transfers] aborting all transactions on 
> interface 0 pipe 1
>
> Can't read anymore! Aborting.
>
> FAILED!
>
> Uh oh. Erase/write failed. Checking if anything has changed.
>
> Reading current flash chip contents... done.
>
> Good, writing to the flash chip apparently didn't do anything.
>
> Please check the connections (especially those to write protection pins) 
> between
>
> the programmer and the flash chip. If you think the error is caused by 
> flashrom
>
> 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: flashrom FAILED

[Mike Banon]

what's the length of your cables between a programmer and a flash
chip, and the overall connection quality? also I'd suggest a simpler
programmer like ch341a (preferably a green PCB version), just make
sure its' voltage is 3.3V

On Tue, Dec 1, 2020 at 12:29 AM Bálint Boldizsár Varga
 wrote:
>
> Dear Team!
>
> I got an error while librebooting my thinkpad x200.
>
> The error message was:
> Verifying flash... FAILED at 0x0003a709! Expected=0xb8, Found=0x80, failed 
> byte count from 0x-0x007f: 0x124fYour flash chip is in an unknown 
> state.
>
> I used this command:
> ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=128 -w 
> /home/pi/x200/x200_8mb_deqwertz_vesafb.rom -V -c MX25L6405D
>
> I followed the instructions of this reddit post:
> https://www.reddit.com/r/libreboot/comments/7dajn6/x200_libreboot_tutorial_for_raspberry_pi_with/
>
> Should I retry the flashrom?
>
> Thank you in advance!
>
> Balint
> ___
> 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: Fail on CHIP "W25Q256.V"

[Mike Banon]

Please check the possible failure reasons that aren't a fault of flashrom:
1) old flashrom version. Compile the latest version from the source code
2) unreliable connection or too long cables between a flasher and a chip

On Fri, Nov 20, 2020 at 3:18 AM Igor Omelchenko  wrote:
>
> Adding logs.
>
>
>
> ср, 18 нояб. 2020 г. в 09:00, Igor Omelchenko :
>>
>> Hello!
>>
>> Tried to flash BIOS on "W25Q256.V" chip, got below  errors:
>>  (Tried with 24-45k spispeed. tried with -n and without -n)
>> Thanks for your amazing work!
>>
>> squid@squid:~$ sudo flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=24000 
>> -n -w  /squid/Squid/Files/SES5_00_2020WW45.1.01.bin
>> flashrom  on Linux 4.14.108-ti-r137 (armv7l)
>> 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 "W25Q256.V" (32768 kB, SPI) on linux_spi.
>> Reading old flash chip contents... done.
>> Erasing and writing flash chip... FAILED at 0x0002! Expected=0xff, 
>> Found=0x7f, failed byte count from 0x-0x0fff: 0xffc
>> ERASE FAILED!
>> Reading current flash chip contents... done. Looking for another erase 
>> function.
>> FAILED at 0x0002! Expected=0xff, Found=0x7f, failed byte count from 
>> 0x-0x7fff: 0x7fee
>> ERASE FAILED!
>> Reading current flash chip contents... done. Looking for another erase 
>> function.
>> FAILED at 0x0002! Expected=0xff, Found=0x7f, failed byte count from 
>> 0x-0x: 0xffde
>> ERASE FAILED!
>> Reading current flash chip contents... done. Looking for another erase 
>> function.
>> FAILED at 0x0002! Expected=0xff, Found=0x7f, failed byte count from 
>> 0x-0x01ff: 0x1ffbf90
>> ERASE FAILED!
>> Reading current flash chip contents... done. Looking for another erase 
>> function.
>> FAILED at 0x0002! Expected=0xff, Found=0x7f, failed byte count from 
>> 0x-0x01ff: 0x1ffbe3a
>> ERASE FAILED!
>> Reading current flash chip contents... done. Looking for another erase 
>> function.
>> Looking for another erase function.
>> Looking for another erase function.
>> No usable erase functions left.
>> FAILED!
>> Uh oh. Erase/write failed. Checking if anything has changed.
>> Reading current flash chip contents... done.
>> Apparently at least some data has changed.
>> 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!
>>
>> --
>> Omelchenko Igor
>> 0543-066-855
>
>
>
> --
> Omelchenko Igor
> 0543-066-855
> ___
> 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: Successful Flashrom Install - Thanks to all!

[Mike Banon]

Please note that sometimes a "BIOS update" app installs not just a
BIOS update but also an update for EC controller firmware etc (which
isn't always possible with flashrom)

On Sat, Nov 7, 2020 at 11:05 AM Clay Daniels  wrote:
>
> The success continues: A new bios update became available for my MSI 
> motherboard this week, and I used my newly working install to write it to the 
> flash chip thus:
> root@clay-MS-7C37:~# flashrom -p internal -w E7C37AMS.HB0 -V
>  And it worked! I now have successfully updated my bios with flashrom.
>
> On Thu, Nov 5, 2020 at 12:58 AM Clay Daniels  
> wrote:
>>
>> All the pieces finally came together. I made a fresh install of Ubuntu, 
>> installed all the needed tools. cloned flashrom, modified sb600spi.c per 
>> Rene's patch to include my AMD X570 "0x61" spi, did a make install, and it 
>> works!
>>
>> root@clay-MS-7C37:~# flashrom -p internal
>> flashrom v1.2-135-g07edbb9-dirty on Linux 5.8.0-26-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 chipset "AMD FP4".
>> Enabling flash write... Warning: spireadmode not set, leaving spireadmode 
>> unchanged.Warning: spispeed not set, leaving spispeed unchanged.OK.
>> Found Winbond flash chip "W25Q256.W" (32768 kB, SPI) mapped at physical 
>> address 0xfe00.
>> No operations were specified.
>> root@clay-MS-7C37:~#
>>
>> Thanks to everyone,
>> Clay
>> (Boot_Dawg)
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Chip burner CH341A commands

[Mike Banon]

If this HDD board is too power hungry - the surrounding elements of a
BIOS chip are trying to "eat" too much current through a programmer -
then a programmer could become unresponsive and even overheat. Had
such a problem while trying to read a firmware of a HDMI capturer
device. Could you detect your programmer at Ubuntu when it's not
connected to a HDD board?

On Mon, Oct 12, 2020 at 9:25 AM Hîj Vasile via flashrom
 wrote:
>
> Hi Flashrom,
>
> I have a PCB of a HDD which is damaged by heat, but I was trying to read the 
> bios chip. I have tried with CH341a Programmer 1.29 and 1.41, but I cannot 
> find my bios 25S40A 00 LFGC. I have tried second option with Ubuntu command 
> (installed as a subsystem of Windows).
>
> So, I am using this command sudo flashrom --programmer ch341a_spi -r b
> Couldn't open device 1a86:5512.
> Error: Programmer initialization failed.
>
> It is a because I run Ubuntu as described, the cleat not touching the pins 
> enough or my chip is burned too?
>
> I would appreciate any help.
>
>
> Kind regards,
>
> Vasile
>
> ___
> 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: Beginners-Guide-to-Using-a-CH-A-SPI-Programmer with AMD

[Mike Banon]

Not at all! The need for 3.3v ---> 1.8v adapter - depends not on
"Intel vs AMD", but on the model of that SPI flash chip. You see the
markings on the back of such a chip, google them, find a correct
datasheet, open it and read what's the working voltage for this chip -
3.3v or 1.8v.

On Wed, Oct 7, 2020 at 9:43 AM Clay Daniels  wrote:
>
> https://www.win-raid.com/t4287f16-GUIDE-The-Beginners-Guide-to-Using-a-CH-A-SPI-Programmer-Flasher-With-Pictures.html
>
> Nice article in general, but it also says:
> "Note: If you are flashing an AMD motherboard, you need to put the 1.8V 
> adapter into the SPI, and then put the clip assembly onto that."
>
> So is this right? 3.3v for Intel, 1.8v for AMD?
> ___
> 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: XM25QH64A

[Mike Banon]

> flashrom v0.9.9-r1954

The reports for such an old flashrom version usually do not count. If
your old Linux doesn't provide a newer version at repositories, please
build it by yourself - following the instructions from a flashrom
wiki. It's quite easy and you'll have the latest flashrom version,
with the support for more chips and important bug fixes.
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: MSI X570-A PRO (MS-7C37)

[Mike Banon]

Little "block" thing isn't physical - it's a white paint highlighting
the 1st pin. And actually your motherboard seems to have 11 pins at
JSPI1 header (one of the pins is missing - perhaps to clarify the
alignment). Maybe this JSPI1 pinout changed with time, so please check
out the pinout pictures of "new JSPI1" on the Internet. Hope that
helps.

On Sat, Sep 19, 2020 at 8:35 AM Clay Daniels  wrote:
>
> Wow! The NIX Russian online store link to my motherboard really lets you see 
> the layout. Much better than anything I had gotten from MSI directly. When I 
> built my computer I bought a large case for an ATX motherboard that has an 
> open side covered by a clear plastic window that shows the face of the 
> motherboard. Most of the time I don't see it because I have limited room on 
> my computer bench, but just now I dug out my flashlight (it's night here in 
> Ft. Worth Texas) and moved the monitor back, and without opening the case at 
> all, I can see JSPI1 just exactly where the picture from NIX shows.
>
> Apparently JSPI1 is a special pin-out for MSI's bios, and can be used like 
> you say to flash the bios. One thing that confuses me a little is that the 
> page at flashrom:
> https://www.flashrom.org/MSI_JSPI1
> shows a 10 pin layout and the picture shows 2x6=12 pin layout, and in fact my 
> own mb has 12 pins at the JSPI1 header. Your picture seems to show a little 
> "block" thing on the left end, maybe to keep these two pins from connecting? 
> Anyway, it's clear I have a lot of options. It may be tricky to get in 
> between my video card & cpu cooler, but I can see JSPI1.
>
> Thanks so much for your help,
> Clay
>
> On Fri, Sep 18, 2020 at 10:43 AM Ivan Ivanov  wrote:
>>
>> NIX russian online store - often has the high resolution quality
>> photos of their products. Open this link and close a pop-up window
>> which says this motherboard is unavailable and offers some
>> alternatives - 
>> https://www.nix.ru/autocatalog/motherboards_msi/MSI-X570-A-PRO-RTL-AM4-X570-2xPCI-E-HDMI-GbLAN-SATA-ATX-4DDR4_427748.html
>> . Then click on a motherboard main picture and use a + magnifier /
>> gallery.
>>
>> MSI's own flashing methods - work only as long as its' installed BIOS
>> is working - otherwise, there's no other option than the external
>> flashing methods. And of course MSI's BIOS is far from being perfect
>> and may have significant bugs + security issues. If you care about
>> really controlling your computer, consider getting a motherboard
>> supported by opensource coreboot BIOS - such as ASUS A88XM-E. Of
>> course it's less powerful than Ryzen, but offers much more
>> customization, great security and even possible to add floppy-based OS
>> and run them right from a BIOS. And of course MBR is not a thing of
>> the past: SeaBIOS coreboot's payload is a "modern legacy BIOS" and
>> I've never had any problems with its' MBR. Pushing for new standards
>> that are more and more complicated and closed - shouldn't be done just
>> for the sake of new-ness. "One old friend is better than two new ones"
>>
>> пт, 18 сент. 2020 г. в 18:35, Miraz Shuvra :
>> >
>> >
>> > On Fri, Sep 18, 2020, 10:56 AM Clay Daniels  
>> > wrote:
>> >>
>> >> Ivan, thanks so much for the valuable information! It seems to me you 
>> >> have found a more detailed picture of the motherboard than I have. All I 
>> >> can find is marketing pictures, and a 'quick start guide', but no real 
>> >> picture that shows stuff like you describe. Please do let me know the 
>> >> link to the picture you are looking at.
>> >>
>> >> The project is not really that urgent, and I have no trouble using the 
>> >> MSI flash routine in the bios. The board is new enough that there are 
>> >> regular updates to the bios, 10 versions (1 thru A) since I bought the 
>> >> motherboard & built the machine the summer of 2019.
>> >>
>> >> Another thing that MSI offers on the motherboard is a "flash button" and 
>> >> dedicated usb port for the source bios on the back of the board. I have 
>> >> not used this feature, but it may offer some direct flash route to the 
>> >> bios for all I know.
>> >>
>> >> The MSI bios is ok, and seems very advanced with a lot of graphics but 
>> >> actually is kind of primitive in how it deals with bootable disks and 
>> >> devices. Everything is an icon, and sometimes the icons don't match the 
>> >> device very well. I think it's geared to a gamer who has one big disk 
>> >> drive, and they really want you to use UEFI/GPT, and treat MBR as totally 
>> >> a thing of the past, which may or may not be true. I have NetBSD running 
>> >> on a MBR whole disk setup on my older 2014 HP Pavilion that originally 
>> >> came with Windows 8.1. It works fine using MBR & NetBSD. No icons in that 
>> >> bios. The machine is really nice for what it is, but is too slow for much 
>> >> action. The newer home-built machine is my main hobby, I suppose.
>> >>
>> >> Anyway, thanks for the info, and do send me a link to the detailed 
>> >> 

[flashrom] Re: Flashing iPXE rom on motherboard NIC

[Mike Banon]

It's BIOS chips are soldered SOIC-8 ones, so - in addition to a
programmer like - you'll need a SOIC-8 test clip to backup the
contents of these chips. USB extension cable is also recommended for
more convenience. You can do a backup of both chips (BIOS and Intel
ME) and then proceed.

On Tue, Sep 15, 2020 at 1:02 PM bizan...@gmail.com  wrote:
>
> On 09/15/2020 12:39 PM, Mike Banon wrote:
> > Tell us your motherboard model etc, so that we can learn more about
> > the possible recovery options just in case. Maybe you can get a dirt
> > cheap (2 dollar) flashrom-supported programmer like CH341A (green
> > PCB), remove a chip using a PLCC clip, insert to a programmer, backup
> > the contents and then do the experiments you'd like to try - and, if
> > anything goes wrong, you just restore a knowing good image using
> > another computer.
> >
> > On Mon, Sep 14, 2020 at 11:49 AM bizan...@gmail.com  
> > wrote:
> >> Hi,
> >>
> >> I did an attempt just to see if flashing a ROM works on my motherboard
> >> before flashing i-PXE rom.
> >> I try to backup with command: flashrom -p internal -V -r biosback
> >> Then flashing the same backup: flashrom -p internal -V -w biosback
> >> No error occurs and after a reboot the system is OK.
> >>
> >> I am frightened to destroy entire BIOS while flashing an i-PXE rom on my
> >> onboard NIC.
> >> The previous mentioned backup is 1,048,576 bytes and seems realy large
> >> and may be it contains bios data other than PXE code.
> >> I have doubt where the program retrieve and write his data because there
> >> is no atheros feature for it.
> >>
> >> I want to know if there is any danger to alter the entire BIOS if I
> >> flash an i-PXE ROM on my onboard NIC ?
> >>
> >> Thanks
> >> ___
> >> flashrom mailing list -- flashrom@flashrom.org
> >> To unsubscribe send an email to flashrom-le...@flashrom.org
>
> Hi,
>
> The mother board is a Gigabyte GA-G41MT-S2P (rev.1.5)
>
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Flashing iPXE rom on motherboard NIC

[Mike Banon]

Tell us your motherboard model etc, so that we can learn more about
the possible recovery options just in case. Maybe you can get a dirt
cheap (2 dollar) flashrom-supported programmer like CH341A (green
PCB), remove a chip using a PLCC clip, insert to a programmer, backup
the contents and then do the experiments you'd like to try - and, if
anything goes wrong, you just restore a knowing good image using
another computer.

On Mon, Sep 14, 2020 at 11:49 AM bizan...@gmail.com  wrote:
>
> Hi,
>
> I did an attempt just to see if flashing a ROM works on my motherboard
> before flashing i-PXE rom.
> I try to backup with command: flashrom -p internal -V -r biosback
> Then flashing the same backup: flashrom -p internal -V -w biosback
> No error occurs and after a reboot the system is OK.
>
> I am frightened to destroy entire BIOS while flashing an i-PXE rom on my
> onboard NIC.
> The previous mentioned backup is 1,048,576 bytes and seems realy large
> and may be it contains bios data other than PXE code.
> I have doubt where the program retrieve and write his data because there
> is no atheros feature for it.
>
> I want to know if there is any danger to alter the entire BIOS if I
> flash an i-PXE ROM on my onboard NIC ?
>
> 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: Hello FlashRom Rescue Team !

[Mike Banon]

"only firm can do" - of course not true, you just need to get the
hardware tools for yourself. Luckily, the cheapest programmer
supported by flashrom - *** CH341A USB (preferably with a green PCB) -
costs just 2 dollars with a free shipping (if to get directly from
AliExpress/China), but more expensive if to get locally. Of course,
you need to somehow connect this programmer to this chip. Many desktop
boards have a BIOS chip in DIP-8 shape inserted inside a socket, from
where it's easy to remove it using a *** PLCC clip (to avoid
bending/breaking the chip legs during the removal), plug it into a
programmer, flash a good BIOS image then put it back. But in your case
- if I correctly understood that your friend's PC motherboard model is
Acer D1F-AD (is it true?) - at the blurry Internet pictures, a BIOS
chip seems to be in a SOIC-8 shape and soldered to a board (not
socketed). Can see this chip near a big black heatsink, it's a chip
with 8 legs near the "ROM1 SPI_DEBUG1" label if I'm not mistaken. To
avoid the soldering, you need a *** SOIC8 test clip with some wires
which you plug into a programmer and attach a SOIC8 test clip to that
chip (make sure to check the polarity, round pit on a chip is near a
1st leg - CS). The whole process is described at
http://dangerousprototypes.com/docs/Flashing_a_BIOS_chip_with_Bus_Pirate
, a bottom image there is for CH341A flashing a SOIC8 chip on a laptop
motherboard. It contains more description of tools as well. I also
recommend you to get a *** USB extension cable, without it it's much
less convenient. And of course you need another computer, either with
Linux installed or booted from a LiveUSB of some user-friendly distro
like Linux Mint for beginners, so that you could install a flashrom
software and control a CH341A programmer. (Linux version of flashrom
is much better than a Windows one). As you see, the whole set of tools
cost less than 10 dollars, and you can use them for other repairs as
well + maybe freelancing ;-) And you could extract a good BIOS image
from the files taken from a manufacturer's website, sometimes you may
need to play with archiver or Hex editor to extract it and maybe cut
some unnecessary header, let me know if you need help there.

Best regards,
Mike Banon

On Sun, Sep 13, 2020 at 9:57 AM Jean-Marc Petit
 wrote:
>
> A casual story ...
>
> a bios of a friend of mine is stuck 
> from a fail update through Os Windows 10 by AMI ( gui mode ).
>
> About the concerned computer : 
> https://www.packardbell.com/pb/fr/FR/content/download
> SN : 23502301192
> Brand : Packard-Bell
> Model/number : imedia s2110
>
> I pick the bios update from packard-bell url :
> so the chosen version is : P11-B3.CAP
>
> one the update pass, the computer reboot ... and then 'black screen' - no 
> more display.
>
> the mother-board looks on, and beep when I pull off ram.
> it avoid bios access...
>
> I realize cmos reset ( with clear position ), then button battery out ...
>
> one thing I  note , by some try the fan are high speed ( like in fail safe 
> mode/ or on a new fresh cmos setup ... )
> other thing : the Hdd?/cpu? light sometimes is ON until I turn off the 
> computer, but nothing else..
> or this light seems to 'works' but 20 seconds and then nothing...
> I heard Hdd access too, it's a noise I recognize.
>
> The POST don't get over..
>
> To comment about firm answer('s) :
> its money or nothing ... and not costless ( 150 euros... ) , buying a new 
> computer is not so far 
> no relevant ways or accurates answers on acer forum ( packard bell is now 
> acer.. )..
> and a crowd of 'solutions', do but don't do that.. keystrokes but the other 
> one, but after 3 reboot.
>
> As I'm IT worker, but not hardware enough,
> I have to crawl lots of ressources and docs.
>
> So, in front of amibios / afudos / afuwinx64 ...
> I really don't know which one I need, as I can't confim my USB key is read.
>
> I did a usb boot key ( free dos in ), format fat32. with script afudos, then 
> afuminx64 and a batch with amibios advise... but no more display, no more 
> bios.
>
> I don't know if I need a keys combination to launch the usb reading ...at 
> startup.
> I call few It friends , I heard often "only firm can do". ( I don't trust 
> that ... )
>
> Updating a bios is a task I do 1 time a year... computers are globally ok. 
> But it's deep learning for me every time ...
>
> I don't know what you can do for me, if you have an answer...
> I don't know If you need support, or a have pay solutions.
>
> Best regards,
> Jean-Marc Petit
> France. ( Normandy ).
> 01:10 AM - sunday 13/09/2020
>
>
>
>
> ___
> 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: Ch341a support

[Mike Banon]

1) it is ch341a_spi, not sip 2) perhaps a flashrom of Ubuntu hasn't
been built with a libusb support (which is needed for devices like
CH341A). In this case, I recommend you to clone the latest flashrom
sources and build it from the source code - it's really easy to do and
not many dependencies. Full build instructions could be found in a
flashrom wiki

On Sun, Sep 13, 2020 at 9:56 AM John Dixon  wrote:
>
> H
> I have downloaded the most recent version of flashrom in Ubuntu
>
> I have a Ch341a programmer. However flashrom is telling me that ch341_sip is 
> not a valid parameter to the programmer switch
>
> It is not listed under the valid options in the help page
>
> Can you please help
>
> Thanks
> John
>
>
>
> Sent from my iPhone
> ___
> 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: Spansion S25FL127S with 16 MB

[Mike Banon]

Yes, you will need to build a latest flashrom version (i.e. git clone)
from source. Luckily it's pretty easy to build - and, if any
questions, you could always ask us.


On Sun, Aug 23, 2020 at 3:56 PM  wrote:
>
> Hallo,
>
> I use flashrom on a Raspberry PI 4 ( Version 1.0-1)
> Need i building it from the source on a PI 4 ? Bacause is is not version 1.2 
> and when i need to update
> on 1.2 how on PI 4 ?
> --
> Sicher gesendet mit Tutanota. Hol dir deine eigene verschlüsselte & 
> werbefreie Mailbox:
> https://tutanota.com
>
>
> 18. Aug. 2020, 12:32 von mikeb...@gmail.com:
>
> What flashrom version are you using? Maybe yours is outdated? Try
> building it from the source
>
> On Wed, Aug 12, 2020 at 10:35 AM ruckzuck--- via flashrom
>  wrote:
>
>
> Hallo,
>
> If i make Flashrom -L i see in the List only listet :
>
> Spansion S25FL127S-64kB PREW 16384 SPI
> Spansion S25FL127S-256kB 16384 SPI
>
> But not Spansion S25FL127S-128kB for me that lock so that it is not supported
> Need Flashrom a update for the chip ? i think yes.
>
> best reguards
> zuck
>
>
>
>
> --
> Sicher gesendet mit Tutanota. Hol dir deine eigene verschlüsselte & 
> werbefreie Mailbox:
> https://tutanota.com
>
>
> 7. Juli 2020, 18:38 von ruckz...@tuta.io:
>
> allo,
>
> In the End of the Program is written that i send you this:
>
>
> I try to flash the S25FL127S with 16 MB but in the list is it not
>
> then i try with S25FL127S-256kB and this happen:
>
> flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1000 -w out.bin -c 
> S25FL127S-256kB
> flashrom on Linux 4.19.118+ (armv6l)
> flashrom is free software, get the source code at https://flashrom.org
>
> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> Found Spansion flash chip "S25FL127S-256kB" (16384 kB, SPI) on linux_spi.
> ===
> This flash part has status UNTESTED 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!
> Reading old flash chip contents... done.
> Erasing and writing flash chip... spi_nbyte_program called for too long a 
> write
> Reading current flash chip contents... done. Looking for another erase 
> function.
> spi_nbyte_program called for too long a write
> Reading current flash chip contents... done. Looking for another erase 
> function.
> spi_nbyte_program called for too long a write
> Reading current flash chip contents... done. Looking for another erase 
> function.
> Looking for another erase function.
> Looking for another erase function.
> No usable erase functions left.
> FAILED!
> Uh oh. Erase/write failed. Checking if anything has changed.
> Reading current flash chip contents... done.
> Good, writing to the flash chip apparently didn't do anything.
> Please check the connections (especially those to write protection pins) 
> between
> the programmer and the flash chip. If you think the error is caused by 
> flashrom
> please report this on IRC at chat.freenode.net (channel #flashrom) or
> mail flashrom@flashrom.org, thanks!
>
> Need Flashrom a update for the chip ?
>
> best reguards
>
> zuck
>
>
>
> --
> Sicher gesendet mit Tutanota. Hol dir deine eigene verschlüsselte & 
> werbefreie Mailbox:
> https://tutanota.com
>
>
> ___
> 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: flashrom mx25l3255e

[Mike Banon]

If by OTP you mean "One-time programmable bits" - maybe it depends on
a chip you'd like to use. For a chip you've mentioned - mx25l3255e -
everything should be accessible for both read and write (writes - up
to 10 times if I'm not mistaken). Personally I haven't encountered
any flashrom-supported chips which could be programmed only once.

On Sat, Aug 22, 2020 at 5:03 PM bmgd...@gmx.de  wrote:
>
> Thanks! It works now! Great! I connected WP and HOLD to 3.3V.
>
> One more question: Is it possible to dump the OTP with flashrom also?
>
> best regards
>
> Daniel
>
>
> Am 19.08.2020 um 19:26 schrieb Mike Banon:
> > Based on your description, this seems to be a connection problem. What
> > Bus Pirate you're using - v3 or v4 ? I have v4 and never had to modify
> > any flashrom source files. If you clone the latest flashrom sources
> > and build them, they should work for you without any modifications.
> > How did you connect the cables? As you could see from this manual
> > http://dangerousprototypes.com/docs/Flashing_a_BIOS_chip_with_Bus_Pirate#1P_to_3P_adapter
> > , it's advised to connect not just VCC but also WP and HOLD, - to a
> > single 3.3v pin, because a Bus Pirate only has one.
> >
> > On Wed, Aug 19, 2020 at 8:15 PM bmgd...@gmx.de  wrote:
> >> Hi Mike,
> >>
> >> thanks for helping. I have taken a step forward. First problem was using
> >> bus pirate in virtual box (with linux ubuntu). After that i installed
> >> ubuntu on my computer as second operating system. Then flashrom reads
> >> the mx25l3255e chip.
> >>
> >> But there is a second issue. I get only 00's. I sent you the dump file,
> >> log file and the config files which i used. I implanted the chip there.
> >>
> >> Do you see a mistake in the config files or do you see a problem in the
> >> log file?
> >>
> >>
> >> Best regards
> >>
> >> Daniel
> >>
> >>
> >>
> >> Am 18.08.2020 um 12:29 schrieb Mike Banon:
> >>> How long have you waited? Depending on a firmware installed, Bus
> >>> Pirate may be a little slow: check the Bus Pirate Community Firmware
> >>> project for the firmware updates. Also, try running this with a higher
> >>> verbosity, i.e. -VV or -VVV or even more V - that could give you some
> >>> hints. Also please make sure that your connectivity is good enough
> >>>
> >>> On Sun, Aug 16, 2020 at 11:23 PM bmgd...@gmx.de  wrote:
> >>>> Hi flashrom team,
> >>>>
> >>>> i try to read the mx25l3255e 
> >>>> (https://media.digikey.com/pdf/Data%20Sheets/Macronix/MX25L3255E.pdf) 
> >>>> chip. But it don't work. I have tried to patch flashrom but output say:
> >>>>
> >>>> sudo ./flashrom -f -p buspirate_spi:dev=/dev/ttyUSB0,spispeed=115 -V -r 
> >>>> test_mx25l3255e.bin -c MX25L3255E
> >>>>
> >>>> flashrom unknown on Linux 5.4.0-42-generic (x86_64)
> >>>> flashrom is free software, get the source code at https://flashrom.org
> >>>>
> >>>> flashrom was built with libpci 3.6.4, GCC 9.3.0, little endian
> >>>> Command line (8 args): ./flashrom -f -p 
> >>>> buspirate_spi:dev=/dev/ttyUSB0,spispeed=115 -V -r test_mx25l3255e.bin -c 
> >>>> MX25L3255E
> >>>> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> >>>> Initializing buspirate_spi programmer
> >>>> Invalid SPI speed, using default.
> >>>> Detected Bus Pirate hardware 3.5
> >>>> Detected Bus Pirate firmware 7.0
> >>>> Using SPI command set v2.
> >>>> SPI speed is 8MHz
> >>>> Bus Pirate v3 or newer detected. Set serial speed to 2M baud.
> >>>> Serial speed is 200 baud
> >>>> Raw bitbang mode version 1
> >>>> Raw SPI mode version 1
> >>>> The following protocols are supported: SPI.
> >>>> Probing for Macronix MX25L3255E, 4096 kB: probe_spi_rdid_generic: id1 
> >>>> 0xc2, id2 0x9e16
> >>>> Found Macronix flash chip "MX25L3255E" (4096 kB, SPI) on buspirate_spi.
> >>>> Chip security register: 0x80
> >>>>   WPSEL is ON
> >>>> Chip status register is 0x7c.
> >>>> Chip status register: Status Register Write Disable (SRWD, SRP, ...) is 
> >>>> not set
> >>>> Chip status register: Bit 6 is set
> >>>> Chip status register: Blo

[flashrom] Re: flashrom mx25l3255e

[Mike Banon]

Based on your description, this seems to be a connection problem. What
Bus Pirate you're using - v3 or v4 ? I have v4 and never had to modify
any flashrom source files. If you clone the latest flashrom sources
and build them, they should work for you without any modifications.
How did you connect the cables? As you could see from this manual
http://dangerousprototypes.com/docs/Flashing_a_BIOS_chip_with_Bus_Pirate#1P_to_3P_adapter
, it's advised to connect not just VCC but also WP and HOLD, - to a
single 3.3v pin, because a Bus Pirate only has one.

On Wed, Aug 19, 2020 at 8:15 PM bmgd...@gmx.de  wrote:
>
> Hi Mike,
>
> thanks for helping. I have taken a step forward. First problem was using
> bus pirate in virtual box (with linux ubuntu). After that i installed
> ubuntu on my computer as second operating system. Then flashrom reads
> the mx25l3255e chip.
>
> But there is a second issue. I get only 00's. I sent you the dump file,
> log file and the config files which i used. I implanted the chip there.
>
> Do you see a mistake in the config files or do you see a problem in the
> log file?
>
>
> Best regards
>
> Daniel
>
>
>
> Am 18.08.2020 um 12:29 schrieb Mike Banon:
> > How long have you waited? Depending on a firmware installed, Bus
> > Pirate may be a little slow: check the Bus Pirate Community Firmware
> > project for the firmware updates. Also, try running this with a higher
> > verbosity, i.e. -VV or -VVV or even more V - that could give you some
> > hints. Also please make sure that your connectivity is good enough
> >
> > On Sun, Aug 16, 2020 at 11:23 PM bmgd...@gmx.de  wrote:
> >> Hi flashrom team,
> >>
> >> i try to read the mx25l3255e 
> >> (https://media.digikey.com/pdf/Data%20Sheets/Macronix/MX25L3255E.pdf) 
> >> chip. But it don't work. I have tried to patch flashrom but output say:
> >>
> >> sudo ./flashrom -f -p buspirate_spi:dev=/dev/ttyUSB0,spispeed=115 -V -r 
> >> test_mx25l3255e.bin -c MX25L3255E
> >>
> >> flashrom unknown on Linux 5.4.0-42-generic (x86_64)
> >> flashrom is free software, get the source code at https://flashrom.org
> >>
> >> flashrom was built with libpci 3.6.4, GCC 9.3.0, little endian
> >> Command line (8 args): ./flashrom -f -p 
> >> buspirate_spi:dev=/dev/ttyUSB0,spispeed=115 -V -r test_mx25l3255e.bin -c 
> >> MX25L3255E
> >> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> >> Initializing buspirate_spi programmer
> >> Invalid SPI speed, using default.
> >> Detected Bus Pirate hardware 3.5
> >> Detected Bus Pirate firmware 7.0
> >> Using SPI command set v2.
> >> SPI speed is 8MHz
> >> Bus Pirate v3 or newer detected. Set serial speed to 2M baud.
> >> Serial speed is 200 baud
> >> Raw bitbang mode version 1
> >> Raw SPI mode version 1
> >> The following protocols are supported: SPI.
> >> Probing for Macronix MX25L3255E, 4096 kB: probe_spi_rdid_generic: id1 
> >> 0xc2, id2 0x9e16
> >> Found Macronix flash chip "MX25L3255E" (4096 kB, SPI) on buspirate_spi.
> >> Chip security register: 0x80
> >>  WPSEL is ON
> >> Chip status register is 0x7c.
> >> Chip status register: Status Register Write Disable (SRWD, SRP, ...) is 
> >> not set
> >> Chip status register: Bit 6 is set
> >> Chip status register: Block Protect 3 (BP3) is set
> >> Chip status register: Block Protect 2 (BP2) is set
> >> Chip status register: Block Protect 1 (BP1) is set
> >> Chip status register: Block Protect 0 (BP0) is set
> >> Chip status register: Write Enable Latch (WEL) is not set
> >> Chip status register: Write In Progress (WIP/BUSY) is not set
> >> This chip may contain one-time programmable memory. flashrom cannot read
> >> and may never be able to write it, hence it may not be able to completely
> >> clone the contents of this chip (see man page for details).
> >> ===
> >> This flash part has status UNTESTED 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.
&g

[flashrom] Re: Spansion S25FL127S with 16 MB

[Mike Banon]

What flashrom version are you using? Maybe yours is outdated? Try
building it from the source

On Wed, Aug 12, 2020 at 10:35 AM ruckzuck--- via flashrom
 wrote:
>
> Hallo,
>
> If i make Flashrom -L i see in the List only listet :
>
> Spansion  S25FL127S-64kB PREW  16384  SPI
> Spansion  S25FL127S-256kB 16384  SPI
>
> But not Spansion  S25FL127S-128kB  for me that lock so that it is not 
> supported
> Need Flashrom a update for the chip ? i think yes.
>
> best reguards
> zuck
>
>
>
>
> --
> Sicher gesendet mit Tutanota. Hol dir deine eigene verschlüsselte & 
> werbefreie Mailbox:
> https://tutanota.com
>
>
> 7. Juli 2020, 18:38 von ruckz...@tuta.io:
>
> allo,
>
> In the End of the Program is written that i send you this:
>
>
> I try to flash the S25FL127S with 16 MB but in the list is it not
>
> then i try with S25FL127S-256kB and this happen:
>
> flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1000 -w out.bin -c 
> S25FL127S-256kB
> flashrom  on Linux 4.19.118+ (armv6l)
> flashrom is free software, get the source code at https://flashrom.org
>
> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> Found Spansion flash chip "S25FL127S-256kB" (16384 kB, SPI) on linux_spi.
> ===
> This flash part has status UNTESTED 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!
> Reading old flash chip contents... done.
> Erasing and writing flash chip... spi_nbyte_program called for too long a 
> write
> Reading current flash chip contents... done. Looking for another erase 
> function.
> spi_nbyte_program called for too long a write
> Reading current flash chip contents... done. Looking for another erase 
> function.
> spi_nbyte_program called for too long a write
> Reading current flash chip contents... done. Looking for another erase 
> function.
> Looking for another erase function.
> Looking for another erase function.
> No usable erase functions left.
> FAILED!
> Uh oh. Erase/write failed. Checking if anything has changed.
> Reading current flash chip contents... done.
> Good, writing to the flash chip apparently didn't do anything.
> Please check the connections (especially those to write protection pins) 
> between
> the programmer and the flash chip. If you think the error is caused by 
> flashrom
> please report this on IRC at chat.freenode.net (channel #flashrom) or
> mail flashrom@flashrom.org, thanks!
>
> Need Flashrom a update for the chip ?
>
> best reguards
>
> zuck
>
>
>
> --
> Sicher gesendet mit Tutanota. Hol dir deine eigene verschlüsselte & 
> werbefreie Mailbox:
> https://tutanota.com
>
>
> ___
> 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: (no subject)

[Mike Banon]

Check your connectivity, if the wires are good enough. Maybe the
connection is poor

On Mon, Aug 17, 2020 at 10:01 AM Buhrow, Simon
 wrote:
>
> Hi,
>
>
>
> could you send the whole output?
>
> Use –VVV and/or –o  and post the output here.
>
>
>
> Regards,
>
> Simon
>
>
>
> Von: Gjglesias 
> Gesendet: Donnerstag, 13. August 2020 20:07
> An: flashrom@flashrom.org
> Betreff: [flashrom] (no subject)
>
>
>
> When i try to flash bios using arduino uno,i get this "Found Generic flash 
> chip "unknown SPI chip (RDID)" (0 kb,SPI) on serprog. I use windbond w25Q32 
> chip. How i fix this?
>
> ___
> 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: flashrom mx25l3255e

[Mike Banon]

How long have you waited? Depending on a firmware installed, Bus
Pirate may be a little slow: check the Bus Pirate Community Firmware
project for the firmware updates. Also, try running this with a higher
verbosity, i.e. -VV or -VVV or even more V - that could give you some
hints. Also please make sure that your connectivity is good enough

On Sun, Aug 16, 2020 at 11:23 PM bmgd...@gmx.de  wrote:
>
> Hi flashrom team,
>
> i try to read the mx25l3255e 
> (https://media.digikey.com/pdf/Data%20Sheets/Macronix/MX25L3255E.pdf) chip. 
> But it don't work. I have tried to patch flashrom but output say:
>
> sudo ./flashrom -f -p buspirate_spi:dev=/dev/ttyUSB0,spispeed=115 -V -r 
> test_mx25l3255e.bin -c MX25L3255E
>
> flashrom unknown on Linux 5.4.0-42-generic (x86_64)
> flashrom is free software, get the source code at https://flashrom.org
>
> flashrom was built with libpci 3.6.4, GCC 9.3.0, little endian
> Command line (8 args): ./flashrom -f -p 
> buspirate_spi:dev=/dev/ttyUSB0,spispeed=115 -V -r test_mx25l3255e.bin -c 
> MX25L3255E
> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> Initializing buspirate_spi programmer
> Invalid SPI speed, using default.
> Detected Bus Pirate hardware 3.5
> Detected Bus Pirate firmware 7.0
> Using SPI command set v2.
> SPI speed is 8MHz
> Bus Pirate v3 or newer detected. Set serial speed to 2M baud.
> Serial speed is 200 baud
> Raw bitbang mode version 1
> Raw SPI mode version 1
> The following protocols are supported: SPI.
> Probing for Macronix MX25L3255E, 4096 kB: probe_spi_rdid_generic: id1 0xc2, 
> id2 0x9e16
> Found Macronix flash chip "MX25L3255E" (4096 kB, SPI) on buspirate_spi.
> Chip security register: 0x80
> WPSEL is ON
> Chip status register is 0x7c.
> Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not 
> set
> Chip status register: Bit 6 is set
> Chip status register: Block Protect 3 (BP3) is set
> Chip status register: Block Protect 2 (BP2) is set
> Chip status register: Block Protect 1 (BP1) is set
> Chip status register: Block Protect 0 (BP0) is set
> Chip status register: Write Enable Latch (WEL) is not set
> Chip status register: Write In Progress (WIP/BUSY) is not set
> This chip may contain one-time programmable memory. flashrom cannot read
> and may never be able to write it, hence it may not be able to completely
> clone the contents of this chip (see man page for details).
> ===
> This flash part has status UNTESTED 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!
> Some block protection in effect, disabling... Block protection could not be 
> disabled!
> Chip security register: 0x80
> WPSEL is ON
> Chip status register is 0x7c.
> Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not 
> set
> Chip status register: Bit 6 is set
> Chip status register: Block Protect 3 (BP3) is set
> Chip status register: Block Protect 2 (BP2) is set
> Chip status register: Block Protect 1 (BP1) is set
> Chip status register: Block Protect 0 (BP0) is set
> Chip status register: Write Enable Latch (WEL) is not set
> Chip status register: Write In Progress (WIP/BUSY) is not set
> Reading flash...
>
> But then nothing happens. Can you help? That would be great!
>
>
> Best regards
>
> Daniel
>
> ___
> 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: Ch341 issues

[Mike Banon]

Check if the connectivity is good enough and provide some logs please.

On Sun, Aug 16, 2020 at 11:23 PM Tanka Chin  wrote:
>
> Hi
> I'm trying to flash a bios chip W25Q64FV. I have ch341
> The program emptied, and blank but won't write new bios
> Can you assist?
>
> ___
> 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: Error flashrom BIOS macronix

[Mike Banon]

Check the quality of cables, reduce their length if possible, and try again

On Fri, Jun 12, 2020 at 10:36 AM Julián Carrizo  wrote:
>
> juluciano@juluciano-System-Product-Name:~$ sudo flashrom --programmer 
> ch341a_spi -E
> flashrom v1.2 on Linux 5.4.0-37-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 Macronix flash chip "MX25L8005/MX25L8006E/MX25L8008E/MX25V8005" (1024 
> kB, SPI) on ch341a_spi.
> Erasing and writing flash chip... FAILED at 0x! Expected=0xff, 
> Found=0x02, failed byte count from 0x-0x0fff: 0xfdf
> ERASE FAILED!
> Looking for another erase function.
> FAILED at 0x! Expected=0xff, Found=0x02, failed byte count from 
> 0x-0x: 0xfe83
> ERASE FAILED!
> Looking for another erase function.
> FAILED at 0x! Expected=0xff, Found=0x02, failed byte count from 
> 0x-0x: 0xfe83
> ERASE FAILED!
> Looking for another erase function.
> FAILED at 0x! Expected=0xff, Found=0x02, failed byte count from 
> 0x-0x000f: 0xd658b
> ERASE FAILED!
> Looking for another erase function.
> FAILED at 0x! Expected=0xff, Found=0x02, failed byte count from 
> 0x-0x000f: 0xd658b
> 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: Do you have support for W25Q128FW and W25Q256.W?

[Mike Banon]

Dear Shekar,

I hope that Dave and Amin (and other concerned people subscribed to a
flashrom mailing list) will test the W25Q128FW and W25Q256.W parts as soon
as possible and tell the results. Huge benefit of flashrom is that it is
100% open source (so much less likely to suffer from bad code quality and
security issues), and flashrom supports the inexpensive programmers like
CH341A which costs just $2. The commercial programmers are often expensive
and have a proprietary closed source software, which is usually bloated,
may have the security holes (sometimes the deliberate backdoors) and often
are supported only by Windows OS, so they aren't an option for many people.
Our goal is to ensure the flashrom's good function in as many use cases and
for as many parts as possible - and hope that together, with your kind
help, we will achieve it.

Best regards,
Mike Banon

On Thu, May 28, 2020 at 4:27 AM kcshe...@winbond.com 
wrote:

> Hi Dave and Amin,
>
>
>
> Just following up to ensure this programming issue was resolved at your
> end. Since the newer parts are supported on most commercial programmers and
> we did not hear back from you, we thought you have been able to program the
> parts successfully and have been able to use these parts on the AMD board.
> These parts are already supported on the AMD reference boards with Renoir.
> Thanks.
>
>
>
> Regards,
>
> Shekar
>
>
>
> *From:* US00 Krishna Shekar
> *Sent:* Friday, May 8, 2020 1:33 PM
> *To:* Mike Banon 
> *Cc:* US40 Jack Lee ; SM10 YLLi5 ;
> Wu, Amin ; flashrom@flashrom.org; David Hendricks <
> david.hendri...@gmail.com>
> *Subject:* RE: [flashrom] Re: Do you have support for W25Q128FW and
> W25Q256.W?
>
>
>
> Copying Dave Hendricks.
>
>
>
> *From:* US00 Krishna Shekar
> *Sent:* Friday, May 8, 2020 1:31 PM
> *To:* Mike Banon 
> *Cc:* US40 Jack Lee ; SM10 YLLi5 ;
> Wu, Amin ; flashrom@flashrom.org
> *Subject:* RE: [flashrom] Re: Do you have support for W25Q128FW and
> W25Q256.W?
>
>
>
> Resending this message with datasheet links below
>
>
>
>
> https://www.winbond.com/resource-files/W25Q256JW%20SPI%20RevG%2011252019%20Plus.pdf
>
> https://www.winbond.com/resource-files/W25Q128JW_RevD_03132020%20Plus.pdf
>
>
>
> *From:* US00 Krishna Shekar
> *Sent:* Thursday, May 7, 2020 12:14 PM
> *To:* Mike Banon 
> *Cc:* US40 Jack Lee ; SM10 YLLi5 ;
> Wu, Amin ; flashrom@flashrom.org
> *Subject:* RE: [flashrom] Re: Do you have support for W25Q128FW and
> W25Q256.W?
>
>
>
> W25Q128FW and W25Q256FW are older products and have been replaced by the
> latest W25Q128JW and W25Q256JW serial flash products. These newer
> datasheets are publicly available on the Winbond web site www.winbond.com.
> Please see these datasheets attached. Thanks.
>
>
>
> Regards,
>
> Shekar
>
>
>
> *From:* Mike Banon [mailto:mikeb...@gmail.com ]
> *Sent:* Thursday, May 7, 2020 12:01 PM
> *To:* US00 Krishna Shekar 
> *Cc:* US40 Jack Lee ; SM10 YLLi5 ;
> Wu, Amin ; flashrom@flashrom.org
> *Subject:* Re: [flashrom] Re: Do you have support for W25Q128FW and
> W25Q256.W?
>
>
>
> flashrom is really preferable: it's the open source (important!) software
> that supports a lot of programmers, including the inexpensive ones like
> CH341A which costs just $2. To add a support for W25Q128FW and W25Q256FW to
> flashrom - hopefully would be enough to create the correct chip definitions
> in flashchips.c / flashchips.h files using the datasheets for W25Q128FW and
> W25Q256FW. If these datasheets aren't publicly available yet, please
> provide them.
>
>
>
> On Thu, May 7, 2020 at 4:23 PM kcshe...@winbond.com 
> wrote:
>
> Hi Everyone,
>
>
>
> The latest part numbers I would recommend your using are W25Q128JWSSIQ or
> W25Q128JWEIQ (128Mb serial flash) and W25Q256JWEIQ (256Mb serial flash) on
> your designs. The part numbers mentioned below are old parts and the part
> numbers are incomplete. The part numbers I have mentioned are supported on
> the AMD Renoir reference boards, and in turn supports all the CPUs that AMD
> offers today. If you have further questions about support for AMD products,
> please contact Jason Hawken at AMD, Toronto.
>
>
>
> I am not sure if these are supported on Raspberry. Please take a look at
> the link below to look at the support provided by several programmer
> vendors for Winbond flash parts.
>
>
>
>
> https://www.winbond.com/resource-files/AN012%20CodeStorageMemoryProgrammingSupport%20Guide%20v4.2%2002282020.pdf
>
>
>
> I would recommend using Dediprog programmers - You are likely to find good
> support on Dediprog programmers for Winbond parts.
>
>
>
> If you already have the

[flashrom] Re: Flashrom verification failed

[Mike Banon]

1) Use a modern flashrom version by building it from source. Instead
of the ancient 0.9 which you perhaps got from your distro repository.
2) If that's ISP flashing, try using the shorter/thicker wires and
better quality wires (copper instead of aluminium) to reduce the
electrical resistance which might've affected your results
3) Please use some online text/image hosting that gives a direct link,
the next time

On Thu, May 14, 2020 at 1:57 PM Sam Armstrong  wrote:
>
> https://www.sendspace.com/file/6095av
>
> Can you please check and let me know the remediation? Thanks.
>
> -Sam
> ___
> 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: Do you have support for W25Q128FW and W25Q256.W?

[Mike Banon]

 flashrom is really preferable: it's the open source (important!) software
that supports a lot of programmers, including the inexpensive ones like
CH341A which costs just $2. To add a support for W25Q128FW and W25Q256FW to
flashrom - hopefully would be enough to create the correct chip definitions
in flashchips.c / flashchips.h files using the datasheets for W25Q128FW and
W25Q256FW. If these datasheets aren't publicly available yet, please
provide them.

On Thu, May 7, 2020 at 4:23 PM kcshe...@winbond.com 
wrote:

> Hi Everyone,
>
>
>
> The latest part numbers I would recommend your using are W25Q128JWSSIQ or
> W25Q128JWEIQ (128Mb serial flash) and W25Q256JWEIQ (256Mb serial flash) on
> your designs. The part numbers mentioned below are old parts and the part
> numbers are incomplete. The part numbers I have mentioned are supported on
> the AMD Renoir reference boards, and in turn supports all the CPUs that AMD
> offers today. If you have further questions about support for AMD products,
> please contact Jason Hawken at AMD, Toronto.
>
>
>
> I am not sure if these are supported on Raspberry. Please take a look at
> the link below to look at the support provided by several programmer
> vendors for Winbond flash parts.
>
>
>
>
> https://www.winbond.com/resource-files/AN012%20CodeStorageMemoryProgrammingSupport%20Guide%20v4.2%2002282020.pdf
>
>
>
> I would recommend using Dediprog programmers - You are likely to find good
> support on Dediprog programmers for Winbond parts.
>
>
>
> If you already have the W25Q128FW and W25Q256FW parts with you now, they
> are supported on the Dediprog programmers as well. Trust this information
> is helpful. Let us know if you need any further help. Thanks.
>
>
>
> Regards,
>
> Shekar
>
>
>
> *From:* US40 Jack Lee
> *Sent:* Wednesday, May 6, 2020 7:42 PM
> *To:* SM10 YLLi5 ; Wu, Amin ; US00
> Krishna Shekar 
> *Cc:* David Hendricks ; flashrom@flashrom.org
> *Subject:* Re: [flashrom] Do you have support for W25Q128FW and W25Q256.W?
>
>
>
> Hi Shekar,
>
>
>
> Please help and feedback.
>
>
>
> Thx.
>
>
>
> Jack
> --
>
> *From:* SM10 YLLi5 
> *Sent:* Wednesday, May 6, 2020 7:40 PM
> *To:* Wu, Amin; US40 Jack Lee
> *Cc:* David Hendricks; flashrom@flashrom.org
> *Subject:* FW: [flashrom] Do you have support for W25Q128FW and W25Q256.W?
>
>
>
> Hi Jack,
>
>
>
> Here we have the question below. do you mind to answer for this? Thanks.
>
>
>
> Do you have a plan to support flash bios for W25Q128FW and W25Q256.W via
> flashrom in Raspberry?
>
>
>
>
>
> Regards,
>
> Yulia
>
> *From:* Wu, Amin [mailto:amin...@amd.com ]
> *Sent:* Thursday, May 07, 2020 10:38 AM
> *To:* SM10 YLLi5; David Hendricks
> *Cc:* flashrom@flashrom.org
> *Subject:* RE: [flashrom] Do you have support for W25Q128FW and W25Q256.W?
>
>
>
> [AMD Official Use Only - Internal Distribution Only]
>
>
>
> Thanks David.
>
> I tried flashrom1.2 , W25Q128FW and W25Q256.W are not in the support list.
>
> I want use Raspberry only to flash W25Q128FW and W25Q256.W.
>
>
>
> Hi Yulia,
>
> Can you add W25Q128FW and W25Q256.W to flashrom support list to use
> Raspberry only? Thanks for your responding.
>
>
>
>
>
>
>
>
>
> BR
>
> AMIN
>
> *From:* Yulia Li 
> *Sent:* Thursday, May 7, 2020 10:22 AM
> *To:* David Hendricks ; Wu, Amin <
> amin...@amd.com>
> *Cc:* flashrom@flashrom.org
> *Subject:* RE: [flashrom] Do you have support for W25Q128FW and W25Q256.W?
>
>
>
> [CAUTION: External Email]
>
> Hi Amin,
>
>
>
> Sorry for the late reply, do you still need any other support?
>
> Thanks.
>
>
>
>
>
> Regards,
>
> Yulia
>
>
>
> *From:* David Hendricks [mailto:david.hendri...@gmail.com
> ]
> *Sent:* Saturday, April 25, 2020 12:02 PM
> *To:* Wu, Amin
> *Cc:* AP A0PH mkt_online; flashrom@flashrom.org
> *Subject:* Re: [flashrom] Do you have support for W25Q128FW and W25Q256.W?
>
>
>
> Hi Amin,
>
> Please note that the W25Q128FW is a 1.8V chip, while Raspberry PI IOs are
> 3.3V.
>
>
>
> For Dediprog, pass in the `voltage` parameter, e.g. `flashrom -p
> dediprog:voltage=1.8 -r foo.bin`
>
>
>
> Also, as Mike mentioned it will help if we know the version of flashrom
> which you are trying to use. Some distributions provide very old versions.
>
>
>
> On Wed, Apr 22, 2020 at 1:33 AM Wu, Amin  wrote:
>
> [AMD Official Use Only - Internal Distribution Only]
>
>
>
> Hi David Hendricks,
>
> “No EEPROM/flash device found” pop after I added below code to
> flashchips.c and flashchips.h to install flashrom in Raspberry 4B.
>
> pi@raspberrypi:~ $ sudo flashrom -p
> linux_spi:dev=/dev/spidev0.0,spispeed=4096
>
> flashrom  on Linux 4.19.57-v7l+ (armv7l)
>
> flashrom is free software, get the source code at https://flashrom.org
> 
>
>
>
> Using clock_gettime for delay loops 

[flashrom] Re: Do you have support for W25Q128FW and W25Q256.W?

[Mike Banon]

What version of a flashrom are you trying to use? Ideally, you need to
clone the latest flashrom sources, then build them according to the
instructions from a flashrom's wiki. That's because the flashrom versions,
which could be found as a prebuilt package at various repositories, could
be really outdated and lack a support for some important chips.
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Flash chip is in an unknown state

[Mike Banon]

On Fri, Apr 17, 2020 at 2:33 PM Joao Gabriel Moura de Almeida
 wrote:
>
> Hi all,
>
> Hope you are doing well. I am having some trouble flashing a W25Q64.V and was 
> hoping someone could help me. I am using a CH341a with a SOIC8 clip, and was 
> able to flash that chip beforehand successfully.
>
> The motherboard is an MSI P67a-C43 B3, I am trying to flash to the 1.J 
> Version which can be downloaded here: 
> https://www.msi.com/Motherboard/support/p67ac43_b3
>
> I have pasted my logs from running "flashrom --programmer ch341a_spi -w 
> E7673IMS.1J0 -V" here:
>
> https://paste.flashrom.org/view.php?id=3305
>
> Let me know if I can provide any more information.
>
> Thank you,
>
> Joao
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org

What's the length of cables between CH341A and SOIC8 test clip, and
from what material are they made? (copper has ~1.5x less electrical
resistance than aluminium, so more likely to work). Ideally, <=10 cm
of copper wires. If everything else fails, you could try my "gingerly"
patch, however I didn't rebase it on a flashrom master for quite long.
https://review.coreboot.org/c/flashrom/+/31830
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: will SPI flash GD25LB128D (GD25LB128DSIG) be soon supported?

[Mike Banon]

On Fri, Apr 17, 2020 at 2:31 PM Stefan Priehse  wrote:
>
> This is the bios chip on ASUS ROG STRIX B450-F GAMING mainboard.
>
> This should be the data sheet of this family of SPI flash chips.
> https://www.gigadevice.com/flash-memory/gd25lb128d/
>
> I tried to connect it to a raspberry pi-4 with SOIC test clip and 1,8v power 
> supply and logic-level converter,
> but flashrom v0.9.9-r1954 on Linux 4.19.105-v8-28 (aarch64)
> only found:
> flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1000
> "...
> Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI) on linux_spi.
> Probing for Generic unknown SPI chip (REMS), 0 kB: REMS returned 0xc0 0x01. 
> probe_spi_rems: id1 0xc0, id2 0x1
> Found Generic flash chip "unknown SPI chip (RDID)" (0 kB, SPI).
> ===
> This flash part has status NOT WORKING for operations: PROBE READ ERASE WRITE
> ..."
>
> I saw in newest version 
> https://github.com/flashrom/flashrom/blob/master/flashchips.h
> this chip is still not listed. So probably also not supported in newest 
> development version.
>
>
> regards
> s.priehse
> ___
> flashrom mailing list -- flashrom@flashrom.org
> To unsubscribe send an email to flashrom-le...@flashrom.org

You could try adding its' definitions to flashchips.c / flashchips.h ,
using the definitions or other GigaDevice chips as the base and
datasheet if available. Hopefully this would be more simple than it
seems for you. Then you could submit a working patch.

Best regards,
Mike Banon
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: CH341 verifying fail under Linux

[Mike Banon]

Are you using any test clip - and, if yes, have you tried using the
shorter wires? There may be also a problem of a chip or a programmer
(it'd be helpful if you had a spare CH341A or a different
flashrom-supported programmer, to see if its' a hardware issue)
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Flashrom report

[Mike Banon]

On Thu, Jan 23, 2020 at 3:46 PM Dennis Dale-Green
 wrote:
>
> Does the 1.8v adapter board drop into the usb boards chip holder?
>

Depends on what adapter you're talking about. Those I've seen on
AliExpress and sometimes are being sold together with CH341A as a
bundle, seem to be compatible, but as I've never encountered any 1.8v
parts I didn't have a chance to try yet. Don't throw away a chip yet,
maybe it's still alive.
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Flashrom report

[Mike Banon]

On Wed, Jan 22, 2020 at 8:46 PM Dennis Dale-Green
 wrote:
>
> The BIOS I'm trying to flash is for a Gigabyte Brix mini PC.  I originally 
> tried flashing with the surface mounted chip in place using windows software 
> but the flash failed to verify the data so would not compete the operation.  
> I unsoldered the chip and tried again with the same failed result. I thought 
> perhaps the chip was broken so I bought a new one and tried programming it 
> again through windows.  This also failed.
>
> So I thought I'd try Flashing using Linux, both the old and new chip failed 
> with the result shown in my original email.
>
> I'll solder the chip onto the programmer's piggyback board and give that a 
> try (got nothing to loose!) that will bypass any test clip issue.
>
> On Wed, 22 Jan 2020 at 15:04, Mike Banon  wrote:
>>
>> On Wed, Jan 22, 2020 at 2:07 PM Dennis  wrote:
>> >
>> > Hi. Please see the report below.  I've tried flashing 2 eproms but get the
>> > same result. Any ideas? Thanks, Dennis
>> >
>> > Calibrating delay loop... OK.
>> > Found Macronix flash chip "MX25U6435E/F" (8192 kB, SPI) on ch341a_spi.
>> > Reading old flash chip contents... done.
>> > Erasing and writing flash chip... Erase/write done.
>> > Verifying flash... FAILED at 0x0010! Expected=0x5a, Found=0x5b,
>> > failed byte count from 0x-0x007f: 0x332be2
>> > 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!
>>
>> Please describe your flashing setup. Are you trying the ISP (in-system
>> programming) using a SOIC clip? Maybe the wires between ch341a and
>> this test clip are too long or poor quality (have a high resistance,
>> i.e. aluminium has 1.5x higher resistance than copper)
>

Yes, flashing using Linux is preferable. Some faulty CH341A are giving
5V instead of 3.3V, please test yours with a multimeter. Have you ever
successfully flashed any chip with your CH341A? By the way I've
stumbled upon two CH341A (two posts on reddit's r/coreboot), one
CH341A had a badly soldered chip leg and another was missing a
capacitor. Easy to fix, but only if you have at least one working
CH341A to compare i.e. the voltages at various points of a faulty vs
working one.
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Flashrom report

[Mike Banon]

On Wed, Jan 22, 2020 at 2:07 PM Dennis  wrote:
>
> Hi. Please see the report below.  I've tried flashing 2 eproms but get the
> same result. Any ideas? Thanks, Dennis
>
> Calibrating delay loop... OK.
> Found Macronix flash chip "MX25U6435E/F" (8192 kB, SPI) on ch341a_spi.
> Reading old flash chip contents... done.
> Erasing and writing flash chip... Erase/write done.
> Verifying flash... FAILED at 0x0010! Expected=0x5a, Found=0x5b,
> failed byte count from 0x-0x007f: 0x332be2
> 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!

Please describe your flashing setup. Are you trying the ISP (in-system
programming) using a SOIC clip? Maybe the wires between ch341a and
this test clip are too long or poor quality (have a high resistance,
i.e. aluminium has 1.5x higher resistance than copper)
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: In a bind

[Mike Banon]

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.

[flashrom] Re: In a bind

[Mike Banon]

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

[Mike Banon]

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

[Mike Banon]

> 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: Flashrom for Windows 10

[Mike Banon]

If that's so difficult for you, please consider running flashrom from
installed Linux or at least from a Linux LiveCD/LiveUSB. With a couple
of commands you could get a flashrom from your distro's repository,
and with a few more commands ( "Downloads / Installation from source"
at the flashrom wiki) you'll clone and build the latest available
flashrom. It should take less than 5 minutes.

On Thu, Oct 31, 2019 at 9:20 PM  wrote:
>
> Could the flashrom or someone build releases? Because setting  up the mingw 
> environment is very difficult...
> ___
> 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: (no subject)

[Mike Banon]

First of all, you are using an old version of flashrom, which you
probably got from your Linux distro's repository. Please get the
latest one: clone the official flashrom repository, install the
dependencies listed at Downloads / Installation from source page at
flashrom wiki, and run "make" - it is really simple and fast.

T25S40 chip doesn't seem to be supported by flashrom, but you could
try force flashing it like another chip (would need some source code
modifications). Some people suggested that T25S40 is similar to N25S40
which is supported by flashrom, but I don't know if it's really so.

On Mon, Oct 28, 2019 at 4:33 PM Masud Samarin  wrote:
>
> hello dear flashrom :)
>
> i tried to probe a brand new "T25s40" chip.But I couldn't get the right 
> answer.
> what am i supposed to do? also send log file to you.
> thank in advance
>
> masmoog
> ___
> 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: Last resort?

[Mike Banon]

Based on the info from your post (especially "the touchpad and
keyboard don't work") it really seems that something is wrong with the
EC firmware, it may be corrupted. If my guess is correct, even if you
would manually reflash your BIOS chip, maybe using a SOIC8 test clip
together with some cheap flashrom-supported programmer like USB CH341A
(external hardware flashing method if the internal one doesn't work),
with a known good BIOS image - it wouldn't help you. However, if you'd
somehow succeed flashing using a vendor's BIOS updating utility, it
will update your EC firmware as well and the problem will be solved.

Here's how an embedded controller EC could be flashed using a flashrom
and flashrom-supported programmer like CH341A or Bus Pirate, through a
keyboard connector -
http://dangerousprototypes.com/docs/Flashing_KB9012_with_Bus_Pirate .
You need to check if your motherboard's EC is supported by flashrom,
i.e. KB9012 is supported. If your EC isn't supported, you would need
to either add its' support to flashrom, or get a proprietary
programmer that supports it. If my info is correct, your laptop has
IT8886HE EC. It doesn't seem to be supported by flashrom, but perhaps
such a support can be added: it seems that this IT* shares a similar
flashing algorithm to the older IT*.

On Tue, Oct 22, 2019 at 11:40 AM Russell Morgan
 wrote:
>
> Good morning,
>
> I'm thinking about using Flashrom as a last resort to fix my BIOS - it's for 
> a laptop which I know you say is absolutely a terrible idea, but this looks 
> like the only way I can flash a new BIOS without needing to reboot.
>
> Here's a long-winded explanation:
>
> I bought this laptop secondhand, a Lenovo V510-15ikb, knowing it didn't quite 
> work. But I didn't realise quite how perplexing it would be.
>
> First, the touchpad and keyboard don't work. The caps lock key lights up when 
> it turns on, but then as soon as the Lenovo logo appears, it turns off, and 
> the keyboard doesn't respond at all.
>
> So, using a usb keyboard and mouse, I formatted the laptop, and put a fresh 
> copy of Windows 10 on it. But then, when it went to restart, it just stopped 
> on the blue restart screen. Everything still worked, I could move the mouse, 
> and it looked like the hard drive was reading something, but four hours 
> later, still no restart. So, I use the power button to restart. This leads to 
> a series of problems, where the laptop won't consistently boot. But after a 
> few attempts, I can get into Windows.
>
> Now, from inside Windows, everything seems fine, the system loads quickly, 
> wifi connects. But when I run windows update, it freezes - the system works, 
> but update itself just freezes. When I run Lenovo system update, it stops at 
> 97%. Firefox won't load, but Chrome will.  And I can't restart the system.  
> Again, it gets to the blue restart screen, the mouse still moves, but it 
> never restarts.  I don't know for sure, but it seems like it can't 
> communicate with the motherboard correctly to actually restart.
>
> So, I boot into BIOS. There's a newer version available, and from the BIOS 
> itself, I can restart the system.  So I boot back into Windows, and run Win64 
> - from part of the Lenovo BIOS update .exe which is supposed to flash the 
> BIOS. But to do that, it needs to reboot the system, so it tries and it fails.
>
> So, in windows, I try to run Phoenix UEFI Winflash, which tells me "Please 
> select the correct BIOS image". I'm using bios.cap from 2WCN42WW from here: 
> https://pcsupport.lenovo.com/no/en/products/laptops-and-netbooks/lenovo-v-series-laptops/v510-15ikb/...
>
> So, I figure maybe I can do it from the command prompt, so I use the Windows 
> 10 USB stick and get to the command prompt, run win64.bat, and it still needs 
> to reboot. Which doesn't happen. I also try accessing UEFI from here, which 
> freezes the system.
>
> So, I figure maybe I can do it from FreeDOS. I make a FreeDOS boot USB, run 
> win64.bat and am told the software can't be run from DOS.
>
> So, I use the DOS version, phlash16, and I turn the .cap file into a .bin 
> using UEFITool, and phlash16 runs and looks like it's going to work... but 
> then I get the message, "platform signature not found in the interface."
>
> So, I figure maybe I can do it from Linux. I install Ubuntu using wubi, and 
> try to boot into it, but after a hefty amount of time on a black screen, I 
> get a bluescreen of death. I try to boot linux from USB, but same problem.
>
> I instead install Ubuntu to a USB, and can boot from it - but I see a large 
> list of ACPI errors.  I try to flash the bios using fwupdate, but it can't 
> seem to communicate with /dev/sda2 which is where my efi is supposedly.  
> Plus, I still can't reboot.
>
> So, I check event viewer from Windows to see what's happening when I'm 
> rebooting, and I get this error message:
>
> : The embedded controller (EC) did not respond within the specified timeout 
> period. This may indicate that there 

[flashrom] Re: Mac Pro Mojave with AMD RX580 need to fix ROM for boot screen.

[Mike Banon]

Dear Ray,

Sorry, but I am quite sure that you will not be able to successfully
flash a memory chip of your video card using the flashrom's Internal
flashing mode, especially on a Mac: even the internal flashing of its'
own BIOS chip is likely not supported (if a chipset isn't) and could
result in a (software) bricking. So, most likely you'll have to use
the external flashing adapter, like USB CH341A, which hopefully could
be connected to a memory chip of your video card using a test clip (to
avoid the soldering). Then, the command line will look like

sudo ./flashrom -p ch341a_spi -r dump.bin -V

And you could find an example of flashing setup here:
http://dangerousprototypes.com/docs/Flashing_a_BIOS_chip_with_Bus_Pirate#CH341A_flashing_coreboot_open_source_BIOS_to_Lenovo_G505S_hacking

I am sending a copy of this e-mail to a flashrom mailing list, just in
case someone would see a mistake in my message and would like to
clarify or add some useful info.

Best regards,
Mike

On Thu, Sep 5, 2019 at 10:39 PM Ray Nygren  wrote:
>
> Sorry for the misunderstanding.
> I have flashrom install on mac pro correctly.
> I am not flahing mac pro rom its the AMD RX580 Video card which has a mistake 
> in the ROM bios that
> need updated to make it compatable with Mac as the pre graphics screen is 
> blank
> I attached the link in the reques you replied to on the fix
> My question to forum is:
> 1. what is the arg to dump list of roms seen.
> 2. need to identify and dump rom from RX580 video card
> 3. edit 5 bytes and flash video card rom
>
> If you are not able to help please forward to anyone who can assist me.
> Thanks
>
> Sent: Monday, September 02, 2019 at 6:26 AM
> From: "Mike Banon" 
> To: rnyg...@mail.com, flashrom 
> Subject: Re: [flashrom] Mac Pro Mojave with AMD RX580 need to fix ROM for 
> boot screen.
> Are you trying the internal flashing mode? If a Mac Pro chipset is not
> supported by a flashrom, it wouldn't be successful.
> You might need the external flashing: get a hardware programmer like
> CH341A, find a ROM chip at RX 580 motherboard,
> try to connect CH341A to a chip using some test clip which is
> compatible with a chip (make sure this chip supports 3.3V
> since there are some flash chips that are 1.8V), and try. This is how
> I would have tried to do it.
>
> On Fri, Aug 30, 2019 at 9:45 PM  wrote:
> >
> > I found a link to correct the problem that many people have but no one has 
> > completed with flashrom on Mac they e 580 from Mac Pro then insert to PC to 
> > use flash program,
> > I would like to try to do all on MAC usin flash rom. I was able to complete 
> > install brew then flashrom but now am overwelmened by manual
> > here is the link with fix
> > https://forums.macrumors.com/threads/turn-a-new-sapphire-rx580-pulse-into-the-mac-edition-card.2101909/
> >
> > I need arguments to dump rx580 ROM to file
> > copy to backup
> > edit changes
> > save file
> > flash rx580 card
> >
> > What args should I use to dump to file and then flash
> > ___
> > 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: Mac Pro Mojave with AMD RX580 need to fix ROM for boot screen.

[Mike Banon]

Are you trying the internal flashing mode? If a Mac Pro chipset is not
supported by a flashrom, it wouldn't be successful.
You might need the external flashing: get a hardware programmer like
CH341A, find a ROM chip at RX 580 motherboard,
try to connect CH341A to a chip using some test clip which is
compatible with a chip (make sure this chip supports 3.3V
since there are some flash chips that are 1.8V), and try. This is how
I would have tried to do it.

On Fri, Aug 30, 2019 at 9:45 PM  wrote:
>
> I found a link to correct the problem that many people have but no one has 
> completed with flashrom on Mac they e 580 from Mac Pro then insert to PC to 
> use flash program,
> I would like to try to do all on MAC usin flash rom. I was able to complete 
> install brew then flashrom but now am overwelmened by manual
> here is the link with fix
> https://forums.macrumors.com/threads/turn-a-new-sapphire-rx580-pulse-into-the-mac-edition-card.2101909/
>
> I need arguments to dump rx580 ROM to file
> copy to backup
> edit changes
> save file
> flash rx580 card
>
> What args should I use to dump to file and then flash
> ___
> 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: lenovo c540

[Mike Banon]

You need to extract a clean BIOS ROM ( "clean" = without any
system-specific settings ) from a BIOS update utility. Try to open
this utility (called something like "winflash_3.00.exe") as an archive
with 7zip, and extract the contents of this .exe file using 7zip. If
successful, it would give you a set of files, one of which might
contain this clean BIOS ROM. Could be called something like
WinVALGC300.bin ( you could guess it by looking at the file sizes ).
Then open this file using a hexedit, search for $_IFLASH_BIOSIMG
header. Not directly after but slightly further after this header, at
the closest address ending by 0 (rounded by 0x10) there is a start of
BIOS section, the size of which should be equal to a size of your BIOS
chip. Copy-paste it into a new binary file, then you could try using
it (but only after making a backup of your current chip contents!).
You could also compare the contents of your original ROM image vs this
"clean" image, to get an idea where a password might be stored (could
be encoded instead of a plain text).

On Thu, Aug 15, 2019 at 4:27 PM Darko Svilkovic
 wrote:
>
> Hi,
>
> Yes flashed with a windows update tool,which automaticly updates,has no 
> download ...
>
> Any help which program tu use to download the bios ...
>
> Read somthing like there are 2 chips for bios (one for bios and the other for 
> password and settings) ...
>
> thx
>
> On Thu, Aug 15, 2019 at 2:28 PM Mike Banon  wrote:
>>
>> "I have flashed the bios to a new version" - how you did that, using a
>> windows tool provided by a laptop manufacturer? If yes, then it
>> preserves the originally set password and maybe the other settings.
>> Try to extract a "clean" BIOS image from the BIOS update utility
>> provided by a laptop manufacturer. Then, using a flashrom-supported
>> programmer like USB CH341A with a test clip (SOIC8 ?) together with
>> our flashrom opensource tool, you might be able to flash a clean BIOS
>> image (without any passwords/settings) into your BIOS chip. Of course
>> please make a backup before flashing a new image, in the case it's
>> incorrect or you'd need to borrow some Intel ME-related regions or to
>> have a MAC address specified in your ROM in order for onboard Ethernet
>> working.
>>
>> On Wed, Aug 7, 2019 at 12:01 PM Darko Svilkovic
>>  wrote:
>> >
>> > hi,
>> >
>> > Hawe a problem with lenovo c540 AIO,bought this from a second hand,and 
>> > didn't see,and he didn,t mention that there is a bios admin pass ...
>> >
>> > I have flashed the bios to a new wersion,taked out the cmos 
>> > battery,jumpered the cmos jumper but with no success ...
>> >
>> > Now i heard that the password is in eeprom ...
>> >
>> > How to remowe it ???
>> >
>> > thx
>> >
>> > Darko/Croatia
>> > ___
>> > 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: New SPI NOR Flash product Support

[Mike Banon]

Good day! flashrom source code is open, so you could check how the
support for already-supported-by-flashrom GigaDevice chips has been
added, and try to do something similar - following the Development
Guidelines from a flashrom wiki here :
https://www.flashrom.org/Development_Guidelines .

Best regards,
Mike Banon

On Tue, Jul 30, 2019 at 6:47 PM Vlim  wrote:
>
> Hi,
>
> I am the FAE manager for GigaDevice.
> We are a manufacturer for the SPI NOR Flash.
> I know that FlashRom is currently supporting our SPI NOR products.
> We have released many new products lately. Would like to know how can we add 
> these products to your support list.
>
>
> Regards,
>
> Victor Lim
>
> Sr. FAE Manager,
> GigaDevice America,
> 100 Century Center Ct, Ste 120,
> San Jose, CA 95112
>
> 4088833856
> www.gigadevice.com
>
>
>
> -Original Message-
> From: Stefan Tauner [mailto:stefan.tau...@alumni.tuwien.ac.at]
> Sent: Monday, May 9, 2016 11:50 PM
> To: Victor Lim 
> Cc: David Hendricks ; flashrom@flashrom.org; Katherine 
> (GigaDevice//US) 
> Subject: Re: [flashrom] New SPI NOR Flash product Support
>
> On Mon, 9 May 2016 20:46:18 -0700
> David Hendricks  wrote:
>
> > Hi Victor,
> > From Flashrom's software perspective all chips with the same ID are
> > indistinguishable.
> >
> > Part number often includes characteristics such as package and thermal
> > tolerance which do not affect software compatibility.
>
> However, we will add the new names to the in-program (and hence
> wiki) database so that this new information becomes public. Thanks for the 
> heads up, Victor.
>
> --
> Kind regards/Mit freundlichen Grüßen, Stefan Tauner
>
> ___
> 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: Problem with BIOS flashin.

[Mike Banon]

It's known that flashrom internal flashing may be working or not
working depending on a platform. For example, laptops EC controller
might interfere with the internal flashing attempt, causing it to
fail. Do you have a physical access to this server? If yes, could you
use some external flashrom-supported programmer, something like
CH341A, with a (SOIC8 ?) test clip to attach to a BIOS chip without
any soldering? Check these articles: https://www.flashrom.org/ISP ,
http://dangerousprototypes.com/docs/Flashing_a_BIOS_chip_with_Bus_Pirate
(last part of this article describes the process for CH341A)

On Sun, Aug 4, 2019 at 1:01 AM Michał Rączka-Dudek  wrote:
>
> Hi.
> Recently i have experienced problems with flashi bios in broken NAS server.
> Flahrom was able to detect the chip but couldn't do anything with it.
> Below is the output from the tool. Can you help me somehow or direct me the 
> way to find solutuon myself?
>
> Thanks!
>
> Found Winbond flash chip "W25Q64.W" (8192 kB, SPI).
> This chip may contain one-time programmable memory. flashrom cannot read
> and may never be able to write it, hence it may not be able to completely
> clone the contents of this chip (see man page for details).
> Erasing and writing flash chip... Trying erase function 0... 
> 0x00-0x000fff:EFAILED at 0x! Expected=0xff, Found=0x00, failed 
> byte count from 0x-0x0fff: 0x1000
> ERASE FAILED!
> Looking for another erase function.
> Trying erase function 1... 0x00-0x007fff:EFAILED at 0x! 
> Expected=0xff, Found=0x00, failed byte count from 0x-0x7fff: 
> 0x8000
> ERASE FAILED!
> Looking for another erase function.
> Trying erase function 2... 0x00-0x00:EFAILED at 0x! 
> Expected=0xff, Found=0x00, failed byte count from 0x-0x: 
> 0x1
> ERASE FAILED!
> Looking for another erase function.
> Trying erase function 3... 0x00-0x7f:EFAILED at 0x! 
> Expected=0xff, Found=0x00, failed byte count from 0x-0x007f: 
> 0x80
> ERASE FAILED!
> Looking for another erase function.
> Trying erase function 4... 0x00-0x7f:EFAILED at 0x! 
> Expected=0xff, Found=0x00, failed byte count from 0x-0x007f: 
> 0x80
> ERASE FAILED!
> Looking for another erase function.
> Trying erase function 5... not defined. 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!
>
>
>
> Pozdrawiam
>
> mrd
>
> ___
> 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: BIOS Update

[Mike Banon]

Please note that a BIOS upgrade utility provided by your board
manufacturer - might be upgrading more things than just a BIOS. For
example: EC firmware for a controller which i.e. may be adjusting the
fan speeds depending on a temperature. As you see, simply upgrading a
BIOS via flashrom may leave you with the old version of EC firmware,
which could be undesirable.

On Tue, Aug 6, 2019 at 10:11 PM Patrick Rogers
 wrote:
>
> Hello,
>
> There is a very likely chance in your situation that flashrom will be
> able to read and write to the chip even if it's not on the supported
> chips list. This command simply identifies the chip and tells you if
> everything is working.
>
> flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=2000 -V
>
> You might get some error about how you might not be able to write to the
> chip, but from my experience with an ASUS BIOS chip and a Raspberry Pi,
> this was still possible.
>
> https://www.rototron.info/recover-bricked-bios-using-flashrom-on-a-raspberry-pi/
>
> On 2019-08-05 4:39 p.m., Shaver,Zachary J wrote:
> > Hey,
> >
> > I'm considering using flashrom to upgrade the bios on a MSI B450M Pro-M2
> > Motherboard. It's BIOS ROM appears to be a MX25U12873F but I only see
> > MX25U12835F in the supported chips for flashrom. I did a cursory
> > comparison of the datasheets for the two and they look very similar. Is
> > there a chance I could flash the 73 with the 35 profile in flashrom? I
> > am aware that they are 1.8V and will need a 1.8V supply and 1.8V gpio
> > from the programmer (in my case raspberry pi).
> >
> > 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 mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: lenovo c540

[Mike Banon]

"I have flashed the bios to a new version" - how you did that, using a
windows tool provided by a laptop manufacturer? If yes, then it
preserves the originally set password and maybe the other settings.
Try to extract a "clean" BIOS image from the BIOS update utility
provided by a laptop manufacturer. Then, using a flashrom-supported
programmer like USB CH341A with a test clip (SOIC8 ?) together with
our flashrom opensource tool, you might be able to flash a clean BIOS
image (without any passwords/settings) into your BIOS chip. Of course
please make a backup before flashing a new image, in the case it's
incorrect or you'd need to borrow some Intel ME-related regions or to
have a MAC address specified in your ROM in order for onboard Ethernet
working.

On Wed, Aug 7, 2019 at 12:01 PM Darko Svilkovic
 wrote:
>
> hi,
>
> Hawe a problem with lenovo c540 AIO,bought this from a second hand,and didn't 
> see,and he didn,t mention that there is a bios admin pass ...
>
> I have flashed the bios to a new wersion,taked out the cmos battery,jumpered 
> the cmos jumper but with no success ...
>
> Now i heard that the password is in eeprom ...
>
> How to remowe it ???
>
> thx
>
> Darko/Croatia
> ___
> 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: Flashrom & bus pirate v4 - supported?

[Mike Banon]

What is your BPv4 bootloader version? I've tried many builds of BPv4
community firmware, the latest is from 12 June 2018 sources (didn't
feel the need to upgrade it later) and never had any problem with
flashrom. However, my firmware builds have been always paired with the
latest builds of BPv4 bootloader.

My firmware builds are shared here -
http://dangerousprototypes.com/forum/viewtopic.php?f=28=8498=65255#p65290
- please try a 12062018 build to see if it solves your problem. If
not, then you'll have to upgrade your bootloader - to do that you may
need to get a Pickit2 tool (about 8 usd with free ship from aliexpress
/ china). See the instructions here for more details -
http://dangerousprototypes.com/docs/Bus_Pirate_v4_and_Pickit2_(bootloader_and_firmware_updates)

Also, perhaps your command should look like " sudo ./flashrom -p
buspirate_spi:dev=/dev/ttyACM0,spispeed=1M ..." , this is the first
time I see a weird "tty.usbmodem00011" and it might be incorrect.
In addition, hope you could test your BPv4 with Linux, maybe there
would be a better result (don't know the quality of OS X brew ports).

On Thu, Aug 8, 2019 at 6:20 AM Nick Sayer via flashrom
 wrote:
>
> I did get it working by backing back down to v7.0 of the BP firware, but now 
> we’re back to it locking up after every invocation. But I do appear to have 
> successfully programmed my W25Q64JVSSIM by adding a flashrom.c entry for it - 
> basically copying the one for the 0x7018 and chopping the sizes in half.
>
> But I would like to know what the *optimal* BP firmware version is (and where 
> to get it). I want this flashrom / BP4 combination exclusively for this job 
> (burning flash chips), so it doesn’t necessarily have to be good at anything 
> else.
>
> > On Aug 7, 2019, at 7:10 PM, Nick Sayer via flashrom  
> > wrote:
> >
> > Yes. Nothing changes. I slowed it down in an attempt to get probing to work.
> >
> > I’ve upgraded the pirate to v7.11 firmware, and that got rid of the need to 
> > reset it every time, but it still doesn’t work.
> >
> > I’ve attempted to add support for the chip into flashchips.c - to at least 
> > get it to recognize the 0x7017 ID, but that doesn’t work either.
> >
> > %./flashrom --programmer 
> > buspirate_spi:dev=/dev/tty.usbmodem00011,spispeed=1M -c W25Q64.V..M -V 
> > -V -V
> > […]
> > The following protocols are supported: SPI.
> > Probing for Winbond W25Q64.V..M, 8192 kB: programmer_map_flash_region: 
> > mapping W25Q64.V..M from 0xff80 to 0x
> > buspirate_sendrecv: write 6, read 4 Sending 0x04 0x00 0x01 0x00 0x03 0x9f, 
> > receiving 0x01 0x00 0x00 0x00
> > RDID returned 0x00 0x00 0x00. RDID byte 0 parity violation. 
> > probe_spi_rdid_generic: id1 0x00, id2 0x00
> > programmer_unmap_flash_region: unmapped 0x
> > No EEPROM/flash device found.
> > Note: flashrom can never write if the flash chip isn't found automatically.
> >
> > It’s as if flashrom isn’t talking to the chip properly at all. I do see it 
> > lighting up “mode” and “pwr” LEDs briefly while trying to probe, but it 
> > just doesn’t work.
> >
> > But standalone, it works fine:
> >
> > SPI>[ 0x9f r r r ]
> > /CS ENABLED
> > WRITE: 0x9F
> > READ: 0xEF
> > READ: 0x70
> > READ: 0x17
> > /CS DISABLED
> >
> >
> >
> >> On Aug 7, 2019, at 7:04 PM, awokd via flashrom  
> >> wrote:
> >>
> >> Nick Sayer via flashrom:
> >>
> >>> % flashrom --programmer 
> >>> buspirate_spi:dev=/dev/tty.usbmodem00011,spispeed=30k
> >>
> >> That spispeed looks unusual. Have you tried spispeed=1M?
> >> ___
> >> 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 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: Copy / backup ENTIRE flash chip; does "-r" already do this?

[Mike Banon]

I'm sure that, if your motherboard has a single flash chip or you have
removed this chip and plugged it into a programmer, flashrom -r should
backup the whole contents of a chip regardless of its' internal memory
map. But I don't know if this is true for all the possible cases for
the boards with two flash chips (one for BIOS and another for ME) -
i.e. if you're trying to read the contents "internally" (using a
flashrom's internal mode). Hopefully someone could clarify.

On Tue, Jul 30, 2019 at 12:35 AM Rafael Send  wrote:
>
> Hi there-
> I'm looking at swapping out the physical flash chip on my machine for a 
> larger capacity one, so I wanted to get a quick sanity check:
>
> Does a flashrom -r pick up all the various regions in the chip, or does it 
> only go after the BIOS region if I don't specify a layout file?
>
> I.e if I do a flashrom -r on the old chip then flashrom -w on the new one, 
> will I get an identical copy of the entire thing?
>
> Thanks and apologies if this can be found in the documentation, please feel 
> free to point me there instead.
>
> Rafael
> ___
> 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: Timeout in reading whit ch341a programmer

[Mike Banon]

Perhaps you have a problem with your libusb library. Please try to
upgrade or reinstall it and maybe this problem will go away.

On Thu, Aug 8, 2019 at 10:20 AM Marino.Gregorio--- via flashrom
 wrote:
>
> Hi flashrom developers, first af all thankyou for your awesome work.
> I recently migrated from linux mint 13 (ubuntu 12.04 based) to Linux Mint 
> lmde (Debian stretch based) and i'm aving some problems in using flashrom 
> with a ch341a based programmer.
> When trying to read an spi flash i got this error :
>
>
> cb_in: error: LIBUSB_TRANSFER_TIMED_OUT
>
> cb_in: error: LIBUSB_TRANSFER_TIMED_OUT
>
> cb_in: error: LIBUSB_TRANSFER_TIMED_OUT
> ch341a_spi_spi_send_command: Failed to read 4100 bytes
> Read operation failed!
> FAILED.
>
> Sometimes, but very rarely, i can achieve a complete read.
>
> Everything work fine if i reboot in the old OS, so, i think, it's not an 
> hardware problem.
>
> Have you got any advice for me? Or is there any way i can help you to figure 
> out the trouble?
> Thankyou 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: LA-894 Parrot

[Mike Banon]

When you run the "apt-get install flashrom" command, you get the
flashrom version that was build by the package maintainers of your
Linux. If they cloned and built this flashrom version quite long ago,
you get the old version with this apt-get. The easiest way to get the
latest version is to clone the latest flashrom source code - git clone
https://review.coreboot.org/flashrom , and then build it from source
by running " make " command. Maybe you need some dependencies
installed before you could successfully compile this. Please check
this page - https://www.flashrom.org/Downloads#Installation_from_source
- it contains some package names that you might have to install before
running "make" .
On Thu, May 9, 2019 at 9:35 AM fugee ohu  wrote:
>
> I see sorry about that I might have checked what version I was running
> The message made me think my version was too new and I was actually
> even trying to install older versions starting with 9.0 and FTDI
> support wasn't found so make failed Installing FTDI support requires
> file operations and symlinks and there's no easy way to install
> otherwise that I know of I assume you built FTDI support into later
> versions Whatever version I was running, that's what I got when I ran
> apt-get install flashrom on raspbian Will I have to compile the latest
> release from source?
>
> On Thu, May 9, 2019 at 2:29 AM Mike Banon  wrote:
> >
> > Could you please test with the latest flashrom version? Yours is a bit
> > outdated, maybe git clone https://review.coreboot.org/flashrom and
> > make? Also, what is a chip that you are trying to access, please tell
> > the markings written on it. And check that your connectivity is
> > correct, that the wires aren't too long, etc.
> >
> > On Wed, May 8, 2019 at 7:47 PM fugee ohu  wrote:
> > >
> > > I get the long error message shown below but I can't find the log file
> > > to show you I don't know where it is, it's not in /var/log I assume
> > > there's only one Winbond chip on the board I found the Winbond chip
> > > and assume it's the bios chip
> > >
> > > 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 at 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.
> > > [florin at stick flashrom]$ sudo ./flashrom -p ch341a_spi -r 
> > > ~/Desktop/bios.bin
> > > flashrom v0.9.9-r1954 on Linux 4.10.11-1-ARCH (x86_64)
> > > flashrom is free software, get the source code at https://flashrom.org
> > >
> > > Calibrating delay loop... ^[[AOK.
> > >
> > > Found Generic flash chip "unknown SPI chip (RDID)" (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 at 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.
> > > ___
> > > 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: LA-894 Parrot

[Mike Banon]

Could you please test with the latest flashrom version? Yours is a bit
outdated, maybe git clone https://review.coreboot.org/flashrom and
make? Also, what is a chip that you are trying to access, please tell
the markings written on it. And check that your connectivity is
correct, that the wires aren't too long, etc.

On Wed, May 8, 2019 at 7:47 PM fugee ohu  wrote:
>
> I get the long error message shown below but I can't find the log file
> to show you I don't know where it is, it's not in /var/log I assume
> there's only one Winbond chip on the board I found the Winbond chip
> and assume it's the bios chip
>
> 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 at 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.
> [florin at stick flashrom]$ sudo ./flashrom -p ch341a_spi -r 
> ~/Desktop/bios.bin
> flashrom v0.9.9-r1954 on Linux 4.10.11-1-ARCH (x86_64)
> flashrom is free software, get the source code at https://flashrom.org
>
> Calibrating delay loop... ^[[AOK.
>
> Found Generic flash chip "unknown SPI chip (RDID)" (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 at 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.
> ___
> 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] Green CH341A didn't work, turned out it's a badly soldered CS leg. Fixed now ;-)

[Mike Banon]

My spare green CH341A almost always was unable to find a chip. Luckily
I have another working CH341A, so started comparing them with a
multimeter :

When a "healthy" CH341A is simply plugged into a USB port, without any
chips connected, there is a 3.15V - 3.3V voltage between GND hole and
other 7 holes at 25xx socket. But a "glitchy" CH341A, when put to the
same situation, did not have a ~3V voltage difference between GND and
CS pin.

Then I checked a resistance between CS leg of CH341A chip ( found it
using this document -
https://www.onetransistor.eu/2017/08/ch341a-mini-programmer-schematic.html
) and CS pin at the bottom of programmer (instead of CS hole for
convenience) - it was almost always "infinite", but sometimes - when I
pushed CS leg with a multimeter pin - there was a close to 0 Ohm
resistance, almost zero.

So I did a small soldering of CH341A CS leg, see a picture
https://i.redd.it/mfrgs45beuv21.jpg - luckily this CS leg is at the
corner of chip so was quite convenient to solder - and now this CH341A
is happy and working perfectly! ;-) Will flash many BIOSes :3
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Bug Report

[Mike Banon]

Hi there Paulo,

>  flashrom v0.9.9-unknown on Linux 4.14.98-v7+ (armv7l)
This flashrom version is probably very outdated, and we don't know if
the same problem exists in the latest flashrom as well. Please, could
you get the latest flashrom sources (e.g. git clone
https://review.coreboot.org/flashrom/ , build them using the
instructions here -
https://www.flashrom.org/Downloads#Installation_from_source , and try
again?

Best regards,
Mike Banon

On Mon, Apr 29, 2019 at 3:00 AM Paulo Zorzan  wrote:
>
> ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -r romread_v1.rom
>
>  ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -w
> x200_8mb_ukqwerty_txtmode.rom
>
>  flashrom v0.9.9-unknown on Linux 4.14.98-v7+ (armv7l)
> flashrom is free software, get the source code at https://flashrom.org
>
> Calibrating delay loop... OK.
> Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi.
> Error: WIP bit after WRSR never cleared
> spi_write_status_register failed.
> Reading old flash chip contents...
>
> Calibrating delay loop... OK.
> Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi.
> Error: WIP bit after WRSR never cleared
> spi_write_status_register failed.
> Reading old flash chip contents... done.
> Erasing and writing flash chip... Erase/write done.
> Verifying flash... FAILED at 0x! Expected=0x5a, Found=0x00,
> failed byte count from 0x-0x007f: 0x1d1
> 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 -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -w x200_8mac.rom
> flashrom v0.9.9-unknown on Linux 4.14.98-v7+ (armv7l)
> flashrom is free software, get the source code at https://flashrom.org
>
> Calibrating delay loop... OK.
> Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi.
> Error: WIP bit after WRSR never cleared
> spi_write_status_register failed.
> Reading old flash chip contents... done.
> Erasing and writing flash chip... Erase/write done.
> Verifying flash... FAILED at 0x! Expected=0x5a, Found=0x00,
> failed byte count from 0x-0x007f: 0x2d1
> 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 -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -w x200_8mac.rom
> flashrom v0.9.9-unknown on Linux 4.14.98-v7+ (armv7l)
> flashrom is free software, get the source code at https://flashrom.org
>
> Calibrating delay loop... OK.
> Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi.
> Error: WIP bit after WRSR never cleared
> spi_write_status_register failed.
> Reading old flash chip contents... done.
> Erasing and writing flash chip... FAILED at 0x0100! Expected=0xff,
> Found=0x89, failed byte count from 0x-0x0fff: 0x2d
> ERASE FAILED!
> Reading current flash chip contents... done. Looking for another erase
> function.
> Erase/write done.
> Verifying flash... FAILED at 0x! Expected=0x5a, Found=0x00,
> failed byte count from 0x-0x007f: 0x1d1
> 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 -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -w x200_8mac.rom
> flashrom v0.9.9-unknown on Linux 4.14.98-v7+ (armv7l)
> flashrom is free software, get the source code at https://flashrom.org
>
> Calibrating delay loop... OK.
> Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi.
> Reading old flash chip contents... done.
> Erasing and writing flash chip... FAILED at 0x! Expected=0xff,
> Found=0x5a, failed byte count from 0x-0x0fff: 0x66
> ERASE FAILED!
> Reading current flash chip contents... done. Looking for another erase
> function.
> Erase/write done.
> Verifying flash... FAILED at 0x! Expected=0x5a, Found=0x00,
> failed byte count from 0x-0x007f: 0x3d1
> 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 -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -w
> x200_8mb_ukqwerty_vesafb.rom
> flashrom v0.9.9-unknown on Linux 4.14.98-v7+ (armv7l)
> flashrom is free software, get the source code at https://flashrom.org
>
> Calibrating delay loop... OK.
> Found Macronix flash chip "MX25L6405D" (8192 kB, SPI) on linux_spi.
> Error: WIP bit after WRSR never cleared
> spi_write_status_register failed.
> Reading old flash chip con

[flashrom] Re: Fwd: confirm a56f2da945a80ad7b5155fd90206ef7a9609ae37

[Mike Banon]

Hi there Allen, perhaps your last message has been lost - could only
see the first one. Congratulations with your successful W25Q64.V
flashing using a flashrom!

On Tue, Apr 9, 2019 at 10:59 AM Allen  wrote:
>
>
> Best Regards,
> Allen Analian | President & Senior Electrical Engineer
> Allen Productions Inc. / Engineering
> 1200 E Mission Blvd
> Pomona, CA 91766
> Website: http://www.allen.dj
> Mobile: (562) 242-8479 - Available 24/7/365 (Emergencies Only)
>
> CONFIDENTIALITY NOTICE:
>
> This transmission may be privileged and may contain confidential information 
> intended only for the recipient(s) named above.  Any other distribution, 
> re-transmission, copying or disclosure of this message is strictly 
> prohibited.  If you have received this transmission in error, please notify 
> me immediately by telephone or return email, and delete this message from 
> your servers and local system.
>
>
> -- Forwarded message -
> From: Allen 
> Date: Tue, Apr 9, 2019 at 12:46 AM
> Subject: Re: confirm a56f2da945a80ad7b5155fd90206ef7a9609ae37
> To: 
>
>
> Flashrom works with Alienware Aurora R4 motherboard, with winbond ic: W25Q64.V
>
> Had a successful flash using rpi environment! The flash image was A11.bin - 
> latest version
>
> Best Regards,
> Allen Analian | President & Senior Electrical Engineer
> Allen Productions Inc. / Engineering
> 1200 E Mission Blvd
> Pomona, CA 91766
> Website: http://www.allen.dj
> Mobile: (562) 242-8479 - Available 24/7/365 (Emergencies Only)
>
> CONFIDENTIALITY NOTICE:
>
> This transmission may be privileged and may contain confidential information 
> intended only for the recipient(s) named above.  Any other distribution, 
> re-transmission, copying or disclosure of this message is strictly 
> prohibited.  If you have received this transmission in error, please notify 
> me immediately by telephone or return email, and delete this message from 
> your servers and local system.
>
>
> On Tue, Apr 9, 2019 at 12:41 AM 
>  
> wrote:
>>
>> Email Address Registration Confirmation
>>
>> Hello, this is the GNU Mailman server at flashrom.org.
>>
>> We have received a registration request for the email address
>>
>> al...@allen.dj
>>
>> Before you can start using GNU Mailman at this site, you must first confirm
>> that this is your email address.  You can do this by replying to this 
>> message,
>> keeping the Subject header intact.
>>
>> If you do not wish to register this email address, simply disregard this
>> message.  If you think you are being maliciously subscribed to the list, or
>> have any other questions, you may contact
>>
>> flashrom-ow...@flashrom.org
>
> ___
> 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: flashrom Program compile problems

[Mike Banon]

Hi Sven,

On Sun, Feb 17, 2019 at 11:37 AM Sven AOL  wrote:
>
> After replacing the new memory IC, the memory contents are missing. The 
> flashfile is not the "software update file" from the manufacturer of the 
> device. Or is a software update always the whole file written on the IC?
>

Maybe this software update updates only a small part of your device
memory contents - I don't know.

>
> In my repair I downloaded the offered file of the homepage
>

Seems to be a correct approach - maybe someone just made a dump of
complete memory contents and shared it. Have you flashed it already
and is it working?

>
> Do you have a good buy recommendation for a good flash programmer that works 
> well with your software?
>

CH341A USB programmer - it works fine and also very cheap - about $2
or $3 with free shipping from China (e.g. AliExpress) or maybe
slightly more expensive to get it locally. Make sure to get a "green
PCB" version of it and also check that it outputs 3.3V instead of 5V
before using it: there was a small number of (mostly black PCB) CH341A
which gave 5V instead of 3.3V - although it's possible to fix them.

Best regards,
Mike Banon
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: flashrom Program compile problems

[Mike Banon]

Hi Sven, I think it would be much more efficient for you to just use
some user friendly Linux LiveCD/LiveUSB (it unpacks to your RAM
without touching a hard drive), then you temporary install a linux
version of flashrom and use it for flashing + could mount a Windows
partition to copy the binaries. flashrom wiki contains the
step-by-step instructions on how to build it under Linux, or your
could simply install a package from your Linux distro (something like
"sudo apt-get install flashrom" at Ubuntu/Linux Mint) but please note
that this package would be outdated so if you need a chip which only
recently became supported by flashrom, you'd need to git clone the
repository and build from source - luckily it's very simple also and
well documented.

Best regards,
Mike Banon

On Mon, Feb 11, 2019 at 6:16 PM Sven Frey via flashrom
 wrote:
>
> Hello Flashrom Support Team,
>
>
>
> I have a Windows 10 32 bit PC. I need your program flashrom. Unfortunately I 
> can not compile the program. Can you send me the program compiled? I would be 
> very grateful. Many thanks for the help.
>
>
>
> Best regards,
>
> Sven
>
> ___
> 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: Updating the e-flash on an ITE SuperIO chip

[Mike Banon]

It would be really nice if you could share a datasheet for IT8623E
(found at Asus AM1I-A amd early-16h motherboard (no PSP)) or at least
tell if it contains the internal memory like KB9012 or not - is there
something we will need to flash in case of IT8623E chip replacement

On Mon, Feb 11, 2019 at 8:56 PM Angel Pons  wrote:
>
> Hello,
>
> On Mon, Feb 11, 2019, 18:26 Richard Hughes >
>> On Mon, 11 Feb 2019 at 17:00, Angel Pons  wrote:
>> > The it85spi driver is commented out in code, apparently because it
>> > relies on firmware-specific functions. AFAIK, there isn't much to read
>> > the internal flash on ECs, other than the ENE KB9012's via EDI.
>>
>> Okay, that was a very useful read, thanks. Different, but related of course.
>>
>> > > Whilst I now have a datasheet, I
>> > For those chips? I'm interested in them: How did you obtain them?
>>
>> I've been working with an ODM for an un-named OEM, who supplied me the
>> datasheet for the IT89 without signing an NDA. I don't think I can
>> redistribute it without issues.
>
>
> Oh, bummer.
>
>> > I don't think much has been done for the internal flash on these ICs on
>> > flashrom. For instance, I didn't know the IT8987 had an internal flash.
>>
>> As I understand it, at least for the the hardware I have here, the
>> IT89 has both. The SPI "external" flash is only used to populate the
>> "internal" e-flash at manufacturing time and then after than it's
>> unused. I imagine you could reprogram the 128k external SPI chip using
>> the indirect mapping thing although at least for me it's a nice "get
>> out of jail" feature as the current firmware seems to look for the
>> A5A5A5A5 16 byte header on the e-flash to check if it's valid. Of
>> course, I could have misunderstood this all wildly.
>
>
> I now recall reading something like that. I'm not sure about the header bit, 
> though.
>
>> On Mon, 11 Feb 2019 at 17:11, Carl-Daniel Hailfinger
>>  wrote:
>> > IT87 handling was easy and straightforward because all they did
>> > (regarding flash) was translating LPC flash accesses to SPI flash
>> > accesses in passthrough mode and offering a separate SPI-centric
>> > programming interface for full access.
>>
>> I think IT89 is much like a IT87 -- some of the LDNs seem a bit
>> different (and there are more!) but it looks basically the same kind
>> of beast.
>
>
> Well, the IT87  and IT86 series are usually Super IO chips, whereas the IT85 
> and IT89 chips are ECs, which seem to have a SuperIO-like part, with LDNs and 
> such.
>
>> Richard.
>
>
> Best regards,
>
> Angel Pons
>
> ___
> 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: ENE KB9012QF A3 reflash help needed

[Mike Banon]

Maybe try inserting some extra programmer_delay(n) to your ichspi.c ?
Also I had a patch for the unreliable flashing environments -
https://review.coreboot.org/c/flashrom/+/23840 - but didn't improve it
yet so it haven't been merged, and already incompatible with the
latest flashrom. Also maybe it doesn't affect KB9012 if its' flashing
functions are different, but maybe it could be useful somehow. Still I
hope that you've already ordered that CH341A since it costs very
cheap, just $2-$3, and could save a lot of your time.

On Sun, Jan 20, 2019 at 3:35 AM Nyúlós Lónyál  wrote:
>
> Thanks for replying at my noob questions. :) The spispeed parameter, yea, I 
> thought about it after looking into flashrom's source on GitHub. Sadly it's 
> not in the code of ICH7 chipset (ichspi.c), so the spispeed option in 
> flashrom command is unavailable. Someone already did that for AMD SB600 
> chipset (sb600spi.c), found a link about it: 
> https://mail.coreboot.org/pipermail/flashrom/2013-August/011410.html
>
> I don't know much about C programming language, so I can't transform that 
> code for ICH7. I have no more ideas, maybe it's possible to modify the 
> default SPI frequency in ichspi.c, I'm not sure.
>
> Mike Banon  ezt írta (időpont: 2019. jan. 19., Szo, 
> 23:25):
>>
>> Sorry for a long reply, I just watched your video and - unless you
>> changed its' speed - it seems to me that your KB9012 operations are
>> going faster than expected, e.g. it reached 0x4*** address almost
>> instantly while in my CH341A case it was almost certainly slower. So
>> maybe you could experiment with spispeed parameter, like flashrom -p
>> internal:spispeed=frequency , please look it up online ( I can't at
>> the moment )
>>
>>
>> On Wed, Jan 16, 2019 at 5:01 PM Nyúlós Lónyál  
>> wrote:
>> >
>> > Same problem with 5cm long copper wires. Here is a video of what's 
>> > happening: https://www.youtube.com/watch?v=JlbRGK9_gPg
>> >
>> > Nyúlós Lónyál  ezt írta (időpont: 2019. jan. 
>> > 16., Sze, 1:38):
>> >>
>> >> The wires are ~20-25cm made of aluminium, but I have some broken USB 
>> >> cables with copper wires. I can reduce the distance of laptop's keyboard 
>> >> connector and DIP8 socket to about 5cm wire length, will give it a try 
>> >> tomorrow. And something that I've noticed at verifying with flashrom, it 
>> >> always gives a random hex number after "failed byte count from 
>> >> 0x-0x0001". Maybe the "Timed out waiting for SPI not busy!" 
>> >> error is caused by the wires too. Thanks for the idea, I will reply back 
>> >> with results.
>> >>
>> >> Mike Banon  ezt írta (időpont: 2019. jan. 16., Sze, 
>> >> 1:09):
>> >>>
>> >>> Sorry if I've already asked this question, but how long are your
>> >>> wires? Ideally they should be about 10cm length and made of good
>> >>> copper. Although it could work even for 30cm poor aluminum wires,
>> >>> still when there are read/write errors - the first suggestion which
>> >>> comes to my mind is to shorten the wires. I understand that it could
>> >>> be difficult to use short wires at your flashing setup, but hope it is
>> >>> possible for you to try. And also I hope that you've ordered CH341A
>> >>> just in case our suggestions wouldn't work.
>> >>> > The laptop can't boot, doesn't even react to power button or recovery 
>> >>> > key combination, and no charging LED lighting up
>> >>> Everything from this list is expected if there is a corrupted KB9012
>> >>> firmware, because it is KB9012 which listens for your power button
>> >>> keypresses / controls the LEDs / etc
>> >>>
>> >>> On Tue, Jan 15, 2019 at 2:44 PM Nyúlós Lónyál 
>> >>>  wrote:
>> >>> >
>> >>> > Sorry for the confusion. :( I think you have misunderstood me.
>> >>> >
>> >>> > My laptop's motherboard is taken out of the laptop. I have another 
>> >>> > machine, a desktop PC which I've used for trying rayer_spi programmer. 
>> >>> > Now I connect the laptop's KB9012's debug pins into the desktop PC 
>> >>> > motherboard's DIP8 BIOS socket with wires, after it booted the linux 
>> >>> > distribution with flashrom installed and removing it's original BIOS 
>> >>> > SPI chip. The two machine's GND, DIP8 socket's GND, and KB9012's pin 
>> >>> > 42 are

[flashrom] Re: ENE KB9012QF A3 reflash help needed

[Mike Banon]

Sorry for a long reply, I just watched your video and - unless you
changed its' speed - it seems to me that your KB9012 operations are
going faster than expected, e.g. it reached 0x4*** address almost
instantly while in my CH341A case it was almost certainly slower. So
maybe you could experiment with spispeed parameter, like flashrom -p
internal:spispeed=frequency , please look it up online ( I can't at
the moment )


On Wed, Jan 16, 2019 at 5:01 PM Nyúlós Lónyál  wrote:
>
> Same problem with 5cm long copper wires. Here is a video of what's happening: 
> https://www.youtube.com/watch?v=JlbRGK9_gPg
>
> Nyúlós Lónyál  ezt írta (időpont: 2019. jan. 16., 
> Sze, 1:38):
>>
>> The wires are ~20-25cm made of aluminium, but I have some broken USB cables 
>> with copper wires. I can reduce the distance of laptop's keyboard connector 
>> and DIP8 socket to about 5cm wire length, will give it a try tomorrow. And 
>> something that I've noticed at verifying with flashrom, it always gives a 
>> random hex number after "failed byte count from 0x-0x0001". 
>> Maybe the "Timed out waiting for SPI not busy!" error is caused by the wires 
>> too. Thanks for the idea, I will reply back with results.
>>
>> Mike Banon  ezt írta (időpont: 2019. jan. 16., Sze, 
>> 1:09):
>>>
>>> Sorry if I've already asked this question, but how long are your
>>> wires? Ideally they should be about 10cm length and made of good
>>> copper. Although it could work even for 30cm poor aluminum wires,
>>> still when there are read/write errors - the first suggestion which
>>> comes to my mind is to shorten the wires. I understand that it could
>>> be difficult to use short wires at your flashing setup, but hope it is
>>> possible for you to try. And also I hope that you've ordered CH341A
>>> just in case our suggestions wouldn't work.
>>> > The laptop can't boot, doesn't even react to power button or recovery key 
>>> > combination, and no charging LED lighting up
>>> Everything from this list is expected if there is a corrupted KB9012
>>> firmware, because it is KB9012 which listens for your power button
>>> keypresses / controls the LEDs / etc
>>>
>>> On Tue, Jan 15, 2019 at 2:44 PM Nyúlós Lónyál  
>>> wrote:
>>> >
>>> > Sorry for the confusion. :( I think you have misunderstood me.
>>> >
>>> > My laptop's motherboard is taken out of the laptop. I have another 
>>> > machine, a desktop PC which I've used for trying rayer_spi programmer. 
>>> > Now I connect the laptop's KB9012's debug pins into the desktop PC 
>>> > motherboard's DIP8 BIOS socket with wires, after it booted the linux 
>>> > distribution with flashrom installed and removing it's original BIOS SPI 
>>> > chip. The two machine's GND, DIP8 socket's GND, and KB9012's pin 42 are 
>>> > united.
>>> >
>>> > Like when recovering a regular motherboard BIOS with hot-swapping chips, 
>>> > just the only difference I connect the laptop's KBC instead of another 
>>> > BIOS chip: https://www.coreboot.org/FAQ#Developers
>>> >
>>> > I think the desktop motherboard's BIOS socket can be used as an SPI 
>>> > programmer this way, originally it has W25Q80BVAIG DIP8 chip which can be 
>>> > removed. That gave me these results, read and write errors which I sent 
>>> > before, but at least it can detect KB9012. I've tested with the original 
>>> > BIOS chip, flashrom can read, erase, and write it. The motherboard is an 
>>> > Asrock G41C-GS first generation, rev 1.0.2.
>>> >
>>> > The laptop can't boot, doesn't even react to power button or recovery key 
>>> > combination, and no charging LED lighting up, since it got bricked with a 
>>> > wrong BIOS update, this is why I want to reflash KB9012 with an external 
>>> > tool, like the desktop PC motherboard's DIP8 socket.
>>> >
>>> > Mike Banon  ezt írta (időpont: 2019. jan. 14., H, 
>>> > 22:43):
>>> >>
>>> >> That is because KB9012 is active after your laptop has booted and not
>>> >> in debug state where it is possible to reflash it without a problem.
>>> >>
>>> >> Have you double checked your laptop's datasheet to make sure your
>>> >> connection is correct, and also that your laptop's corner ground is
>>> >> really connected to its' ground? (what if not all its' copper circles
>>> >> are the grounds in your case

[flashrom] Re: ENE KB9012QF A3 reflash help needed

[Mike Banon]

Sorry if I've already asked this question, but how long are your
wires? Ideally they should be about 10cm length and made of good
copper. Although it could work even for 30cm poor aluminum wires,
still when there are read/write errors - the first suggestion which
comes to my mind is to shorten the wires. I understand that it could
be difficult to use short wires at your flashing setup, but hope it is
possible for you to try. And also I hope that you've ordered CH341A
just in case our suggestions wouldn't work.
> The laptop can't boot, doesn't even react to power button or recovery key 
> combination, and no charging LED lighting up
Everything from this list is expected if there is a corrupted KB9012
firmware, because it is KB9012 which listens for your power button
keypresses / controls the LEDs / etc

On Tue, Jan 15, 2019 at 2:44 PM Nyúlós Lónyál  wrote:
>
> Sorry for the confusion. :( I think you have misunderstood me.
>
> My laptop's motherboard is taken out of the laptop. I have another machine, a 
> desktop PC which I've used for trying rayer_spi programmer. Now I connect the 
> laptop's KB9012's debug pins into the desktop PC motherboard's DIP8 BIOS 
> socket with wires, after it booted the linux distribution with flashrom 
> installed and removing it's original BIOS SPI chip. The two machine's GND, 
> DIP8 socket's GND, and KB9012's pin 42 are united.
>
> Like when recovering a regular motherboard BIOS with hot-swapping chips, just 
> the only difference I connect the laptop's KBC instead of another BIOS chip: 
> https://www.coreboot.org/FAQ#Developers
>
> I think the desktop motherboard's BIOS socket can be used as an SPI 
> programmer this way, originally it has W25Q80BVAIG DIP8 chip which can be 
> removed. That gave me these results, read and write errors which I sent 
> before, but at least it can detect KB9012. I've tested with the original BIOS 
> chip, flashrom can read, erase, and write it. The motherboard is an Asrock 
> G41C-GS first generation, rev 1.0.2.
>
> The laptop can't boot, doesn't even react to power button or recovery key 
> combination, and no charging LED lighting up, since it got bricked with a 
> wrong BIOS update, this is why I want to reflash KB9012 with an external 
> tool, like the desktop PC motherboard's DIP8 socket.
>
> Mike Banon  ezt írta (időpont: 2019. jan. 14., H, 22:43):
>>
>> That is because KB9012 is active after your laptop has booted and not
>> in debug state where it is possible to reflash it without a problem.
>>
>> Have you double checked your laptop's datasheet to make sure your
>> connection is correct, and also that your laptop's corner ground is
>> really connected to its' ground? (what if not all its' copper circles
>> are the grounds in your case)
>>
>> On Fri, Jan 11, 2019 at 5:01 PM Nyúlós Lónyál  
>> wrote:
>> >
>> > Sorry for double mail. Erasing and writing fails too.
>> >
>> > xubuntu@xubuntu:~/flashrom$ sudo ./flashrom -p internal -c "KB9012 (EDI)" 
>> > -w /home/xubuntu/Desktop/EC-FD-Extract.bin
>> > flashrom p1.0-141-g9cecc7e on Linux 4.15.0-20-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 chipset "Intel ICH7/ICH7R".
>> > Enabling flash write... OK.
>> > edi_read: Retrying read with greater buffer length!
>> > edi_read: Retrying read with greater buffer length!
>> > Found ENE flash chip "KB9012 (EDI)" (128 kB, SPI) mapped at physical 
>> > address 0xfffe.
>> > Reading old flash chip contents... done.
>> > Erasing and writing flash chip... edi_chip_block_erase: Timed out waiting 
>> > for SPI not busy!
>> > Reading current flash chip contents... done. Looking for another erase 
>> > function.
>> > Looking for another erase function.
>> > Looking for another erase function.
>> > Looking for another erase function.
>> > Looking for another erase function.
>> > Looking for another erase function.
>> > Looking for another erase function.
>> > No usable erase functions left.
>> > FAILED!
>> > Uh oh. Erase/write failed. Checking if anything has changed.
>> > Reading current flash chip contents... done.
>> > Apparently at least some data has changed.
>> > Your flash chip is in an unknown state.
>> > Get help on IRC at chat.freenode.net (channel #flashrom) or
>> > mail flashrom@flashrom.org with the subject "FAILED: "!
>> > --

[flashrom] Re: ENE KB9012QF A3 reflash help needed

[Mike Banon]

for delay loops (clk_id: 1, resolution: 1ns).
>> Found chipset "Intel ICH7/ICH7R".
>> Enabling flash write... OK.
>> edi_read: Retrying read with greater buffer length!
>> edi_read: Retrying read with greater buffer length!
>> Found ENE flash chip "KB9012 (EDI)" (128 kB, SPI) mapped at physical address 
>> 0xfffe.
>> Verifying flash... FAILED at 0x34c2! Expected=0xff, Found=0x78, failed 
>> byte count from 0x-0x0001: 0x6c52
>>
>>
>> Nyúlós Lónyál  ezt írta (időpont: 2019. jan. 10., 
>> Cs, 12:14):
>>>
>>> Yea, tried to discharge the motherboard, taken out CMOS battery too, it 
>>> didn't help. I don't know if this is programmer related or not, I have 
>>> reflashed 2 types of BIOS SPI chips with it, EN25QH16 and W25Q32BV. But 
>>> these chips are maybe different from KB9012's debug interface. I can't get 
>>> a CH341A for now, maybe some months later. It would be good to recover the 
>>> laptop if it's possible with the tools I have currently, but not very 
>>> urgent. Here is the programmer's config, if it helps: 
>>> https://github.com/flashrom/flashrom/blob/master/rayer_spi.c
>>>
>>> Mike Banon  ezt írta (időpont: 2019. jan. 9., Sze, 
>>> 18:59):
>>>>
>>>> Just to double-check: please discharge the motherboard completely by
>>>> trying to turn it on while there is no power adapter connected, then
>>>> unite three grounds (KB9012 / programmer / motherboard ) and only then
>>>> connect the board's power adapter . After doing all that, please check
>>>> if you could read it now. Also, what if your issues are programmer
>>>> related? Is it possible for you to try another programmer, like CH341A
>>>> ? (because it costs like $2-$3 with free shipping from china, just
>>>> prefer to get a green PCB version because there were some 3.3/5V
>>>> issues with some black PCB CH341A , and blue PCB version costs the
>>>> same low price while having fewer pins) Or maybe you could get it
>>>> locally for a (hopefully) small premium if you're in hurry
>>>>
>>>> On Wed, Jan 9, 2019 at 3:20 PM Nyúlós Lónyál  
>>>> wrote:
>>>> >
>>>> > Hi Mike!
>>>> >
>>>> > I've followed the linked guide, it gave me these results. The grounds 
>>>> > are united, still the same error happens. I have tried to GND pin 42 of 
>>>> > KB9012 as mentioned in the guide, and tried to connect both pin 41 and 
>>>> > 42 to GND, as in KBC's datasheet at EDI related part, still no success, 
>>>> > flashrom doesn't detect it.
>>>> >
>>>> > Mike Banon  ezt írta (időpont: 2019. jan. 8., K, 
>>>> > 16:08):
>>>> >>
>>>> >> Hi Nyulos,
>>>> >> Have you tried following the KB9012 flashing instructions at
>>>> >> DangerousPrototypes wiki?
>>>> >> http://dangerousprototypes.com/docs/Flashing_KB9012_with_Bus_Pirate
>>>> >> Although that is for Bus Pirate / CH341A programmers and LA-A091P,
>>>> >> should be similar for your Rayer programmer and LA-8241P motherboard.
>>>> >> Most importantly, before plugging the power adapter you should unite
>>>> >> three grounds:
>>>> >> 1) GND of laptop's motherboard
>>>> >> 2) GND of your programmer
>>>> >> 3) GND of KB9012
>>>> >> Best regards,
>>>> >> Mike Banon
>>>> >>
>>>> >> On Tue, Jan 8, 2019 at 3:30 PM Nyúlós Lónyál 
>>>> >>  wrote:
>>>> >> >
>>>> >> > Hi!
>>>> >> >
>>>> >> > I'm trying to flash an ENE KB9012QF A3 KBC on LA-8241P motherboard. 
>>>> >> > The problem is flashrom can't detect the internal SPI of it, fails 
>>>> >> > with error.
>>>> >> >
>>>> >> > flashrom p1.0-141-g9cecc7e on Linux 4.15.0-20-generic (x86_64)
>>>> >> > flashrom is free software, get the source code at https://flashrom.org
>>>> >> >
>>>> >> > flashrom was built with libpci 3.5.2, GCC 7.3.0, little endian
>>>> >> > Command line (5 args): ./flashrom -p rayer_spi -c KB9012 (EDI) -V
>>>> >> > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
>>>> >> > Initializing rayer_spi programmer
>>>> >> > Using address 0x378 as I/O base for parallel port access.
>>>> >> > Using RayeR SPIPGM pinout.
>>>> >> > The following protocols are supported: SPI.
>>>> >> > Probing for ENE KB9012 (EDI), 128 kB: edi_chip_probe: reading 
>>>> >> > hwversion failed
>>>> >> > No EEPROM/flash device found.
>>>> >> > Note: flashrom can never write if the flash chip isn't found 
>>>> >> > automatically.
>>>> >> >
>>>> >> > How to get it working? Thanks a lot for help!
>>>> >> > ___
>>>> >> > 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: ENE KB9012QF A3 reflash help needed

[Mike Banon]

Just to double-check: please discharge the motherboard completely by
trying to turn it on while there is no power adapter connected, then
unite three grounds (KB9012 / programmer / motherboard ) and only then
connect the board's power adapter . After doing all that, please check
if you could read it now. Also, what if your issues are programmer
related? Is it possible for you to try another programmer, like CH341A
? (because it costs like $2-$3 with free shipping from china, just
prefer to get a green PCB version because there were some 3.3/5V
issues with some black PCB CH341A , and blue PCB version costs the
same low price while having fewer pins) Or maybe you could get it
locally for a (hopefully) small premium if you're in hurry

On Wed, Jan 9, 2019 at 3:20 PM Nyúlós Lónyál  wrote:
>
> Hi Mike!
>
> I've followed the linked guide, it gave me these results. The grounds are 
> united, still the same error happens. I have tried to GND pin 42 of KB9012 as 
> mentioned in the guide, and tried to connect both pin 41 and 42 to GND, as in 
> KBC's datasheet at EDI related part, still no success, flashrom doesn't 
> detect it.
>
> Mike Banon  ezt írta (időpont: 2019. jan. 8., K, 16:08):
>>
>> Hi Nyulos,
>> Have you tried following the KB9012 flashing instructions at
>> DangerousPrototypes wiki?
>> http://dangerousprototypes.com/docs/Flashing_KB9012_with_Bus_Pirate
>> Although that is for Bus Pirate / CH341A programmers and LA-A091P,
>> should be similar for your Rayer programmer and LA-8241P motherboard.
>> Most importantly, before plugging the power adapter you should unite
>> three grounds:
>> 1) GND of laptop's motherboard
>> 2) GND of your programmer
>> 3) GND of KB9012
>> Best regards,
>> Mike Banon
>>
>> On Tue, Jan 8, 2019 at 3:30 PM Nyúlós Lónyál  
>> wrote:
>> >
>> > Hi!
>> >
>> > I'm trying to flash an ENE KB9012QF A3 KBC on LA-8241P motherboard. The 
>> > problem is flashrom can't detect the internal SPI of it, fails with error.
>> >
>> > flashrom p1.0-141-g9cecc7e on Linux 4.15.0-20-generic (x86_64)
>> > flashrom is free software, get the source code at https://flashrom.org
>> >
>> > flashrom was built with libpci 3.5.2, GCC 7.3.0, little endian
>> > Command line (5 args): ./flashrom -p rayer_spi -c KB9012 (EDI) -V
>> > Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
>> > Initializing rayer_spi programmer
>> > Using address 0x378 as I/O base for parallel port access.
>> > Using RayeR SPIPGM pinout.
>> > The following protocols are supported: SPI.
>> > Probing for ENE KB9012 (EDI), 128 kB: edi_chip_probe: reading hwversion 
>> > failed
>> > No EEPROM/flash device found.
>> > Note: flashrom can never write if the flash chip isn't found automatically.
>> >
>> > How to get it working? Thanks a lot for help!
>> > ___
>> > 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: ENE KB9012QF A3 reflash help needed

[Mike Banon]

This rayer_spi is "RayeR parallel port programmer" which is external.
Internal flashing will not work until someone will reverse engineer
the proprietary UEFI update mechanism part of updating EC firmware.

P.S. Meanwhile I'm contributing various patches to coreboot,
although they are not discrete GPU-related yet (sorry I'm such a slowpoke!)
you may want to take a look, e.g. some of them are for ACPI S3 inspired by HJK
https://review.coreboot.org/q/mikeb+mikeb

On Wed, Jan 9, 2019 at 12:45 AM awokd via flashrom
 wrote:
>
> Mike Banon wrote on 1/8/19 3:08 PM:
> > Hi Nyulos,
> > Have you tried following the KB9012 flashing instructions at
> > DangerousPrototypes wiki?
> > http://dangerousprototypes.com/docs/Flashing_KB9012_with_Bus_Pirate
> > Although that is for Bus Pirate / CH341A programmers and LA-A091P,
> > should be similar for your Rayer programmer and LA-8241P motherboard.
> > Most importantly, before plugging the power adapter you should unite
> > three grounds:
> > 1) GND of laptop's motherboard
> > 2) GND of your programmer
> > 3) GND of KB9012
> > Best regards,
> > Mike Banon
> >
> > On Tue, Jan 8, 2019 at 3:30 PM Nyúlós Lónyál  
> > wrote:
> >>
> >> Hi!
> >>
> >> I'm trying to flash an ENE KB9012QF A3 KBC on LA-8241P motherboard. The 
> >> problem is flashrom can't detect the internal SPI of it, fails with error.
> >>
> >> flashrom p1.0-141-g9cecc7e on Linux 4.15.0-20-generic (x86_64)
> >> flashrom is free software, get the source code at https://flashrom.org
> >>
> >> flashrom was built with libpci 3.5.2, GCC 7.3.0, little endian
> >> Command line (5 args): ./flashrom -p rayer_spi -c KB9012 (EDI) -V
> >> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> >> Initializing rayer_spi programmer
> >> Using address 0x378 as I/O base for parallel port access.
> >> Using RayeR SPIPGM pinout.
> >> The following protocols are supported: SPI.
> >> Probing for ENE KB9012 (EDI), 128 kB: edi_chip_probe: reading hwversion 
> >> failed
> >> No EEPROM/flash device found.
> >> Note: flashrom can never write if the flash chip isn't found automatically.
> >>
> >> How to get it working? Thanks a lot for help!
>
> I think he's trying to use an internal SPI (maybe he should try "-p
> internal_spi" instead of "-p rayer_spi"?), so tying grounds probably
> won't help for that? He might have to use an external programmer
> instead, so he'd want to tie grounds then!
>
> ___
> 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: ENE KB9012QF A3 reflash help needed

[Mike Banon]

Hi Nyulos,
Have you tried following the KB9012 flashing instructions at
DangerousPrototypes wiki?
http://dangerousprototypes.com/docs/Flashing_KB9012_with_Bus_Pirate
Although that is for Bus Pirate / CH341A programmers and LA-A091P,
should be similar for your Rayer programmer and LA-8241P motherboard.
Most importantly, before plugging the power adapter you should unite
three grounds:
1) GND of laptop's motherboard
2) GND of your programmer
3) GND of KB9012
Best regards,
Mike Banon

On Tue, Jan 8, 2019 at 3:30 PM Nyúlós Lónyál  wrote:
>
> Hi!
>
> I'm trying to flash an ENE KB9012QF A3 KBC on LA-8241P motherboard. The 
> problem is flashrom can't detect the internal SPI of it, fails with error.
>
> flashrom p1.0-141-g9cecc7e on Linux 4.15.0-20-generic (x86_64)
> flashrom is free software, get the source code at https://flashrom.org
>
> flashrom was built with libpci 3.5.2, GCC 7.3.0, little endian
> Command line (5 args): ./flashrom -p rayer_spi -c KB9012 (EDI) -V
> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
> Initializing rayer_spi programmer
> Using address 0x378 as I/O base for parallel port access.
> Using RayeR SPIPGM pinout.
> The following protocols are supported: SPI.
> Probing for ENE KB9012 (EDI), 128 kB: edi_chip_probe: reading hwversion failed
> No EEPROM/flash device found.
> Note: flashrom can never write if the flash chip isn't found automatically.
>
> How to get it working? Thanks a lot for help!
> ___
> 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

Re: [flashrom] error message from running flashrom , message said to send log

[Mike Banon]

Good day Mr.Frog, all I'm seeing from your (rather long) log is that :
for unknown to me reason, flashrom can't detect your flash chip. To
help you, we need to know more about your flashing environment. Are
you using SOIC8 test clip? What is the length of wires between your
RPi and MBAir's flash chip? By the way, while RPi is a multipurpose
tool, its far from being an ideal flashrom programmer: if you'd look
through the mailing lists, as well as /r/coreboot and /r/flashrom at
reddit, you'll see that such problems aren't uncommon with RPi.

I recommend you to get a dedicated one-purpose hardware tool,
supported by flashrom of course. It is CH341A USB hardware programmer,
it costs just $2-$3 (if directly from China with free shipping) but if
you need it urgently you could get it locally for 2x-3x of the price.
It is very reliable, and maybe it would work better than RPi in your
environment. However, if its still not working with this dedicated
programmer, the next step would be to check the length of your wires
between the programmer and the test clip you are trying to use for
In-System-Programming (SOIC8 ?). Ideally, they should be shorter than
10cm, and made of copper not aluminium (because copper is about 1.5x
times more electrically conductive in comparison)

If any other questions, you are welcome

Best regards,
Mike Banon

On Tue, Aug 7, 2018 at 10:15 AM, frogfrogfrogfrog Frogfrog
 wrote:
> apoligize,  i have forgotten to add the spispeed=8000 to the intial command,
> thank you for you time
>
>
>
>
> On Tue, Aug 7, 2018 at 3:09 AM, frogfrogfrogfrog Frogfrog
>  wrote:
>>
>> :: after running the command::
>>
>> flashrom -r ~/efi/read1.bin -V -p linux_spi:dev=/dev/spidev0.0
>>
>> :: on a Rpi3b+  connected to a macbook air EFI spi programmer port i
>> recieved ::
>>
>> flashrom p1.0-87-g9891b75 on Linux 4.14.52-v7+ (armv7l)
>> flashrom is free software, get the source code at https://flashrom.org
>>
>> flashrom was built with libpci 3.5.2, GCC 6.3.0 20170516, little endian
>> Command line (5 args): flashrom -r /root/efi/read1.bin -V -p
>> linux_spi:dev=/dev/spidev0.0
>> Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
>> Initializing linux_spi programmer
>> Using device /dev/spidev0.0
>> linux_spi_init: Using value from /sys/module/spidev/parameters/bufsiz as
>> max buffer size.
>> linux_spi_init: max_kernel_buf_size: 4096
>> The following protocols are supported: SPI.
>> Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for AMIC A25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: probe_spi_rdid_generic: id1
>> 0x10, id2 0xdd0b
>> Probing for AMIC A25LQ64, 8192 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0x10, id2
>> 0xdd0b
>> Probing for Atmel AT25DF021A, 256 kB: probe_spi_rdid_generic: id1 0x10,
>> id2 0xdd0b
>> Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0x10,
>> id2 0xdd0b
>> Probing for Atmel AT25DF081, 1024 kB: prob

Re: [flashrom] join IRC

[Mike Banon]

Maybe it would've been easier to just tear down that PC and directly
connect to a BIOS chip (In-System Programming, using some test clip to
avoid the soldering, or maybe your chip is socketed so you could
remove it and insert to your hardware programmer). Although this way
requires you to have the external programmer, there are some models
like CH341A which could be got for really cheap ($2-$3 from China in
this case). And there is 100% confidence that this way will work,
regardless of your chipset and other factors

On Tue, Aug 7, 2018 at 12:14 PM, Владимир Амельянович
 wrote:
> Thank you for information.
> One more question.
> I have industrial PC, manufacturer didn't  provide any BIOS tool.
> When i run flashrom i get the warning about problems with unsupported
> laptops BIOSes and the following message:
> "Aborting.
> Error: Programmer initialization failed"
> I use command "flashrom -p internal"
> How could i fix it?
>
> 2018-08-06 14:17 GMT+03:00 Stefan Tauner :
>>
>> On Mon, 6 Aug 2018 10:07:47 +0300
>> Владимир Амельянович  wrote:
>>
>> > Hello.
>> > Please could you help me?
>> > I have chipset "Intel ICH7/ICH7R". It is marked as fully supported. I
>> > did
>> > the following steps 1) made backup 2) changed some setting(disable
>> > internal
>> > audio) 3) made backup again.  I made hexdump comparision of files from
>> > steps 1), 3) and there are no changes at all. What did i wrong?
>> >
>>
>> Hi,
>>
>> there is nothing wrong. On old boards such settings are often saved in
>> the CMOS NVRAM, which is not part of the flash memory.
>>
>> --
>> Kind regards/Mit freundlichen Grüßen, Stefan Tauner
>
>
>
> ___
> flashrom mailing list
> flashrom@flashrom.org
> https://mail.coreboot.org/mailman/listinfo/flashrom

___
flashrom mailing list
flashrom@flashrom.org
https://mail.coreboot.org/mailman/listinfo/flashrom

Re: [flashrom] Update bios (not full flash) with flashrom

[Mike Banon]

It could be that a manufacturer has released the same motherboards
with two various sizes of a BIOS chip. You could try padding your 256
KB image with FF's to increase its' size up to 512 KB and then flash
to the chip, after making a full backup ofcourse. Also you could look
through your existing backup, to see how much of your 512 KB image is
really occupied with anything thats not FF's, especially at the end.
Could use some simple hex editor like Okteta to quickly check this

On Tue, May 29, 2018 at 10:45 PM, Skoll RC  wrote:
> I have an external programmer and a full backup of my current bios. nothing
> writen, there was a label but it had to come off with time.
> How can I concatenate images? The update is not a full bios, is it?
> 
> De : David Hendricks 
> Envoyé : mardi 29 mai 2018 19:19
> À : Skoll RC
> Cc : flashrom@flashrom.org
> Objet : Re: [flashrom] Update bios (not full flash) with flashrom
>
> On Sun, May 27, 2018 at 11:44 AM, Skoll RC  wrote:
>> Hi everyone,
>>
>> I would like to update my GA-8I915P-MF's bios with flashrom but Gigabyte
>> only provide updates and no full bios so when I try to update with
>> flashrom -p internal -w 8i9pmf.f2 I have an error message: Error: Image
>> size
>> (262144 B) doesn't match the flash chip's size (524288 B)!
>> How can I fix it?
>
> That's unfortunate. Do you have an external programmer (something like
> a buspirate) that can be used in case things go wrong? Can you tell if
> there is anything written to the lower half of the chip? It could be
> as simple as concatenating the 256KB image to itself to create a 512KB
> image. But I wouldn't recommend trying that unless you have a good
> means of recovering.
>
> ___
> flashrom mailing list
> flashrom@flashrom.org
> https://mail.coreboot.org/mailman/listinfo/flashrom

___
flashrom mailing list
flashrom@flashrom.org
https://mail.coreboot.org/mailman/listinfo/flashrom

Re: [flashrom] ITE 8518 flashing through keyboard port

[Mike Banon]

> Directly flashing the SPI chip maybe be dangerous since the EC can interfere 
> unless the SPI chip is desoldered.

EC will not interfere if the board will be powered off, and you could
directly flash a SPI chip without desoldering by attaching a test clip
to it (which is connected to a flashrom-supported programmer like a
cheap CH341A). Examples of the instruction:
https://www.flashrom.org/ISP ,
http://dangerousprototypes.com/docs/Flashing_a_BIOS_chip_with_Bus_Pirate
(for CH341A its the same, just a connection scheme and flashrom
commands are a little bit different)

On Fri, May 25, 2018 at 9:06 AM, Curi0  wrote:
> Hi,
> I have a laptop with ITE 8518 and I want to try to port coreboot. The SPI
> flash chip is shared between the EC and BIOS and is connected to the ITE
> 8518. Directly flashing the SPI chip maybe be dangerous since the EC can
> interfere unless the SPI chip is desoldered.
>
> The ITE 8518 has a mode where the keyboard connector can be used a parallel
> port for flashing
> (http://www.recomb-omsk.ru/published/SC/html/scripts/doc/94689_datasheet_IT8512E_F_V0.4.1.pdf
> similar chip) but there isn't any information on the software required. This
> video (https://www.youtube.com/watch?v=GYedPOLiUOo) shows flashing the BIOS
> using a proprietary programmer software so it should be possible.
>
> So is there any way I could reverse engineer the parallel port if I don't
> have access to the ITE flashing software and the programmer in the video
> costs $150 and even if it could be reverse engineered there won't be any way
> to see the raw parallel port commands it sends.Possibly there are some
> documents floating on the internet with the information.
>
> Curi0
>
> ___
> flashrom mailing list
> flashrom@flashrom.org
> https://mail.coreboot.org/mailman/listinfo/flashrom

___
flashrom mailing list
flashrom@flashrom.org
https://mail.coreboot.org/mailman/listinfo/flashrom