Tried to flash but cannot commence flash with v1.2

[Stephen Wong]

Hello guys

i have a laptop equipped with GIGADEVICE chip, attached the photo for 
the ram chip

i can't seem to proceed with flashing the bios with flashrom version 1.2

i not sure if this chip being supported

wondering if it's supported or i did something wrong?

Thanks!

Stephen

[Angel Pons]

Hi Stephen,

On Tue, Aug 4, 2020 at 12:51 PM Stephen Wong  wrote:
> Hello guys
>
> i have a laptop equipped with GIGADEVICE chip, attached the photo for
> the ram chip

I don't see any RAM chip in the picture. That GigaDevice chip is a
flash chip, though. Looks like it's a 512 KiB (kibibytes) part.

Another interesting thing I see is the big square chip to the right of
the flash chip. Sure, I only see a small part of it, but it looks like
it says "ITE". It's probably an EC (Embedded Controller). If it is an
EC, then it's very likely that the flash chip is directly connected to
it, which makes in-circuit reflashing harder: powering the flash chip
often powers the EC as well, and the EC starts talking with the SPI
flash. Having two or more active masters on a SPI bus almost always
ends up badly (not working).
> i can't seem to proceed with flashing the bios with flashrom version 1.2
>
> i not sure if this chip being supported
>
> wondering if it's supported or i did something wrong?

Logs, logs, logs... What would we do without them? :P
You can append the `-o logfile.txt` command-line argument to your
flashrom command to generate a log file. Then, you can paste it on
paste.flashrom.org (or send it as an attachment, I don't really care)
so that we can see what exactly went wrong.

If you're using a Debian-based distribution and flashrom complains
about -o not being supported in standalone mode, add `-VV` instead and
copy the resulting output. If redirecting to a file, remember to also
redirect stderr!
> Thanks!
>
> Stephen
>
> flashrom mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

Best regards,
Angel

[Stephen Wong]

Hello

Appreciate your reply.
Let me try it up and get to you

Thanks!

Regards

Stephen

On 8/4/2020 9:26 PM, Angel Pons wrote:
> Hi Stephen,
>
> On Tue, Aug 4, 2020 at 12:51 PM Stephen Wong  wrote:
> > Hello guys
> >
> > i have a laptop equipped with GIGADEVICE chip, attached the photo for
> > the ram chip
>
> I don't see any RAM chip in the picture. That GigaDevice chip is a
> flash chip, though. Looks like it's a 512 KiB (kibibytes) part.
>
> Another interesting thing I see is the big square chip to the right of
> the flash chip. Sure, I only see a small part of it, but it looks like
> it says "ITE". It's probably an EC (Embedded Controller). If it is an
> EC, then it's very likely that the flash chip is directly connected to
> it, which makes in-circuit reflashing harder: powering the flash chip
> often powers the EC as well, and the EC starts talking with the SPI
> flash. Having two or more active masters on a SPI bus almost always
> ends up badly (not working).
> > i can't seem to proceed with flashing the bios with flashrom version 1.2
> >
> > i not sure if this chip being supported
> >
> > wondering if it's supported or i did something wrong?
>
> Logs, logs, logs... What would we do without them? :P
> You can append the `-o logfile.txt` command-line argument to your
> flashrom command to generate a log file. Then, you can paste it on
> paste.flashrom.org (or send it as an attachment, I don't really care)
> so that we can see what exactly went wrong.
>
> If you're using a Debian-based distribution and flashrom complains
> about -o not being supported in standalone mode, add `-VV` instead and
> copy the resulting output. If redirecting to a file, remember to also
> redirect stderr!
> > Thanks!
> >
> > Stephen
> >
> > flashrom mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
>
> Best regards,
> Angel