--- 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
Marvell AQC113C FourPartID Firmware updater edit
- Gh0st
- 离线
- Newbie
-
Enregistré
- 文章: 3
- Thanks: 0
Re: Marvell AQC113C FourPartID Firmware updater edit
4 個月 3 星期 前
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....
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
-
Administrateur
- 文章: 777
- Thanks: 383
Re: Marvell AQC113C FourPartID Firmware updater edit
4 個月 3 星期 前 - 4 個月 3 星期 前
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)
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
- 离线
- Newbie
-
Enregistré
- 文章: 1
- Thanks: 0
Re: Marvell AQC113C FourPartID Firmware updater edit
3 個月 1 星期 前 - 3 個月 1 星期 前
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
results if you're interested. You can see "ASPM not supported" under "LinkCap:".
03:00.0 Ethernet controller [0200]: Aquantia Corp. AQtion AQC113 NBase-T/IEEE 802.3an Ethernet Controller [Antigua 10G] [1d6a:04c0] (rev 03)
Subsystem: Aquantia Corp. Device [1d6a:0001]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 16
IOMMU group: 14
Region 0: Memory at 80800000 (64-bit, non-prefetchable)
=512K%Region 2: Memory at 808a0000 (64-bit, non-prefetchable)
=4K%Region 4: Memory at 80400000 (64-bit, non-prefetchable)
=4M%Expansion ROM at 80880000 [disabled]
=128K%Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/32 Maskable+ 64bit+
Address: 0000000000000000 Data: 0000
Masking: 00000000 Pending: 00000000
Capabilities: [70] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 25W
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ FLReset-
MaxPayload 256 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
LnkCap: Port #0, Speed 16GT/s, Width x4, ASPM not supported
ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 8GT/s (downgraded), Width x2 (downgraded)
TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+ NROPrPrP- LTR+
10BitTagComp+ 10BitTagReq- OBFF Via message/WAKE#, ExtFmt- EETLPPrefix-
EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
FRS- TPHComp- ExtTPHComp-
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ 10BitTagReq- OBFF Disabled,
AtomicOpsCtl: ReqEn-
LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
LnkCtl2: Target Link Speed: 16GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance Preset/De-emphasis: -6dB de-emphasis, 0dB preshoot
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+ EqualizationPhase1+
EqualizationPhase2+ EqualizationPhase3+ LinkEqualizationRequest-
Retimer- 2Retimers- CrosslinkRes: Upstream Port
Capabilities: [b0] MSI-X: Enable+ Count=32 Masked-
Vector table: BAR=2 offset=00000000
PBA: BAR=2 offset=00000200
Capabilities: [d0] Vital Product Data
Product Name: Marvell AQtion Network Adapter
Read-only fields:
[PN] Part number: 00B1E113
[V0] Vendor specific: MAC Addr: 6C:1F:F7:XX:XX:XX
[V1] Vendor specific: Bundle Version: 1.3.31
[V2] Vendor specific: Fw Version: 1.0.121
[RV] Reserved: checksum good, 0 byte(s) reserved
End
Capabilities: [100 v2] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn-
MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
HeaderLog: 00000000 00000000 00000000 00000000
Capabilities: [148 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed+ WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending- InProgress-
Capabilities: [168 v1] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [178 v1] Secondary PCI Express
LnkCtl3: LnkEquIntrruptEn- PerformEqu-
LaneErrStat: 0
Capabilities: [198 v1] Physical Layer 16.0 GT/s <?>
Capabilities: [1bc v1] Lane Margining at the Receiver <?>
Capabilities: [1d4 v1] Latency Tolerance Reporting
Max snoop latency: 3145728ns
Max no snoop latency: 3145728ns
Capabilities: [1dc v1] L1 PM Substates
L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
PortCommonModeRestoreTime=10us PortTPowerOnTime=14us
L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
T_CommonMode=0us LTR1.2_Threshold=96256ns
L1SubCtl2: T_PwrOn=44us
Capabilities: [1ec v1] Vendor Specific Information: ID=0002 Rev=4 Len=100 <?>
Capabilities: [2ec v1] Data Link Feature <?>
Capabilities: [2f8 v1] Precision Time Measurement
PTMCap: Requester:+ Responder:- Root:-
PTMClockGranularity: Unimplemented
PTMControl: Enabled:+ RootSelected:-
PTMEffectiveGranularity: 4ns
Capabilities: [304 v1] Vendor Specific Information: ID=0003 Rev=1 Len=054 <?>
Kernel driver in use: atlantic
Kernel modules: atlantic
Thanks.
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
警告:此處有隱藏內容,請點擊閱讀!
03:00.0 Ethernet controller [0200]: Aquantia Corp. AQtion AQC113 NBase-T/IEEE 802.3an Ethernet Controller [Antigua 10G] [1d6a:04c0] (rev 03)
Subsystem: Aquantia Corp. Device [1d6a:0001]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 16
IOMMU group: 14
Region 0: Memory at 80800000 (64-bit, non-prefetchable)
=512K%Region 2: Memory at 808a0000 (64-bit, non-prefetchable)
=4K%Region 4: Memory at 80400000 (64-bit, non-prefetchable)
=4M%Expansion ROM at 80880000 [disabled]
=128K%Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/32 Maskable+ 64bit+
Address: 0000000000000000 Data: 0000
Masking: 00000000 Pending: 00000000
Capabilities: [70] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 25W
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ FLReset-
MaxPayload 256 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
LnkCap: Port #0, Speed 16GT/s, Width x4, ASPM not supported
ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 8GT/s (downgraded), Width x2 (downgraded)
TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+ NROPrPrP- LTR+
10BitTagComp+ 10BitTagReq- OBFF Via message/WAKE#, ExtFmt- EETLPPrefix-
EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
FRS- TPHComp- ExtTPHComp-
AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ 10BitTagReq- OBFF Disabled,
AtomicOpsCtl: ReqEn-
LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
LnkCtl2: Target Link Speed: 16GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance Preset/De-emphasis: -6dB de-emphasis, 0dB preshoot
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+ EqualizationPhase1+
EqualizationPhase2+ EqualizationPhase3+ LinkEqualizationRequest-
Retimer- 2Retimers- CrosslinkRes: Upstream Port
Capabilities: [b0] MSI-X: Enable+ Count=32 Masked-
Vector table: BAR=2 offset=00000000
PBA: BAR=2 offset=00000200
Capabilities: [d0] Vital Product Data
Product Name: Marvell AQtion Network Adapter
Read-only fields:
[PN] Part number: 00B1E113
[V0] Vendor specific: MAC Addr: 6C:1F:F7:XX:XX:XX
[V1] Vendor specific: Bundle Version: 1.3.31
[V2] Vendor specific: Fw Version: 1.0.121
[RV] Reserved: checksum good, 0 byte(s) reserved
End
Capabilities: [100 v2] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn-
MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
HeaderLog: 00000000 00000000 00000000 00000000
Capabilities: [148 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed+ WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending- InProgress-
Capabilities: [168 v1] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [178 v1] Secondary PCI Express
LnkCtl3: LnkEquIntrruptEn- PerformEqu-
LaneErrStat: 0
Capabilities: [198 v1] Physical Layer 16.0 GT/s <?>
Capabilities: [1bc v1] Lane Margining at the Receiver <?>
Capabilities: [1d4 v1] Latency Tolerance Reporting
Max snoop latency: 3145728ns
Max no snoop latency: 3145728ns
Capabilities: [1dc v1] L1 PM Substates
L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
PortCommonModeRestoreTime=10us PortTPowerOnTime=14us
L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
T_CommonMode=0us LTR1.2_Threshold=96256ns
L1SubCtl2: T_PwrOn=44us
Capabilities: [1ec v1] Vendor Specific Information: ID=0002 Rev=4 Len=100 <?>
Capabilities: [2ec v1] Data Link Feature <?>
Capabilities: [2f8 v1] Precision Time Measurement
PTMCap: Requester:+ Responder:- Root:-
PTMClockGranularity: Unimplemented
PTMControl: Enabled:+ RootSelected:-
PTMEffectiveGranularity: 4ns
Capabilities: [304 v1] Vendor Specific Information: ID=0003 Rev=1 Len=054 <?>
Kernel driver in use: atlantic
Kernel modules: atlantic
Thanks.
Last edit: 3 個月 1 星期 前 by kitkatdarkchocolate.
Please 登錄 或 新增帳號 to join the conversation.
- Shonk
- Topic Author
- 离线
- Super Utilisateur
-
Enregistré
- 文章: 144
- Thanks: 56
Re: Marvell AQC113C FourPartID Firmware updater edit
3 個月 1 星期 前
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
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
- 离线
- Poster
-
Enregistré
- 文章: 10
- Thanks: 4
Re: Marvell AQC113C FourPartID Firmware updater edit
1 星期 4 天 前 - 1 星期 4 天 前
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:
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.
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:
- 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" />'
- Optionally for 1.3.33: Change image to 'AQC113-DirtyWake_Bx_ASPM_Enabled-1.3.33_bdp_aqsign.clx'
- 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'
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 秒