flashrom January 2015

flashrom@flashrom.org

35 participants
121 discussions

[PATCH] ft2232_spi.c: Added MPSSE controller reset
by Boris Baykov 26 Jan '15

26 Jan '15

Added MPSSE reset according to FTDI Application Notes AN114. Signed-off-by: Boris Baykov <dev(a)borisbaykov.com> --- diff -U 5 -N ./flashrom/ft2232_spi.c ./flashrom.ftdi_mpsse_init/ft2232_spi.c --- ./flashrom/ft2232_spi.c 2015-01-25 10:16:05.372174400 +0300 +++ ./flashrom.ftdi_mpsse_init/ft2232_spi.c 2015-01-25 10:17:50.000000000 +0300 @@ -75,10 +75,11 @@ {0}, }; #define DEFAULT_DIVISOR 2 +#define BITMODE_BITBANG_RESET 0 #define BITMODE_BITBANG_NORMAL 1 #define BITMODE_BITBANG_SPI 2 /* The variables cs_bits and pindir store the values for the "set data bits low byte" MPSSE command that * sets the initial state and the direction of the I/O pins. The pin offsets are as follows: @@ -352,10 +353,14 @@ if (ftdi_write_data_set_chunksize(ftdic, 256)) { msg_perr("Unable to set chunk size (%s).\n", ftdi_get_error_string(ftdic)); } + if (ftdi_set_bitmode(ftdic, 0x00, BITMODE_BITBANG_RESET) < 0) { + msg_perr("Unable to reset MPSSE controller (%s).\n", ftdi_get_error_string(ftdic)); + } + if (ftdi_set_bitmode(ftdic, 0x00, BITMODE_BITBANG_SPI) < 0) { msg_perr("Unable to set bitmode to SPI (%s).\n", ftdi_get_error_string(ftdic)); } if (clock_5x) {

2 1

Re: [flashrom] Gmail's blocking flashrom mails
by Stefan Tauner 26 Jan '15

26 Jan '15

On Sat, 17 Jan 2015 21:13:57 -0800 Svetoslav Trochev <svetoslav.trochev(a)gmail.com> wrote: > Hi Stefan, > > Could you please explain a bit more the issue. I have been receiving > flashrom mails just fine ( and I have free gmail account). Once on a while > some of the e-mails would be marked as suspected spam. The most often this > happens on mail originated from East Europe. Are we are talking about those > e-mails, or entirely different issue? Yes. Your and the subscriptions of all others directly addressed has been disabled because too many emails were not accepted by gmail. I am not 100% sure if that was just some kind of greylisting and gmail did accept the mails eventually, but it did report a permanent failure back to our mail server. This looks as follows: SMTP error from remote mail server after end of data: host gmail-smtp-in.l.google.com [2a00:1450:4013:c00::1a]: 550-5.7.1 [2001:470:9f5b::25 12] Our system has detected that this message 550-5.7.1 is likely unsolicited mail. To reduce the amount of spam sent to 550-5.7.1 Gmail, this message has been blocked. Please visit 550-5.7.1 http://support.google.com/mail/bin/answer.py?hl=en&answer=188131 for 550 5.7.1 more information. s3si2581668wjx.75 - gsmtp If mailman (the mailing list software) gets too many of those for a certain subscriber address then it automatically unsubscribes the recipient because it does expect this to be permanent. There are some things we could change on the mail server to mitigate it as I wrote before, but it seems that nothing really works and it is rather a race between gmail demanding senders to jump through further hoops and the senders implementing that. I am not too familiar with mail and DNS servers though. If you want more technical details I can ask Patrick to respond. > The main reason I use GMail as my > public e-mail address is exactly their spam filter. It is by far the most > accurate of Hotmail, Yahoo or almost working e-mail service provided by my > ISPs available to me. > > Do you have any other recommendations for e-mail provider?! One that allows to whitelist mailing lists manually for example ;) -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

3 3

GF615M-P33: flashrom -V
by Parker Reed 25 Jan '15

25 Jan '15

