- flashrom - mail.coreboot.org

Re: [flashrom] Asus P5W-DH board enable problem
by Stefan Tauner 18 Feb '15

18 Feb '15

On Wed, 18 Feb 2015 16:26:35 +0300 "nicolae788 ." <nicolae788(a)gmail.com> wrote: > Hello, > > I am trying to write a chip SST 49LF008A in a P5W-DH board. This is not the > original chip of the board, it's a hot flash. The flashrom properly detects > the ICH7R chipset and the chip described above, but can only read from it > no erase or write. The problem is that it does not enable the TBL pin on > the chip, it stays low. I checked if the pin can be enabled by using the > onboard flash utility from whitin the original BIOS of this board an i get > a high on that pin ( +3.3V ) so it means that the chipset it's doing the > work if properly enabled. > […] > Can someone please instruct me on how to proceed further? Thank you very > much for your kindness. > Hi, as the name suggests a board enable is rather board-specific. It is usually required to toggle a GPIO pin of the southbridge that is connected to the TBL or #WP pin of the flash chip. What needs to be done is actually encoded in the BIOS image (not the flash tool) so it can be recovered by reverse engineering. See http://flashrom.org/Board_Enable for more details. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Asus P5W-DH board enable problem
by nicolae788 . 18 Feb '15

18 Feb '15

Hello, I am trying to write a chip SST 49LF008A in a P5W-DH board. This is not the original chip of the board, it's a hot flash. The flashrom properly detects the ICH7R chipset and the chip described above, but can only read from it no erase or write. The problem is that it does not enable the TBL pin on the chip, it stays low. I checked if the pin can be enabled by using the onboard flash utility from whitin the original BIOS of this board an i get a high on that pin ( +3.3V ) so it means that the chipset it's doing the work if properly enabled. I tryied specifying another board model that has the same chipset, but it exists with a message that " no suitable boar enable found for the board name and manufacturer...". I tried with version 0.9.7-r1711 and 0.9.5.2-r1546 under linux. Both gave the same results. When it tries to erase/write to the chip i get "erase failed at 0x00000000! expected=0xff read=0x6d, failed byte count from 0x00000000 - 0x0000ffff: 0x837 erase failed ! Reading current flash chip contents...done. erase failed at 0x00000000! Expected 0x0xff, Read=0x6d, failed byte count from 0x00000000 - 0x0000ffff: 0x66dc Erase failed ! Failed ! Can someone please instruct me on how to proceed further? Thank you very much for your kindness. Alex.

1 0

[PATCH] Fix a number of problems in mstarddc_spi.c.
by Stefan Tauner 18 Feb '15

18 Feb '15

