from:"Buhrow, Simon"

[flashrom] Re: new chip - GD25LR256E

2022-05-24 Thread Buhrow, Simon

> trying to add a new chip GigaDevices into flashchips.c, without success.

What did you try? What fails? Some more details are required…


Von: Igor Omelchenko 
Gesendet: Donnerstag, 19. Mai 2022 14:14
An: flashrom@flashrom.org
Betreff: [flashrom] new chip - GD25LR256E

Hello guys,
trying to add a new chip GigaDevices into flashchips.c, without success.
Can someone help me to add it.
Thanks.

trying something like this:
{
.vendor = "GigaDevice",
.name = "GD25LR256E",
.bustype = BUS_SPI,
.manufacture_id = GIGADEVICE_ID,
.model_id = GIGADEVICE_GD25LR256E,
.total_size = 32768,
.page_size = 256,
/* OTP: 1024B total, 256B reserved; read 0x48; write 0x42, erase 0x44 */
.feature_bits = FEATURE_WRSR_WREN | FEATURE_OTP,
.tested = TEST_UNTESTED,
.probe = probe_spi_rdid,
.probe_timing = TIMING_ZERO,
.block_erasers =
{
{
.eraseblocks = { {4 * 1024, 8192} },
.block_erase = spi_block_erase_20,
}, {
.eraseblocks = { {32 * 1024, 1024} },
.block_erase = spi_block_erase_52,
}, {
.eraseblocks = { {64 * 1024, 512} },
.block_erase = spi_block_erase_d8,
}, {
.eraseblocks = { {32 * 1024 * 1024, 1} },
.block_erase = spi_block_erase_60,
}, {
.eraseblocks = { {32 * 1024 * 1024, 1} },
.block_erase = spi_block_erase_c7,
}
},
.printlock = spi_prettyprint_status_register_bp4_srwd,
.unlock = spi_disable_blockprotect_bp4_srwd, /* TODO: 2nd status reg (read with 
0x35) */
.write = spi_chip_write_256,
.read = spi_chip_read, /* Fast read (0x0B) and multi I/O supported */
.voltage = {1695, 1950},}
--
Omelchenko Igor
0543-066-855
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: MX25L12833F

2022-05-02 Thread Buhrow, Simon

Hi,

it would be easier to help if you post the flashrom output.

However just guessing I would say you are running an old version (e.g. 1.2) of 
flashrom. The chip support was added last year. Since there was no new release 
since 1.2, probably you have to download (/clone) the current master branch 
manually.

Regards,

Simon



Von: Jon Bowen 
Gesendet: Samstag, 30. April 2022 10:24
An: flashrom@flashrom.org
Betreff: [flashrom] MX25L12833F

Hello and thank you for reading this email.
 I was told about your software over on the OpenWRT forums and I've gone as far 
as installing Ubuntu on a second drive to use it, building a windows image 
seemed beyond me.

 I'm trying to read and copy data from one nor chip to another on some access 
points I've bricked but sadly I'm a bit of an idiot.  I have a ch341a 
programmer which your software immediately found which was great, but it 
doesn't seem to read the MX25L12833F nor chips the access points are using does 
flashrom support this chip or was I informed incorrectly?
Hoping you can help
Many thanks JB
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: ERASE FAILED!

2022-04-06 Thread Buhrow, Simon

Hi Pascal,

did you check whether WP# pin (write protection) is passive?

Regards,

Simon

Von: Pascal Boidart 
Gesendet: Freitag, 1. April 2022 23:40
An: flashrom@flashrom.org
Betreff: [flashrom] ERASE FAILED!

Hello Flashrom,

I'm on latest Linux Mint.
programmer ch341a_spi
chip is a Macronix type MX25L6406E

I'm trying to erase a chip with: sudo flashrom --programmer ch341a_spi --erase 
-c "MX25L6406E/MX25L6408E"

And I'm getting a erase failed.
See log.
pascal@pascal-mini:~/Desktop/Flashrom$ sudo flashrom --programmer ch341a_spi 
--erase -c "MX25L6406E/MX25L6408E"
flashrom v1.2 on Linux 5.4.0-107-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 "MX25L6406E/MX25L6408E" (8192 kB, SPI) on ch341a_spi.
Erasing and writing flash chip... FAILED at 0x! Expected=0xff, 
Found=0x00, failed byte count from 0x-0x0fff: 0x1000
ERASE FAILED!
Looking for another erase function.
FAILED at 0x! Expected=0xff, Found=0x00, failed byte count from 
0x-0x: 0xfad7
ERASE FAILED!
Looking for another erase function.
FAILED at 0x! Expected=0xff, Found=0x00, failed byte count from 
0x-0x: 0xfad7
ERASE FAILED!
Looking for another erase function.
FAILED at 0x! Expected=0xff, Found=0x00, failed byte count from 
0x-0x007f: 0x6b7ef1
ERASE FAILED!
Looking for another erase function.
FAILED at 0x! Expected=0xff, Found=0x00, failed byte count from 
0x-0x007f: 0x6b7ef1
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!

Any idea?
Thanks
Pascal
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Questions regarding Easy project and GSoC

2022-04-01 Thread Buhrow, Simon

Hi Aarya,

> still felt a bit slow not as slow as before

