--- 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

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

Re: Marvell AQC113C FourPartID Firmware updater edit

1 星期 3 天 前
#4040
Hi ok I will remind you that there are risks in updating the firmware, thanks for all the information 

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.

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

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

Re: Marvell AQC113C FourPartID Firmware updater edit

1 星期 3 天 前
#4041
@QuadDamage Well ok, something is indeed strange with 1.5.42.
After the update it survived a reboot without a problem, but not a power off & power on.
So, for now I will go back to 1.3.33 (with ASPM) and test the other 1.5.x versions later again.
This is my 1.3.33 image:  www.dropbox.com/scl/fi/okyhfc7c73m08baty...30e&st=qiogb195&dl=0

The rest of the 1MB flash is filled with 0xff.

 
The following user(s) said Thank You: QuadDamage

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

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

Re: Marvell AQC113C FourPartID Firmware updater edit

6 天 7 小時 前 - 6 天 7 小時 前
#4045
@QuadDamage Well ok, something is indeed strange with 1.5.42.
After the update it survived a reboot without a problem, but not a power off & power on.
So, for now I will go back to 1.3.33 (with ASPM) and test the other 1.5.x versions later again.
This is my 1.3.33 image:  www.dropbox.com/scl/fi/okyhfc7c73m08baty...30e&st=qiogb195&dl=0

The rest of the 1MB flash is filled with 0xff.




 

I flashed this to my card earlier with flashupdate2 --reflash ATL2-8.0.1_AGENT_sign.CLX hu4567.clx
it flashed fine mac is preserved suspend and wakeup still fine
power off still fine

what exactly is different to this in comparison to the original file
as i have tried flashing via this method in the past and there is no link after suspending the pc or powering it off

flashed my second card also mac also preserved

thanks btw..

