--- SURVEY Are you satisfied with the S-D site? ---

Hello to all of you and thank you again for your loyalty,
Today I want to know if you are satisfied with the site since the change of the server and some touch-ups of the color and the change of the theme of the Forum.
Of course I am aware that there may still be work to do but the biggest part is done
Thank you for your answers
www.station-drivers.com/index.php/en/for...th-the-s-d-site#3618

lan Marvell AQC113C FourPartID Firmware updater edit

  • Gh0st
  • Gh0st 的個人頭像
  • 离线
  • Newbie
  • Newbie
    Enregistré
  • 文章: 3
  • Thanks: 0

Re: Marvell AQC113C FourPartID Firmware updater edit

4 個月 3 星期 前
#3193
First i clear CMOS and second i reflashed ist because there was an bios update from F28c to F28.

now i configured the bios from scratch and network is enabled but the device manager not showing the 10g network....

Please 登錄新增帳號 to join the conversation.

  • admin
  • admin 的個人頭像
  • 离线
  • Admin
  • Admin
    Administrateur
  • 文章: 777
  • Thanks: 383

Re: Marvell AQC113C FourPartID Firmware updater edit

4 個月 3 星期 前 - 4 個月 3 星期 前
#3194
Try Marvell diagnostics to see if it is active and just needs to be done in recovery

Fix a bricked/dead AQC107 NIC after firmware update gone wrong | Bill Haofei Gong's Blog (billgong.com)
 

Configuration
Asus Z790 Pro Art, Intel Cpu I7 14700K, Memoires 32Go Corsair DDR5 (6000Mhz CL30), Water-cooling Thermaright, nVidia Geforce RTX3060,  Alimentation Asus ROG 850W, Samsung SSD 990 Pro, SSD980 Pro, Clavier Roccat Vulkan , Souris Asus, Boitier NZXT H6, HP Creative SB Kratos Free Fibre 10Gb Cable CAT8/7, Switch 10/5/2.5Gbps, Casque Philips Fedelis.
Last edit: 4 個月 3 星期 前 by admin.

Please 登錄新增帳號 to join the conversation.

  • kitkatdarkchocolate
  • kitkatdarkchocolate 的個人頭像
  • 离线
  • Newbie
  • Newbie
    Enregistré
  • 文章: 1
  • Thanks: 0

Re: Marvell AQC113C FourPartID Firmware updater edit

3 個月 1 星期 前 - 3 個月 1 星期 前
#3493
Hi,
I am facing a similar situation with this IC. I do not need a firmware update, but I require ASPM support for this chip.
I have a question about the PHY and MAC addresses from the XML file and would appreciate your suggestions.It seems that I need to add a line to include my device, as none of the downloaded files contain my FourPartID, which is:
0x1d6a 0x04c0 0x1d6a 0x0001.
This ID comes from Ugreen's new NAS lineup, the DXP4800 Plus.
I am wondering what reference number I should use to reflect the current MAC address of the machine.
There appear to be two kinds of addresses. Could you clarify what they are?
For example, here is the XML from version 1.3.33, which I plan to use as an upgrade FW:
<bdp id="2">
 <hwids>
  <pciid vid="1d6a" did="04c0" sdid="8094" svid="1bcf"/>
 </hwids>
 <mac>01000c0004000000000044000000440002000c00000300004adb9ca1ffffffff</mac>
 
<phy>0301040200e4020003001cc474b1ffff1dc474b1ffff1ec40100ffff</phy>
 <exprom>True</exprom>
 <image>AQC113-DirtyWake_Bx_ASPM_Enabled-1.3.33_bdp_aqsign.clx</image>
</bdp>

Additionally, I plan to dump the EEPROM files beforehand to avoid bricking the device. Are there any extra steps I should take to ensure this process is safe?