Better than feeling is measuring ☺ . You could insert it into your code 
(https://review.coreboot.org/c/flashrom/+/47805) or you can just run 
https://linux.die.net/man/1/time .

> make it use the erase whole chip function and performed the erase operation 
> for the whole chip.

Check comments on https://review.coreboot.org/c/flashrom/+/58467 for some 
information about run time (see “random data”, this effects much the run time, 
depending on how many “FF” are present).

> For the "Optimise erase functions" project how are we supposed to measure the 
> efficiency of the algorithm?

Well with a given flash (and it´s erase times), a given state of flash and 
given data to be written a possible minimum run time can be calculated. However 
my understanding of this project is not to get the very last 1% in run time 
saving but the 10-30% for certain use cases. Furthermore it will be a trade-off 
efficiency vs. good code. So we have to discuss this in detail during the 
project. I think one hard request will be:: There should be no use case where 
the new algorithm yields increased run time.

> Also are there any other approaches that we can consider to optimize the 
> erase operations?

Not discussed yet (but there might be in some people mind). However feel free 
to think about other ways. But just have in mind that before putting too much 
effort on a solution discuss it to avoid disappointment. But for more detailed 
discussion we should wait until project starts (sorry to make you wait – I 
appreciate your curiosity! - , but this does not make much sense if finally 
there is no match you and the project).

Regards,

Simon

Von: Aarya Chaumal 
Gesendet: Donnerstag, 31. März 2022 23:00
An: Buhrow, Simon 
Cc: Anastasia Klimchuk ; flashrom@flashrom.org
Betreff: Re: [flashrom] Re: Questions regarding Easy project and GSoC

Hi Simon,

I tried to change the selection of the erase function to make it use the erase 
whole chip function and performed the erase operation for the whole chip. It 
still felt a bit slow not as slow as before (didn't feel a significant 
reduction in time). Is this normal?

For the "Optimise erase functions" project how are we supposed to measure the 
efficiency of the algorithm?
Also are there any other approaches that we can consider to optimize the erase 
operations?

Aarya.

On Tue, Mar 29, 2022 at 11:52 AM Buhrow, Simon 
mailto:simon.buh...@sieb-meyer.de>> wrote:
Hi Aarya,

so you are curious and went on. Very good.

To be honest, I do not know how overlapping regions would behave (I have never 
worked with layout files as this was not necessary for us yet). If you want 
just give it a try. Operations like this shouldn´t damage anything (if flashrom 
allows this at all).

Sorry, I´m not a native speaker, that´s why I´m not sure if “a look ahead 
algorithm” is a good choice of word. However you got it very right. What you 
have proposed is exactly what I wanted to say. ☺ This might sound like an easy 
task. However the current structure does not give much advantage to implement 
such thing, why the task results to be harder than it might look now.

It´s very good how far you got now. At the moment I do not have much more to 
say. Nevertheless if you have any further questions or discussions just let us 
know.

Regards,

Simon

Von: Aarya Chaumal mailto:aarya.chau...@gmail.com>>
Gesendet: Samstag, 26. März 2022 06:45
An: Buhrow, Simon 
mailto:simon.buh...@sieb-meyer.de>>
Cc: Anastasia Klimchuk mailto:a...@chromium.org>>; 
flashrom@flashrom.org<mailto:flashrom@flashrom.org>
Betreff: Re: [flashrom] Re: Questions regarding Easy project and GSoC

Hi Simon,

I performed (read, write, erase) on specific regions of the flash using the 
layout file. Do the regions in the layout file have to be exclusive or they can 
overlap?

Also, I'm not sure what a look ahead algorithm means. A brief search tells me 
it evaluates the effect of the procedure before doing it. Not sure how it is to 
be implemented.

I have the following approach in my mind. Keep using the largest erase function 
which erases just less than the region to be erased. For example, if we have to 
erase 200kB and have erase functions for 4kB,32kB,64kB. We would use the 64kB 
eraser three times first. Then the region left to be erased would be 8kB. Then 
we would use the 4kB eraser twice. Is this what you mean by look-ahead 
algorithm?

Aarya

On Thu, Mar 24, 2022 at 3:36 PM Buhrow, Simon 
mailto:simon.buh...@sieb-meyer.de>> wrote:
Hi Aarya,

sounds great. Very good that you got the programmer. And very good that you 
already dived into the code.

AFAICS you now have a good understanding of the problem to be solved. ☺ The 
details of how to implement a better solution is part of the project.

I think there is not much to do before the project starts (you understand the 
problem + you have got

[flashrom] Re: Questions regarding Easy project and GSoC

2022-03-29 Thread Buhrow, Simon

Hi Aarya,

so you are curious and went on. Very good.

To be honest, I do not know how overlapping regions would behave (I have never 
worked with layout files as this was not necessary for us yet). If you want 
just give it a try. Operations like this shouldn´t damage anything (if flashrom 
allows this at all).

Sorry, I´m not a native speaker, that´s why I´m not sure if “a look ahead 
algorithm” is a good choice of word. However you got it very right. What you 
have proposed is exactly what I wanted to say. ☺ This might sound like an easy 
task. However the current structure does not give much advantage to implement 
such thing, why the task results to be harder than it might look now.

It´s very good how far you got now. At the moment I do not have much more to 
say. Nevertheless if you have any further questions or discussions just let us 
know.

Regards,

Simon


Von: Aarya Chaumal 
Gesendet: Samstag, 26. März 2022 06:45
An: Buhrow, Simon 
Cc: Anastasia Klimchuk ; flashrom@flashrom.org
Betreff: Re: [flashrom] Re: Questions regarding Easy project and GSoC

Hi Simon,

I performed (read, write, erase) on specific regions of the flash using the 
layout file. Do the regions in the layout file have to be exclusive or they can 
overlap?

Also, I'm not sure what a look ahead algorithm means. A brief search tells me 
it evaluates the effect of the procedure before doing it. Not sure how it is to 
be implemented.

I have the following approach in my mind. Keep using the largest erase function 
which erases just less than the region to be erased. For example, if we have to 
erase 200kB and have erase functions for 4kB,32kB,64kB. We would use the 64kB 
eraser three times first. Then the region left to be erased would be 8kB. Then 
we would use the 4kB eraser twice. Is this what you mean by look-ahead 
algorithm?

Aarya

On Thu, Mar 24, 2022 at 3:36 PM Buhrow, Simon 
mailto:simon.buh...@sieb-meyer.de>> wrote:
Hi Aarya,

sounds great. Very good that you got the programmer. And very good that you 
already dived into the code.


AFAICS you now have a good understanding of the problem to be solved. ☺ The 
details of how to implement a better solution is part of the project.

I think there is not much to do before the project starts (you understand the 
problem + you have got hardware to test = you are quite ready to start). 
However if you are curious and want to do some more steps you are very welcome 
to do the following steps:

* Have a look at https://review.coreboot.org/c/flashrom/+/58467 , the comments 
will give you a deeper understanding of the problem and possible starting 
points (and by the way will show you that there are people willing to help 
kindly ☺ ). I think we are running into something like using a look-ahead 
algorithm to determine which erase-function to use.

* Get familiar with writing only certain regions of a flash (i.e. using a 
layout file) for better understanding of all the use cases

Just let us know if you got any further questions or ideas.

Regards,

Simon




Von: Aarya Chaumal mailto:aarya.chau...@gmail.com>>
Gesendet: Montag, 21. März 2022 22:16
An: Buhrow, Simon 
mailto:simon.buh...@sieb-meyer.de>>
Cc: Anastasia Klimchuk mailto:a...@chromium.org>>; 
flashrom@flashrom.org<mailto:flashrom@flashrom.org>
Betreff: Re: [flashrom] Re: Questions regarding Easy project and GSoC

Hi Simon,

I got my hardware yesterday and I played around with it and flashrom. I also 
studied the code flow for the erase functions. I saw that flashrom tries 
different erase functions given in the flashctx->chip->block_erasers[] by 
iterating through the list. Assuming these functions are in order of the length 
(number of sectors)  they erase, the first one would get selected most of the 
time as it erases the smallest length. But this would be inefficient as the 
function which erases more length would do the job faster although it might not 
give the required granularity. A better approach could be to use the latter (if 
necessary) until the remaining length is less than the length that this 
function can erase.

Aarya

On Wed, Mar 16, 2022 at 4:45 PM Buhrow, Simon 
mailto:simon.buh...@sieb-meyer.de>> wrote:
Hi Aarya,

nice progress!

I´m writing having "optimizing erase-function" in mint. However the following 
might apply fully or in parts to the other topic(s) as well:

As written to Hui Xiang:
As it´s never a good idea to experiment with the workhorse itself, I would 
recommend to do tests on extra hardware. (There might be some things you can 
test with software dummies, someone else must tell you about that). A very 
cheap programmer often mentioned here is the CH341A Programmer, however there 
are many other affordable programmers with ftdi chips, the raspberry pi and 
other manufactures as well (https://www.flashrom.org/Supported_programmers).
In addition you would need any supported Flash in a DIP package or a in 
SO-Package plus DIP-adapter.

[flashrom] Re: Questions regarding Easy project and GSoC

2022-03-24 Thread Buhrow, Simon

Hi Aarya,

sounds great. Very good that you got the programmer. And very good that you 
already dived into the code.

AFAICS you now have a good understanding of the problem to be solved. ☺ The 
details of how to implement a better solution is part of the project.

I think there is not much to do before the project starts (you understand the 
problem + you have got hardware to test = you are quite ready to start). 
However if you are curious and want to do some more steps you are very welcome 
to do the following steps:

* Have a look at https://review.coreboot.org/c/flashrom/+/58467 , the comments 
will give you a deeper understanding of the problem and possible starting 
points (and by the way will show you that there are people willing to help 
kindly ☺ ). I think we are running into something like using a look-ahead 
algorithm to determine which erase-function to use.

* Get familiar with writing only certain regions of a flash (i.e. using a 
layout file) for better understanding of all the use cases

Just let us know if you got any further questions or ideas.

Regards,

Simon

Von: Aarya Chaumal 
Gesendet: Montag, 21. März 2022 22:16
An: Buhrow, Simon 
Cc: Anastasia Klimchuk ; flashrom@flashrom.org
Betreff: Re: [flashrom] Re: Questions regarding Easy project and GSoC

Hi Simon,

I got my hardware yesterday and I played around with it and flashrom. I also 
studied the code flow for the erase functions. I saw that flashrom tries 
different erase functions given in the flashctx->chip->block_erasers[] by 
iterating through the list. Assuming these functions are in order of the length 
(number of sectors)  they erase, the first one would get selected most of the 
time as it erases the smallest length. But this would be inefficient as the 
function which erases more length would do the job faster although it might not 
give the required granularity. A better approach could be to use the latter (if 
necessary) until the remaining length is less than the length that this 
function can erase.

Aarya

On Wed, Mar 16, 2022 at 4:45 PM Buhrow, Simon 
mailto:simon.buh...@sieb-meyer.de>> wrote:
Hi Aarya,

nice progress!

I´m writing having "optimizing erase-function" in mint. However the following 
might apply fully or in parts to the other topic(s) as well:

As written to Hui Xiang:
As it´s never a good idea to experiment with the workhorse itself, I would 
recommend to do tests on extra hardware. (There might be some things you can 
test with software dummies, someone else must tell you about that). A very 
cheap programmer often mentioned here is the CH341A Programmer, however there 
are many other affordable programmers with ftdi chips, the raspberry pi and 
other manufactures as well (https://www.flashrom.org/Supported_programmers).
In addition you would need any supported Flash in a DIP package or a in 
SO-Package plus DIP-adapter.
There are several examples along the internet using flashrom and a programmer 
plus flash or target board with a soldered flash. Just pick any and start with 
that.

>> Can you suggest some tasks so that I can know more about these projects
> A question from me: have you tried to build and run flashrom from your local 
> repo source code?

Building flashrom is a good start. Furthermore possible steps to play a bit 
around would be this:
* Read a good article (e.g. wikipedia) about flash memory technology and 
understand why there are “block erase” functions (instead of byte wise erase).
* When you have done so and have any supported programmer plus flash at your 
hands (see above), take the datasheet of the flash and explore the parts about 
the different erase functions.
* Then try running erase (parts of or the entire) flash memory. Check (via 
debugging/print messages/verbose output) which block erase function is used.
* Compare the result with the best theoretical option derived from datasheet 
values. (“best” = fastest)

Hope this helps and you´ve got some dollars for the hardware. If anyone else 
has some thoughts about making progress without proposing a purchase, just let 
Aarya know.

Regards,

Simon

Von: Anastasia Klimchuk mailto:a...@chromium.org>>
Gesendet: Sonntag, 13. März 2022 07:45
An: flashrom@flashrom.org<mailto:flashrom@flashrom.org>; Aarya Chaumal 
mailto:aarya.chau...@gmail.com>>
Betreff: [flashrom] Re: Questions regarding Easy project and GSoC

Aarya,

Thank you so much for your patches, awesome work!

Don't worry about merging for now. Merging almost never happens immediately. 
Reviewers will come back to the patches, check that everything is fine, all the 
comments are resolved etc. If everything is alright, reviewers will approve and 
then at some point merge.
It can also happen that you get another iteration of comments: but don't worry 
this is a normal process!
From your side, you always (for now, and for future) need to understand all the 
comments, resolve and reply - once this is done, it

[flashrom] Re: Questions regarding Easy project and GSoC

2022-03-16 Thread Buhrow, Simon

Hi Aarya,

nice progress!

I´m writing having "optimizing erase-function" in mint. However the following 
might apply fully or in parts to the other topic(s) as well:

As written to Hui Xiang:
As it´s never a good idea to experiment with the workhorse itself, I would 
recommend to do tests on extra hardware. (There might be some things you can 
test with software dummies, someone else must tell you about that). A very 
cheap programmer often mentioned here is the CH341A Programmer, however there 
are many other affordable programmers with ftdi chips, the raspberry pi and 
other manufactures as well (https://www.flashrom.org/Supported_programmers).
In addition you would need any supported Flash in a DIP package or a in 
SO-Package plus DIP-adapter.
There are several examples along the internet using flashrom and a programmer 
plus flash or target board with a soldered flash. Just pick any and start with 
that.

>> Can you suggest some tasks so that I can know more about these projects
> A question from me: have you tried to build and run flashrom from your local 
> repo source code?

Building flashrom is a good start. Furthermore possible steps to play a bit 
around would be this:
* Read a good article (e.g. wikipedia) about flash memory technology and 
understand why there are “block erase” functions (instead of byte wise erase).
* When you have done so and have any supported programmer plus flash at your 
hands (see above), take the datasheet of the flash and explore the parts about 
the different erase functions.
* Then try running erase (parts of or the entire) flash memory. Check (via 
debugging/print messages/verbose output) which block erase function is used.
* Compare the result with the best theoretical option derived from datasheet 
values. (“best” = fastest)

Hope this helps and you´ve got some dollars for the hardware. If anyone else 
has some thoughts about making progress without proposing a purchase, just let 
Aarya know.

Regards,

Simon

Von: Anastasia Klimchuk 
Gesendet: Sonntag, 13. März 2022 07:45
An: flashrom@flashrom.org; Aarya Chaumal 
Betreff: [flashrom] Re: Questions regarding Easy project and GSoC

Aarya,

Thank you so much for your patches, awesome work!

Don't worry about merging for now. Merging almost never happens immediately. 
Reviewers will come back to the patches, check that everything is fine, all the 
comments are resolved etc. If everything is alright, reviewers will approve and 
then at some point merge.
It can also happen that you get another iteration of comments: but don't worry 
this is a normal process!
From your side, you always (for now, and for future) need to understand all the 
comments, resolve and reply - once this is done, it is the Reviewer's turn :)

It is very good that you identified two projects that are interesting for you. 
You will discuss a project in more detail with someone who plans to be Mentor 
for the project. Let me check who that will be.
Also, if someone who plans to be a Mentor for "optimizing erase-function" or 
"fixing endianness issues" is reading this, you can just reply :) What would be 
the best next steps for Aarya to prepare?

A question from me: have you tried to build and run flashrom from your local 
repo source code? To begin with you can run

flashrom -h

which is help information. It tells you all command line operations and 
arguments. It is served by cli_classic.c file.
So you can read about "erase" operation and then explore the code which 
implements it.

Meanwhile, just to check, have you read official resources from gsoc? These 
ones:
Student Guidelines https://google.github.io/gsocguides/student/
Rules https://summerofcode.withgoogle.com/rules (especially p.7)
And timeline https://developers.google.com/open-source/gsoc/timeline

Anastasia.

On Sun, Mar 13, 2022 at 1:44 PM Aarya Chaumal 
mailto:aarya.chau...@gmail.com>> wrote:
As suggested, I have been doing some of the easy projects till now and
I have enjoyed it. I have submitted a few patches till now and some of
them have gotten +2 code-reviews but still, they were not merged. Is
there anything that is required to get the changes to be merged?
Also, I have fixed most of the issues I got by running scan-build,
only 2 classes of issues were remaining which I feel are false
positives (showing underflow error but those cases won't occur or are
handled seprately) created by the tool and can be ignored.
As was going through your proposed projects for GSoC, I found
"optimizing erase-function" and "fixing endianness issues"
interesting and would like to do that in the summer. Can you suggest
some tasks so that I can know more about these projects and get an
idea of how to write my proposal for GSoC for doing this project?
Thanks :)

On Thu, Mar 10, 2022 at 10:45 AM Anastasia Klimchuk 
mailto:a...@chromium.org>> wrote:
>
> Hello Aarya,
>
> Nice to meet you! I think I saw your question on the IRC channel, and someone 
> replied, was that your question?
> Do you still

[flashrom] Re: Help !

2022-03-11 Thread Buhrow, Simon

Hi,

a possible problem could be signal integrity. That is: your wiring might 
cause/catch to much noise (s. below).

Here some hints:

# For electrical issues:
Do read operation several times and check for equality.
Touch the cable/wires before starting a new read operation. 
Just to check whether contacts are good.
If all reads give you the same file there shouldn´t be any problem at 
electrical level.
If you get diffs between the files you have an electrical problem -> check 
contacts, use as short wires as possible and try a lower frequency (if 
programmer supports this, do not overvalue the impact of frequency on total 
programming time, for some programmers most of the time is lost on other stages 
like usb communication etc.).

https://www.flashrom.org/Board_Testing_HOWTO

Hope this helps,

Simon


Von: Guillaume Rallon 
Gesendet: Freitag, 11. März 2022 11:27
An: flashrom@flashrom.org
Betreff: [flashrom] Help !

Hello,

 I request your help for a little problem.
I try to unbrick my MSI Gaming 5 Z97 motherboard, using flashrom using a 
raspberry Pi 4b vi the JSPI1 port.

I plugged it like this  :

Hold 0V  o oWP 3.3V
   x o
   o oGND
  CLK  o oCS
   SI-SO  o oSO-SI
   o o VCC


The plugin seems to be good as Flashrom detects the chipset as a Winbond 
W25Q64.V
The battery of the mother board is removed, no other external current source 
plugged.

When I launch the writing sequence everything  goes flawlessly and the problem 
appears during the flash verification. I receive this message : Verifying 
flash... FAILED at 0x0014! Expected=0x03, Found=0x02, failed byte count 
from 0x-0x007f: 0x3d6c96
Your flash chip is in an unknown state.

I tried to put HOLD at 3.3V and let the CMOS battery but it is always the same 
message.
Maybe my chipset has an internal defect ? If yes, I think I can buy a new chip 
and solder it but it's a brutal solution ;)

I would really be pleased if you could give me at least a clue.

Best regards

Guillaume RALLON


The whole messages are below :

flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 -w 
/home/Yogiadmin/flashrom/E7917IMS.190
flashrom v1.2-644-g79e2bd0 on Linux 5.10.92-v8+ (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 Winbond flash chip "W25Q64.V" (8192 kB, SPI) on linux_spi.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... FAILED at 0x0014! Expected=0x03, Found=0x02, failed byte 
count from 0x-0x007f: 0x3d6c96
Your flash chip is in an unknown state.
Please report this to the mailing list at 
flashrom@flashrom.org or
on IRC (see https://www.flashrom.org/Contact for details), thanks!



--
RALLON Guillaume
19 CHEMIN DE LA RETARDIERE
44700 ORVAULT
FRANCE
06 79 69 15 60
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Questions About Flashrom Of Gsoc

2022-03-11 Thread Buhrow, Simon

Hi Hui,

>> My current devices are a Windows 11 laptop (processor 11370H, Tiger 
>> Lake-H35) and a Mac. Is it possible for me to try out some patches on my 
>> computer? Also, could you provide me with any resources or introductions to 
>> chip packaging (DIP32, PLCC32, DIP8...)?

As it´s never a good idea to experiment with the workhorse itself, I would 
recommend to do tests on extra hardware. (There might be some things you can 
test with software dummies, someone else must tell you about that). A very 
cheap programmer often mentioned here is the CH341A Programmer, however there 
are many other affordable programmers with ftdi chips, the raspberry pi and 
other manufactures as well (https://www.flashrom.org/Supported_programmers).

About basics of packaging you can find on 
https://en.wikipedia.org/wiki/List_of_integrated_circuit_packaging_types . 
Flashrom itself typically does not care about packaging (as you can see in 
flashchips.c are no packaging info). That´s only important for wiring between 
programmer hardware and flash chip. If you have a programmer with a DIP-Socket 
on board, you can use any supported Flash in a DIP package (with <= pins than 
the socket).

>> and decided to start my job with "Find chips without voltage data." What can 
>> I do about it?

I checked the “.voltage” of the chips given in flashchips.c and I couldn´t find 
any chip without voltage data in flashchips.c So I think it´s obsolete. Could 
anyone with wr-permission correct this article? (or tell me where I´m wrong… 
:-) ).

>> Is it necessary for me to install an IRC client on my computer?

I think the webclient works fine so far, however there might be some benefits 
of having it installed locally.

Hope this helps,

Simon

Von: Anastasia Klimchuk 
Gesendet: Freitag, 11. März 2022 09:54
An: Hui Xiang ; flashrom 
Betreff: [flashrom] Re: Questions About Flashrom Of Gsoc

Hi Hui,

First of all, I wanted to say, you replied to me only and not to the mailing 
list (and I only noticed now). Most likely you clicked the "Reply" button 
instead of "Reply All". I am adding the mailing list back, but for future 
please keep in mind to Reply All.
The most important reason is that if you send your questions to the mailing 
list, then everyone in our community can help you! Which is really good. You 
will have various questions, and you never know who is the best person to 
answer. So, pay attention that the mailing list is on the To line ;)

Some things I can answer:

>> The platform Gerrit is mentioned in the "Development Guidelines." All I know 
>> about it is that it is a code management tool. Are there any tutorial videos 
>> or articles that I can use to learn more about Gerrit?

Gerrit is also a code review tool. Gerrit has an official website with lots of 
presentations, look here https://www.gerritcodereview.com/presentations.html , 
hopefully that's useful!

>> I went to GitHub's official Flashrom mirror.

You can browse all code on GitHub, no problem, and yes it can be a convenient 
way to browse. Just keep in mind GitHub is a mirror, so that's pretty much only 
for browsing code. When you start with trying to make changes by yourself, you 
need to set up flashrom git repository locally. When you come to that point, 
open https://review.coreboot.org/admin/repos/flashrom and choose your desired 
method to clone the repository. Supported methods are HTTPS and SSH. The same 
method will also be used when you push your changes to Gerrit later.

>> My current devices are a Windows 11 laptop (processor 11370H, Tiger 
>> Lake-H35) and a Mac. Is it possible for me to try out some patches on my 
>> computer? Also, could you provide me with any resources or introductions to 
>> chip packaging (DIP32, PLCC32, DIP8...)?

I am wondering if someone else can take these questions? We need community help 
on this :)

Thanks!

On Thu, Mar 10, 2022 at 6:59 AM Hui Xiang 
mailto:zavier2...@outlook.com>> wrote:

Dear Anastasia,

Thank you for your response. I read the "Contributor Guidelines" and have some 
questions.

>> "work with our git repository."

I went to GitHub's official Flashrom mirror. The repository contains a large 
number of files. Which file would you recommend I start with if I want to 
familiarize myself with the current codes on GitHub? The platform Gerrit is 
mentioned in the "Development Guidelines." All I know about it is that it is a 
code management tool. Are there any tutorial videos or articles that I can use 
to learn more about Gerrit?

>> "downloaded and built flashrom as well as applied some patches."

My current devices are a Windows 11 laptop (processor 11370H, Tiger Lake-H35) 
and a Mac. Is it possible for me to try out some patches on my computer? Also, 
could you provide me with any resources or introductions to chip packaging 
(DIP32, PLCC32, DIP8...)? I looked them up on Google, but there is not much 
information about them.

>> "Check Easy projects or ask for simple tasks on the mailing

[flashrom] Re: Experimental GD25Q40(B) support

2022-03-09 Thread Buhrow, Simon

Thanks,

I marked the chip as tested.

https://review.coreboot.org/c/flashrom/+/62712

Regards,

Simon

-Ursprüngliche Nachricht-
Von: Wolf Dieter Brandt  
Gesendet: Montag, 7. Februar 2022 22:34
An: flashrom@flashrom.org
Betreff: [flashrom] Experimental GD25Q40(B) support


___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: EN25F10 read/write support log files

2022-03-09 Thread Buhrow, Simon

Thanks Wolf Dieter,

you posted similar information last summer. And it was added soon: 

https://review.coreboot.org/c/flashrom/+/58031 

Looks like you are working with the same version. There is no newer release 
than 1.2 yet, but if you want to you can get the current master branch:
Clone: https://review.coreboot.org/flashrom.git

Regards,

Simon
 


-Ursprüngliche Nachricht-
Von: Wolf Dieter Brandt  
Gesendet: Montag, 7. Februar 2022 11:27
An: flashrom@flashrom.org
Betreff: [flashrom] EN25F10 read/write support log files

Here you go! 

Thanks fro this great tool!



___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Erase Failed - MX25L12805D, MX25L12835F/...

2022-03-09 Thread Buhrow, Simon

Hi Dean,

if reading works and erasing fails that sounds to me like there is any Block 
Protect or similar setting.

Regards,

Simon

Von: dean rooney 
Gesendet: Sonntag, 30. Januar 2022 22:14
An: flashrom@flashrom.org
Betreff: [flashrom] Erase Failed - MX25L12805D, MX25L12835F/...


Hello,



I am trying to fix a bricked motherboard (Z170A Mpower Gaming Titanium).

The motherboard does have a MX25L12873F (not seen on your supported list) but 
does have the MX25L12805D and MX25L12835F/MX25L12845E/MX25L12865E as similar 
chips.



I am using flashrom on a Raspberry Pi 3 and had gotten quite far using the 
forums until I came across "ERASE FAILED".

I am able to read the chip, but I am unable to write as it has this Erase 
Failed appears every time.



I'm not sure if there is a work around. I've seen the -f force erase but I'm 
not aware how to use this function.



Any help would be greatly appreciated.



Kind Regards,

Dean
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Call for Mentors for GSoC 2022

2022-01-31 Thread Buhrow, Simon

Hi Felix,

feel free to do so. It´s a good idea to collect this type of information in the 
document.

Regards,

Simon

-Ursprüngliche Nachricht-
Von: Felix Singer  
Gesendet: Samstag, 29. Januar 2022 08:10
An: Buhrow, Simon ; Anastasia Klimchuk 
; flashrom 
Betreff: Re: [flashrom] Re: Call for Mentors for GSoC 2022

On Fri, 2022-01-28 at 08:29 +, Buhrow, Simon wrote:
> Overall I liked to read the topic “Optimize Erase-Function Selection”. 
> I´d like to support this enhancement. I.e. I can´t do the “mentor” 
> job, however I can do code review, real HW-testing and similar actions 
> supporting the mentor and/or contributor.
>  
> So when there will be a mentor for this topic, he/she is welcome to 
> get in touch with me to see if/how I can help.

Hi Simon,

thank you for reaching out and for offering your help!

Would you mind if we add a note to the document that you can help out with code 
reviews and things?

// Felix

___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Call for Mentors for GSoC 2022

2022-01-28 Thread Buhrow, Simon

Hi Anastasia,

thanks to you and all the brainstormers. Sounds good so far.

Overall I liked to read the topic “Optimize Erase-Function Selection”. I´d like 
to support this enhancement. I.e. I can´t do the “mentor” job, however I can do 
code review, real HW-testing and similar actions supporting the mentor and/or 
contributor.

So when there will be a mentor for this topic, he/she is welcome to get in 
touch with me to see if/how I can help.

Regards,

Simon



Von: Anastasia Klimchuk 
Gesendet: Dienstag, 25. Januar 2022 12:31
An: flashrom 
Cc: Felix Singer 
Betreff: [flashrom] Call for Mentors for GSoC 2022

Good Day Flashrom People!

As you might know already, we are currently preparing an application for GSoC 
2022 (also known as Google Summer of Code, 
FAQ). We have gathered a 
list of Project Ideas, and it's time to call for Mentors!
If you are interested in being a Mentor, please let us know. If you want to 
help, but not sure you can be a Mentor yourself, you can be a secondary Mentor. 
Or you can help by doing code reviews.

Have a look into our Projects ideas, are you interested to Mentor one of these 
projects?
https://docs.google.com/document/d/1AxMobB2v8Dv2uUwZPZ_vCmmONYDJuliHcnjfWOs4qIs/edit?usp=sharing
Or maybe you have another project idea that you want to mentor? Great!

GSoC runs by a timeline 
https://developers.google.com/open-source/gsoc/timeline, check that dates are 
OK for you.

How to let us know if you are interested: Reply All to this email. If you are 
in doubt, you can contact me (Anastasia/aklm) directly.

Some more useful information:

Mentor responsibilities (short) 
https://developers.google.com/open-source/gsoc/help/responsibilities#mentor_responsibilities

Mentor guides (long, lots of details)
https://google.github.io/gsocguides/mentor/

If you have any questions, you are welcome to ask! ;)

Your GSoC Org Admin,
Anastasia.
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Found Eon flash chip "EN25F10" (128 kB, SPI) on ch341a_spi (UNTESTED)

2021-09-29 Thread Buhrow, Simon

Thanks for the info.

Merge-Request is created:
https://review.coreboot.org/c/flashrom/+/58031

Regards,
Simon

Von: Wolf Dieter Brandt 
Gesendet: Montag, 9. August 2021 20:34
An: flashrom@flashrom.org
Betreff: [flashrom] Found Eon flash chip "EN25F10" (128 kB, SPI) on ch341a_spi 
(UNTESTED)

Reading and writing to this chip worked, did several test with writing and read 
and compare using files system tools.

Thanks for your great work!

---


Write Log:


me@iMac % flashrom --programmer ch341a_spi -w O.rom
flashrom v1.2 on Darwin 20.6.0 (x86_64)
flashrom is free software, get the source code at https://flashrom.org

Calibrating delay loop... OK.
Found Eon flash chip "EN25F10" (128 kB, SPI) on ch341a_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... Erase/write done.
Verifying flash... VERIFIED.
me@iMac %

Read Log:

me@iMac % flashrom --programmer ch341a_spi -r A.rom
flashrom v1.2 on Darwin 20.6.0 (x86_64)
flashrom is free software, get the source code at https://flashrom.org

Calibrating delay loop... OK.
Found Eon flash chip "EN25F10" (128 kB, SPI) on ch341a_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 flash... done.
me@iMac %







___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: MX25L6433F chip is not supported

2021-09-29 Thread Buhrow, Simon

Hi,

depending on your background feel free to add a new "database entry" by 
yourself:

https://www.flashrom.org/Development_Guidelines -> Sending a patch + 
Adding/reviewing a new flash chip
tells you how to do.

Regards,

Simon


Von: Joaquin Linares 
Gesendet: Samstag, 21. August 2021 22:32
An: flashrom@flashrom.org
Betreff: [flashrom] MX25L6433F chip is not supported

Hi there.

The MX25L6433F chip is not supported.

They would be so kind to correct the problem.
Thank you so much.





Joaquin Linares
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Choosing a bigger erase block size

2021-09-27 Thread Buhrow, Simon

Hi,

choosing the best fitting erase block size can safe a significant amount of 
runtime. That´s why I would like to check if this can be improved.

Just to get the right starting point, here some thoughts to be discussed from 
my point of limited view: As I understand the code, the algorithm for standard 
erase operation (e.g. before writing some random data) is this: 

1) take the first entry of `flash->chip->block_erasers`
2) try to erase using this parameters
3) if check_block_eraser() fails try the next entry of 
`flash->chip->block_erasers`

