Firmware upgrade using Linux tool, requires no hardware

Adjusting BENQ Blur Reduction and DyAc (Dynamic Acceleration) including Blur Busters Strobe Utility. Supports most BenQ/Zowie Z-Series monitors (XL2411, XL2420, XL2720, XL2735, XL2540, XL2546)
Post Reply
User avatar
Chief Blur Buster
Site Admin
Posts: 11653
Joined: 05 Dec 2013, 15:44
Location: Toronto / Hamilton, Ontario, Canada
Contact:
Contact Chief Blur Buster

Re: Firmware upgrade using Linux tool, requires no hardware

Post by Chief Blur Buster » 16 May 2014, 19:40

s3bish wrote:When i use the "Vertical Total 1350" Tweak combined with Blur Reduction, i get a blackscreen. So i have to stick with the default resolution :( Would this fix be a big enhancement?
Launch Blur Busters Strobe Utility, and then adjust Crosstalk to 0, BEFORE applying the VT1350 tweak.

Sometimes the Crosstalk setting is at a setting beyond Blur Busters Strobe Utility's adjustment range -- which causes a blackout during the VT1350 tweak.
Head of Blur Busters - BlurBusters.com | TestUFO.com | Follow @BlurBusters on Twitter

Image
Forum Rules wrote:  1. Rule #1: Be Nice. This is published forum rule #1. Even To Newbies & People You Disagree With!
  2. Please report rule violations If you see a post that violates forum rules, then report the post.
  3. ALWAYS respect indie testers here. See how indies are bootstrapping Blur Busters research!
Top
s3bish
Posts: 2
Joined: 16 May 2014, 14:44

Re: Firmware upgrade using Linux tool, requires no hardware

Post by s3bish » 17 May 2014, 04:58

  • Model: BenQ XL2411Z @Fimrware 2.0x
    Video Card: Nvidia GTX 770
    Resolution tried: 1920x1080@120Hz
@mdzapeer & Chief Blur Buster:

Setting Crosstalk to Zero simply did the job. Thank you very much, i am going to test my new Benq XL2411Z and GTX 770 3x OC now :mrgreen: :D !
Top
rid
Posts: 1
Joined: 17 May 2014, 14:17

Re: Firmware upgrade using Linux tool, requires no hardware

Post by rid » 17 May 2014, 14:26

Thanks everyone! I successfully updated my XL2411Z to V2 using my laptop.
Ubuntu was acting up with the nouveau driver - whenever i connected the VGA cable to my laptop it would reboot, so i went with the proprietary nvidia driver, all went well. Took about double the time than said in the article, but hey it did work all at the 1st try!

So yeah, blur reduction now ROCKS the place!
Top
Xeifer64
Posts: 3
Joined: 17 May 2014, 23:14

Re: Firmware upgrade using Linux tool, requires no hardware

Post by Xeifer64 » 18 May 2014, 00:29

Hi all! I recently got a XL2411z which came with V1 :x and like many in this thread i'm a Linux newbie so i've been running into many problems trying to upgrade to V2. I'm using a laptop with a Radeon intergrated GPU, connecting to the monitor via VGA. This is the problem i've run into now:

Code: Select all

ubuntu@ubuntu:~/flashrom$ sudo ./flashrom -p mstarddc_spi:dev=/dev/i2c-7:49
flashrom v0.9.7-r1795 on Linux 3.13.0-24-generic (x86_64)
flashrom is free software, get the source code at http://www.flashrom.org

Calibrating delay loop... OK.
Info: Will try to use device /dev/i2c-7 and address 0x49.
Info: WILL reset the device at the end.
Found ST flash chip "unknown ST SPI chip" (0 kB, SPI) on mstarddc_spi.
===
This flash part has status NOT WORKING 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 [email protected] if any of the above operations
work correctly for you with this flash part. Please include the flashrom
output with the additional -V option for all operations you tested (-V, -Vr,
-VE, -Vw), and mention which mainboard or programmer you tested.
Please mention your board in the subject line. Thanks for your help!
No operations were specified.
When trying to identify the flash chip it's finding an 'unknown ST SPI chip' but going onto the step I get this:

Code: Select all

ubuntu@ubuntu:~/flashrom$ sudo ./flashrom -p mstarddc_spi:dev=/dev/i2c-7:49 -c "MX25L1605A/MX25L1606E" -r backup.bin
flashrom v0.9.7-r1795 on Linux 3.13.0-24-generic (x86_64)
flashrom is free software, get the source code at http://www.flashrom.org

Calibrating delay loop... OK.
Info: Will try to use device /dev/i2c-7 and address 0x49.
Info: WILL reset the device at the end.
No EEPROM/flash device found.
Note: flashrom can never write if the flash chip isn't found automatically.
Which gives me the error 'No EEPROM/flash device found'. I've tried to find posts of others who might of had this problem here and came up with nothing of use.
Here is all the i2c buses it finds, with the monitor being found at 7:

Code: Select all

ubuntu@ubuntu:~/flashrom$ sudo i2cdetect -l
i2c-0	i2c       	Radeon i2c bit bus 0x90         	I2C adapter
i2c-1	i2c        	Radeon i2c bit bus 0x91         	I2C adapter
i2c-2	i2c        	Radeon i2c bit bus 0x92         	I2C adapter
i2c-3	i2c       	Radeon i2c bit bus 0x93         	I2C adapter
i2c-4	i2c       	Radeon i2c bit bus 0x94         	I2C adapter
i2c-5	i2c       	Radeon i2c bit bus 0x95         	I2C adapter
i2c-6	i2c       	Radeon aux bus eDP-auxch        	I2C adapter
i2c-7	i2c       	Radeon aux bus DP-auxch         	I2C adapter
Any help at all would be appreciated, this is getting frustrating, thanks! :D
Top
pipomolo42
Posts: 30
Joined: 24 Apr 2014, 06:08

Re: Firmware upgrade using Linux tool, requires no hardware

Post by pipomolo42 » 18 May 2014, 06:35

Xeifer64 wrote:When trying to identify the flash chip it's finding an 'unknown ST SPI chip' but going onto the step I get this:

Code: Select all

ubuntu@ubuntu:~/flashrom$ sudo ./flashrom -p mstarddc_spi:dev=/dev/i2c-7:49 -c "MX25L1605A/MX25L1606E" -r backup.bin
Which gives me the error 'No EEPROM/flash device found'.
Well, if the chip was identified as a "unknown ST SPI chip", you can't expect it to work with -c "MX25L1605A/MX25L1606E", which are Macronix chips.

Maybe flashrom doesn't support your flash chip yet. Could you re-run the identify command in full verbose mode, and paste part of the output here ? (sudo ./flashrom -p mstarddc_spi:dev=/dev/i2c-7:49 -VVV)

It should at least contain some 3 or 4 byte hexadecimal string, containing your chip's answer to the identification commands, which might help us finding which chip you have.
Top
Xeifer64
Posts: 3
Joined: 17 May 2014, 23:14

Re: Firmware upgrade using Linux tool, requires no hardware

Post by Xeifer64 » 18 May 2014, 07:52

Hi, thanks for the response. Running the command in full verbose mode gives this:

Code: Select all

RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Eon EN25S10, 128 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffe0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Eon EN25S20, 256 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffc0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Eon EN25S40, 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Eon EN25S80, 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Eon EN25S16, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Eon EN25S32, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Eon EN25S64, 8192 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff800000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for GigaDevice GD25LQ32, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for GigaDevice GD25Q512, 64 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffff0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for GigaDevice GD25Q10, 128 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffe0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for GigaDevice GD25Q20(B), 256 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffc0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for GigaDevice GD25Q40(B), 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for GigaDevice GD25Q80(B), 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for GigaDevice GD25Q16(B), 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for GigaDevice GD25Q32(B), 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for GigaDevice GD25Q64(B), 8192 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff800000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for GigaDevice GD25Q128B, 16384 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff000000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for GigaDevice GD25T80, 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Intel 25F160S33B8, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Intel 25F160S33T8, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Intel 25F320S33B8, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Intel 25F320S33T8, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Intel 25F640S33B8, 8192 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff800000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Intel 25F640S33T8, 8192 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff800000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX23L3254, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25L512(E)/MX25V512(C), 64 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffff0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25L1005(C)/MX25L1006E, 128 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffe0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25L2005(C), 256 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffc0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25L4005(A/C), 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25L8005/MX25V8005, 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25L1605, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25L1605A/MX25L1606E, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25L1605D/MX25L1608D/MX25L1673E, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25L1635D, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25L1635E, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25L3205(A), 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25L3205D/MX25L3208D, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25L3206E, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25L3273E, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25L3235D, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25L6405(D), 8192 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff800000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25L6406E/MX25L6436E, 8192 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff800000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25L6445E/MX25L6473E, 8192 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff800000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25L12805(D), 16384 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff000000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25U1635E, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25U3235E/F, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix MX25U6435E/F, 8192 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff800000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M25P05-A, 64 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffff0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M25P05, 64 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffff0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. Ignoring RES in favour of RDID.
Probing for Micron/Numonyx/ST M25P10-A, 128 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffe0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M25P10, 128 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffe0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. Ignoring RES in favour of RDID.
Probing for Micron/Numonyx/ST M25P20, 256 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffc0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M25P20-old, 256 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffc0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. Ignoring RES in favour of RDID.
Probing for Micron/Numonyx/ST M25P40, 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M25P40-old, 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. Ignoring RES in favour of RDID.
Probing for Micron/Numonyx/ST M25P80, 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M25P16, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M25P32, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M25P64, 8192 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff800000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M25P128, 16384 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff000000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M25PE10, 128 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffe0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M25PE20, 256 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffc0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M25PE40, 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M25PE80, 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M25PE16, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M25PX80, 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M25PX16, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M25PX32, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M25PX64, 8192 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff800000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M45PE10, 128 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffe0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M45PE20, 256 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffc0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M45PE40, 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M45PE80, 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST M45PE16, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST N25Q016, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST N25Q032..1E, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST N25Q032..3E, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST N25Q064..1E, 8192 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff800000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST N25Q064..3E, 8192 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff800000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST N25Q128..1E, 16384 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff000000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Micron/Numonyx/ST N25Q128..3E, 16384 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff000000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Nantronics N25S10, 128 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffe0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Nantronics N25S20, 256 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffc0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Nantronics N25S40, 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Nantronics N25S80, 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Nantronics N25S16, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for PMC Pm25LD256C, 32 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffff8000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for PMC Pm25LD512(C), 64 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffff0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for PMC Pm25LD010(C), 128 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffe0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for PMC Pm25LD020(C), 256 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffc0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for PMC Pm25LD040(C), 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for PMC Pm25LV512(A), 64 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffff0000 to 0x0000000000000000
RES returned 0x14 0x14 0x14. probe_spi_res3: id1 0x1414, id2 0x14
Probing for PMC Pm25LV010, 128 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffe0000 to 0x0000000000000000
RES returned 0x14 0x14 0x14. probe_spi_res3: id1 0x1414, id2 0x14
Probing for PMC Pm25LV010A, 128 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffe0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for PMC Pm25LV020, 256 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffc0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for PMC Pm25LV040, 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for PMC Pm25LV080B, 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for PMC Pm25LV016B, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Sanyo LE25FU406B, 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RES returned 0x14 0x14. probe_spi_res2: id1 0x14, id2 0x14
Probing for Sanyo LE25FW203A, 256 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffc0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Sanyo LE25FW403A, 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Sanyo LE25FW418A, 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RES returned 0x14 0x14. probe_spi_res2: id1 0x14, id2 0x14
Probing for Sanyo LE25FW806, 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RES returned 0x14 0x14. probe_spi_res2: id1 0x14, id2 0x14
Probing for Sanyo LE25FW808, 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RES returned 0x14 0x14. probe_spi_res2: id1 0x14, id2 0x14
Probing for Spansion S25FL004A, 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Spansion S25FL008A, 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Spansion S25FL016A, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Spansion S25FL032A/P, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Spansion S25FL064A/P, 8192 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff800000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Spansion S25FL204K, 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Spansion S25FL208K, 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Spansion S25FL116K/S25FL216K, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Spansion S25FL132K, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Spansion S25FL164K, 8192 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff800000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Spansion S25FL128S......0, 16384 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff000000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for SST SST25LF020A, 256 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffc0000 to 0x0000000000000000
REMS returned 0x14 0xc2. probe_spi_rems: id1 0x14, id2 0xc2
Probing for SST SST25LF040A, 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RES returned 0x14 0x14. probe_spi_res2: id1 0x14, id2 0x14
Probing for SST SST25LF080(A), 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RES returned 0x14 0x14. probe_spi_res2: id1 0x14, id2 0x14
Probing for SST SST25VF512A, 64 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffff0000 to 0x0000000000000000
REMS returned 0x14 0xc2. probe_spi_rems: id1 0x14, id2 0xc2
Probing for SST SST25VF010, 128 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffe0000 to 0x0000000000000000
REMS returned 0x14 0xc2. probe_spi_rems: id1 0x14, id2 0xc2
Probing for SST SST25VF020, 256 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffc0000 to 0x0000000000000000
REMS returned 0x14 0xc2. probe_spi_rems: id1 0x14, id2 0xc2
Probing for SST SST25VF020B, 256 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffc0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for SST SST25VF040, 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
REMS returned 0x14 0xc2. probe_spi_rems: id1 0x14, id2 0xc2
Probing for SST SST25VF040B, 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for SST SST25VF040B.REMS, 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
REMS returned 0x14 0xc2. probe_spi_rems: id1 0x14, id2 0xc2
Probing for SST SST25VF080B, 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for SST SST25VF016B, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for SST SST25VF032B, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for SST SST25VF064C, 8192 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff800000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for SST SST25WF512, 64 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffff0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for SST SST25WF010, 128 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffe0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for SST SST25WF020, 256 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffc0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for SST SST25WF040, 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for SST SST25WF080, 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Winbond W25Q80.V, 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Winbond W25Q16.V, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Winbond W25Q32.V, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Winbond W25Q64.V, 8192 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff800000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Winbond W25Q128.V, 16384 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff000000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Winbond W25Q20.W, 256 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffc0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Winbond W25Q40.W, 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Winbond W25Q80.W, 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Winbond W25Q16.W, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Winbond W25Q32.W, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Winbond W25Q64.W, 8192 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff800000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Winbond W25X10, 128 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffe0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Winbond W25X20, 256 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fffc0000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Winbond W25X40, 512 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff80000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Winbond W25X80, 1024 kB: programmer_map_flash_region: mapping flash chip from 0x00000000fff00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Winbond W25X16, 2048 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffe00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Winbond W25X32, 4096 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ffc00000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Winbond W25X64, 8192 kB: programmer_map_flash_region: mapping flash chip from 0x00000000ff800000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Unknown SFDP-capable chip, 0 kB: programmer_map_flash_region: mapping flash chip from 0x0000000000000000 to 0x0000000000000000
spi_sfdp_read_sfdp_chunk: addr=0x0, len=2, data:
 0x46 0x44
spi_sfdp_read_sfdp_chunk: addr=0x2, len=2, data:
 0x50 0x00
Signature = 0x00504446 (should be 0x50444653)
No SFDP signature found.
Probing for AMIC unknown AMIC SPI chip, 0 kB: programmer_map_flash_region: mapping flash chip from 0x0000000000000000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2 0x20. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Atmel unknown Atmel SPI chip, 0 kB: programmer_map_flash_region: mapping flash chip from 0x0000000000000000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Eon unknown Eon SPI chip, 0 kB: programmer_map_flash_region: mapping flash chip from 0x0000000000000000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Macronix unknown Macronix SPI chip, 0 kB: programmer_map_flash_region: mapping flash chip from 0x0000000000000000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for PMC unknown PMC SPI chip, 0 kB: programmer_map_flash_region: mapping flash chip from 0x0000000000000000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for SST unknown SST SPI chip, 0 kB: programmer_map_flash_region: mapping flash chip from 0x0000000000000000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for ST unknown ST SPI chip, 0 kB: programmer_map_flash_region: mapping flash chip from 0x0000000000000000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Found ST flash chip "unknown ST SPI chip" (0 kB, SPI) on mstarddc_spi.
Probing for Sanyo unknown Sanyo SPI chip, 0 kB: programmer_map_flash_region: mapping flash chip from 0x0000000000000000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Winbond unknown Winbond (ex Nexcom) SPI chip, 0 kB: programmer_map_flash_region: mapping flash chip from 0x0000000000000000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Generic unknown SPI chip (RDID), 0 kB: programmer_map_flash_region: mapping flash chip from 0x0000000000000000 to 0x0000000000000000
RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Probing for Generic unknown SPI chip (REMS), 0 kB: programmer_map_flash_region: mapping flash chip from 0x0000000000000000 to 0x0000000000000000
REMS returned 0x14 0xc2. probe_spi_rems: id1 0x14, id2 0xc2
Found ST flash chip "unknown ST SPI chip" (0 kB, SPI).
===
This flash part has status NOT WORKING 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 [email protected] if any of the above operations
work correctly for you with this flash part. Please include the flashrom
output with the additional -V option for all operations you tested (-V, -Vr,
-VE, -Vw), and mention which mainboard or programmer you tested.
Please mention your board in the subject line. Thanks for your help!
No operations were specified.
Am I right in thinking this a problem solely down to the Radeon chip? If so, I could probably fish out an older laptop and restart the process on a Nvidia card.

Again, thanks for the help :D
Top
pipomolo42
Posts: 30
Joined: 24 Apr 2014, 06:08

Re: Firmware upgrade using Linux tool, requires no hardware

Post by pipomolo42 » 19 May 2014, 11:37

Xeifer64 wrote:

Code: Select all

RDID returned 0x20 0x15 0xc2. probe_spi_rdid_generic: id1 0x20, id2 0x15c2
Ah, you actually encountered a "known" bug : in some cases, the returned bytes are rotated, and flashrom cannot interpret them correctly. (it should have been "0xc2 0x20 0x15" instead of "0x20 0x15 0xc2")

I've had the case with an old Benq FP93GX display, but it's the first time I've heard of it on a recent screen…

Maybe you could try with a different laptop/desktop, to see if you get different results?

I'm really sorry, but since I've got no datasheet from Mstar, I don't really understand why and when this happens, and how to fix it.
Top
dsad_NA
Posts: 1
Joined: 23 May 2014, 13:43

Re: Firmware upgrade using Linux tool, requires no hardware

Post by dsad_NA » 23 May 2014, 13:49

Xeifer64

Same problem was here with integrated VGA in A8-6600K. There were rotated bytes pipomolo42 indicated. I borrowed my friend's laptop with Intel HD4000 graphics and things have become fine.

Thanks pipomolo42 for your genius work.
Top
Xeifer64
Posts: 3
Joined: 17 May 2014, 23:14

Re: Firmware upgrade using Linux tool, requires no hardware

Post by Xeifer64 » 26 May 2014, 14:57

Hi, after getting a DVI to VGA adapter I restarted the process again on my desktop with a Geforce 760 and success!

It was well worth the effort to upgrade. Thanks to pipomolo42 for the help and work, and thanks to Chief for the awesome utility. :)
Top
lolmachine4
Posts: 4
Joined: 27 May 2014, 05:41

