Problem with flashing MX25L12873F

[onelook]

Hi guys,

I am having problem with flashing (writing) BIOS Chip MX25L12873F on HP 830 G6.

With the flashrom software in Linux i got the error:
Erasing and writing flash chip... FAILED at 0x00011000! Expected=0xff, Found=0x00, failed byte count from 0x00011000-0x00011fff: 0x18
ERASE FAILED!
Looking for another erase function.
FAILED at 0x00018000! Expected=0xff, Found=0x00, failed byte count from 0x00018000-0x0001ffff: 0x12

Then i used Asprogrammer in Windows it showed me:
Possible protection is enabled. Press "Unprotect" and check datasheet
I have pressed "Unprotect" but no success

The Reading was good without any problem. Both in Linux and Windows. All the read files have same SHA256 Checksum.

I think there's something block writing on the Chip.

Maybe you can help.

Thank you

[SMDFlea]

Re: Problem with flashing MX25L12873F

Is the chip desoldered,or are you using a clip

[onelook]

Re: Problem with flashing MX25L12873F

Is the chip desoldered,or are you using a clip

Hi,
The chip is desoldered.
I am using CH341a Black. I mean i haven't had any Problem with Winbond Chips.

[SMDFlea]

Re: Problem with flashing MX25L12873F

Hi,
The chip is desoldered.
I am using CH341a Black. I mean i haven't had any Problem with Winbond Chips.

Try NeoProgrammer software from this post. https://www.badcaps.net/forum/showpo...50&postcount=5
There`s also a link to a 3.3V mod for the black pcb version,it can make it more stable.

[Maxpower3]

Re: Problem with flashing MX25L12873F

I don"t use this programmer, but there is no problem with 5v instead of 3.3v on these models ??
take the VCC voltage on the chip.
https://www.chucknemeth.com/usb-devi.../3v-ch341a-mod
https://www.eevblog.com/forum/repair...75/#msg1323775

Try NeoProgrammer software from this post. https://www.badcaps.net/forum/showpo...50&postcount=5
There`s also a link to a 3.3V mod for the black pcb version,it can make it more stable.

at same time

[onelook]

Re: Problem with flashing MX25L12873F

Try NeoProgrammer software from this post. https://www.badcaps.net/forum/showpo...50&postcount=5
There`s also a link to a 3.3V mod for the black pcb version,it can make it more stable.

I have tried. Sadly no Success
Current programmer: CH341a
12:07:56
Erasing memory...
WARNING, probable erasure failure, check protection bits in status registers.
Execution time: 00:00:00.061
Old protection Register: 01000000(0x40),
New protection Register: 01000000(0x40),

I have read the Datasheet. There is 4K-bit secured OTP (see attached Picture)

I will try later with the Volt measurement

Thanks very much for your answers sofar

[ahmedmph]

Re: Problem with flashing MX25L12873F

mx25l12873f

[ahmedmph]

Re: Problem with flashing MX25L12873F

I have tried. Sadly no Success
Current programmer: CH341a
12:07:56
Erasing memory...
WARNING, probable erasure failure, check protection bits in status registers.
Execution time: 00:00:00.061
Old protection Register: 01000000(0x40),
New protection Register: 01000000(0x40),

I have read the Datasheet. There is 4K-bit secured OTP (see attached Picture)

I will try later with the Volt measurement

Thanks very much for your answers sofar

How did you solve this problem, any suggestions?

[rgomer]

Re: Problem with flashing MX25L12873F

Hi just found this forum searching for this chip and this thread point me in the right direction (I guess). The recommended tool up above (NeoProgrammer) almost worked, but still I wasn't able to write on the chip.

Using NeoProgrammer V2.2.0.10 I managed to write a new BIOS in this chip. Unfortunately seems like this didn't solve my problem (Gigabyte motherboard bricked because I enabled secure boot without an APU, only having a NVidia GPU).

Hope you guys have more luck.

[BHR]

Re: Problem with flashing MX25L12873F

I just had the same problem on ASRock X370, bios would write but verification failed. I'm using Asprogrammer and CH341 with a clip. I download Neo but before I even ran it, chip would verify. What I did was erase the chip, read it (confirm all FFs), then write it again and verify. Not sure what the issue was, perhaps poor connection on the clip?