flashrom v0.9.7-r1711 on Linux 3.18.2-2-ARCH (x86_64) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.0, GCC 4.8.2, little endian Command line (2 args): flashrom --programmer=internal -V Calibrating delay loop... OS timer resolution is 1 usecs, 1406M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 999 us, 10000 myus = 10121 us, 4 myus = 4 us, OK. Initializing internal programmer No coreboot table found. DMI string system-manufacturer: "MICRO-STAR INTERNATIONAL CO.,LTD" DMI string system-product-name: "MS-7597" DMI string system-version: "1.0" DMI string baseboard-manufacturer: "MICRO-STAR INTERNATIONAL CO.,LTD" DMI string baseboard-product-name: "GF615M-P33 (MS-7597)" DMI string baseboard-version: "1.0" DMI string chassis-type: "Desktop" Found chipset "NVIDIA MCP61" with PCI ID 10de:03e0. Enabling flash write... This chipset is not really supported yet. Guesswork... ISA/LPC bridge reg 0x8a contents: 0x00, bit 6 is 0, bit 5 is 0 Flash bus type is LPC Found SMBus device 10de:03eb at 00:01:1 MCP SPI BAR is at 0xfec80000 Strange. MCP SPI BAR is valid, but chipset apparently doesn't have SPI enabled. Please send the output of "flashrom -V" to flashrom(a)flashrom.org with your board name: flashrom -V as the subject to help us finish support for your chipset. Thanks. OK. The following protocols are supported: LPC. Probing for AMIC A49LF040A, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Atmel AT49LH002, 256 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL002, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020A, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF080A, 1024 kB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF160C, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040A, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW116, 2048 kB: probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040A, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040B, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V040C, 512 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080A, 1024 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W49V002A, 256 kB: probe_jedec_common: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. Restoring PCI config space for 00:01:0 reg 0x6d Restoring PCI config space for 00:01:0 reg 0x90 Restoring PCI config space for 00:01:0 reg 0x8c Restoring PCI config space for 00:01:0 reg 0x88

1 0

[PATCH] Refine version check of libpci function pci_get_dev.
by Stefan Tauner 25 Jan '15

25 Jan '15