In this case the first entry given to `block_erasers` in `flashchips.c` is as 
the default entry used for erase operation for the given flashchip. As the 
first entry normally goes with the least block size this should work in almost 
every case. But on the other hand this is generally the worse choice regarding 
to run time if a erase operation with a bigger erase size would do the job as 
well.

A) Would it be reasonable to just change the order and go from the bigger block 
size to lower block size? So the biggest size block erase operation is handled 
as a default and only in case it does not fit an erase operation with lower 
block size is used.

I might have overseen some important aspects, so here just some other options:
B) Make `block_eraser` entry selectable via cmd line parameter
C) Add timing values of erase operations to flashchips.c and calculate and 
choose best runtime 


Let me know what do you think.

Regards,
Simon

Simon Buhrow
SIEB & MEYER AG
21339 Lüneburg
Germany
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: SFDP autodetected flash chip p25q80h

2021-02-15 Thread Buhrow, Simon

Hi Michael,

thanks.

Did you succesfully read and write the chip?

Depending on your background feel free to add a new “database entry” by 
yourself:
https://www.flashrom.org/Development_Guidelines -> Sending a patch + 
Adding/reviewing a new flash chip 
tells you how to do.

Regards,
Simon


-Ursprüngliche Nachricht-
Von: Michael Kerscher  
Gesendet: Sonntag, 10. Januar 2021 12:02
An: flashrom@flashrom.org
Betreff: [flashrom] SFDP autodetected flash chip p25q80h