FYI, I have tried various methods to enable ASPM on the current motherboard, but none of them have worked. Below are the
Code:
lspci -vv -nn
results if you're interested. You can see "ASPM not supported" under "LinkCap:".
警告:此處有隱藏內容,請點擊閱讀!


Thanks.

 
Last edit: 3 個月 1 星期 前 by kitkatdarkchocolate.

Please 登錄新增帳號 to join the conversation.

  • Shonk
  • Shonk 的個人頭像 Topic Author
  • 离线
  • Super Utilisateur
  • Super Utilisateur
    Enregistré
  • 文章: 144
  • Thanks: 56

Re: Marvell AQC113C FourPartID Firmware updater edit

3 個月 1 星期 前
#3509
Sorry i cant help im not sure exactly how it works
hence my problems updating mine

if you work it out plz let me know

remember you have to pull the flash chip to back it up
you get corrupt data trying to dump it in situ

Please 登錄新增帳號 to join the conversation.

  • hu4567
  • hu4567 的個人頭像
  • 离线
  • Poster
  • Poster
    Enregistré
  • 文章: 10
  • Thanks: 4

Re: Marvell AQC113C FourPartID Firmware updater edit

1 星期 4 天 前 - 1 星期 4 天 前
#4028
Hi,

I was able to update my Fenvi AQC113C card. Thanks  @Shonk for the info you provided, especially the hint to dump the flash chip first!

I now use 1.3.33 but I think I successfully tried 1.3.36 and 1.5.38, too.

If anyone wants to take the risk and try it:
  1. In the updatedata.xml, add '<pciid vid="1d6a" did="14c0" sdid="0001" svid="1d6a" />' to the existing entry with '<pciid vid="1d6a" did="04c0" sdid="0001" svid="1d6a" />'
  2. Optionally for 1.3.33: Change image to 'AQC113-DirtyWake_Bx_ASPM_Enabled-1.3.33_bdp_aqsign.clx'
  3. Edit flashUpdateScript.ps1, change './flashUpdate2 --update  ATL2-8.0.1_agent_SIGN.clx updated.clx' to './flashUpdate2 --reflash  ATL2-8.0.1_agent_SIGN.clx updated.clx'
Especially 2. seems to be important on this card. At least the flash chip on my card doesn’t like to be simply written/updated, it wants to be erased first. Otherwise, the data is corrupted afterwards!

My goal was to get ASPM working. And it looks like it does… well, at least it reports that it is working. This is the reason why I stay with 1.3.33. I’m not sure if any image from the other versions has ASPM, too.
@Shonk: Can you tell if ASPM is supported for your Gigabyte?



As this might help to get it working for other cards, these are roughly my steps to get it working:
I first ran customclx2 manually with the IDs from a random card to see by comparison what it changes in the firmware file. And of course, using a Hex editor to look at the files.

While it also changes something at the top, the interesting part was near the end, inside a zero (“00”) block. There was the “phy” value followed by the “mac” value.
Then I looked in the flash chip dump of my card and found this block at address 0x7FC20 (about the middle of the dump, end of the used area).
Though of course with a different value.

After comparing the begin of the block with the “phy” values from the updatedata.xml of a as close as possible version (my card had 1.3.21, so I checked 1.3.33), I found the entry mentioned above. The “phy” value matched exactly and the “mac” had the same length and looked similar.

I first thought I need to create a custom entry with a correct “mac” value for my card. It looks like the first part is depended on the card and the end is dependent on the version.
But that didn’t work. Staying with the value from the found entry was better.

I also noticed the “phy” value slightly changed in version 1.5.x.

Oh and I used the CH341A flash chip programmer a lot… I actually ended up improvising a socket on the card for the flash chip, so that I can quickly swap the chip between the card and the programmer.
It is possible to directly flash the updated.clx with it.
Last edit: 1 星期 4 天 前 by hu4567.
The following user(s) said Thank You: Shonk

Please 登錄新增帳號 to join the conversation.

建立頁面時間:0.080 秒
討論區核心: Kunena 論壇