Both of you have the same SPI chip as Hanson. You need the patched flasher for the chip to be detected. The reading has been tested by Hanson and it works. It would have been better if any of you would have uploaded a <any_name>.bin obtained by using "go -r". If it says "read out SPI..." then it works and you should have a *.bin file on the root of USB. This way we would have verified that reading works from 3 different sources (even though it is the same chip).

What both of you can do is ask nicely for Hanson to test the writing by using the package he uploaded with "go" or "go -y". If the card still works after the updating, then it is only about flashing once and proper (and not every image that we can think of). If it doesn't work, then it is the flasher that does something behind the scene. I have compared the entered bytes with the ones from the datasheet and they are a perfect match. There really isn't anything else I can do. Marvell has left you with a broken image and not a single way of updating, except the programmer.

@THZ

If you choose to ignore my advice and test on your own the writing of the patched flasher, then boot with the package uploaded by Hanson and type "go". Once it is completed, shutdown the PC for a short period. Boot and check the card. He has flashed this image with a programmer and it works fine.

If any of you have access to a programmer, then take IMAG_RB.bin from that package and write it to the chip. It has latest loader, latest BIOS/OROM, latest firmware for 91xx. Only the autoload is kept as original, because it is specific to this card and it won't work once updated.

Added later:
- after inputing any command like "go" "go -r", you will be prompted with the line "Press Y to start, others to skip", where you will type "Y". If you don't want to see this message, then use "go -y" or "go -r -y" to skip this check. That is why the *.bin was missing the last time you tried "go -r", you forgot to press Y when asked.
- Image 1.0.1.1606 is older than 1.0.0.1813. In fact, it is the oldest image I have found. If you want the latest, then SP1813 - 1.0.0.1813 is your choice, included in the uploaded package.

Thank you. I did like you told me, typed "go -r" and "y", and shut down - and here is the IMAG_RB.bin

@lordkag

@THZ

You have the same image - CRC EB66A935 - that Hanson reported as given BSOD. It would seem this was pre-installed on all U3S6 cards. The problem with this image is that is has a broken inner firmware: it is missing the header section and Program0 has the first F60 bytes blanked with FF. It is a wonder it ever worked.

You either go safe and ask Hanson to test the modded flasher before you: "go", shutdown + boot, test the card, "go -r" and upload the IMAG_RB.bin for inspection. It is your problem in convincing him. He has already been an amazing fellow by testing my craziest ideas on his hardware.

Or you take the risk on your own. The image should work - tested; the flasher should work - reading tested, erasing tested by biondo79. My suspicion is that biondo79 has broken his card by multiple cycles of erasing, writing different images, without a full shutdown in between. And he also flashed an image for another card.

@X-tick

The image 2.3.0.1007 (or maybe 2.2.1.1007) has been provided to Gaudi by Asrock. It is the latest firmware for 91xx that has been spotted in the wild. I also found a 2.3.0.1006 in Asus mainboards.

Don't flash anything until we have all the details. Download the package uploaded by Hanson a few pages back and add the content to the root of a bootable USB. Type "go -r" and nothing more or less at the prompt. When asked to "Press Y..." type "Y". Upload the image IMAG_RB.bin from the root of USB. If there is a warning message, post a screenshot.

The SPI chip is located next to Marvell controller. My guess is that is just above "Asrock" word, bellow the first PCIe slot and left to "ATI" word.

Is this in reply to to X-tick or to me?...

Above post was edited.

@X-tick

From your second screenshot it seems that I need the ID of SPI chip to go any further.

Thank you!!
It worked! I was able to successfully flash to 1.0.0.1813 ! I did it on 3 Computers all with the same card!...

I was getting a little anxious about this. If you could do me/us a big favor and run "go -r" again to see if the image was written properly. Afterwards upload IMAG_RB.bin here.

What do you mean about 3 times? On 3 U3S6 cards or on 3 PC with the same card?

@lordkag

Zitat von lordkag im Beitrag #143

---

I was getting a little anxious about this. If you could do me/us a big favor and run "go -r" again to see if the image was written properly. Afterwards upload IMAG_RB.bin here.

What do you mean about 3 times? On 3 U3S6 cards or on 3 PC with the same card?

---

@X-tick

The first link you posted clearly says 92xx, so it is obviously for 92xx.

Your safest bet is to ask Asrock, of course. But Marvell should provide a new flasher, since this one doesn't support your chip. Until then I can have a look if you post the ID here.

Download Rufus, create a bootable USB, place this content on the USB. Boot and type only "go -r".

But as I said, I need the chip's ID before the flasher will see it.

@THZ

Everything is in order, the flasher worked as it should. Furthermore, it has been confirmed (for myself, nothing to be concerned) that the final bytes are just for logging the actions of the flasher.

@THZ

Can you describe all the steps you've done step by step please ?


@lordkag

why it did not work the first flash for me?

I just flashed so the package of hanson

go -e -y
go -y


:(

maybe I have omitted "go -r" before?

@biondo79: I first typed "go -r" in order to verify my actual firmware version, then pressed any key to quit and then just typed "go", and for confirmation afterwards "y". After successfully flashing I shut down my computer and waited half a minute and then started againwith the USB stick and typed once more "go -r" to verify the new firmware really has been flashed.

Zitat von THZ im Beitrag #149

---

@biondo79: I first typed "go -r" in order to verify my actual firmware version, then pressed any key to quit and then just typed "go", and for confirmation afterwards "y". After successfully flashing I shut down my computer and waited half a minute and then started againwith the USB stick and typed once more "go -r" to verify the new firmware really has been flashed.

---