Hello,

I wanted to read/write a chip "p25q80h" with flashrom and a ch341a programmer 
and flashrom told me to help you by mailing the attached output to this address 
to add the chip.

If you need more information, feel free to reach out to me.

best regards,
Michael Kerscher

___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: HDD in-circuit reprogramming

2021-02-03 Thread Buhrow, Simon

Hi,

what does „other chips work fine” mean? With the same WD HDD setup? Or on other 
HDDs/Boards?

Which programmer are you using?
Could you provide a logfile with the output of flahrom when trying to detect 
the chip and running with the –V parameter?

> Will supplying power through 3.3V Vcc and SATA connector at same time fry the 
> chip?
It should not. If SATA is 3.3V as well (not sure if SATA uses 5V?) and you 
connect the Ground there should not be fried nothing. But on the other hand I´m 
not sure if this is your real issue. Better you do steps mentioned above first.

Regards,

Simon


Von: Thomasheidler via flashrom 
Gesendet: Samstag, 2. Januar 2021 11:48
An: flashrom@flashrom.org
Betreff: [flashrom] HDD in-circuit reprogramming

Hi

I need to reprogram the firmware on a WD HDD with SOIC8 Winbond chip supported 
by flashrom. I tried reading in-circuit but my programmer does not detect it 
(other chips work fine). Probably other components are drawing voltage so I 
disconnected Vcc and tried to power it through regular SATA connectors which 
didn't work. Do you have any recommendations how to workaround this issue? Will 
supplying power through 3.3V Vcc and SATA connector at same time fry the chip?