Coverity has brought up the following problems: mstarddc_spi_send_command(): - CID 1270702: bad comparison of malloced pointer 'cmd'. - CID 1270701: a NULL pointer dereference possible because of above. Simply checking the return value of malloc in a valid way fixes both problems. mstarddc_spi_init(): - CID 1270699 and 1270700: Memory leak of i2c_device. This patch revamps the function in various ways to fix these issues and some other irritating bits. It reduces scopes of variables where possible, pushes the code towards our coding standards and introduces a label-based resource cleanup at the end. Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> --- mstarddc_spi.c | 53 ++++++++++++++++++++++++++++------------------------- 1 file changed, 28 insertions(+), 25 deletions(-) diff --git a/mstarddc_spi.c b/mstarddc_spi.c index 0b41a1b..809d690 100644 --- a/mstarddc_spi.c +++ b/mstarddc_spi.c @@ -74,37 +74,37 @@ static int mstarddc_spi_shutdown(void *data) /* Returns 0 upon success, a negative number upon errors. */ int mstarddc_spi_init(void) { - char *i2c_device; - char *i2c_address; - char *noreset; + int ret = 0; // Get device, address from command-line - i2c_device = extract_programmer_param("dev"); - if (i2c_device && strlen(i2c_device)) { - if ((i2c_address = strchr(i2c_device, ':'))) { + char *i2c_device = extract_programmer_param("dev"); + if (i2c_device != NULL && strlen(i2c_device) > 0) { + char *i2c_address = strchr(i2c_device, ':'); + if (i2c_address != NULL) { *i2c_address = '\0'; i2c_address++; } - if (!i2c_address || !strlen(i2c_address)) { + if (i2c_address == NULL || strlen(i2c_address) == 0) { msg_perr("Error: no address specified.\n" "Use flashrom -p mstarddc_spi:dev=/dev/device:address.\n"); - return -1; + ret = -1; + goto out; } - mstarddc_addr = strtol(i2c_address, NULL, 16); + mstarddc_addr = strtol(i2c_address, NULL, 16); // FIXME: error handling } else { msg_perr("Error: no device specified.\n" "Use flashrom -p mstarddc_spi:dev=/dev/device:address.\n"); - return -1; + ret = -1; + goto out; } - msg_pinfo("Info: Will try to use device %s and address 0x%02x.\n", - i2c_device, mstarddc_addr); + msg_pinfo("Info: Will try to use device %s and address 0x%02x.\n", i2c_device, mstarddc_addr); // Get noreset=1 option from command-line - if ((noreset = extract_programmer_param("noreset")) - && noreset[0] == '1') + char *noreset = extract_programmer_param("noreset"); + if (noreset != NULL && noreset[0] == '1') mstarddc_doreset = 0; - msg_pinfo("Info: WILL %sreset the device at the end.\n", - mstarddc_doreset ? "" : "NOT "); + free(noreset); + msg_pinfo("Info: Will %sreset the device at the end.\n", mstarddc_doreset ? "" : "NOT "); // Open device if ((mstarddc_fd = open(i2c_device, O_RDWR)) < 0) { switch (errno) { @@ -119,16 +119,17 @@ int mstarddc_spi_init(void) i2c_device); break; default: - msg_perr("Error opening %s: errno %d.\n", - i2c_device, errno); + msg_perr("Error opening %s: %s.\n", i2c_device, strerror(errno)); } - return -1; + ret = -1; + goto out; } // Set slave address if (ioctl(mstarddc_fd, I2C_SLAVE, mstarddc_addr) < 0) { msg_perr("Error setting slave address 0x%02x: errno %d.\n", mstarddc_addr, errno); - return -1; + ret = -1; + goto out; } // Enable ISP mode uint8_t cmd[5] = { 'M', 'S', 'T', 'A', 'R' }; @@ -141,7 +142,8 @@ int mstarddc_spi_init(void) msg_perr("Error enabling ISP mode: errno %d & %d.\n" "Please check that device (%s) and address (0x%02x) are correct.\n", enable_err, errno, i2c_device, mstarddc_addr); - return -1; + ret = -1; + goto out; } } // Register shutdown function @@ -149,7 +151,9 @@ int mstarddc_spi_init(void) // Register programmer register_spi_master(&spi_master_mstarddc); - return 0; +out: + free(i2c_device); + return ret; } /* Returns 0 upon success, a negative number upon errors. */ @@ -160,9 +164,8 @@ static int mstarddc_spi_send_command(struct flashctx *flash, unsigned char *readarr) { int ret = 0; - uint8_t *cmd; - - if ((cmd = malloc((writecnt + 1) * sizeof(uint8_t))) < 0) { + uint8_t *cmd = malloc((writecnt + 1) * sizeof(uint8_t)); + if (cmd == NULL) { msg_perr("Error allocating memory: errno %d.\n", errno); ret = -1; } -- Kind regards, Stefan Tauner

1 0

Re: [flashrom] flashrom support for Spansion S25FL128S
by Stefan Tauner 17 Feb '15

17 Feb '15

On Tue, 17 Feb 2015 04:46:16 -0600 <Ron_Taylor(a)DELL.com> wrote: > 0x54: 0x000f0000 FREG0: Warning: Flash Descriptor region (0x00000000-0x0000ffff) is read-only. > 0x58: 0x07ff0200 FREG1: BIOS region (0x00200000-0x007fffff) is read-write. The problem is that the flash descriptor regions do not cover the whole flash chip. There is a hole between 0x10000 and 0x1fffff (and the second half of the chip is not mapped either). The chipset does not allow accessing these holes but flashrom does try it by default anyway because it reads the complete chip. With some patching of flashrom this can be avoided but there is no ready solution as far as I know. There are some patches regarding layout handling that might be part of a possible solution, cf. http://patchwork.coreboot.org/project/flashrom/list/ -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] ARM-USB-OCD works!
by Stefan Tauner 17 Feb '15

17 Feb '15

On Tue, 17 Feb 2015 19:04:24 +0100 skrizi(a)web.de wrote: > Hi, > i just want to confirm that the ARM-USB-OCD (without H suffix) works too so you can check this in the supported devices. > […] Hello skrizi, thanks for your report! I have marked the ARM-USB-OCD as working OK and will commit that later together with other small changes. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

SPI flash, correction
by skrizi＠web.de 17 Feb '15

17 Feb '15

1 0

ARM-USB-OCD works!
by skrizi＠web.de 17 Feb '15

17 Feb '15

1 0

Re: [flashrom] flashrom support for Spansion S25FL128S
by Antonio Ospite 17 Feb '15

17 Feb '15

On Mon, 16 Feb 2015 20:50:39 -0600 <Lakesh_Sharma(a)DELL.com> wrote: > > Hi Idwer > > I had fixed the compilation issues and could generate the binary. > I tried to read the bios chip first, but it does not seem to recognize S25FL128S > > (1) It lists the chip as supported: > flashrom# ./flashrom --list-supported | grep S25FL128S > Spansion S25FL128S......0 16384 SPI > Spansion S25FL128S......1 16384 SPI > > > (2) However when it is specified with --chip options, it says not supported or unknown. > > flashrom# ./flashrom --chip S25FL128S flashrom# ./flashrom --chip "SS25FL128S......0" or the other one depending on your actual chip. The dots are placeholders for variable characters in the chip name for different chip variants. And remember to add the -c option also when you perform the other operations, flashrom still can't discriminate between the variants on its own. > flashrom v0.9.8-rc1-r1883 on Linux 3.14.0-rc8 (x86_64) > flashrom is free software, get the source code at http://www.flashrom.org > > Error: Unknown chip 'S25FL128S' specified. > Run flashrom -L to view the hardware supported in this flashrom version. > > > (3) Tried to read the chip first. It could not determine the chip type. > > > ./flashrom -p internal:laptop=this_is_not_a_laptop -r file_name.bin > flashrom v0.9.8-rc1-r1883 on Linux 3.14.0-rc8 (x86_64) > flashrom is free software, get the source code at http://www.flashrom.org > > Calibrating delay loop... OK. > ======================================================================== > WARNING! You may be running flashrom on an unsupported laptop. We could > not detect this for sure because your vendor has not setup the SMBIOS > tables correctly. You can enforce execution by adding > '-p internal:laptop=this_is_not_a_laptop' to the command line, but > please read the following warning if you are not sure. > > Laptops, notebooks and netbooks are difficult to support and we > recommend to use the vendor flashing utility. The embedded controller > (EC) in these machines often interacts badly with flashing. > See the manpage and http://www.flashrom.org/Laptops for details. > > If flash is shared with the EC, erase is guaranteed to brick your laptop > and write may brick your laptop. > Read and probe may irritate your EC and cause fan failure, backlight > failure and sudden poweroff. > You have been warned. > ======================================================================== > Proceeding anyway because user forced us to. > Found chipset "Intel Avoton/Rangeley". > This chipset is marked as untested. If you are using an up-to-date version > of flashrom *and* were (not) able to successfully update your firmware with it, > then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. > Thank you! > Enabling flash write... Warning: SPI Configuration Lockdown activated. > OK. > Found Spansion flash chip "S25FL127S-64kB" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. > Found Spansion flash chip "S25FL127S-256kB" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. > Found Spansion flash chip "S25FL128P......0" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. > Found Spansion flash chip "S25FL128P......1" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. > Found Spansion flash chip "S25FL128S......0" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. > Found Spansion flash chip "S25FL128S......1" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. > Found Spansion flash chip "S25FL129P......0" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. > Found Spansion flash chip "S25FL129P......1" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. > Multiple flash chip definitions match the detected chip(s): "S25FL127S-64kB", "S25FL127S-256kB", "S25FL128P......0", "S25FL128P......1", "S25FL128S......0", "S25FL128S......1", "S25FL129P......0", "S25FL129P......1" > Please specify which chip definition to use with the -c <chipname> option. > IOT just do what flashrom is telling you here :) Ciao, Antonio -- Antonio Ospite http://ao2.it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?

2 1

Re: [flashrom] flashrom support for Spansion S25FL128S
by Lakesh_Sharma＠DELL.com 17 Feb '15

17 Feb '15

Hi Idwer I had fixed the compilation issues and could generate the binary. I tried to read the bios chip first, but it does not seem to recognize S25FL128S (1) It lists the chip as supported: flashrom# ./flashrom --list-supported | grep S25FL128S Spansion S25FL128S......0 16384 SPI Spansion S25FL128S......1 16384 SPI (2) However when it is specified with --chip options, it says not supported or unknown. flashrom# ./flashrom --chip S25FL128S flashrom v0.9.8-rc1-r1883 on Linux 3.14.0-rc8 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org Error: Unknown chip 'S25FL128S' specified. Run flashrom -L to view the hardware supported in this flashrom version. (3) Tried to read the chip first. It could not determine the chip type. ./flashrom -p internal:laptop=this_is_not_a_laptop -r file_name.bin flashrom v0.9.8-rc1-r1883 on Linux 3.14.0-rc8 (x86_64) flashrom is free software, get the source code at http://www.flashrom.org Calibrating delay loop... OK. ======================================================================== WARNING! You may be running flashrom on an unsupported laptop. We could not detect this for sure because your vendor has not setup the SMBIOS tables correctly. You can enforce execution by adding '-p internal:laptop=this_is_not_a_laptop' to the command line, but please read the following warning if you are not sure. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See the manpage and http://www.flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. ======================================================================== Proceeding anyway because user forced us to. Found chipset "Intel Avoton/Rangeley". This chipset is marked as untested. If you are using an up-to-date version of flashrom *and* were (not) able to successfully update your firmware with it, then please email a report to flashrom(a)flashrom.org including a verbose (-V) log. Thank you! Enabling flash write... Warning: SPI Configuration Lockdown activated. OK. Found Spansion flash chip "S25FL127S-64kB" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. Found Spansion flash chip "S25FL127S-256kB" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. Found Spansion flash chip "S25FL128P......0" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. Found Spansion flash chip "S25FL128P......1" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. Found Spansion flash chip "S25FL128S......0" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. Found Spansion flash chip "S25FL128S......1" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. Found Spansion flash chip "S25FL129P......0" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. Found Spansion flash chip "S25FL129P......1" (16384 kB, SPI) mapped at physical address 0x00000000ff000000. Multiple flash chip definitions match the detected chip(s): "S25FL127S-64kB", "S25FL127S-256kB", "S25FL128P......0", "S25FL128P......1", "S25FL128S......0", "S25FL128S......1", "S25FL129P......0", "S25FL129P......1" Please specify which chip definition to use with the -c <chipname> option. regards lakesh ________________________________________ From: Sharma, Lakesh Sent: Monday, February 16, 2015 3:42 PM To: Idwer Vollering Cc: flashrom; Taylor, Ron; Natarajan, Kannan Subject: RE: [flashrom] flashrom support for Spansion S25FL128S Dell - Internal Use - Confidential Hi Idwer I could not access the svn based link. Also the changeset link is not accessible. So instead I have download it from https://github.com/jhcloos/flashrom as it stated that “Mirror of svn://flashrom.org/flashrom” Once I try to compile it, I see following error. Can you pls help. flashrom > make Replacing all version templates with 0.9.8-rc1-r1883. Package libftdi was not found in the pkg-config search path. Perhaps you should add the directory containing `libftdi.pc' to the PKG_CONFIG_PATH environment variable No package 'libftdi' found Package libusb was not found in the pkg-config search path. Perhaps you should add the directory containing `libusb.pc' to the PKG_CONFIG_PATH environment variable No package 'libusb' found Checking for a C compiler... found. Target arch is x86 Target OS is Linux Checking for libpci headers... found. Checking version of pci_get_dev... new version (including PCI domain parameter). Checking if libpci is present and sufficient... yes. Checking for libusb-0.1/libusb-compat headers... .test.c:5:17: fatal error: usb.h: No such file or directory #include <usb.h> ^ compilation terminated. not found. Please install libusb-0.1 headers or libusb-compat headers. See README for more information. make: *** [hwlibs] Error 1 -----Original Message----- From: Idwer Vollering [mailto:vidwer@gmail.com] Sent: Monday, February 16, 2015 3:09 PM To: Sharma, Lakesh Cc: flashrom; Taylor, Ron; Natarajan, Kannan Subject: Re: [flashrom] flashrom support for Spansion S25FL128S 2015-02-16 22:19 GMT+01:00 : > Dell - Internal Use - Confidential This disclaimer is useless on a public mailing list ;) > > Hello flashrom team. > > > > > > We are trying to access Spansion S25FL128S chip using flashrom (ver 0.9.7). > > It is connected to Rangeley cpu using SPI i/f. > > It seems that this chip is not supported in current version of flashrom ? Support for that particular chip is present in development code, see subversion revision r1858 ( http://tracker.coreboot.org/trac/flashrom/changeset/1858 ). You can obtain the development code through the steps mentioned here: http://flashrom.org/Downloads#Installation_from_source > > Pls see the errors seen during read and write in attachments. > > > > Do we need to import patch listed in url below for suppothing this chip: > > > > http://flashrom.flashrom.narkive.com/zDxnVzWn/s25fl128s-0-on-usbblaste > r-spi > > > > > > regards > > lakesh HTH, Idwer > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

1 0

Re: [flashrom] flashrom support for Spansion S25FL128S
by Lakesh_Sharma＠DELL.com 17 Feb '15

17 Feb '15

Dell - Internal Use - Confidential Hi Idwer I could not access the svn based link. Also the changeset link is not accessible. So instead I have download it from https://github.com/jhcloos/flashrom as it stated that "Mirror of svn://flashrom.org/flashrom" Once I try to compile it, I see following error. Can you pls help. flashrom > make Replacing all version templates with 0.9.8-rc1-r1883. Package libftdi was not found in the pkg-config search path. Perhaps you should add the directory containing `libftdi.pc' to the PKG_CONFIG_PATH environment variable No package 'libftdi' found Package libusb was not found in the pkg-config search path. Perhaps you should add the directory containing `libusb.pc' to the PKG_CONFIG_PATH environment variable No package 'libusb' found Checking for a C compiler... found. Target arch is x86 Target OS is Linux Checking for libpci headers... found. Checking version of pci_get_dev... new version (including PCI domain parameter). Checking if libpci is present and sufficient... yes. Checking for libusb-0.1/libusb-compat headers... .test.c:5:17: fatal error: usb.h: No such file or directory #include <usb.h> ^ compilation terminated. not found. Please install libusb-0.1 headers or libusb-compat headers. See README for more information. make: *** [hwlibs] Error 1 -----Original Message----- From: Idwer Vollering [mailto:vidwer@gmail.com] Sent: Monday, February 16, 2015 3:09 PM To: Sharma, Lakesh Cc: flashrom; Taylor, Ron; Natarajan, Kannan Subject: Re: [flashrom] flashrom support for Spansion S25FL128S 2015-02-16 22:19 GMT+01:00 : > Dell - Internal Use - Confidential This disclaimer is useless on a public mailing list ;) > > Hello flashrom team. > > > > > > We are trying to access Spansion S25FL128S chip using flashrom (ver 0.9.7). > > It is connected to Rangeley cpu using SPI i/f. > > It seems that this chip is not supported in current version of flashrom ? Support for that particular chip is present in development code, see subversion revision r1858 ( http://tracker.coreboot.org/trac/flashrom/changeset/1858 ). You can obtain the development code through the steps mentioned here: http://flashrom.org/Downloads#Installation_from_source > > Pls see the errors seen during read and write in attachments. > > > > Do we need to import patch listed in url below for suppothing this chip: > > > > http://flashrom.flashrom.narkive.com/zDxnVzWn/s25fl128s-0-on-usbblaste > r-spi > > > > > > regards > > lakesh HTH, Idwer > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

1 0

Re: [flashrom] flashrom support for Spansion S25FL128S
by Idwer Vollering 17 Feb '15

17 Feb '15

2015-02-16 22:19 GMT+01:00 <Lakesh_Sharma(a)dell.com>: > Dell - Internal Use - Confidential This disclaimer is useless on a public mailing list ;) > > Hello flashrom team. > > > > > > We are trying to access Spansion S25FL128S chip using flashrom (ver 0.9.7). > > It is connected to Rangeley cpu using SPI i/f. > > It seems that this chip is not supported in current version of flashrom ? Support for that particular chip is present in development code, see subversion revision r1858 ( http://tracker.coreboot.org/trac/flashrom/changeset/1858 ). You can obtain the development code through the steps mentioned here: http://flashrom.org/Downloads#Installation_from_source > > Pls see the errors seen during read and write in attachments. > > > > Do we need to import patch listed in url below for suppothing this chip: > > > > http://flashrom.flashrom.narkive.com/zDxnVzWn/s25fl128s-0-on-usbblaster-spi > > > > > > regards > > lakesh HTH, Idwer > > > _______________________________________________ > flashrom mailing list > flashrom(a)flashrom.org > http://www.flashrom.org/mailman/listinfo/flashrom

1 0

flashrom support for Spansion S25FL128S
by Lakesh_Sharma＠DELL.com 16 Feb '15

16 Feb '15

Dell - Internal Use - Confidential Hello flashrom team. We are trying to access Spansion S25FL128S chip using flashrom (ver 0.9.7). It is connected to Rangeley cpu using SPI i/f. It seems that this chip is not supported in current version of flashrom ? Pls see the errors seen during read and write in attachments. Do we need to import patch listed in url below for suppothing this chip: http://flashrom.flashrom.narkive.com/zDxnVzWn/s25fl128s-0-on-usbblaster-spi regards lakesh

1 0

Re: [flashrom] [PATCH] Add programmer for the MSTAR I2C ISP protocol
by Stefan Tauner 16 Feb '15

16 Feb '15

On Mon, 9 Feb 2015 00:53:40 +0100 Idwer Vollering <vidwer(a)gmail.com> wrote: > 2014-05-04 18:20 GMT+02:00 Alexandre Boeglin <alex(a)boeglin.org>: > > Hi, > > > > Here is a patch, that provides support for the MSTAR ISP protocol. > > > > Basically, among other chips, MSTAR manufactures SoCs that equip TV sets > > and computer screens, and it seems that all of their products use the > > same in-system programming protocol. Basically, they use the DDC channel > > of VGA or DVI connectors, which is actually an I2C bus, to encapsulate > > SPI frames (the flash chip is connected to the SoC through an SPI bus). > > > > I wrote this patch since the screen I bought had a software bug, and the > > manufacturer only released a new firmware binary, but no tool or > > instructions on flashing it. > > > > More details can be found here: > > http://boeglin.org/blog/index.php?entry=Flashing-a-BenQ-Z-series-for-free(d… > > There seems to be a silicon (=SoC) bug as well. > > One can recover by rotating the original image (YOU DO HAVE BACKUPS, > RIGHT :) ) _back_wards - the example assumes the read file is 128 > kilobyte large: > tail -c 1 orig_read.bin > realimage.bin; head -c 131071 orig_read.bin > >> realimage.bin; flashrom -p mstar -w realimage.bin --noverify hm... I wonder if that is a bug in how we do it... but the write routine looks really trivial. Maybe it would be a good idea to start a list with monitors, SoC revisions... (whatever ID data is accessible) that require this hack. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

2 1

Re: [flashrom] Verbose Log
by Stefan Tauner 15 Feb '15

15 Feb '15

On Tue, 6 Jan 2015 22:24:31 +0100 Rainer Spillmann <rainerspillmann(a)googlemail.com> wrote: > Hello Stefan, > > yes. Hello Rainer, I have added your board to our list of supported hardware and will commit that later together with other small changes. > 2015-01-06 0:41 GMT+01:00 Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at>: > > > On Sun, 4 Jan 2015 23:35:09 +0100 > > Rainer Spillmann <rainerspillmann(a)googlemail.com> wrote: > > > > > Hello Flashrom, > > > > > > I could update a Fujitsu Esprimo E5625 (mainboard D2724-A1x) to a Esprimo > > > E5635 (mainboard D2904-A1x) to support AMD AM2/AM3 C3 revision > > processors. > > > I have used the official E5635 bios from the fujitsu website which > > normally > > > would say when trying to update that the bios does not match the system > > due > > > to it is a E5625. The only difference of the E5635 is a chassis lock on > > the > > > mainboard. It now works perfect. > > > > > > Normally the used Esprimo E5625 does only support due to missing > > microcode > > > and older AMD agesa rom up to AMD C2 prozessors witht the official E5625 > > > bios. > > > ( > > > > > http://en.wikipedia.org/wiki/List_of_AMD_Phenom_microprocessors#.22Rana.22_… > > > ) > > > > Hello Rainer, > > > > thank you for your report. The log file got mangled too much to be > > useful (you better should have used the -o option of flashrom I guess). > > Anyway, if I interpret your mail correctly apart from sharing your story > > you also want me to add the D2724-A1x to our list of tested boards. Is > > that correct? > > > > -- > > Kind regards/Mit freundlichen Grüßen, Stefan Tauner > > -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] Add PICkit2 as an SPI programmer
by Justin Chevrier 14 Feb '15

14 Feb '15

The patch as committed works fine here (only tested read). In addition, I tried other voltage values (eg. 2.9V, 3.3V, 3.1V) beyond the 3 currently supported and the hardware happily sets those voltages as well. Thanks again, Justin On Sun, Feb 8, 2015 at 6:23 PM, Justin Chevrier <jchevrier(a)gmail.com> wrote: > Hey Stefan, > > Apologies for the late response. > > voltage=0V along with the 3 voltage levels was basically just a matter > of doing the same thing as the Dediprog code. The 3 voltage levels in > particular made sense as I assumed that covered all current SPI chips. > I'm not sure what the hardware will do if other values are chosen, > although you've piqued my interest. If someone else doesn't beat me to > it, I'll try out the committed (thanks btw) version of the patch and > attempt setting other voltages. > > Justin > > On Sat, Jan 31, 2015 at 9:56 PM, Stefan Tauner > <stefan.tauner(a)alumni.tuwien.ac.at> wrote: >> On Fri, 26 Dec 2014 20:53:47 -0500 >> Justin Chevrier <jchevrier(a)gmail.com> wrote: >> >>> Hi Stefan, >>> >>> It seems you're correct. Signed off is below. >>> >>> Signed-off-by: Justin Chevrier <jchevrier(a)gmail.com> >>> >> >> Does the option to set voltage=0V really make sense? But since this is >> even possible... I would rather set it to 0V at shutdown. If that turns >> off the drivers completely it might be very useful while doing >> in-circuit programming because the programmer could remain attached >> even when the target is running. >> >> Why do we restrict the levels to 3 values although the API seems to >> allow to transmit a much finer resolution? What does the hardware >> actually do with these values? >> >> -- >> Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Intel HM65
by roberto.russo＠x-akseli.fi 12 Feb '15

12 Feb '15

FAILED

1 0

FAILED
by roberto.russo＠x-akseli.fi 12 Feb '15

12 Feb '15

Hi, I've just tried using flashrom on my mb Intel HM65.

1 0

ANNOUNCE: flashrom 0.9.8-rc1 is out - please test!
by Stefan Tauner 12 Feb '15

12 Feb '15

Hello everyone, we have published a release candidate for flashrom 0.9.8 yesterday and plan to do the final release of 0.9.8 at the end of February. You can find a (currently) preliminary summary of changes since 0.9.7 here: http://flashrom.org/Flashrom/0.9.8 The respective status of hardware support is listed here: http://flashrom.org/Flashrom/0.9.8/Supported_Hardware Thanks to everybody contributing to the development of flashrom! Please consider testing your previously and newly supported hardware with the release candidate to find regressions and newly introduced bugs before the stable release, thank you. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

[commit] r1884 - tags/0.9.8-rc1
by repository service 11 Feb '15

11 Feb '15

Author: stefanct Date: Wed Feb 11 23:30:30 2015 New Revision: 1884 URL: http://flashrom.org/trac/flashrom/changeset/1884 Log: Tag flashrom 0.9.8-rc1. Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Acked-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> Acked-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Added: tags/0.9.8-rc1/ - copied from r1883, trunk/

1 0

[commit] r1883 - trunk
by repository service 11 Feb '15

11 Feb '15

Author: stefanct Date: Wed Feb 11 23:21:03 2015 New Revision: 1883 URL: http://flashrom.org/trac/flashrom/changeset/1883 Log: Increase flashrom version number to 0.9.8-rc1. Signed-off-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Acked-by: Stefan Tauner <stefan.tauner(a)alumni.tuwien.ac.at> Acked-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Modified: trunk/Makefile Modified: trunk/Makefile ============================================================================== --- trunk/Makefile Tue Feb 10 09:03:10 2015 (r1882) +++ trunk/Makefile Wed Feb 11 23:21:03 2015 (r1883) @@ -386,7 +386,7 @@ # will not require subversion. The downloadable snapshots are already exported. SVNVERSION := $(shell ./util/getrevision.sh -u 2>/dev/null ) -RELEASE := 0.9.7 +RELEASE := 0.9.8-rc1 VERSION := $(RELEASE)-$(SVNVERSION) RELEASENAME ?= $(VERSION)

1 0

Re: [flashrom] Flashrom Bug for MX25L6405(D) parts
by Stefan Tauner 11 Feb '15

11 Feb '15

On Wed, 11 Feb 2015 17:38:52 +0000 "McMurtrey, Reggie (GE Intelligent Platforms, US)" <reggie.mcmurtrey(a)ge.com> wrote: > Looks like a bug in flashchips.c relating to the MX25L6405(D) chip. The first entry in the .block_erasers array seems to be wrong. > > Currently it is: > > .block_erasers = > { > { > .eraseblocks = { {64 * 1024, 128} }, > .block_erase = spi_block_erase_20, > }, { > […] Thanks for noticing. The block partitioning shown is correct for the 6405 w/o the D suffix. That is what was added originally to flashrom. Later someone (probably myself) has changed the name to include (D) because they share the same RDID, but as you correctly state... the 6405D is erased in (the usual) 4kB-sized blocks with the 0x20 opcode. I have corrected the situation by splitting the definition into two with correct details. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Flashrom Bug for MX25L6405(D) parts
by McMurtrey, Reggie (GE Intelligent Platforms, US) 11 Feb '15

11 Feb '15

Looks like a bug in flashchips.c relating to the MX25L6405(D) chip. The first entry in the .block_erasers array seems to be wrong. Currently it is: .block_erasers = { { .eraseblocks = { {64 * 1024, 128} }, .block_erase = spi_block_erase_20, }, { .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, } }, I believe it should be: .block_erasers = { { .eraseblocks = { {4 * 1024, 2048} }, .block_erase = spi_block_erase_20, }, { .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, } }, --Reggie

1 0

[PATCH 2/2] serprog: fix bad serbuf and opbuf usage checks
by Urja Rannikko 11 Feb '15

11 Feb '15

I wasnt sure of the write-n opbuf checks, but atleast now it should be always checked. Signed-off-by: Urja Rannikko <urjaman(a)gmail.com> --- -- Urja Rannikko

1 0

[PATCH 1/2] serprog: Fix FWH/LPC by implementing serprog_map
by Urja Rannikko 11 Feb '15

11 Feb '15

also make serprog_map report if mapping doesnt fit in the 24-bit address space of serprog. Signed-off-by: Urja Rannikko <urjaman(a)gmail.com> ---

1 0

[PATCH 0/2] serprog bugfixes
by Urja Rannikko 11 Feb '15

11 Feb '15

Hi, I'll be following with two patches; one to implement a serprog_map that just returns the phys_addr for all valid cases and reports a warning if a mapping is attempted that is not in the 24-bit address space of serprog* and does what the current code would do - return NULL. * effectively being the upper 16MB of the 4GB address space of x86. The other one is to fix two stupid serial buffer usage checks that used to check if we havent already gone over by the amount the next message would be (ugh...), also has some opbuf check robusting. Given the closeness of 0.9.8 i thought it'd be nice to suggest these in for that, although i'm not holding my breath. The effect of these two should be localized to serprog parallel/lpc/fwh - which doesnt seem to be getting much use given that lpc/fwh is currently broken - also note that current SPI in-tree effectively doesn't use opbuf much - only for delays, and does all operations synchronously - thus serbuf checks dont affect it either... Thus i think these are safe to include in that nobody should be worse off _even if this somehow broke something_, which i think it doesn't. (Note: I'm trying to thread these, but ... gmail, so i dunno what how this will go.) -- Urja Rannikko

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom