I have recently downloaded and installed the Firmware for MV-91xx Version 2.2.0.1125b onto the Marvell 9123 onboard SATA3 controller of my Asrock x58 Extreme3 motherboard (BIOS 2.80).Since then, I have not been able to boot from the channel 1 of the controller from my Samsung 840 Pro SSD drive.

So far the controller address the ports as following:Port 1: SATA3Port 2: SATA3/eSATA

I have performed different tests and found that the port is fully functional, but the computer refuses to boot from it. The drive connected to port 1 will not boot, the screen remains with a blinking cursor. If I switch the disk to port 2 on the controller, it boots perfectly.RAID configuration manager is functional, and BIOS sees the drive while connected on any of the two ports.

After booting, if I plug any other disk to the Port 1, Windows sees the drive and I can access it.

So far I have tried by resetting to defaults the BIOS (did not clear the CMOS), and reflashing the current motherboard BIOS to check if it reflashed the controller as well (as I have seen that some motherboards do reflash the controller on reboot/reflash BIOS).Also, I reflashed many times the controller package (if it matteres, I did not disable the controller in the BIOs prior to flashing).

While looking for a solution, I have found your page, together with the firmware post.

Based on your knowledge, could you suggest a possible way to fix this?I have not yet done a cMOS reset, although as it is an external controller I do not know if it will fix anything.

Considering that there might be a problem/bug in the used firmware/bios, would it be possible to flash your posted firmware with the "go.bat" tool from the provided link?If so, what would be the steps to create the rigth flashing image?I have checked the Image Creator tool that rebuilds a image for flashing, but would not like to mess with it.

Any help/hint will be really appreciated.Regards

EDIT by Fernando: The thread title has been customized by me, because I wanted to open it for all problems regarding the update of Marvell SATA BIOS modules.

I have checked the BIOSes for my motherboard (8 mb AMI BIOS), and found no trace of the controller ROM inside it, which indicates that the update is done externally (as I have already done).Would it be possible to inject the controller ROM into them in order to reflash it?

Meanwhile I have checked the latest BIOSes for your ASRock mainboard and couldn't find a Marvell OROM either.So there is no chance to update this specific OROM module. Furthermore I doubt, that you will be able to successfully insert any Marvell 91xx AHCI/RAID ROM module into the BIOS (no conjunction with the system BIOS, not enough space within the BIOS).So the only chance to get the Marvell 91xx SATA Controller better working may be to flash a newer Firmware by using the related Firmware installer.

I will be asking for your help as an experienced bios modder because you may have some more background than I do.

I went ahead and did some more research. I have found that there is a way to use the Marvell Flash Tool (found on different forums) to dump an image of the firmware of the onboard controller.It is by using the "go.bat -r -v" command, which is a "frontend" to the mvf_mag.exe tool.

The help for it is as following:

Zitattype 'go' to update Magni firmwaretype 'go -y' to update Magni firmware with Yes includedtype 'go -h -v' to display detailed help screen (this screen)type 'go -e' to erase every sector that was written type 'go -w' to erase the whole SPI chiptype 'go -a' to flash only autoloadtype 'go -b' to flash only BIOS on MAGNItype 'go -b -e' to erase only BIOStype 'go -x' to flash only Firmware on MAGNItype 'go -x -e' to erase only Firmware on MAGNItype 'go -v' to show verbose messagetype 'go -r' read back SPI content, no flashingtype 'go -aid 0' to update the specified the adapter 0

example_hba_info.txt is a sample for user*All numbers in the hba_info.txt are hex. The start_addr is the lba in terms of number of sectors.The size is in terms of number of sectors.The ssd type is specified as follows:0 - ssd, 1 - turbo boot, 2 - turbo standby, 3 - turbo hibernation, 4 - recover cdThe ssd attribute specifies whether the os has access to it, bios has access to it or if it is deletable.* hba_info.txt should be the correct name to use in actual operation

I have managed to dump the image. Find attached both the image included (wich is the one I flashed into my controller) "image", and the dumped one "IMAG_RB.BIN". I tried to rename the IMAG_RB.BIN into "image", but reflashing throwed an error. Files are different size. I have hex edited to see the content, and at some point there are similarities, but that is the best I could do.I have also found that the package includes a Image_Creator folder that has a tool to rebuild an image to flash. Perhaps this dumped image can be splitted and rebuild into a usable file.As of that, I have found another user with this very same motherboard who is willing to help.

Based on your knowledge, can you suggest how to dump the image from a working MB and reflash it into mine?

Since I never had a System with an on-board Marvell SATA Controller, I don't have any own experience regarding the Marvell Firmware flashing procedure.Nevertheless I hope, that someone else will be able to help you.