The way more elegant check for the header fails unfortunately on CentOS 4.9 because PCI_LIB_VERSION is not defined at all although the domain parameter is present. This patch jumps through the hoops via an additional check in the Makefile to determine if the function accepts 5 parameters (new version) or not (old version). Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> --- Makefile | 28 ++++++++++++++++++++++++++++ board_enable.c | 2 +- 2 files changed, 29 insertions(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 1f39f41..d5438cf 100644 --- a/Makefile +++ b/Makefile @@ -711,6 +711,8 @@ endif ifeq ($(NEED_PCI), yes) CHECK_LIBPCI = yes FEATURE_CFLAGS += -D'NEED_PCI=1' +FEATURE_CFLAGS += $(shell LC_ALL=C grep -q "OLD_PCI_GET_DEV := yes" .libdeps && printf "%s" "-D'OLD_PCI_GET_DEV=1'") + PROGRAMMER_OBJS += pcidev.o physmap.o hwaccess.o ifeq ($(TARGET_OS), NetBSD) # The libpci we want is called libpciutils on NetBSD and needs NetBSD libpci. @@ -840,6 +842,27 @@ int main(int argc, char **argv) endef export LIBPCI_TEST +define PCI_GET_DEV_TEST +/* Avoid a failing test due to libpci header symbol shadowing breakage */ +#define index shadow_workaround_index +#if !defined __NetBSD__ +#include <pci/pci.h> +#else +#include <pciutils/pci.h> +#endif +struct pci_access *pacc; +struct pci_dev *dev = {0}; +int main(int argc, char **argv) +{ + (void) argc; + (void) argv; + pacc = pci_alloc(); + dev = pci_get_dev(pacc, dev->domain, dev->bus, dev->dev, 1); + return 0; +} +endef +export PCI_GET_DEV_TEST + define LIBUSB0_TEST #include <usb.h> int main(int argc, char **argv) @@ -862,6 +885,11 @@ ifeq ($(CHECK_LIBPCI), yes) echo "Please install libpci headers (package pciutils-devel)."; \ echo "See README for more information."; echo; \ rm -f .test.c .test.o; exit 1) + @printf "Checking version of pci_get_dev... " + @echo "$$PCI_GET_DEV_TEST" > .test.c + @$(CC) -c $(CPPFLAGS) $(CFLAGS) .test.c -o .test.o >/dev/null 2>&1 && \ + ( echo "new version (including PCI domain parameter)."; echo "OLD_PCI_GET_DEV := no" >> .libdeps ) || \ + ( echo "old version (without PCI domain parameter)."; echo "OLD_PCI_GET_DEV := yes" >> .libdeps ) @printf "Checking if libpci is present and sufficient... " @$(CC) $(LDFLAGS) .test.o -o .test$(EXEC_SUFFIX) $(LIBS) $(PCILIBS) >/dev/null && \ echo "yes." || ( echo "no."; \ diff --git a/board_enable.c b/board_enable.c index 456e206..ac361b6 100644 --- a/board_enable.c +++ b/board_enable.c @@ -1047,7 +1047,7 @@ static int nvidia_mcp_gpio_set(int gpio, int raise) return -1; } -#if PCI_LIB_VERSION >= 0x020200 +#if !defined(OLD_PCI_GET_DEV) dev = pci_get_dev(pacc, dev->domain, dev->bus, dev->dev, 1); #else /* pciutils/libpci before version 2.2 is too old to support -- Kind regards, Stefan Tauner

1 0

[commit] r1875 - trunk
by repository service 25 Jan '15

25 Jan '15

Author: stefanct Date: Mon Jan 26 00:57:08 2015 New Revision: 1875 URL: http://flashrom.org/trac/flashrom/changeset/1875 Log: Fix "unterminated variable reference" on ancient versions of GNU make. Add a workaround for the GNU make that shipped with CentOS 4.9, which apparently does not like semicolons in shell code (and which also ignores info functions altogether by the way). Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Acked-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Modified: trunk/Makefile Modified: trunk/Makefile ============================================================================== --- trunk/Makefile Mon Jan 26 00:45:14 2015 (r1874) +++ trunk/Makefile Mon Jan 26 00:57:08 2015 (r1875) @@ -382,7 +382,9 @@ # Inform user if there is no meaningful version string. If there is version information from a VCS print # something anyway because $(info...) will print a line break in any case which would look suspicious. -$(info $(shell ./util/getrevision.sh -c 2>/dev/null || echo "Files don't seem to be under version control." ; \ +# The && between the echos is a workaround for old versions of GNU make that issue the error "unterminated +# variable reference" if a semicolon is used instead. +$(info $(shell ./util/getrevision.sh -c 2>/dev/null || echo "Files don't seem to be under version control." && \ echo "Replacing all version templates with $(VERSION)." )) ###############################################################################

1 0

[commit] r1874 - trunk
by repository service 25 Jan '15

25 Jan '15

Author: stefanct Date: Mon Jan 26 00:45:14 2015 New Revision: 1874 URL: http://flashrom.org/trac/flashrom/changeset/1874 Log: Shadowing fix in nicintel_eeprom.c for ancient libpci. Very old versions (<2.2) of pciutils had a typedef named "word" in types.h. That does not play well with previous local variable names of nicintel_eeprom.c. Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Acked-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Modified: trunk/nicintel_eeprom.c Modified: trunk/nicintel_eeprom.c ============================================================================== --- trunk/nicintel_eeprom.c Mon Jan 26 00:42:57 2015 (r1873) +++ trunk/nicintel_eeprom.c Mon Jan 26 00:45:14 2015 (r1874) @@ -103,7 +103,7 @@ return 1; } -static int nicintel_ee_read_word(unsigned int addr, uint16_t *word) +static int nicintel_ee_read_word(unsigned int addr, uint16_t *data) { uint32_t tmp = BIT(EERD_START) | (addr << EERD_ADDR); pci_mmio_writel(tmp, nicintel_eebar + EERD); @@ -113,7 +113,7 @@ for (i = 0; i < 10000000; i++) { tmp = pci_mmio_readl(nicintel_eebar + EERD); if (tmp & BIT(EERD_DONE)) { - *word = (tmp >> EERD_DATA) & 0xffff; + *data = (tmp >> EERD_DATA) & 0xffff; return 0; } } @@ -123,26 +123,26 @@ static int nicintel_ee_read(struct flashctx *flash, uint8_t *buf, unsigned int addr, unsigned int len) { - uint16_t word; + uint16_t data; /* The NIC interface always reads 16 b words so we need to convert the address and handle odd address * explicitly at the start (and also at the end in the loop below). */ if (addr & 1) { - if (nicintel_ee_read_word(addr / 2, &word)) + if (nicintel_ee_read_word(addr / 2, &data)) return -1; - *buf++ = word & 0xff; + *buf++ = data & 0xff; addr++; len--; } while (len > 0) { - if (nicintel_ee_read_word(addr / 2, &word)) + if (nicintel_ee_read_word(addr / 2, &data)) return -1; - *buf++ = word & 0xff; + *buf++ = data & 0xff; addr++; len--; if (len > 0) { - *buf++ = (word >> 8) & 0xff; + *buf++ = (data >> 8) & 0xff; addr++; len--; }

1 0

[PATCH] ft2232_spi.c: use ftdi.h named constants instead of magic numbers
by Antony Pavlov 24 Jan '15

24 Jan '15

Signed-off-by: Antony Pavlov <antonynpavlov(a)gmail.com> --- ft2232_spi.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ft2232_spi.c b/ft2232_spi.c index 7e7e2b1..4921caa 100644 --- a/ft2232_spi.c +++ b/ft2232_spi.c @@ -350,7 +350,7 @@ int ft2232_spi_init(void) if (clock_5x) { msg_pdbg("Disable divide-by-5 front stage\n"); - buf[0] = 0x8a; /* Disable divide-by-5. */ + buf[0] = DIS_DIV_5; if (send_buf(ftdic, buf, 1)) { ret = -5; goto ftdi_err; @@ -361,7 +361,7 @@ int ft2232_spi_init(void) } msg_pdbg("Set clock divisor\n"); - buf[0] = 0x86; /* command "set divisor" */ + buf[0] = TCK_DIVISOR; buf[1] = (divisor / 2 - 1) & 0xff; buf[2] = ((divisor / 2 - 1) >> 8) & 0xff; if (send_buf(ftdic, buf, 3)) { @@ -374,7 +374,7 @@ int ft2232_spi_init(void) /* Disconnect TDI/DO to TDO/DI for loopback. */ msg_pdbg("No loopback of TDI/DO TDO/DI\n"); - buf[0] = 0x85; + buf[0] = LOOPBACK_END; if (send_buf(ftdic, buf, 1)) { ret = -7; goto ftdi_err; @@ -453,7 +453,7 @@ static int ft2232_spi_send_command(struct flashctx *flash, * read command, then do the fetch of the results. */ if (readcnt) { - buf[i++] = 0x20; + buf[i++] = MPSSE_DO_READ; buf[i++] = (readcnt - 1) & 0xff; buf[i++] = ((readcnt - 1) >> 8) & 0xff; ret = send_buf(ftdic, buf, i); -- 2.1.4

3 5

[commit] r1872 - trunk
by repository service 24 Jan '15

24 Jan '15

Author: stefanct Date: Sun Jan 25 04:52:47 2015 New Revision: 1872 URL: http://flashrom.org/trac/flashrom/changeset/1872 Log: ft2232_spi.c: use constants from ftdi.h instead of magic numbers. Also, improve documentation of static variables cs_bits and pindir. Signed-off-by: Antony Pavlov <antonynpavlov(a)gmail.com> Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Acked-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Modified: trunk/ft2232_spi.c Modified: trunk/ft2232_spi.c ============================================================================== --- trunk/ft2232_spi.c Sat Jan 24 16:16:14 2015 (r1871) +++ trunk/ft2232_spi.c Sun Jan 25 04:52:47 2015 (r1872) @@ -80,13 +80,16 @@ #define BITMODE_BITBANG_NORMAL 1 #define BITMODE_BITBANG_SPI 2 -/* Set data bits low-byte command: +/* The variables cs_bits and pindir store the values for the "set data bits low byte" MPSSE command that + * sets the initial state and the direction of the I/O pins. The pin offsets are as follows: + * SCK is bit 0. + * DO is bit 1. + * DI is bit 2. + * CS is bit 3. + * + * The default values (set below) are used for most devices: * value: 0x08 CS=high, DI=low, DO=low, SK=low * dir: 0x0b CS=output, DI=input, DO=output, SK=output - * - * JTAGkey(2) needs to enable its output via Bit4 / GPIOL0 - * value: 0x18 OE=high, CS=high, DI=low, DO=low, SK=low - * dir: 0x1b OE=output, CS=output, DI=input, DO=output, SK=output */ static uint8_t cs_bits = 0x08; static uint8_t pindir = 0x0b; @@ -200,6 +203,9 @@ } else if (!strcasecmp(arg, "jtagkey")) { ft2232_type = AMONTEC_JTAGKEY_PID; channel_count = 2; + /* JTAGkey(2) needs to enable its output via Bit4 / GPIOL0 + * value: 0x18 OE=high, CS=high, DI=low, DO=low, SK=low + * dir: 0x1b OE=output, CS=output, DI=input, DO=output, SK=output */ cs_bits = 0x18; pindir = 0x1b; } else if (!strcasecmp(arg, "picotap")) { @@ -228,6 +234,9 @@ ft2232_vid = OLIMEX_VID; ft2232_type = OLIMEX_ARM_OCD_PID; channel_count = 2; + /* arm-usb-ocd(-h) has an output buffer that needs to be enabled by pulling ADBUS4 low. + * value: 0x08 #OE=low, CS=high, DI=low, DO=low, SK=low + * dir: 0x1b #OE=output, CS=output, DI=input, DO=output, SK=output */ cs_bits = 0x08; pindir = 0x1b; } else if (!strcasecmp(arg, "arm-usb-tiny")) { @@ -238,6 +247,7 @@ ft2232_vid = OLIMEX_VID; ft2232_type = OLIMEX_ARM_OCD_H_PID; channel_count = 2; + /* See arm-usb-ocd */ cs_bits = 0x08; pindir = 0x1b; } else if (!strcasecmp(arg, "arm-usb-tiny-h")) { @@ -350,7 +360,7 @@ if (clock_5x) { msg_pdbg("Disable divide-by-5 front stage\n"); - buf[0] = 0x8a; /* Disable divide-by-5. */ + buf[0] = DIS_DIV_5; if (send_buf(ftdic, buf, 1)) { ret = -5; goto ftdi_err; @@ -361,7 +371,7 @@ } msg_pdbg("Set clock divisor\n"); - buf[0] = 0x86; /* command "set divisor" */ + buf[0] = TCK_DIVISOR; buf[1] = (divisor / 2 - 1) & 0xff; buf[2] = ((divisor / 2 - 1) >> 8) & 0xff; if (send_buf(ftdic, buf, 3)) { @@ -374,7 +384,7 @@ /* Disconnect TDI/DO to TDO/DI for loopback. */ msg_pdbg("No loopback of TDI/DO TDO/DI\n"); - buf[0] = 0x85; + buf[0] = LOOPBACK_END; if (send_buf(ftdic, buf, 1)) { ret = -7; goto ftdi_err; @@ -441,7 +451,7 @@ buf[i++] = pindir; if (writecnt) { - buf[i++] = 0x11; + buf[i++] = MPSSE_DO_WRITE | MPSSE_WRITE_NEG; buf[i++] = (writecnt - 1) & 0xff; buf[i++] = ((writecnt - 1) >> 8) & 0xff; memcpy(buf + i, writearr, writecnt); @@ -453,7 +463,7 @@ * read command, then do the fetch of the results. */ if (readcnt) { - buf[i++] = 0x20; + buf[i++] = MPSSE_DO_READ; buf[i++] = (readcnt - 1) & 0xff; buf[i++] = ((readcnt - 1) >> 8) & 0xff; ret = send_buf(ftdic, buf, i);

1 0

S25FL128SAIF00 erase doesn't work
by Alexander Graf 24 Jan '15

24 Jan '15

Hi, Trying to write to an S25FL128S (SAIF00) chip directly connected to SPI on a BeagleBone Black I'm running into weird issues. I can read the chip just fine, but writing fails horribly in the erase step already. I'm pretty puzzled on why this could be (#WP is disconnected, connecting it to VCC doesn't change anything) and discussing this with Stefan on IRC he didn't have any immediate smart idea either. However, if anyone (including Stefan) has any idea what could really be causing this, I'm more than happy to heard suggestions. The chip itself is brand new - I only wrote some initial data to it once (which didn't manage to ever write the first 0x200 bytes either). Thanks a lot! Alex --- $ flashrom -p linux_spi:dev=/dev/spidev1.0 -w foo.raw -c "S25FL128S......0" -V flashrom v0.9.7-r1871 on Linux 3.11.10-91-default (armv7l) flashrom is free software, get the source code at http://www.flashrom.org flashrom was built with libpci 3.2.0, GCC 4.8.1 20130909 [gcc-4_8-branch revision 202388], little endian Command line (7 args): flashrom -p linux_spi:dev=/dev/spidev1.0 -w foo.raw -c S25FL128S......0 -V Calibrating delay loop... OS timer resolution is 3 usecs, 183M loops per second, 10 myus = 12 us, 100 myus = 103 us, 1000 myus = 1134 us, 10000 myus = 10123 us, 12 myus = 15 us, OK. Initializing linux_spi programmer Using device /dev/spidev1.0 The following protocols are supported: SPI. Probing for Spansion S25FL128S......0, 16384 kB: probe_spi_rdid_generic: id1 0x01, id2 0x2018 Found Spansion flash chip "S25FL128S......0" (16384 kB, SPI) on linux_spi. Chip status register is 0x00. Chip status register: Status Register Write Disable (SRWD, SRP, ...) is not set Chip status register: Program Fail Flag (P_FAIL) is not set Chip status register: Erase Fail Flag (E_FAIL) is not set Chip status register: Block Protect 2 (BP2) is not set Chip status register: Block Protect 1 (BP1) is not set Chip status register: Block Protect 0 (BP0) is not set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set This chip may contain one-time programmable memory. flashrom cannot read and may never be able to write it, hence it may not be able to completely clone the contents of this chip (see man page for details). === This flash part has status UNTESTED for operations: PROBE READ ERASE WRITE The test status of this chip may have been updated in the latest development version of flashrom. If you are running the latest development version, please email a report to flashrom(a)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... Trying erase function 0... 0x000000-0x00ffff:EFAILED at 0x00001000! Expected=0xff, Found=0x4e, failed byte count from 0x00000000-0x0000ffff: 0xee4a ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Trying erase function 1... 0x000000-0xffffff:EFAILED at 0x00001000! Expected=0xff, Found=0x4e, failed byte count from 0x00000000-0x00ffffff: 0xa04d5c ERASE FAILED! Reading current flash chip contents... done. Looking for another erase function. Trying erase function 2... 0x000000-0xffffff:EFAILED at 0x00001000! Expected=0xff, Found=0x4e, failed byte count from 0x00000000-0x00ffffff: 0xa04d5c ERASE FAILED! Looking for another erase function. No usable erase functions left. FAILED! Uh oh. Erase/write failed.Checking if anything has changed. Reading current flash chip contents... done. Good, writing to the flash chip apparently didn't do anything. Please check the connections (especially those to write protection pins) between the programmer and the flash chip. If you think the error is caused by flashrom please report this on IRC at chat.freenode.net (channel #flashrom) or mail flashrom(a)flashrom.org, thanks!

1 0

Re: [flashrom] AT45db642d - SPI Mode Ft2232h - Successfull operation - Read/Wirte /Erase
by Stefan Tauner 24 Jan '15

24 Jan '15

On Sat, 24 Jan 2015 10:20:45 -0800 Mahesh Mokal <mahesh.mokal(a)gmail.com> wrote: > Hi. > > Flashrom is wonderfull project and help me lot. i am successfully able > to copy AT45db642d into new chip. i used Ft2232H chip in FT2232SPI > Programming Option. Read, Write , Erase Successfully working, Chip > is successfully tested on Production board > > Details > Operatig System- Ubunty 14,04 ,32 Bit > Flashrom version - flashrom_0.9.7+r1852-1 > Programmer - FT2232SPI > Tested Chip - AT45db642D > Read- Success > Write - Success > Erase- Success > > > Logs attached for referece Hello Mahesh, thanks for your report! I have marked the flash chip as fully tested and will commit that later together with other small changes. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

← Newer
1
2
3
4
5
6
7
...
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom January 2015