Zitat von lordkag im Beitrag #208

---

@holeckar

@THZ

The keyword is 92xx and the list of supported IDs. Since you have an U3S6R1 with 9120 ID, this is obviously not for your card.

---

One question. If I had another PCI card (message), I can export all software (firmware + BIOS + ...) [full image]. How?
Thanks

@holeckar

To dump the content of the chip, you boot from DOS with any firmware package and type "go -r" for reading SPI content or "go -aid x -r" for reading SPI content of adapter x. Since you most likely have one card, "go -r" is enough. You will find an IMAG_RB.BIN on the flash USB if everything went well.

Here are the images I have promised. The testing goes like this: create a bootable DOS flash and drop the content of the archive on the root of the USB. Then you run "go" and answer with yes to questions. But you already know this, since you already run the flasher before.

- Image safe1 is probably your safest bet, since it was built on top of a firmware dedicated to an external card with 9128, just the inner firmware has been updated. You have a version.txt with updated components.
- Image safe2 is the built on top of safe1, but the BIOS has been updated to 1.0.0.1038. You shouldn't have problems with it, but please check if this BIOS version has any bugs. A version.txt is attached.
- Image risk1 is stepping into dangerous lands, by also updating the loader to the latest version. From what I have seen, the loader is not internal/external dependent, but you never know.
- Image risk2 is absolutely dangerous, since I updated both the autoload and the loader, but with components from a firmware release for onboard controller. You have 80% chances of bricking your card, so this is just for those that have a programmer to recover.

Test only safe1, safe2 and if you are truly brave, risk1. Choose between safe1 and safe2 for your daily use. The image risk2 is only for those with a programmer to recover. Every archive has a PROG.bin image inside bin folder, which can be used with a programmer. All images are for external card use, not for onboard controller.

Safe 1

...
Flashing section 1
Verify failed at 30001, io_size 10
Expecting:
But found:
Flashing failed!!
Flash Failed!!
Flash error, wipeout autoload!!

Safe 2, Risk 1 and Risk 2 too