Re: Firmware upgrade using Linux tool, requires no hardware

Post by lolmachine4 » 27 May 2014, 07:00

So, my 5 year old Samsung just died yesterday. I wanted to buy a 2411Z for months now but coudn't be arsed due the firmware bug. When I figured out I couldn't save the old Syncmaster I bought it straight away from Amazon (Germany) w/ express shipping - arrived this morning.

After struggeling with entering the damn Service Menu (the key sequence seems to be rather tricky) I finally found out I got mine shipped with V1 installed. It seems the menu doe not show up if it's not connected to an input source, or atleast it seemd to work way better with the VGA-cable plugged in.

I used the Ubuntu live ISO which I "burned" onto an USB-Drive with Rufus (http://rufus.akeo.ie) and booted Ubuntu on an old laptop that was laying around at work (the perks of working in IT - you can flash monitors during worktimes and nobody gives a sh*t :D). The laptop was running an Intel-Chipset.

I used this information after the system was up and running, BUT there is a fault in the command.
The right line is >/etc/apt/sources.list<. Mind the s at the end of the word sources. If you fail to notice this error the rest of the commands will not work, so be aware.
pipomolo42 wrote:Here's what you'll need to build the tool, using the Ubuntu 14.04 LTS iso (which also behaves as a live CD):
  • boot in "Try ubuntu" mode (the default), open a terminal (Ctrl + Alt + T);
  • type "sudo gedit /etc/apt/source.list";
  • an editor opens, add "universe multiverse" at the end of the second line, to it reads "deb http://archive.ubuntu.com/ubuntu/ trusty main restricted universe multiverse" Save, then exit the editor;
  • type "sudo apt-get update", to update the package list;
  • type "sudo apt-get install i2c-tools subversion libpci-dev" to install required packages.
You can then follow the procedure, building flashrom with the patch, and detecting your I2C buses.
After that, I simply used the patcher linked in the first post of this thread, I even had the same setup in i2c-channels, I didn't even have to change one line in the commands posted.

Great tutorial, awesome find, and I'm happy to test this new baby once I'm at home.
Also, have some pictures! :)

The setup, used a normal VGA-VGA-cable.
Image

Success!
Image
Top
Post Reply

Return to “BENQ Zowie Tweaking — Strobe Utility / Blur Reduction / DyAc”