Firmware upgrade using Linux tool, requires no hardware

[Falkentyne]

The only way to get the monitor to work again is to either send it to Benq and hope they service it, or to buy the Mstar ISP device.
There is _no_ other way. Keep in mind that nothing ever has a 100% success rate in the realm of computers so please don't sue me if it doesn't work. Things can and do go wrong and I'm sorry about that. I hope you can fix it with it if you choose to buy it.

Right now I'm disabled, dealing with a swollen back, possibly life threatening physical issues as well as being in danger of becoming homeless, so forgive me if I'm not exactly acting too concerned about this problem. I've given you all the help I can give. I know you're angry, but keep this in mind--at least you have a place to live.


It's not surprising that 0x37 disappears if the monitor firmware is not functional. That's the DDC/CI communication port.

The I2C address is still accessible but you have to flash the monitor with a hardware tool. As I said, this failure has happened before, way back in the thread, and no one knows -exactly- why. Most were fixable by changing to a different computer. In your case that didn't work.

if you decide to get the Mstar device, get the V4 firmware while you're at it, from the other thread. Don't even bother with V2 since V4 is available, if you're going to already go through that trouble. You don't need to resize anything with the mstar device. you just install the windows driver for it, hook up the monitor and follow the instructions in the "DYI V2" upgrade section, and flash (you will be upgrading to V4, however).

[roman]

It's okay. I am also not particulary angry about this more like annoyed and desperate in fixing it lol. Well seems like i have no other choice left than get an mstar tool. I also knew the risk from the start and knew something could go wrong and took the gamble knowing that.
Well anyhow, still thanks for trying to fix it. Its not the end of the world that this monitor does not run for the moment, but yeah i will eventually get it running again in a month or so.

About your personal issues im sorry to hear that. I cant imagine what incident you had but i had to live homeless for about 1,5 years in the past and hope you can be spared of that experience :/

I wish you the best of luck and well beeing and hope things will turn to the best one day again. Dont give up!

[Falkentyne]

Just hope you can get the monitor fixed.
As long as the firmware chip is not damaged, it can be reflashed.
I intentionally bricked a VG248QE by flashing an XL2420Z firmware into it with the mstar ISP device (the VG248QE has a compatible flash chip (winbond), and recovered it successfully after flashing the backup firmware (the mstar can create backups). Restoring the correct EDID was harder as the VG248 doesn't store the EDID in the firmware like the Benqs do). So if the Mstar can recover a completely bricked monitor that has a completely manufacturer's firmware on it, it should restore yours too.

[janne907]

Roman, i have exactly same problem. I just got this same error and my screen stays black. Im gonna try with another computer now. Hope to get this fixed.

Code: Select all

ubuntu@ubuntu:~/flashrom/flashrom$ sudo ./flashrom -p nmstarddc_spi:dev=/dev/i2c-1:49 -c "MX25L1605A/MX25L1606E" -w firmware.bin
flashrom v0.9.7-r1846 on Linux 3.19.0-25-generic (i686)
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-1 and address 0x49.
Info: WILL reset the device at the end.
Found Macronix flash chip "MX25L1605A/MX25L1606E" (2048 kB, SPI) on mstarddc_spi.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... FAILED at 0x00000000! Expected=0x02, Found=0xb0, failed byte count from 0x00000000-0x001fffff: 0xfe
Your flash chip is in an unknown state.
Please report this on IRC at chat.freenode.net (channel #flashrom) or
mail [email protected], thanks!

EDIT
I repeated this last command straight after that previous error message and now my screen is working again!

Code: Select all

ubuntu@ubuntu:~/flashrom/flashrom$ sudo ./flashrom -p mstarddc_spi:dev=/dev/i2c-1:49 -c "MX25L1605A/MX25L1606E" -w firmware.bin
flashrom v0.9.7-r1846 on Linux 3.19.0-25-generic (i686)
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-1 and address 0x49.
Info: WILL reset the device at the end.
Found Macronix flash chip "MX25L1605A/MX25L1606E" (2048 kB, SPI) on mstarddc_spi.
Reading old flash chip contents... ^Adone.
Erasing and writing flash chip... Erase/write done.
Verifying flash... VERIFIED.

[Falkentyne]

That explains why his flash failed.
Your flash failed the first time because of a *TYPO*.
Notice this?

nmstarddc_spi:

Now compare what you did the next time.
mstarddc_spi:dev=/dev/i2c-1:49

If he got the same error as you, then it means he made a typo originally.

[janne907]

That explains why his flash failed.
Your flash failed the first time because of a *TYPO*.
Notice this?

nmstarddc_spi:

Now compare what you did the next time.
mstarddc_spi:dev=/dev/i2c-1:49

If he got the same error as you, then it means he made a typo originally.

You are right, i didn't notice that before. Hope Roman can get his screen repaired too.

[radekpw]

I got my MStar today. I ran into more problems. I get the following prompt when I start the software tool. " Cannot install driver to your system. Your Printer port will not work" Then the tool starts after I hit ok. When I further try to follow the guide I get the message. "Program File Not Ready!!" I tried both with the VGA and DVI cables, same exact results.

[radekpw]

It seems even though I'm connecting to the pc through the USB cable it auto sets to the printer port. I tried changing it to the usb in the settings but it's not working still. Instead of USB xKHz it says Printer 40KHz.

[Falkentyne]

Hi,
That error is normal
You get the error when you haven't loaded a program file (the firmware file you are going to flash) into the Mstar unit
It goes "Program file not ready!"

it should say "firmware file not ready".

If you get the "print port will not work" it's because the drivers aren't installed correctly.
Did you install these drivers yet?

http://www.blurbusters.com/files/MSTAR_ ... v45082.zip
Extract it with directory structure.
Run the CDM*** setup file first which should be in a subfolder.

Then navigate to the i386 folder afterwards and run the isp tool exe from there.

[Garfelf]

Had to create an account here in the hopes of updating my firmware too ^_^

Could you tell me what I'm doing wrong? I've done what you (Falkentyne) explained in your walkthrough, however when I scan for the i2c ID and do the dump, I find nothing on the i2cdetect 0-5 interval, the only ones I get data from is 6 & 7 which are DPDDC-A and DPDDC-B.

I have tried installing the BenQ Display Pilot and rebooting the computer, but no result. What can I do differently to catch the bus where the screen is located?

I am currently running the v2 firmware on the screen, but as I read, there is supposedly a v4 firmware now, that should fix the DP issues I am having...