:(

Zitat

---

@lordkag

To dump the content of the chip, you boot from DOS with any firmware package and type "go -r" for reading SPI content or "go -aid x -r" for reading SPI content of adapter x. Since you most likely have one card, "go -r" is enough. You will find an IMAG_RB.BIN on the flash USB if everything went well.

---

If I have IMAG_RB.BIN, I flash with a programmer or I can use Marvell Flash Tool.

You either have a problem with the chip or some left-overs from old firmwares that trick the flasher. The flasher also has the option "go -w" to erase the chip before flashing, but I haven't seen anyone try that before. I remember reading some official instructions in one firmware package that users should first run "go -w" and right after that run "go", with NO reboot in between. Your hardware, your risk.

IMAG_RB.BIN is only for programmer use, but I can build one small image from it, for flasher use. But your main problem will still be the one from above. You have to erase the chip before flashing, either with "go -w" or with a programmer.

Zitat

---

@lordkag
IMAG_RB.BIN is only for programmer use, but I can build one small image from it, for flasher use.

---

How I can build one small image from IMG_RB.bin?

----

Safe 1

Flashed Successful!!

But it does not work :(

Safe 2, Risk 1 and Risk 2 too

What exactly did you do and what "doesn't work" mean? Have you shut down after successful flash?

After successful flash, i have shutdown, but PCIe card is not detected (without CTRL + M).

The boot message does not appear? The card is not detected in Windows? Do you have a hard drive connected to the card? Please be more specific. One user reported the same thing and it turned out that he had nothing connected to the card and thus the message was not displayed.

Everything OK :)

I flashed Safe2 (I have not tried other).

Info:

Using safe2 is more than enough. The other two bring little to no gain, but many risks. For other users who may need assistance and especially for me, can you write what steps did you followed? Was the "go -w" successful, did you connected a drive?

I flashed from Boot USB.

go -w -y ..... Erased Succesful!!
go -y ..... Flashed Successful!!

I connected a drive. [I forgot to connect a drive. ]

------------------------------------------------------------------

I tested other ...

Info (Safe1) ... OK
Info (Risk1) ... OK
Info (Risk2) ... OK

Why Risk1 and Risk2 are identical to the Safe2 (see Summary Info)?

Summary Info: (from Marvell Storage Management)
			Original	Safe1			Safe2			Risk1			Risk2
BIOS Version		1.0.0.1027	1.0.0.1033		1.0.0.1038		1.0.0.1038		1.0.0.1038
Firmware Version	2.1.0.1504	2.3.0.1007		2.3.0.1007		2.3.0.1007		2.3.0.1007
Boot Loader Version	1.0.1.0002	1.0.1.0002		1.0.1.0002		1.0.1.0002		1.0.1.0002
(by lordkag)				(newer than original)	(same as safe1)		(newer than safe1)	(same as risk1)
Autoload (by lordkag)	?		2.0.0.060C		2.0.0.060C		2.0.0.060C		2.0.0.061D
Driver Version		1.2.0.1041	1.2.0.1041		1.2.0.1041		1.2.0.1041		1.2.0.1041
Chip Revision ID	B1		B1			B1			B1			B1
Vendor ID		1B4B		1B4B			1B4B			1B4B			1B4B
Sub Vendor ID		18AB		1B4B			1B4B			1B4B			1B4B
Device ID		9123		9123			9123			9123			9123
Sub Device ID		9115		9123			9123			9123			9123
Port Count		2		2			2			2			2
Max PCIe Speed		5Gb/s		5Gb/s			5Gb/s			5Gb/s			5Gb/s
Current PCIe Speed	5Gb/s		5Gb/s			5Gb/s			5Gb/s			5Gb/s
Max PCIe Link		1X		1X			1X			1X			1X
Current PCIe Link	1X		1X			1X			1X			1X
Supported RAID Modes	RAID0, RAID1	RAID0, RAID1		RAID0, RAID1		RAID0, RAID1		RAID0, RAID1
Supported Stripe Size	32K 64K		32K 64K			32K 64K			32K 64K			32K 64K
Maximum PD per Adapter	16		6			6			6			6
Supported VD Cache	None		None			None			None			None
Maximum VD per Adapter	2		2			2			2			2
Maximum PD per VD	2		2			2			2			2
Maximum Port Multiplier	1		1			1			1			1

I don't have an old dump for the asrock sata card. I reflashed this card years ago with wrong image from station-drivers. My hope was, someone in here has got a backup of this card.
Nonetheless I flashed this attachment " U3S6R1_Marvell-9120_2.3.0.1007.rar ". It seems to work, Windows recognize the connected hdd and transferring data is fine too.

@holeckar

I see that you were brave enough to flash risk2 and lucky enough to have a working card. It seems that Marvell eventually thought of making the entire firmware work with any controller, because with 9120 and 9123 the autoload (and maybe the loader too) was onboard/external dependent.

The images are not identical:
- original has Autoload 91A3-9123 2.0.0.0611 (IDE type), Loader 1.0.1.0002 (all loaders have this version in 91xx controllers, but yours is in fact older), BIOS 1.0.0.1027, Firmware 2.1.0.1504 (Aug 30 2010).
- safe1 has Autoload 9123 2.0.0.060C (external type, AHCI-RAID), Loader 1.0.1.0002 (but newer than original), BIOS 1.0.0.1033, Firmware 2.3.0.1007 (Sep 20 2012).
- safe2 has Autoload 9123 2.0.0.060C (external type, AHCI-RAID), Loader 1.0.1.0002 (same as safe1), BIOS 1.0.0.1038, Firmware 2.3.0.1007.
- risk1 has Autoload 9123 2.0.0.060C (external type, AHCI-RAID), Loader 1.0.1.0002 (newer than safe1), BIOS 1.0.0.1038, Firmware 2.3.0.1007.
- risk2 has Autoload 9123 2.0.0.061D (onboard type, AHCI-RAID), Loader 1.0.1.0002 (same as risk1), BIOS 1.0.0.1038, Firmware 2.3.0.1007.

You should use safe2 and test risk1/risk2 only if you have boot problems or incompatibilities with other cards, because Autoload + Loader are needed only in the boot stage.

I have also noticed those changed lines, but thought I shouldn't worry you with details. The Sub Vendor and Sub Device are referring to the manufacturer of the card and not something to worry about. They are set by the OEM during production and were probably reset during one of the flashing. I have no control over this and I don't think you can change them in any way. The "Maximum PD per Adapter" was probably changed by the new BIOS or inner firmware. I have not changed anything in the components, it was Marvell call. But if you feel these new firmwares are worse, you can upload your IMAG_RB.bin and I will make a small image for the flasher.