Some investigations have shown, that the original dediprog driver waits
about 200ms after setting voltage up and before setting voltage down.
This patch adds those delays. It helps flash chips to come up in time.
Signed-off-by: Nico Huber nico.hu...@secunet.com
Index: dediprog.c
for the size of the chunks sent over usb earlier.
This patch requires [PATCH] Let the programmer driver decide how to do
AAI transfers.
Signed-off-by: Nico Huber nico.hu...@secunet.com
diff -urp -x.svn flashrom-spi_write_aai/dediprog.c
flashrom-dediprog-own-spi_write_aai/dediprog.c
--- flashrom
this abstraction in the dediprog driver will
follow.
Signed-off-by: Nico Huber nico.hu...@secunet.com
Index: dediprog.c
===
--- dediprog.c (Revision 1541)
+++ dediprog.c (Arbeitskopie)
@@ -709,6 +709,7 @@
.multicommand
. The second word was
mistaken for the size of the chunks sent over usb earlier. The third
byte (first of the second word) is now set to zero. This also adds some
checks for the size of data chunks sent over usb.
Signed-off-by: Nico Huber nico.hu...@secunet.com
Index: dediprog.c
of the second word) is now set to zero. This also adds some
checks for the size of data chunks sent over usb.
Signed-off-by: Nico Huber nico.hu...@secunet.com
Index: dediprog.c
===
--- dediprog.c (Revision 1545)
+++ dediprog.c
the initialization calls have moved into a new function
dediprog_setup() which is called twice.
Signed-off-by: Nico Huber nico.hu...@secunet.com
Index: dediprog.c
===
--- dediprog.c (Revision 1596)
+++ dediprog.c (Arbeitskopie
the programmer after setting the
speed, so the initialization calls have moved into a new function
dediprog_setup() which is called twice.
Signed-off-by: Nico Huber nico.hu...@secunet.com
diff --git a/dediprog.c b/dediprog.c
index a81cf83..60067a8 100644
--- a/dediprog.c
+++ b/dediprog.c
@@ -152,7
This patch tracks the changes in the libusb interface. Nothing changed
in the behaviour of the driver, so far.
It will be used by a follow-up patch. It's based on Enable spi clock
setting in dediprog driver.
Signed-off-by: Nico Huber nico.hu...@secunet.com
diff --git a/Makefile b/Makefile
index
based on Bump dediprog driver to use libusb-1.0.
Signed-off-by: Nico Huber nico.hu...@secunet.com
diff --git a/dediprog.c b/dediprog.c
index a558285..f1c03d8 100644
--- a/dediprog.c
+++ b/dediprog.c
@@ -29,6 +29,7 @@
#define FIRMWARE_VERSION(x,y,z) ((x 16) | (y 8) | z)
#define DEFAULT_TIMEOUT
encountered when a client
wants to restart things after calling programmer_shutdown().
Nico Huber (6):
Make some char pointers const
Add a convenient libflashrom interface
Add Doxyfile for libflashrom documentation
Adapt CLI to use new libflashrom interface' print callback
This makes some char pointers const to get a more convenient libflashrom
interface.
Signed-off-by: Nico Huber nico.hu...@secunet.com
---
flash.h |4 ++--
flashrom.c |8
programmer.h |2 +-
3 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/flash.h b
This renames CLI's print() to fl_print_cb() and registers it through the
new libflashrom interface.
Signed-off-by: Nico Huber nico.hu...@secunet.com
---
cli_classic.c |3 +++
cli_output.c |7 +--
flash.h |2 ++
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git
To get things working correctly again after programmer_shutdown(),
registered_programmer_count has to be reset. Herewith, we can start
another run with programmer_init().
Signed-off-by: Nico Huber nico.hu...@secunet.com
---
flashrom.c |4
1 file changed, 4 insertions(+)
diff --git
, without breaking clients.
A new make target, libinstall, is also added. It installs libflashrom.a
and libflashrom.h in lib/ and include/ dirs respectively.
This commit breaks build of the cli. It will be fixed with a follow-up
commit.
Signed-off-by: Nico Huber nico.hu...@secunet.com
curopcodes in ichspi.c reflects the state of the related chipset
registers. Those are reset on shutdown but curopcodes is left
initialized. This prevented further runs with the same libflashrom
instance.
Signed-off-by: Nico Huber nico.hu...@secunet.com
---
ichspi.c | 14 ++
1 file
Hello Carl-Daniel,
Am 19.02.2013 22:56, schrieb Carl-Daniel Hailfinger:
Hi Nico,
I'm very sorry about the long review delay.
Anyway, thanks for your review.
Am 16.11.2012 11:23 schrieb Nico Huber:
This adds a programmer parameter 'spispeed' to the dediprog driver to
control the transfer
Am 27.03.2013 11:51, schrieb Stefan Tauner:
On Fri, 22 Feb 2013 11:56:03 +0100
Nico Huber nico.hu...@secunet.com wrote:
I'm not quite sure if I changed anything since my post, so I'll rebase,
test, and repost my pending changes.
Were there any pending changes or can we continue with what
to be 5.0.0 or newer.
+Syntax is
.sp
.B flashrom \-p dediprog:spispeed=frequency
.sp
--
M. Sc. Nico Huber
Berater, SINA-Softwareentwicklung
Public Sector
secunet Security Networks AG
Tel.: +49-201-5454-3635, Fax: +49-201-5454-1325
E-Mail: nico.hu...@secunet.com
Mergenthalerallee 77, 65760
Hi Paul,
less comments today.
Nico
On 24.10.2015 13:24, Paul Kocialkowski wrote:
> The ENE Embedded Debug Interface (EDI) is a SPI-based interface for accessing
> the memory of ENE embedded controllers.
>
> The ENE KB9012 EC is an embedded controller found on various laptops such as
> the
Hi Paul,
On 24.10.2015 13:19, Paul Kocialkowski wrote:
> I will probably send v2 right away, feel free to follow up the
> discussion on some of these comments in there, it'll probably be
> easier.
I'll keep some of the general discussion here. Some new comments
will come inline with v2.
>>> +
in use. Some firmwares disable EDI at run-time, so
> it might be necessary to ground pin 42 to reset the 8051 microcontroller
> before
> accessing the KB9012 via EDI.
>
> Signed-off-by: Paul Kocialkowski <cont...@paulk.fr>
Acked-by: Nico Huber <nic...@gmx.de>
> ---
On 11.11.2015 16:55, Paul Kocialkowski wrote:
> Most flash chips are erased to ones and programmed to zeros. However, some
> other
> flash chips, such as the ENE KB9012 internal flash, work the opposite way.
>
> Signed-off-by: Paul Kocialkowski <cont...@paulk.fr>
Acke
On 24.10.2015 13:24, Paul Kocialkowski wrote:
> Most flash chips are erased to ones and programmed to zeros. However, some
> other
> flash chips, such as the ENE KB9012 internal flash, work the opposite way.
>
> Signed-off-by: Paul Kocialkowski
Two comments below.
Nico
> ---
On 22.10.2015 00:24, Denis 'GNUtoo' Carikli wrote:
> On Sat, 17 Oct 2015 12:57:54 +0200
> Nico Huber <nic...@gmx.de> wrote:
>> I'd try with the AC adapter. In that case Vcc must _not_ be connected
>> to your programmer. GND, OTOH, has to stay connected.
> If that happens
On 10.10.2015 16:20, Paul Kocialkowski wrote:
> Some chips such as the ENE KB9012 internal flash require a write granularity
> of
> 128 bytes.
>
> Signed-off-by: Paul Kocialkowski
clean patch, +2
> ---
> flash.h| 1 +
> flashrom.c | 6 ++
> 2 files changed, 7
On 10.10.2015 16:20, Paul Kocialkowski wrote:
> Most flash chips are erased to ones and programmed to zeros. However, some
> other
> flash chips, such as the ENE KB9012 internal flash, work the opposite way.
>
> Signed-off-by: Paul Kocialkowski
Looks good, some comments below.
On 10.10.2015 16:20, Paul Kocialkowski wrote:
> The ENE Embedded Debug Interface (EDI) is a SPI-based interface for accessing
> the memory of ENE embedded controllers.
>
> The ENE KB9012 EC is an embedded controller found on various laptops such as
> the Lenovo G505s. It features a 8051
Rebased this old, rotting patch. Not tested in the last two years, but
might help to speed up some things (ftdi got pretty fast with this).
It has to be enabled per chip (see WINBOND/W25Q64.V for example).
---
chipdrivers.h | 1 +
cli_common.c | 14 +++---
flash.h | 23
Hi Potato,
On 07.06.2016 18:59, potato wrote:
> I know that the programmer works, since I was able to make goods dumps
> of a MX25L8006 that was on a old router, but I was not able to detect a
> MX25L6405D that was on my Thinkpad X200 (it could not even find a chip).
> I know it is not a problem
those that match the layout. This
would simplify things a lot. And, IMO, you can have a layout with erase
block aligned regions in most use cases.
Regards,
Nico
--
M. Sc. Nico Huber
Senior Berater SINA-Softwareentwicklung
Netzwerk- & Client-Sicherheit / Network & Client Security
Divisi
rom is used internally
by flashrom.
Any comments?
Best regards,
Nico
--
M. Sc. Nico Huber
Senior Berater SINA-Softwareentwicklung
Netzwerk- & Client-Sicherheit / Network & Client Security
Division Öffentliche Auftraggeber / Public Authorities
secunet Security Networks AG
Tel.: +49-20
We didn't check the total number of queued transfers in the inner most
loop. Up to DEDIPROG_ASYNC_TRANSFERS - 1 invalid transfers could be
queued therefore. So add another check on the total number.
Signed-off-by: Nico Huber <nico.hu...@secunet.com>
---
dediprog.c | 4 +++-
1 file chan
Signed-off-by: Nico Huber <nico.hu...@secunet.com>
---
dediprog.c | 17 ++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/dediprog.c b/dediprog.c
index 019de46..b7276e5 100644
--- a/dediprog.c
+++ b/dediprog.c
@@ -942,7 +942,7 @@ int dediprog_init(void)
guess. :-P
Signed-off-by: Nico Huber <nico.hu...@secunet.com>
---
ich_descriptors.c | 23 ---
ich_descriptors.h | 11 ---
util/ich_descriptors_tool/Makefile | 2 +-
3 files changed, 9 insertions(+), 27 deletions(-)
diff
Reference documentation for libflashrom can be build with doxygen. With
doxygen Doxyfile
documentation will be put into a libflashrom-doc/ subdirectory.
Signed-off-by: Nico Huber <nico.hu...@secunet.com>
---
Doxyfile | 1781 ++
This renames CLI's print() to fl_print_cb() and registers it through the
new libflashrom interface.
Signed-off-by: Nico Huber <nico.hu...@secunet.com>
---
cli_classic.c | 3 +++
cli_output.c | 13 ++---
flash.h | 2 ++
3 files changed, 11 insertions(+), 7 deletions(-)
This also reduces the data read before the write to the included layout
regions.
Signed-off-by: Nico Huber <nico.hu...@secunet.com>
---
cli_classic.c | 13 +
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/cli_classic.c b/cli_classic.c
index d7e17f7..d23a3a3
Introduce `struct fl_layout` and refactor layout.c a little, so we can
reuse the layout from there and have other sources of layouts beside it.
I didn't want to clutter up flash.h any more. So things went into a new
layout.h.
Signed-off-by: Nico Huber <nico.hu...@secunet.com>
---
flash.h
Signed-off-by: Nico Huber <nico.hu...@secunet.com>
---
cbtable.c| 14 +++---
programmer.h | 2 +-
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/cbtable.c b/cbtable.c
index 1a74e46..c1c264a 100644
--- a/cbtable.c
+++ b/cbtable.c
@@ -38,13 +38,13 @@ stati
*() rewritten with layout support (touch only included regions).
o Moved read/erase/write/verify operations to flashrom.c.
o Added layout pointer and flags to the flash context.
Signed-off-by: Nico Huber <nico.hu...@secunet.com>
---
Makefile | 8 +-
flash.h | 6 ++
flas
, though.
Signed-off-by: Nico Huber <nico.hu...@secunet.com>
---
flash.h| 1 +
flashrom.c | 326 +
2 files changed, 327 insertions(+)
diff --git a/flash.h b/flash.h
index bf381cf..be1134a 100644
--- a/flash.h
+++ b/flash.h
@@
Signed-off-by: Nico Huber <nico.hu...@secunet.com>
---
cli_classic.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/cli_classic.c b/cli_classic.c
index d23a3a3..aef7693 100644
--- a/cli_classic.c
+++ b/cli_classic.c
@@ -376,12 +376,6 @@ int main(int argc, char
No words can describe this feeling.
Signed-off-by: Nico Huber <nico.hu...@secunet.com>
---
cli_classic.c | 24 ++--
flash.h | 5 +-
flashrom.c| 393 +++---
3 files changed, 90 insertions(+), 332 deletions(-)
diff
Signed-off-by: Nico Huber <nico.hu...@secunet.com>
---
board_enable.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/board_enable.c b/board_enable.c
index 2f0c1c0..22e45b4 100644
--- a/board_enable.c
+++ b/board_enable.c
@@ -2457,6 +2457,7 @@ const struct board_match board_m
Add an option (-d|--ifd) to read the ROM layout from an Intel Firmware
Descriptor (IFD). Works the same as the -l option, if given, -i
specifies the images to update.
v2: o Rebased on libflashrom, use libflashrom interface.
o Use functions from ich_descriptors.c.
Signed-off-by: Nico Huber
At least with the -A,--noverify-all switch, this warning isn't true any
more. Maybe we want to force -A in that case?
Signed-off-by: Nico Huber <nico.hu...@secunet.com>
---
flashrom.8.tmpl | 9 +
ichspi.c| 29 -
2 files changed, 1 insertion(
Hi all,
this is my current work on layout support and libflashrom. I don't have
the time currently to clean it more up / respond to a review, as I will
be on vacation for about three weeks.
Most things are pretty clean though. So I sent it in, in case anyone
wants to look at it or just play with
Hi Wen,
On 01.08.2016 21:29, Wen Wang wrote:
> Has anybody tried flashrom on Broadwell-DE SoC? Intel has upstreamed
> coreboot support. But we are having trouble with flashrom. The ME region
> does not seem to be accessible. We cannot read the entire flash (fails when
> reading ME) even though
Hi folks,
now that we have a git repository [1] ready (thanks Stefan!), I've
visited again the flashrom development guidelines [2]. I stumbled
there over a very long, exemplary version number: "0.9.10.1". IMHO,
two things are wrong here: 1st there are too many dots for my taste,
and 2nd the
Hello Alexander,
On 06.08.2016 12:28, Alexander Waldmann wrote:
>
> Basically what it says on the tin. One of my X200 systems works with
> flashrom's internal programmer, as expected, but a recently acquired one
> does not, I get the error about unsupported laptop. Using the
>
Hi Ed,
On 02.08.2016 21:34, Ed Swierk wrote:
> With Nico's patches, I am able to read the BIOS portion of the flash
> (0x0800-0x1000) on a Camelback Mountain board with the stock
> BIOS.
thanks for the report.
> I haven't been able to write the BIOS portion of the flash, though, as
> it
Hi all,
On 09.11.2016 00:20, Charlotte Plusplus wrote:
> Hello
>
> That is very interesting. Do you have a way to automate that?
>
> I am testing ram stuff with coreboot, I don't need to flash a full 8MB
> image. I could just pass a -i of the cbfs content to only change the
> ramstage, and do a
pson.
>
> 2016-11-23 3:20 GMT+08:00 Nico Huber <nic...@gmx.de>:
>
>> Hi Sampson,
>>
>> On 21.11.2016 04:33, Sampson Lee wrote:
>>> I add a few point:
>>>
>>> I use flshrom version:0.99.
>>> I try command "--layout" to
Hi Stefan,
could you please split this up? I started to review but I guess the
patch will have gone through some revisions before I'm done reading.
On 21.11.2016 01:19, Stefan Tauner wrote:
> - Drop support for Subversion in the getrevision script and Makefile.
> - Add .gitignore file
> -
Hi Sampson,
On 21.11.2016 04:33, Sampson Lee wrote:
> I add a few point:
>
> I use flshrom version:0.99.
> I try command "--layout" to read my rom file,but it show error message
> "error parsing layout file".
well, it means what it says, flashrom can't understand the file you gave
to the
On 23.12.2016 08:19, David Hendricks wrote:
> Looks like it failed to overwrite the descriptor region (Intel ME-related
> headache): https://www.flashrom.org/ME
According to the log, the descriptor is writeable. Also the error occurs
right behind it.
When I looked through it first, I thought
the same error
Sorry, I'm just poking in the dark. Another idea: Some other driver or
program might have claimed access to port B and is blocking it. flash-
rom doesn't know how to handle that, maybe your "other softwares" do.
Nico
>
> Regards
>
> Le 22 mars 2017 12:14, &q
On 23.03.2017 20:26, Michael Fuckner wrote:
> Hi,
>
> I got a file, 8MB in size and it contains data. md5sum is not identical
> to original file and binwalk looks different on the beginning.
Not sure, what an "original" file would be. The flash contains data that
is specific to your device like
Hi Zak,
please always keep the mailing list in CC, you will get less attention
otherwise.
On 23.03.2017 12:16, Nico Huber wrote:
>
> Forwarded Message
> Subject: Re: [flashrom] Problem with flashrom and FT2232 Port B
> Date: Wed, 22 Mar 2017 18:01:18 +0100
000
> 0040:
>
> Regards,
> Michael!
>
> On 3/22/2017 1:08 PM, Nico Huber wrote:
>> Hi Michael,
>>
>> On 21.03.2017 20:48, Michael Fuckner wrote:
>>> Hi,
&
Hi Michael,
On 22.03.2017 16:43, Nico Huber wrote:
> On 22.03.2017 16:13, Michael Fuckner wrote:
>> Hi,
>>
>> just tried it- this Board uses a Winbond 25Q64FV (64Mbit) and after
>> reading there is an 8MB file, but it is empty. Anything else I should try?
>
> Sam
Hello Micha,
On 27.03.2017 13:58, Michael Schröder wrote:
> Dear folks,
>
> i am interested in using coreboot with a MacMini 2007 (core2duo). It
> uses the same chipset (GM945) as the macbook2.1 which supported yet.
>
> I managed to read infos about the BIOS with flashrom.
> The verbose output
Hi Michael,
On 24.03.2017 15:14, Michael Fuckner wrote:
> Hi,
>
> I had to use flashrom and my raspi to reflash my bios chip after it got
> corrupted. Now I compare the original Firmware (XH170V00.200) I flashed
> into the Chip with the file I read (flash.bin).
>
> I found the MAC Address in
Hi Zak,
On 21.03.2017 17:28, Zak wrote:
> Hello,
>
> I got flashrom compiled for windows and it works like a charm (has to
> tweet the code a little, add data for the chips i want to work with, add
> 4BA and fast rading for FT2232), it works perfectly fine but only for
> the port A (flashrom -p
Hi Michael,
On 21.03.2017 20:48, Michael Fuckner wrote:
> Hi,
>
> I added PCI ID for my chipset, but I can't access/ read FLash chip. Any
> idea how to proceed?
if you compare the datasheets, you'll see that it's incompatible with
the 9series PCH.
I'm currently working on upstream support for
On 16.03.2017 00:08, David Hendricks wrote:
> On Fri, Mar 10, 2017 at 8:02 AM, Nico Huber <nico.hu...@secunet.com> wrote:
>>
>> Hi,
>>
>> I've just updated my solution to _the_ layout problem that I wrote last
>> year [1]. I'm not asking for a review at
Hello Boyce,
On 12.04.2017 18:23, Boyce Humphries via flashrom wrote:
> hello again @flashrom
>
> Could a flashrom option be added to allow only USB ports to be probed,
> programmed, etc.
> External programmers are cheap and there many laptops out here.
in current flashrom (0.9.9), the default
On 23.04.2017 16:07, Stefan Tauner wrote:
> On Sat, 22 Apr 2017 11:16:18 -0700
> David Hendricks wrote:
>
>> Thanks for getting this discussion going on the list, Nico.
>>
>> For reference, folks can view the proposed libflashrom.h at
>>
Hi flashrom folks,
working again on implementing the libflashrom interface described here
[1]. During review [2] the question arose what `fl_` means and if we
don't want to use something else. The following alternatives were pro-
posed in the wiki:
* fl_ / FL_ (probably *fl*ashrom)
* lf_ /
functions such
> as flash_image_read() and flash_image_write(), but is awkward with some
> other stuff like "flash_set_log_callback()". If we're already typing >2
> letters I think we ought to just use flashrom_ as the prefix to be
> complete, avoid awkward contexts, and avoid names
Hi,
I've just updated my solution to _the_ layout problem that I wrote last
year [1]. I'm not asking for a review at this moment. There are at least
two competing approaches that I want to discuss first (I couldn't start
a discussion before I wrote it, due to time constraints).
We can
1) walk
Hello Martin,
On 18.04.2017 20:36, Martin wrote:
> Hello,
>
> I have problem after trying flash QNAP TS-453A
>
> ...
> Proceeding anyway because user forced us to.
> Found chipset "Intel Braswell".
> This chipset is marked as untested. If you are using an up-to-date version
> of flashrom *and*
On 17.08.2017 11:30, Stefan Tauner wrote:
> On Thu, 17 Aug 2017 10:23:54 +0100
> Richard Hughes wrote:
>
>> On 17 August 2017 at 10:18, Stefan Tauner wrote:
>>> However, this is inevitable sometimes as explained before... so maybe
>>> we need some
Hi David,
On 14.07.2017 18:30, David Hobach wrote:
> For reference:
>
> Apparently the Pi didn't provide enough current to drive the chip and
> whatever else hang in the motherboard together with it.
a word of caution: Applying external power (i.e. connecting the sol-
dered chip's VCC to an
Hi Ian,
jumping in here late because I had no idea yet how to help you.
On 04.08.2017 16:26, Ian Stewart wrote:
> Hi There,
>
> I keep getting Verifying flash... FAILED messages over and over while
> trying to flash an 8mb x200 chip. I'd say I've gotten the message ~10
> times now and I've
t; On Wed, Aug 9, 2017 at 3:41 PM, Nico Huber <nic...@gmx.de> wrote:
>
>> Hi Ian,
>>
>> jumping in here late because I had no idea yet how to help you.
>>
>> On 04.08.2017 16:26, Ian Stewart wrote:
>>> Hi There,
>>>
>>> I keep gettin
Yet another thread (YAT?).
>
> flashrom_set_progress_callbacks(flashrom_progress_cb *cb_progress,
> flashrom_progress_event_cb *cb_event, void *user_data); < We might need
> to add a flashrom context here? No idea how the current staging
> implementation works but eventually we want to fix the
On 17.08.2017 14:09, Stefan Tauner wrote:
>
>
> On Thu, 17 Aug 2017 11:53:58 +0200
> Nico Huber <nico.hu...@secunet.com> wrote:
>
>> B := we need to give the user a really good reason
>>
>> Having a RESET enum value allows us to fulfill B, thus:
>>
Hi,
starting a new thread for this because it's somewhat orthogonal.
> [...] The progress would not be
> constant in speed (e.g. because reading is usually much faster than
> writing), and it would sometimes even be non-monotonic (if a write
> fails, we re-read the whole chip to make absolutely
Hi Richard, David,
On 16.08.2017 23:02, David Hendricks wrote:
> On Tue, Aug 15, 2017 at 4:55 AM, Richard Hughes wrote:
>
>> Hi all,
>>
>> I'm the maintainer of fwupd, which is a daemon for doing firmware
>> updates in Linux. Using fwupd about 200,000 people update firmware
Hi Boyce, Josh,
On 13.06.2017 16:24, Boyce Humphries via flashrom wrote:
> Hello Josh
>
> I dove into the code yesterday and here is what I found. When the bits
> BP0 and BP1 in the status register need to be cleared the function
> spi_disable_blockprotect(flash) is called. To clear these bits
Hi,
On 15.09.2017 18:56, junkheap--- via flashrom wrote:
> I am trying to write to a Winbond W25Q64FVSIG EEPROM (SOIC-8) using
> Flashrom and a Raspberry Pi 3 (running up to date Raspbian). But I
> receive the message "ERASE FAILED!".
>
> I am using the shortest wires which are practical to
Hi Adam,
On 14.09.2017 11:43, Adam Makkos wrote:
> Hi,
>
> Can you please tell if flashrom is able to also read bios settings?
that depends, of course, where the settings are stored and that varies
from device to device (modern PCs usually store them in the BIOS flash).
Though, even if they
assume that the chip is still soldered to a board.
In that case the circuit on the board pulls /HOLD and /WP already.
Nico
PS. Please always keep the mailing list in CC when you respond. Some
email clients have an extra button (e.g. "Reply all") for that.
>
>
> On 16/09
Hi Peter,
On 13.10.2017 08:01, Peter Lemenkov wrote:
Hello Nico,
2017-10-13 2:40 GMT+02:00 Nico Huber <nic...@gmx.de>:
So I propose the following: Forget the two branches model, start
a `master` branch with either the current state of `staging` or
my proposed move to `stable` [3] and r
On 13.10.2017 02:40, Nico Huber wrote:
So I propose the following: Forget the two branches model, start
a `master` branch with either the current state of `staging` or
my proposed move to `stable` [3] and release flashrom-1.0 right
away.
What I didn't realize last night: the `staging` branch
On 04.09.2017 19:31, Nicola Corna wrote:
> September 3, 2017 12:24 AM, "Nico Huber" <nic...@gmx.de> wrote:
>
>> TLDR; it would be a lot slower.
>>
>> Alas, there is no usual byte-program mode. Most chips do a 256B page
>> program which uses op
Hi Billy,
On 24.08.2017 09:03, Billy Isom wrote:
> hello friend
>
> I have been using flashrom for a little while now with great results, but i
> upgraded to the latest Raspbian Distro.
> upon attempting to reinstall Flashrom on my Raspberry PI 3 I receive an
> error.
>
> I was hoping you could
at all.
For the record, this commit enabled the SPI lockdown (e.g. locked the
OPMENU). Which was previously only set after resume by accident.
>
> As suggested by Nico Huber, I tried with `-p
> internal:ich_spi_mode=hwseq`, without success (log attached).
>
Ah, I see why it didn'
Hi,
On 02.09.2017 21:02, Nicola Corna wrote:
> September 2, 2017 5:39 PM, "Nico Huber" <nic...@gmx.de> wrote:
>> From the original op menu these are probably unneeded: byte program
>> (0x02), either one of the block erasers (0x20 and 0xd8) and the fast
>>
a bottleneck.
Thoughts?
Nico
[1] `staging` on https://review.coreboot.org/cgit/flashrom.git
[2] https://www.flashrom.org/Development_Guidelines#Branches
[3] The result if somebody submits the following patch queue:
https://review.coreboot.org/#/q/status:open+branch:stable+owner:"Nico
Hi,
some questions I should have asked about a year ago:
Has anybody ever registered the name "flashrom"? If so, who?
Who runs the flashrom.org infrastructure?
Nico
___
flashrom mailing list
flashrom@flashrom.org
Hello Benedikt,
On 17.10.2017 22:18, Benedikt Broich via flashrom wrote:
Hello,
I am trying to flash the MX25L6405D in my Lenovo X200, but i get the
following Error:
Do you have any Idea what i am doing wrong?
Flashing this chip in an X200 is rather finicky. You either need a
very good
On 17.10.2017 01:14, David Hendricks wrote:
On Sat, Oct 14, 2017 at 7:20 AM, Stefan Tauner wrote:
While there was a bunch of patches that have been piled up back then it
was less of a problem then the increasing divergence between the
chromiumos fork and upstream. Thus we
Hi Michael,
On 18.12.2017 20:18, Michael Fuckner wrote:
> Hi,
>
> I noticed W25Q256FV is supported by flashrom, but I'd like to reflash
> W25Q256JVFQ (used by Supermicro X11DAi-N). It also uses ID 4019, but
> does not support QPI.
>
> My programmer is a custom board connected to a Raspi3 using
Hi Anders,
On 11.11.2017 17:27, Anders Nelson wrote:
Hi again,
I don't see details on what image file formats are supported - does
Flashrom use only binary files?
yes, that's right, conversion from other formats is out of flashrom's
scope.
I see the ROM layout file explanation so I guess I
Hi Harry,
On 16.11.2017 09:39, Harry Prevor wrote:
Attached is a patch to whitelist the Librem 15 laptop on flashrom, so
that I don't have to write "force_I_want_a_brick" every time I use it. I
also added the laptop's info to print.c so it shows up as a supported
device. This is my first ever
Hi Ron,
On 17.11.2017 18:49, ron minnich wrote:
any suggestions on making this part work? I have not done this in a while.
its brother 25Q128*F*V is already supported (as W25Q128.V, where .
is a wildcard, alas, not matching the *J*V). I'd start by copying
the W25Q128.V entry in flashchips.c
Hi Anders,
On 03.11.2017 21:35, Anders Nelson wrote:
> Hi guys,
>
> Here's the error I get trying to apply the patch:
>
> "root@chrx:/home/chrx/Github/flashrom# git apply --check
> /home/chrx/Downloads/ich_descriptors-amd64.patch
> error: patch failed: ich_descriptors.c:1064
> error:
Hi Anders,
On 07.11.2017 21:31, Anders Nelson wrote:
> Argh:
>
> ===
>
> root@chrx:/home/chrx/Github/flashrom# flashrom -p ft2232_spi
> flashrom v0.9.9-rc1-r1942 on Linux 4.9.4-galliumos-braswell (x86_64)
> flashrom is free software, get the source code at https://flashrom.org
>
> Error:
1 - 100 of 300 matches
Mail list logo