Thanks for your help
Tom
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: bios flash

2021-02-03 Thread Buhrow, Simon

Hi Justin,

sounds to mea s you´ve got problem with the signal quality.
i.e. check your cable setting. Make sure contacts are good and cable length as 
short as possible (if they are quite long but you can´t shorten them:  drill 
the whole cable to get the wires tight one to each other)

Before updating I would always make sure that reading works fine. i.e. run 
reading twice and compare read results. Only if they do not differ, I´d 
recommend to write.

Regards,

simon

Von: Justin Eazy Cheeze 
Gesendet: Mittwoch, 23. Dezember 2020 00:15
An: flashrom@flashrom.org
Betreff: [flashrom] bios flash

Hi I tried bios flashing and it ran perfectly till it verified at the end of 
writing the flash

C:\Users\Justin Hardy\Desktop\Flashrom_v1.2_St1cky>flashrom -w FLASH.ROM -p busp
irate_spi:dev=COM5,spispeed=1M
flashrom v1.2 on Windows 6.1 (x86_64)
flashrom is free software, get the source code at https://flashrom.org

Calibrating delay loop... OK.
Found Winbond flash chip "W25Q32.V" (4096 kB, SPI) on buspirate_spi.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... FAILED at 0x0060! Expected=0x00, Found=0x01, failed byte
count from 0x-0x003f: 0xc0af
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!

C:\Users\Justin Hardy\Desktop\Flashrom_v1.2_St1cky>

At first I got a fail reading because I disconnected it somehow, then it worked 
and got this at the very end thanks!
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Information function read

2021-02-03 Thread Buhrow, Simon

Hi Lukas,

hanging while reading is a bit strange but not impossible.

Please use the newest dev version:
git clone https://github.com/flashrom/flashrom.git

And build it at your own
(something like: navigate to the resulting flashrom directory, and do:
make
make install
)

After doing so run it again and check if problem still exists.

Btw: Before updating I would always make sure that reading works fine. i.e. run 
reading cmd twice and compare read results. Only if they do not differ, I´d 
recommend to write.

Regards,

Simon

Von: Lukas Augustin 
Gesendet: Freitag, 18. Dezember 2020 18:33
An: flashrom@flashrom.org
Betreff: [flashrom] Information function read

Hi,

I would like to ask about read parametr. I have PC HP All-in-one and after 
change SSD disk PC blackout, not even logo shown up, so i found instructions 
how to write newer bios(because led double flash and that me bios corrupted) 
using Arduino UNO to ROM_RECOVER bus.Firstly I try backup old ROM used command: 
sudo flashrom -p serprog:dev=/dev/ttyACM0:115200 -r old.ROM and after that I 
saw serial line sending data but after 10 minutes LED TX turn off and at 
Terminal is still Reading flash after 30minute waiting nothing happend. 
Will you advise me?

Thank you,

in attachment is picture of terminal
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Humble request for advice

2021-02-03 Thread Buhrow, Simon

Are you still at that point, mentioned below?

If yes: Send a logfile of flashrom output (-V). This would make it easier to 
help.

Regards,

Simon

Von: sergiy rospysdiyenko 
Gesendet: Samstag, 12. Dezember 2020 11:40
An: flashrom@flashrom.org
Betreff: [flashrom] Humble request for advice

Greetings!

Thanks for creating such wonderful tool.

i would like to ask for a suggestion as developers of the tool will be the best 
one to ask.
Basically i am trying to flash efi chip on imac, micronix MX25L6406E/MX25L6408E 
but just can't get any readings
i got an working macbook with same chip and once i connect to it, everything 
works like charm. i was able to read file from working macbook 10 times(8/10 
checksum matched!). So i can assume my setup is correct! But no luck reading 
same chip from imac motherboard.

Could you please suggest anything?

Could it be that:
 1) because chip is on password locked chip is not readable? (doesn't make 
sense though, right?)
 2) maybe chip is faulty? which is very unlikely
  3) could it be because chip is on motherboard and unsoldering it would 
help?
  4) i am currently reading chip with  sudo flashrom -r oldefi1.bin -V -p 
linux_spi:dev=/dev/spidev0.0
maybe there is some additional arguments, i should try.


Regards,

Sergio
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Info for W25Q16BVSSIG

2020-11-09 Thread Buhrow, Simon

Hi Berké,

your "problem" is that you get a GigDevice and not the expected Winbond 
detection, right?

The ID found is: id1 0xc8, id2 0x4015
The windbond should have (as mentioned in the datasheet):  id1 0x14, id2 0x4015
So they differ in the id1 value.

As 0xc8 and 0x14 differ in many bits I assume that everything is fine and the 
correct ID is 0xc8.

That´s why I´d like to ask: Where did you get the information that make you 
expect a Winbond chip from? Did you get it from a Olimex-Datasheet or did you 
read the chip name from the chip case itself?