can you tell me what type is the SPI flash chip near marvell controller ?

I am trying to recover from a badflash an add-on pci-e Marvell Card with 9128, we may help each other with info.

Hi, thanks for the contact.Please find the attached pictures with the requested info.

Any hint on how to go on? I tried to rebuild the flashable image to use with the GO.BAT tool found in Station-Drivers page by reverse engineering the dump from a working computer and comparing it with the same dump from my controller after the update to no avail. I have no clue on how does the mvf_mag.exe flashing tool work, as it is not documented and I cannot reflash the dumped image.

The image files that the marvell tool can use are supposed to be around 232KB, the tool expands the imaghe in the BIOS IC and then you get the 512KB image file that you had. The structure is different as you said, so you have to use one of the various images found around.

If you still have access to the other original motherboard, you can use the Marvell storage utility ( from inside Windows) to dump an image from your controller, i think that this image should be the one used with mvf_mag.exe

If not, then the correct way is to use the mvf_mag.exe with the -r -v option to jjust dump the image.

To be honest , i havent seen any marvell firmware available online to have the RAID option enabled, i think all are versions from add-on Pci-E cards, maybe you can find a relevant RAID bios from highpoint ( rocketraid ) marvell cards, or the ones by IO-Sata.

All the other ones i've seen have CPU_AHCI fimware or CPU_IDE firmware.

Since you're booting now, i would suggest to leave it as is, unless you don't care experimenting.

Did ASRock support have the original controller bios? They've helped me many times with their boards.

Zitat von felix im Beitrag #11The image files that the marvell tool can use are supposed to be around 232KB, the tool expands the imaghe in the BIOS IC and then you get the 512KB image file that you had. The structure is different as you said, so you have to use one of the various images found around.

If you still have access to the other original motherboard, you can use the Marvell storage utility ( from inside Windows) to dump an image from your controller, i think that this image should be the one used with mvf_mag.exe

If not, then the correct way is to use the mvf_mag.exe with the -r -v option to jjust dump the image.

To be honest , i havent seen any marvell firmware available online to have the RAID option enabled, i think all are versions from add-on Pci-E cards, maybe you can find a relevant RAID bios from highpoint ( rocketraid ) marvell cards, or the ones by IO-Sata.

All the other ones i've seen have CPU_AHCI fimware or CPU_IDE firmware.

Since you're booting now, i would suggest to leave it as is, unless you don't care experimenting.

Did ASRock support have the original controller bios? They've helped me many times with their boards.

I think the image generated using the go.bat -r is the same as you mentioned, as the bat passes the commands to the mvf_mag.exe.I may try to contact again the user that provided me the image to re-dump the firmware using the tool as you mentioned.

I had no luck contacting ASRock. Have you got any support email you can provide me to send them an email?

Are you absolutely sure that your board has a 9123 controller? Because the support page of your mainboard mentions a 9128 with RAID capabilities. Start by looking into Device Manager for its DeviceID, but the definitive proof will come from visually inspecting the chip, like in this image.

As for your problem, the solution is to find the right autoload. If you can upload here the dump you took from a working computer, I can assemble some images for you: one for the mvf flasher and one for a programmer. It is also useful if you upload the firmware that restored boot, but disabled RAID.

Are you absolutely sure that your board has a 9123 controller? Because the support page of your mainboard mentions a 9128 with RAID capabilities. Start by looking into Device Manager for its DeviceID, but the definitive proof will come from visually inspecting the chip, like in this image.

As for your problem, the solution is to find the right autoload. If you can upload here the dump you took from a working computer, I can assemble some images for you: one for the mvf flasher and one for a programmer. It is also useful if you upload the firmware that restored boot, but disabled RAID.

Thanks for the reply.You are absolutely right, the controller is 88SE9128 (see attached picture).

It is strange as the flash tool reports it as a 9123, also the Windows 7 Device Manager: PCI\VEN_1B4B&DEV_9123&SUBSYS_91231849&REV_11See the attached screen captures: blue background is with the flashed bios that had RAID Manager setup enabled (http://www.station-drivers.com/download/...rivers.com).exe)

the other is while running the flash tool to dump the bios after the last flash (boot from SATA port 1 enabled, no RAID setup):

Dumps from mvf-mag.exe.rar contain two files:IMAG_RB.BIN_Original_Backup.BIN: Dumped from a 100% functional motherboard, I guess it is the original Firmware that came with the board.IMAG_RB_Upgraded_Fail.BIN: Dump after the initial flash with the 1125b firmware.

Hope the info is enough. Let me know if there is any other file you may need.I do not have a programmer, so I will appreciate an image to flash using the mvf_mag.exe tool.