you need secure boot disabled to flash
i had turned it on the other week and was getting an error until i disabled it in the bios
Code:
G:\1>kickstart2 kickstart2 x86_64-w64-mingw32-4.10-110-g0d62bf7 Connected to device '0000-0B:00.0' Chip reset completed (boot from flash). Time: 60 ms Loaded MAC FW Version: 1.0.113 Loaded PHY FW Version: 6.1.2 (reported by MAC FW) Loaded bundle: 1.3.21 G:\1>flashupdate2 --reflash ATL2-8.0.1_AGENT_sign.CLX hu4567.clx flashUpdate2 x86_64-w64-mingw32-4.10-110-g0d62bf7 Connected to device '0000-0B:00.0' Starting hostboot (requested by user)... Chip reset completed (boot from host). Time: 391 ms Success load UpdateAgent ERASE start ERASE finish REFLASH start Request for fragment 0x00000000:0x00002000 Request for fragment 0x00002000:0x00004000 Request for fragment 0x00004000:0x00006000 Request for fragment 0x00006000:0x00008000 Request for fragment 0x00008000:0x0000a000 Request for fragment 0x0000a000:0x0000c000 Request for fragment 0x0000c000:0x0000e000 Request for fragment 0x0000e000:0x00010000 Request for fragment 0x00010000:0x00012000 Request for fragment 0x00012000:0x00014000 Request for fragment 0x00014000:0x00016000 Request for fragment 0x00016000:0x00018000 Request for fragment 0x00018000:0x0001a000 Request for fragment 0x0001a000:0x0001c000 Request for fragment 0x0001c000:0x0001e000 Request for fragment 0x0001e000:0x00020000 Request for fragment 0x00020000:0x00022000 Request for fragment 0x00022000:0x00024000 Request for fragment 0x00024000:0x00026000 Request for fragment 0x00026000:0x00028000 Request for fragment 0x00028000:0x0002a000 Request for fragment 0x0002a000:0x0002c000 Request for fragment 0x0002c000:0x0002e000 Request for fragment 0x0002e000:0x00030000 Request for fragment 0x00030000:0x00032000 Request for fragment 0x00032000:0x00034000 Request for fragment 0x00034000:0x00036000 Request for fragment 0x00036000:0x00038000 Request for fragment 0x00038000:0x0003a000 Request for fragment 0x0003a000:0x0003c000 Request for fragment 0x0003c000:0x0003e000 Request for fragment 0x0003e000:0x00040000 Request for fragment 0x00040000:0x00042000 Request for fragment 0x00042000:0x00044000 Request for fragment 0x00044000:0x00046000 Request for fragment 0x00046000:0x00048000 Request for fragment 0x00048000:0x0004a000 Request for fragment 0x0004a000:0x0004c000 Request for fragment 0x0004c000:0x0004e000 Request for fragment 0x0004e000:0x00050000 Request for fragment 0x00050000:0x00052000 Request for fragment 0x00052000:0x00054000 Request for fragment 0x00054000:0x00056000 Request for fragment 0x00056000:0x00058000 Request for fragment 0x00058000:0x0005a000 Request for fragment 0x0005a000:0x0005c000 Request for fragment 0x0005c000:0x0005e000 Request for fragment 0x0005e000:0x00060000 Request for fragment 0x00060000:0x00062000 Request for fragment 0x00062000:0x00064000 Request for fragment 0x00064000:0x00066000 Request for fragment 0x00066000:0x00068000 Request for fragment 0x00068000:0x0006a000 Request for fragment 0x0006a000:0x0006c000 Request for fragment 0x0006c000:0x0006e000 Request for fragment 0x0006e000:0x00070000 Request for fragment 0x00070000:0x00072000 Request for fragment 0x00072000:0x00074000 Request for fragment 0x00074000:0x00076000 Request for fragment 0x00076000:0x00078000 Request for fragment 0x00078000:0x0007a000 Request for fragment 0x0007a000:0x0007c000 Request for fragment 0x0007c000:0x0007e000 Request for fragment 0x0007e000:0x00080000 Request for fragment 0x00080000:0x00080300 REFLASH finish OSB dump: state:        1 avalability:  0x00000070 error:        0 chipId:       0x00B1A113 ecid:         0x6BA13E26 0x61141553 0x480001A8 flashSize:    0x00200000 activeNcb:    0 epoch:        0x00000000 control:      0x00020000 pkHash:       0x00000000 0x00000000 0x00000000 0x00000000               0x00000000 0x00000000 0x00000000 0x00000000 Status: Success G:\1>kickstart2 kickstart2 x86_64-w64-mingw32-4.10-110-g0d62bf7 Connected to device '0000-0B:00.0' Chip reset completed (boot from flash). Time: 100 ms Loaded MAC FW Version: 1.0.121 Loaded PHY FW Version: 6.1.2 (reported by MAC FW) Loaded bundle: 1.3.33
Last edit: 6 天 7 小時 前 by Shonk.

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

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

Re: Marvell AQC113C FourPartID Firmware updater edit

6 天 3 小時 前
#4046
It is the AQC113-DirtyWake_Bx_ASPM_Enabled-1.3.33_bdp_aqsign.clx image file, but already patched with customclx2.
And I used the mac und phy values from entry id 8 (which uses image AQC113-Antigua_Bx-1.3.33_bdp_aqsign.clx, but I wanted ASPM).

I added this additional entry to my updatedata.xml:
Code:
  <bdp id="15">     <hwids>       <pciid vid="1d6a" did="14c0" sdid="0001" svid="1d6a" />     </hwids>     <mac>01000c0040000000000000000100000002000c00000300003ddb9ca1ffffffff</mac>     <phy>0301040200e4030003001cc482b1ffff1dc482b1ffff1ec40100ffff</phy>     <exprom>True</exprom>     <image>AQC113-DirtyWake_Bx_ASPM_Enabled-1.3.33_bdp_aqsign.clx</image>   </bdp>
(and of course, also changed "--update" to "--reflash"... very important...)
 

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

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

Re: Marvell AQC113C FourPartID Firmware updater edit

6 天 2 小時 前 - 6 天 2 小時 前
#4047
can you release a zip with every file edited and ready to go with a command
e.g. ini's edited and it will patch the clx on the fly
i dont want to miss anything

and maybe a txt file in there saying what was changed in what file

actually i think i know everything you done
i will make one and try it myself after dinner
Last edit: 6 天 2 小時 前 by Shonk.

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

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