Btw: There is a newer version of flashrom. It´s never a bad idea to use the new 
one to reduce problems. ( https://www.flashrom.org/Flashrom/1.2 ) 

Regards,

Simon


-Ursprüngliche Nachricht-
Von: Berké Durak  
Gesendet: Sonntag, 1. November 2020 09:54
An: flashrom@flashrom.org
Betreff: [flashrom] Info for W25Q16BVSSIG

Hi,

This is the flashrom -VV output for the W25Q16BVSSIG chip as found on the 
Olimex iCE40HX8K-EVB evaluation board.

From the Debian flashrom 1.0-1 armhf on the SPI pins of a Beaglebone Black, 
with the command :

  flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1 -VV >flashrom.info
--
Berké Durak, Ph.D
ExH R
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: failed flashing ROM on a Dell E7270

2020-11-09 Thread Buhrow, Simon

Hi Richard,

just some generic advices (may be someone else has better ones for your 
specific hardware set):

For chip handling issues:
https://www.flashrom.org/Board_Testing_HOWTO

For electrical issues:
Do read operation several times and check for equality.
Touch the cable/wires before starting a new read operation. Just to 
check whether contacts are good.
If all reads give you the same file there shouldn´t be any problem at 
electrical level. 
If you get diffs between the files you have an electrical problem -> check 
contacts, use as short cables/wires as possible and try a lower frequency (if 
programmer supports this, do not overvalue the impact of frequency on total 
programming time, for some programmers most of the time is lost on other stages 
like usb communication etc.).


Good luck and feel free to put further questions,

Simon


-Ursprüngliche Nachricht-
Von: Richard Horsch  
Gesendet: Montag, 9. November 2020 20:42
An: flashrom@flashrom.org
Betreff: [flashrom] failed flashing ROM on a Dell E7270

Dear all,

I miss-flashed my BIOS on a Dell Latitude E7270 somehow.
So I tried to reflash the chip with flashrom, but it faild.

I was asked to report this to you.
The terminal tells me following:

"
flashrom v1.2 on Linux 5.4.0-52-generic (x86_64) Using clock_gettime for delay 
loops (clk_id: 1, resolution: 1ns).
Found GigaDevice flash chip "GD25Q127C/GD25Q128C" (16384 kB, SPI) on ch341a_spi.
Reading old flash chip contents... done.
Erasing and writing flash chip... FAILED at 0x00f5d000! Expected=0xff, 
Found=0x40, failed byte count from 0x00f5d000-0x00f5dfff: 0x1000 ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
FAILED at 0x0010! Expected=0xff, Found=0x00, failed byte count from
0x-0x7fff: 0x4732
ERASE FAILED!
Reading current flash chip contents... done. Looking for another erase function.
Erase/write done.
Verifying flash... FAILED at 0x0008b500! Expected=0xda, Found=0xff, failed byte 
count from 0x-0x00ff: 0xf0137 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!
"

Is there anything, what could be done further?
Thanks and kind regards,

Richard


--
Richard Horsch
Christian-Steiner-Str. 9
63762 Großostheim

Tel.: +49 6026 949 3820
Mob.: +49 179 144 8160
Fax.: +49 6026 949 3821
___
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

2020-09-24 Thread Buhrow, Simon

Thanks for your e-mail.

Did anyone already answered you?
In case that not:
Depending on your background feel free to add a new "database entry" by 
yourself:

https://www.flashrom.org/Development_Guidelines -> Sending a patch + 
Adding/reviewing a new flash chip
tells you how to do.

If you don´t have any programming skills, no problem: Someone else can do it, 
when there´s time.

Regards,
Simon



Von: Michael S 
Gesendet: Donnerstag, 27. August 2020 23:57
An: flashrom@flashrom.org
Betreff: [flashrom] XM25QH64A

Hi,

Just tried to read an XMC SPI chip (XM25QH64A) and had the request to submit 
this as it wasn't officially supported yet, please see below. Upon multiple 
read attempts, other than the first one, the resulting files were identical 
when repeated and checked with diff, it was tested in situ with an SOIC clip 
and a raspberry pi as a 'reader'.


flashrom -p linux_spi:dev=/dev/spidev0.1,spispeed=512 -VV
flashrom v0.9.9-r1954 on Linux 4.19.66-v7+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

flashrom was built with libpci 3.3.1, GCC 5.3.1 20160205, little endian
Command line (3 args): flashrom -p linux_spi:dev=/dev/spidev0.1,spispeed=512 -VV
Calibrating delay loop... OS timer resolution is 1 usecs, 697M loops per 
second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 999 us, 1 myus = 
10005 us, 4 myus = 4 us, OK.
Initializing linux_spi programmer
Using device /dev/spidev0.1
Using 512 kHz clock
The following protocols are supported: SPI.
Probing for AMIC A25L05PT, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for AMIC A25L05PU, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for AMIC A25L10PT, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for AMIC A25L10PU, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for AMIC A25L20PT, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for AMIC A25L20PU, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for AMIC A25L40PT, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for AMIC A25L40PU, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for AMIC A25L80P, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for AMIC A25L16PT, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for AMIC A25L16PU, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for AMIC A25L512, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for AMIC A25L010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for AMIC A25L020, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for AMIC A25L040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for AMIC A25L080, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for AMIC A25L016, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for AMIC A25L032, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for AMIC A25LQ16, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for AMIC A25LQ032/A25LQ32A, 4096 kB: probe_spi_rdid_generic: id1 0x20, 
id2 0x7017
Probing for AMIC A25LQ64, 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for Atmel AT25DF021, 256 kB: probe_spi_rdid_generic: id1 0x20, id2 
0x7017
Probing for Atmel AT25DF041A, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 
0x7017
Probing for Atmel AT25DF081, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 
0x7017
Probing for Atmel AT25DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 
0x7017
Probing for Atmel AT25DF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 
0x7017
Probing for Atmel AT25DF321, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 
0x7017
Probing for Atmel AT25DF321A, 4096 kB: probe_spi_rdid_generic: id1 0x20, id2 
0x7017
Probing for Atmel AT25DF641(A), 8192 kB: probe_spi_rdid_generic: id1 0x20, id2 
0x7017
Probing for Atmel AT25DL081, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 
0x7017
Probing for Atmel AT25DL161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 
0x7017
Probing for Atmel AT25DQ161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 
0x7017
Probing for Atmel AT25F512, 64 kB: probe_spi_at25f: id1 0x00, id2 0x00
Probing for Atmel AT25F512A, 64 kB: probe_spi_at25f: id1 0x00, id2 0x00
Probing for Atmel AT25F512B, 64 kB: probe_spi_rdid_generic: id1 0x20, id2 0x7017
Probing for Atmel AT25F1024(A), 128 kB: probe_spi_at25f: id1 0x00, id2 0x00
Probing for Atmel AT25F2048, 256 kB: probe_spi_at25f: id1 0x00, id2 0x00
Probing for Atmel AT25F4096, 512 kB: probe_spi_at25f: id1 0x00, id2 0x00
Probing for Atmel AT25FS010, 128 kB: probe_spi_rdid_generic: id1 0x20, id2 
0x7017
Probing for Atmel AT25FS040, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 
0x7017
Probing for Atmel AT26DF041, 512 kB: probe_spi_rdid_generic: id1 0x20, id2 
0x7017
Probing for Atmel AT26DF081A, 1024 kB: probe_spi_rdid_generic: id1 0x20, id2 
0x7017
Probing for Atmel AT26DF161, 2048 kB: probe_spi_rdid_generic: id1 0x20, id2 
0x7017
Probing

[flashrom] Re: (no subject)

2020-08-17 Thread Buhrow, Simon

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] Re: reporting a message

2020-05-20 Thread Buhrow, Simon

Hi,

here just some general information/advice:

Use the latest flashrom version (current version 1.2: 
https://www.flashrom.org/Flashrom/1.2 )

For chip handling issues:
https://www.flashrom.org/Board_Testing_HOWTO

For electrical issues:
Do read operation several times and check for equality.
Touch the cable/wires before starting a new read operation in 
order to find out if the contacts are good.
If all reads give you the same file there shouldn´t be any problem at 
electrical level.
If you get diffs between the files you have an electrical problem -> check 
contacts, use as short cables/wires as possible and try a lower frequency (if 
programmer supports this; do not overvalue the impact of frequency on total 
programming time, for some programmers most of the time is lost on other stages 
like usb communication etc. ). Check again with several read runs.

Regards,

Simon


Von: Sandro C 
Gesendet: Dienstag, 19. Mai 2020 12:48
An: flashrom@flashrom.org
Betreff: [flashrom] reporting a message

Hello, I would like to put a message I keep on getting.
The bios nowadays is not working fine any longer, and the laptop doesn't boot, 
clearly.

#=#=#=#=#=#=#=#=
Erase/write done.
Verifying flash... FAILED at 0x! Expected=0x5a, Found=0x00, failed byte 
count from 0x-0x007f: 0x10c3
Your flash chip is in an unknown state.
#=#=#=#=#=#=#=#=

I would be very happy to get some kind of help, and since I am a newbie, it 
would be great if you feel ready even just to address me to the most relevant 
web pages.
The job is focused on flashing a 16 pin mx bios chip on a lenovo laptop model 
x200, for the use of a specific firmware called LibreBoot.

Many thanks again,

Sandro
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Is this an Error? Problem flashng.

2020-05-20 Thread Buhrow, Simon

Hi,

here just some general information/advice:

Use the latest flashrom version (current version 1.2: 
https://www.flashrom.org/Flashrom/1.2 )

For chip handling issues:
https://www.flashrom.org/Board_Testing_HOWTO

For electrical issues:
Do read operation several times and check for equality.
Touch the cable/wires before starting a new read operation in 
order to find out if the contacts are good.
If all reads give you the same file there shouldn´t be any problem at 
electrical level.
If you get diffs between the files you have an electrical problem -> check 
contacts, use as short cables/wires as possible and try a lower frequency (if 
programmer supports this; do not overvalue the impact of frequency on total 
programming time, for some programmers most of the time is lost on other stages 
like usb communication etc. ). Check again with several read runs.

Regards,

Simon


Von: Nikos Mouzakitis 
Gesendet: Dienstag, 19. Mai 2020 13:33
An: flashrom@flashrom.org
Betreff: [flashrom] Is this an Error? Problem flashng.

Hello this is my output when trying to flash..

Does Incomplete/failed Command Receive Device string plays a role on
the error of verification?
I cannot flash back the original bios contents at the moment on my board.

flashrom v0.9.9-r1954 on Linux 4.15.0-88-generic (x86_64)
flashrom is free software, get the source code at https://flashrom.org

Calibrating delay loop... OK.
Setting voltage to 1800 mV
Incomplete/failed Command Receive Device String!
Found Winbond flash chip "W25Q64.V" (8192 kB, SPI) on dediprog.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... FAILED at 0x0010! Expected=0x5a, Found=0xff, failed byte 
count from 0x-0x007f: 0x2ddb74
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] Re: W25Q256JWEQ 1.8V

2020-04-27 Thread Buhrow, Simon

Hi Nicklas,

well, at least you don´t have a good (enough) connection to the chip.

Check your log file: "probe_spi_rdid_generic:" should give you the same ID as 
given in the datasheet of your chip. Further it should give you always the same 
value.
As the value changes a lot, it seems that you have bad cable connections or an 
signal integrity problem.
Check the cables/cable connections and try with a lower frequency if the 
programmer supports this. Try with cables as short as possible as well.

Regards,

Simon




-Ursprüngliche Nachricht-
Von: Nicklas Lennert  
Gesendet: Dienstag, 21. April 2020 15:49
An: flashrom@flashrom.org
Betreff: [flashrom] W25Q256JWEQ 1.8V

Hi.


I'm trying to flash bios to a motherboard MSI B450M-A PRO MAX.

I have connected to the "new type" JSPI1 connectors.

Think i have a connection to the chip, but its not listed on your chip list. 
Gets a response only once every time i power up the chip.

I use a CH341A PRO programmer with a 1.8V converter. Then connected wires 
directly to the motherboard. No unsoldering. Ubuntu 18.04.4 LTS



https://www.winbond.com/resource-files/w25q256jw%20spi%20revb%2012082017.pdf

https://forum-en.msi.com/index.php?topic=322528.0 - Connected by this 
diagram


Can you help me?

Best regards

Nicklas Lennert

Denmark

___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Error when flashing BIOS

2020-04-17 Thread Buhrow, Simon

Hi Ben,

jep:
https://www.flashrom.org/Flashrom/1.2

Regards,

Simon

Von: Ben Kerr 
Gesendet: Freitag, 17. April 2020 14:41
An: Buhrow, Simon ; flashrom@flashrom.org
Betreff: Re: Error when flashing BIOS

I got the flash rom version from TinyCore. Is there an updated version



Ben Kerr

Support Analyst


|


Fastrack Technology



T +61 2 8025 0500

M +61 435 913 419






From: Buhrow, Simon 
mailto:simon.buh...@sieb-meyer.de>>
Sent: Friday, April 17, 2020 10:00:11 PM
To: Ben Kerr mailto:bk...@ftpl.com.au>>; 
flashrom@flashrom.org<mailto:flashrom@flashrom.org> 
mailto:flashrom@flashrom.org>>
Subject: AW: Error when flashing BIOS


Hi,



I have no idea about that error, but as the flashrom version is quite old may 
be a new (1.1 or 1.2) one has it already fixed?



Regards,



Simon



Von: Ben Kerr mailto:bk...@ftpl.com.au>>
Gesendet: Mittwoch, 15. April 2020 00:16
An: flashrom@flashrom.org<mailto:flashrom@flashrom.org>
Betreff: [flashrom] Error when flashing BIOS



Hi,



I have a customer who attempted to flash a BIOS on one of our products using 
your software and got an error that I haven’t seen before.



[][root@box:/mnt/sda1]$ flashrom -w flash/apu3_v4.11.0.5.rom -p internal

flashrom v0.9.7-r1711-APU on Linux 3.8.13-tinycore (i686)

flashrom is free software, get the source code at 
http://www.flashrom.org<https://aus01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.flashrom.org%2F=02%7C01%7Cbkerr%40ftpl.com.au%7C7388a4040c26451574d608d7e2c6e3fb%7C165804f277f7413fba74844333757e00%7C0%7C0%7C637227216229096805=WLIlONH7yvbGURzK8FEKUicM2WzT7TuPZXylthTB5Sg%3D=0>



Calibrating delay loop... delay loop is unreliable, trying to continue OK.

coreboot table found at 0xdffae000.

Found chipset "AMD FCH". Enabling flash write... FCH device found but SMBus rev.

Please report this to flashrom@flashrom.org<mailto:flashrom@flashrom.org> and 
include this log and

the output of lspci -nnvx, thanks!.

OK.

FIFO pointer corruption! Pointer is 0, wanted 3

Something else is accessing the flash chip and causes random corruption.

Please stop all applications and drivers and IPMI which access the flash chip.

No EEPROM/flash device found.

Note: flashrom can never write if the flash chip isn't found automatically.

No sensors found!

Make sure you loaded all the kernel drivers you need.

Try sensors-detect to find out which these are.

[][root@box:/mnt/sda1]$



The device she was updating was the APU3
https://pcengines.ch/apu3b4.htm<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpcengines.ch%2Fapu3b4.htm=02%7C01%7Cbkerr%40ftpl.com.au%7C7388a4040c26451574d608d7e2c6e3fb%7C165804f277f7413fba74844333757e00%7C0%7C0%7C637227216229106804=D96qYuWP%2FoAu61wJOjQxi%2FH8%2BGFNg%2F5AbKZvUdnMS7E%3D=0>



Let me know if there’s anything you can do to help, nothing was running on the 
board except for TinyCore that holds flashrom.



Thanks






Ben Kerr


Support Analyst



[cid:image001.png@01D614C6.76A9FBE0]<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.fastracktechnology.com.au%2F=02%7C01%7Cbkerr%40ftpl.com.au%7C7388a4040c26451574d608d7e2c6e3fb%7C165804f277f7413fba74844333757e00%7C0%7C0%7C637227216229116793=n0%2B0AVaAHrJbq3X%2BMigKoLlvq1Cpmrx3bJ06bOt8pak%3D=0>



Level 19, Tower A, The Zenith


821 Pacific Highway



Chatswood


NSW



2067






T +61 2 8025 0500


M +61 435 913 419




E bk...@ftpl.com.au<mailto:bk...@ftpl.com.au>


W 
www.fastracktechnology.com.au<https://aus01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.fastracktechnology.com.au%2F=02%7C01%7Cbkerr%40ftpl.com.au%7C7388a4040c26451574d608d7e2c6e3fb%7C165804f277f7413fba74844333757e00%7C0%7C0%7C637227216229116793=LePdhmYYFwz6z9aY8IGXV2aEr8yCAyjvGu2HPCkgkoE%3D=0>






[Click or Tap Link to 
Follow]<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.facebook.com%2FFastrackTechnology=02%7C01%7Cbkerr%40ftpl.com.au%7C7388a4040c26451574d608d7e2c6e3fb%7C165804f277f7413fba74844333757e00%7C0%7C0%7C637227216229126798=44YN5GMhR1JAdTIkKrVJkEL%2FEclnp0vfbyJ1ioDHqbE%3D=0>


[Click or tap link to 
follow]<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2FFastracktech=02%7C01%7Cbkerr%40ftpl.com.au%7C7388a4040c26451574d608d7e2c6e3fb%7C165804f277f7413fba74844333757e00%7C0%7C0%7C637227216229136794=aOEvt3N1Wm9kWu4j1RwcaDeGHeBeXZjcY7TI%2F3Wob2U%3D=0>


[Click or tap link to 
follow]<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Ffastrack-technology-pty-ltd%2F=02%7C01%7Cbkerr%40ftpl.com.au%7C7388a4040c26451574d608d7e2c6e3fb%7C165804f277f7413fba74844333757e00%7C0%7C0%7C637227216229136794=ngvbrGgQsfGi%2FZTRzJfgt8joPSMoG6VUM81is%2FvPC70%3D=0>


[Click or tap link to 
follow]<https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fblog.fastracktechnology.com.au%2Finsights=02%7

[flashrom] Re: Error when flashing BIOS

2020-04-17 Thread Buhrow, Simon

Hi,

I have no idea about that error, but as the flashrom version is quite old may 
be a new (1.1 or 1.2) one has it already fixed?

Regards,

Simon

Von: Ben Kerr 
Gesendet: Mittwoch, 15. April 2020 00:16
An: flashrom@flashrom.org
Betreff: [flashrom] Error when flashing BIOS

Hi,

I have a customer who attempted to flash a BIOS on one of our products using 
your software and got an error that I haven’t seen before.


[][root@box:/mnt/sda1]$ flashrom -w flash/apu3_v4.11.0.5.rom -p internal

flashrom v0.9.7-r1711-APU on Linux 3.8.13-tinycore (i686)

flashrom is free software, get the source code at 
http://www.flashrom.org



Calibrating delay loop... delay loop is unreliable, trying to continue OK.

coreboot table found at 0xdffae000.

Found chipset "AMD FCH". Enabling flash write... FCH device found but SMBus rev.

Please report this to flashrom@flashrom.org and 
include this log and

the output of lspci -nnvx, thanks!.

OK.

FIFO pointer corruption! Pointer is 0, wanted 3

Something else is accessing the flash chip and causes random corruption.

Please stop all applications and drivers and IPMI which access the flash chip.

No EEPROM/flash device found.

Note: flashrom can never write if the flash chip isn't found automatically.

No sensors found!

Make sure you loaded all the kernel drivers you need.

Try sensors-detect to find out which these are.

[][root@box:/mnt/sda1]$


The device she was updating was the APU3
https://pcengines.ch/apu3b4.htm

Let me know if there’s anything you can do to help, nothing was running on the 
board except for TinyCore that holds flashrom.

Thanks



Ben Kerr

Support Analyst


[cid:image001.png@01D614C0.821E2BA0]


Level 19, Tower A, The Zenith

821 Pacific Highway


Chatswood

NSW


2067





T +61 2 8025 0500

M +61 435 913 419



E bk...@ftpl.com.au

W www.fastracktechnology.com.au





[Click or Tap Link to Follow]

[Click or tap link to follow]

[Click or tap link to 
follow]

[Click or tap link to follow]










___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: ftdi_write_chunksize, block_erasers and spi_read_status_register proposals

2019-09-24 Thread Buhrow, Simon

Hi,

sorry, but was there anything bad with my post?
I´m still convinced of my proposals. So may be anyone can comment that or make 
a patch?

Regards,

Simon
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Programming Speed FTDI 2232H to N25Q128

2019-07-30 Thread Buhrow, Simon

I found that libusb calls are mainly responsible for long idle times.

For some improvement/workaround look at E-Mail with topic:  
ftdi_write_chunksize, block_erasers and spi_read_status_register proposals

https://mail.coreboot.org/hyperkitty/list/flashrom@flashrom.org/thread/W2HULJTDPHWPBZY6MLM6TGT7RTHSGHON/

But still looking for further improvement.

Regards,

Simon

___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Support using FTD2XX driver for FT2232H device

2019-07-30 Thread Buhrow, Simon

Hi Steffen,

if that agrees with the free and open source software idea is to discuss by the 
flashrom owners (I think you deserve an answer by the owners...)

Nevertheless I´d like to try it to look if it performs better than libftdi (at 
least for debugging where time could be saved).
Would be nice if you could make it available in any way! (via Mail/git/etc.)

Regards,

Simon

___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Print timestamps

2019-06-18 Thread Buhrow, Simon

Hi,

sometimes I like to know how long an operation took or when I started 
programming.
That´s why I added some timestamp printouts.

May be you want to add it to the sources or do it in a more elegant way? 
What´s about adding the timestamp printout to msg_cinfo ?

Just a proposal...

Regards,

Simon


Signed-off-by: simon Buhrow 
--- flashrom_orig.c 2019-06-03 14:01:40.0 +0200
+++ flashrom.c  2019-06-18 11:19:36.401779000 +0200
@@ -31,6 +31,7 @@
 #include 
 #include 
 #include 
+#include 
 #if HAVE_UTSNAME == 1
 #include 
 #endif
@@ -58,6 +59,9 @@
 /* Is writing allowed with this programmer? */
 int programmer_may_write;
 
+time_t t;
+
+
 const struct programmer_entry programmer_table[] = {
 #if CONFIG_INTERNAL == 1
{
@@ -1679,6 +1683,8 @@
const struct flashrom_layout *const layout = get_layout(flashctx);
 
all_skipped = true;
+time();
+msg_cinfo(" current time is : %s",ctime());
msg_cinfo("Erasing and writing flash chip... ");
 
size_t i;
@@ -1703,6 +1709,8 @@
break;
 
if (info->curcontents) {
+time();
+msg_cinfo(" current time is : %s",ctime());
msg_cinfo("Reading current flash chip 
contents... ");
if (read_by_layout(flashctx, 
info->curcontents)) {
/* Now we are truly screwed. Read 
failed as well. */
@@ -2527,6 +2535,8 @@
 * preserved, but in that case we might perform unneeded erase 
which
 * takes time as well.
 */
+time();
+msg_cinfo("\n current time is : %s",ctime());
msg_cinfo("Reading old flash chip contents... ");
if (verify_all) {
if (flashctx->chip->read(flashctx, oldcontents, 0, 
flash_size)) {
@@ -2570,7 +2580,8 @@
/* Verify only if we actually changed something. */
if (verify && !all_skipped) {
const struct flashrom_layout *const layout_bak = 
flashctx->layout;
-
+time();
+msg_cinfo(" current time is : %s",ctime());
msg_cinfo("Verifying flash... ");
 
/* Work around chips which need some time to calm down. */
@@ -2588,6 +2599,8 @@
emergency_help_message();
else
msg_cinfo("VERIFIED.\n");
+time();
+msg_cinfo(" current time is : %s",ctime());
} else {
/* We didn't change anything. */
ret = 0;
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: N25Q128A

2019-06-06 Thread Buhrow, Simon

I found the error: I had a signal integrity problem.

The chip now is detected correctly as N25Q128..3E .
All commands execute correctly.

So please forget my las mail/post as the chip is already in the flashrom 
database and working fine!! (as my N25Q128A is a N25Q128..3E )

Sorry!

Simon

___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] IS25WP064 tested successfully

2018-09-04 Thread Buhrow, Simon

Hi,

I also tested IS25WP064 successfully (Read and write).

I added:
to flashchips.h:
#define ISSI_IS25WP064  0x7017

to flashchips.c:
{
.vendor = "ISSI",
.name   = "IS25WP064",
.bustype= BUS_SPI,
.manufacture_id = ISSI_ID_SPI,
.model_id   = ISSI_IS25WP064,
.total_size = 8192,
.page_size  = 256,
/* OTP: 1024B total; read 0x48; write 0x42 */
.feature_bits   = FEATURE_WRSR_WREN | FEATURE_OTP,
.tested = TEST_OK_PREW,
.probe  = probe_spi_rdid,
.probe_timing   = TIMING_ZERO,
.block_erasers  =
{
{
.eraseblocks = { {4 * 1024, 2048} },
.block_erase = spi_block_erase_20,
}, {
.eraseblocks = { {4 * 1024, 2048} },
.block_erase = spi_block_erase_d7,
}, {
.eraseblocks = { {32 * 1024, 256} },
.block_erase = spi_block_erase_52,
}, {
.eraseblocks = { {64 * 1024, 128} },
.block_erase = spi_block_erase_d8,
}, {
.eraseblocks = { {8 * 1024 * 1024, 1} },
.block_erase = spi_block_erase_60,
}, {
.eraseblocks = { {8 * 1024 * 1024, 1} },
.block_erase = spi_block_erase_c7,
}
},
.unlock = spi_disable_blockprotect,
.write  = spi_chip_write_256,
.read   = spi_chip_read,
.voltage= {1650, 1950},
},



The console output looks this:

user@user-VirtualBox:~/Downloads/flashrom-1.0$ sudo flashrom -p 
ft2232_spi:type=2232H,port=A,divisor=6 -f -w 
/home/user/Downloads/flashrom-1.0/Flashinhalte/file_8k.bin
flashrom v1.0 on Linux 4.15.0-33-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 ISSI flash chip "IS25WP064" (8192 kB, SPI) on ft2232_spi.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... VERIFIED.

Regards,
Simon

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

Re: [flashrom] 64Mbit IS25LP064A not recognized

2018-08-29 Thread Buhrow, Simon

Hi Nico,

thanks a lot for your quick help.

I got it running by adding the chip data to the database. Before that I run the 
command with the -VV parameter where I could see that the IDs were read 
correctly (-> so there was no signal integrity problem).

To get it running I added the following lines:

in flashchips.h:
#define ISSI_IS25LP064  0x6017

in flashchips.c
{
.vendor = "ISSI",
.name   = "IS25LP064",
.bustype= BUS_SPI,
.manufacture_id = ISSI_ID_SPI,
.model_id   = ISSI_IS25LP064,
.total_size = 8192,
.page_size  = 256,
/* OTP: 1024B total; read 0x48; write 0x42 */
.feature_bits   = FEATURE_WRSR_WREN | FEATURE_OTP,
.tested = TEST_OK_PREW,
.probe  = probe_spi_rdid,
.probe_timing   = TIMING_ZERO,
.block_erasers  =
{
{
.eraseblocks = { {4 * 1024, 2048} },
.block_erase = spi_block_erase_20,
}, {
.eraseblocks = { {4 * 1024, 2048} },
.block_erase = spi_block_erase_d7,
}, {
.eraseblocks = { {32 * 1024, 256} },
.block_erase = spi_block_erase_52,
}, {
.eraseblocks = { {64 * 1024, 128} },
.block_erase = spi_block_erase_d8,
}, {
.eraseblocks = { {8 * 1024 * 1024, 1} },
.block_erase = spi_block_erase_60,
}, {
.eraseblocks = { {8 * 1024 * 1024, 1} },
.block_erase = spi_block_erase_c7,
}
},
.unlock = spi_disable_blockprotect,
.write  = spi_chip_write_256,
.read   = spi_chip_read,
.voltage= {2300, 3600},
},



So the output now is:
>sudo flashrom -p ft2232_spi:type=2232H,port=A,divisor=30 -VV
flashrom v1.0 on Linux 4.15.0-33-generic (x86_64)
...
Probing for ISSI IS25LP064, 8192 kB: probe_spi_rdid_generic: id1 0x9d, id2 
0x6017
Found ISSI flash chip "IS25LP064" (8192 kB, SPI) on ft2232_spi.
...
Found ISSI flash chip "IS25LP064" (8192 kB, SPI) on ft2232_spi.
No operations were specified.
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).
No operations were specified.


As I understand the doc at 
https://www.flashrom.org/Development_Guidelines#Adding.2Freviewing_a_new_flash_chip
I´m not able to add this to the repo. Could anyone do this? (or tell me how to 
do if I can)
I was able to write and read from the flash as well. So should be fine.

Regards,
Simon



-Ursprüngliche Nachricht-
Von: Nico Huber  
Gesendet: Dienstag, 28. August 2018 13:52
An: Buhrow, Simon 
Cc: flashrom@flashrom.org; Stefan Tauner 
Betreff: Re: [flashrom] 64Mbit IS25LP064A not recognized

Hi Simon,

Am 28.08.18 um 10:51 schrieb Buhrow, Simon:
> Measuring the signal I got that the command given above does first a 
> RDJDID Operation and later the RDSFDP operation (which should be 
> according to JESD216).  I attach the signals. You can see the the 
> operations and what is done.

it seems to me that flashrom has already processed parts of the SFDP (5a 00 00 
54 means it requests data at offset 0x54 of the SFDP, right?).
You can probably see more details about why it fails if you add one or two -V 
to your flashrom command.

> According to the datasheet is MF7-MF0: 9Dh and Memory Type + Capacity 
> (ID15 - ID0): 6017h. Which you can see on the RDJDID signals image.
> 
> I know the signal quality is not the best but doing real improves 
> would cost a lot of time. As I already successfully programmed another 
> supported chip and because the Flash chip response the right way I 
> think that it´s not a signal integrity problem.
> 
> So my questions are:
> 1)  Does "unknown SPI chip (RDID)" mean "it´s not in the database"
> or does it mean "RDID could not be read successfully"?

It can mean both as the protocol has no means of error detection. It's
simply: the MISO level wasn't all zero, IIRC.

You can see the response if you add -V to your command. It should print id1:... 
id2:... for each chip probed. For all RDID commands this should be consistently 
the 0x9d 0x6017 of your chip.

> 2)  If it means "RDID cou

38 matches

Mail list logo