That is most likely the firmware location. But if you have a programmer, just dump the content and inspect it or uploaded here. If your programmer can't read the chip, then I would think twice before trying to write something on it.

By the way, you should most likely go for 0.951 or 0.954. Firmware 3.02 and 3.70 seem to be built for PCIe SSD. Just check this page and scroll a bit. You will find this image.

Zitat von lordkag im Beitrag #76

---

That is most likely the firmware location. But if you have a programmer, just dump the content and inspect it or uploaded here. If your programmer can't read the chip, then I would think twice before trying to write something on it.

By the way, you should most likely go for 0.951 or 0.954. Firmware 3.02 and 3.70 seem to be built for PCIe SSD. Just check this page and scroll a bit. You will find this image.

---

The one you circled has the higher chance. But try to read it first and upload the dump. We will see from there.

Zitat von lordkag im Beitrag #78

---

The one you circled has the higher chance. But try to read it first and upload the dump. We will see from there.

---

I don't understand your above post. Could you make it clearer, using a definition for each file?

- 106N0951.bin seems to be the same file as found in asmedia_asm106x_0.951.7z from Station-Drivers. This is the OROM for ASM1061, even though it is labelled as firmware. Was this taken from Station-Drivers or by some other way?
- dump.bin is the same as ahci0951.rom from SD, plus padding. I guess this was taken with the programmer. You have found your chip. Is this the image currently on the card?

Zitat von lordkag im Beitrag #80

---

I don't understand your above post. Could you make it clearer, using a definition for each file?

- 106N0951.bin seems to be the same file as found in asmedia_asm106x_0.951.7z from Station-Drivers. This is the OROM for ASM1061, even though it is labelled as firmware. Was this taken from Station-Drivers or by some other way?
- dump.bin is the same as ahci0951.rom from SD, plus padding. I guess this was taken with the programmer. You have found your chip. Is this the image currently on the card?

---

Do you remember what error you had? A screen would have been nice, but some words could help determine the problem. My guess now is that 3.xx firmware should only be flashed on newer SSD with ASM1061 controller.

Do you remember what firmware you had on the card, before it was broken? Your dump.bin is a valid 0.951 firmware, so either your step 3) worked or your chip has not been flashed at step 2)

It is weird that your card failed with the right firmware. Maybe it needed a full shutdown, maybe even removed from your board for a few minutes, inserted in another slot, inserted in another board, just to reset it.

DON'T flash 106N0951.BIN or any other *.bin on your card. These are only meant for BIOS insertion. For external card always flash idexxx.rom or ahcixxx.rom. Since you have a programmer, you can flash dump.bin back, since it is just ahci0951.rom with padding to fill 0x10000 or 64KB - the size of the chip.

Again, this is my suggestion: flash dump.bin back on the chip. Remove the card from that slot and place it on another slot, place it on another mainboard. If you think the chip can hold other solder/desolder cycles, then try to flash ahci95A1.rom from 0.95 firmware. Just add FF bytes until the file is 0x10000, save it, flash it. If you want, I can also make a 0.954 firmware, but only as a last step, when all the above have failed and you have nothing else to lose. You should always use *.rom files because they have an extra header.

Zitat von tg im Beitrag #25

---

I have a standalone 2 port SATA card using ASmedia Chipset 1061.

tried flashing the firmware provided on this site and then the 3.0.2 from station drivers.
ASMedia-106x_AHCI-ROM_v0.954.7z

Seems to fail erasing SPI rom.
Entire SPI ROM neeed to be re-programmed!!!

Any idea's?

---

Zitat

---

Seems to fail erasing SPI rom.
Entire SPI ROM neeed to be re-programmed!!!

---

the same error when I tried firmware 370 , the same error when I tried to reflash 0951.rom

do not need to add FF to the file ahci0951.rom them adds programmer, right? if not can you padding for me please and attach here ?

why you write ahci95A1.rom ? on station driver i have found ahci0951.rom. are the same file ?

for 0954.rom I read in previous reply that have a bug? it true ?



thanks

The error points to a problem in handling SPI chip, not the firmware itself. Have you ever flashed the firmware on this card before the brick, if yes, by what method? Also can you give me the ID of the chip, the one that you desoldered? I want to see if it is supported by 106spi.exe flasher.

I have attached all the firmwares for programmer use. This is what I advise you to do:

- flash ahci0951dump.rom, try to move the card to another slot or another PC. Check for card detection, either during boot or in Windows.
- flash ahci095dump.rom, try to move the card to another slot or another PC. Check for card detection, either during boot or in Windows. If you fear the chip might not resist all the tests, you can skip this one.
- flash ide0951dump.rom, try to move the card to another slot or another PC. Check for card detection, either during boot or in Windows. Your card will be in IDE mode, but if it works, at least you can flash ahci0951.rom from DOS.
- if you think your card is already lost, you can try ahci0954dump-modded.rom, which is a modded 0.954 OROM with header from 0.951 firmware. These two are very similar, even in PnP sections, so they might work with the same boot configuration. Flash at your own risk.

i brick card at first flash with SPI

tomorrow I flash with programmer with ahci0951dump.rom and let you know the chip ID

thanks so much

see you

unfortunately the card is not detected despite having flashed the chip with the programmer with the file ahci0951dump.rom dropping me

the chip is called PM25LD512

:(


i give up


i try to send to the seller for Replacement

thanks for all

The chip is supported by 106spi.exe, so I don't know why you had that error. Either the chip itself is faulty or the 3.70 firmware messed with the registers of ASM1061 controller. Sadly, I can't seem to find a datasheet for it, to see if there is a hardware reset somewhere.

Have you also tried ide0951dump.rom or ahci095dump.rom? Maybe even ahci0954dump-modded.rom?

But if you can get a replacement, go for it. And stay away from any 3.xx firmware.

Zitat von lordkag im Beitrag #87

---

The chip is supported by 106spi.exe, so I don't know why you had that error. Either the chip itself is faulty or the 3.70 firmware messed with the registers of ASM1061 controller. Sadly, I can't seem to find a datasheet for it, to see if there is a hardware reset somewhere.

Have you also tried ide0951dump.rom or ahci095dump.rom? Maybe even ahci0954dump-modded.rom?

But if you can get a replacement, go for it. And stay away from any 3.xx firmware.

---

the shipping costs are too high for the RMA :(

any suggestions to revive it?

You now have the original firmware, so the problem is in the controller itself or the chip is faulty. A reset would be needed. Have you done what I suggested, to move the card to another PC and test it there?

Since the card is already lost, you can try the hard way:

- flash ide0951dump.rom, try to move the card to another slot or another PC. Check for card detection, either during boot or in Windows. Your card will be in IDE mode, but if it works, at least you can flash ahci0951.rom from DOS.
- flash ahci370dump.rom, try to move the card to another slot or another PC. Check for card detection, either during boot or in Windows. This might force the controller to work with the new firmware. If failed, you can then flash back to ahci0951dump.rom to see if it was revived.
- replace the flashing chip, get a backup from this list: Atmel AT25F512B, EON EN25F05, MXIC MX25L512C,MX25L5121E, Pflash Pm25LD512C, Pm25V512A, Numonyx M25P05A, SST SST25V512A, AMIC A25L5120.

Other than that, I can only think of shorting some pins in the controller, but without a datasheet, the damage could be permanent.