The Corsair User Forums  

Go Back   The Corsair User Forums > Corsair Product Discussion > Corsair Link

Reply
 
Thread Tools Search this Thread Rate Thread Display Modes
  #1  
Old 10-31-2014, 12:10 PM
red-ray red-ray is offline
Banned
red-ray's PC Specs
 
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,152
POST ID # = 739245
red-ray Reputation: 81
Angry How do I recover an H80 after CL 2.7.5361 bricked it

How do I recover the firmware in an H80 after the CL 2.7.5361 program bricked it?
When I ran CL it offered to upgrade from 1.1.12 to 1.2.8. I said OK, the upgrade started and then failed . After the failure CL either no longer detects the H80 at all or detects and unknown device, offers to recover it and then promptly crashes ! I have the H80 connected via a CL Mini with the 1.1.6 firmware.

All in all CL really seems rather unreliable. Is there any other firmware up-loader/recovery tool that actually works that I can use?
Corsair, Please may I have the firmware upload protocol specification so I can write a reliable firmware updater?
. Note that throughout this attempted upgrade no other software was accessing the CL hardware as I am all too well aware that CL fails to use a mutex to interlock accesses with 3rd party applications
Attached Images
File Type: png CL-Crash.png (29.4 KB, 1173 views)

Last edited by red-ray; 10-31-2014 at 12:42 PM.
Reply With Quote


  #2  
Old 11-01-2014, 07:39 AM
Jamesd Jamesd is offline
Registered User
Jamesd's PC Specs
 
Join Date: Nov 2013
Posts: 47
POST ID # = 739361
Jamesd Reputation: 10
Default

I had a similar experience to this which resulted in my H80 being RMA'd probably not the answer you were looking for! Link also bricked my cooling node which I managed to recover doing similar steps to this post

http://forum.corsair.com/forums/show...134#post725134

I did once manage to get the H80 in recovery mode but it wouldn't take the H80 firmware I had. It said it was the wrong version and I couldn't find any other firmware for it. It also wouldn't get the firmware from the net. In the end I raised a ticket with support and they arranged to replace it. A bit of a pain having to RMA but I can't fault the RMA process it was smooth and effort less.
My H80 was still cooling the CPU normally after it was bricked just the fans were on full all the time and I managed to keep using the PC and get a new H80 sent to me before I sent back mine which resulted in very little downtime. Overall excellent service from Corsair!
Reply With Quote


1 members found this post helpful.
  #3  
Old 11-01-2014, 08:49 AM
red-ray red-ray is offline
Banned
red-ray's PC Specs
 
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,152
POST ID # = 739368
red-ray Reputation: 81
Default

Thank you for the information. I can manage to get the H80 into recovery mode, but when I do this both CL 2.7 releases fail to reload the firmware. I also tried CL 2.6 but that seems to get confused by my CL Mini which I guess is too new. I too suspect I will have to either RMA it, return it for a refund (as it does not work) or write my own firmware loader program. I have already raised a ticket with CL support and am awaiting a response.
Reply With Quote


  #4  
Old 07-30-2015, 04:17 AM
red-ray red-ray is offline
Banned
red-ray's PC Specs
 
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,152
POST ID # = 792409
red-ray Reputation: 81
Question Has Firmware update of an H80 or H100 via a CLCC worked for you?

When the firmware update failed the H80 was connected via a CL Mini (CLCC). I now also have an old silver commander and yesterday with an H80 connected via that I successfully updated the H80 firmware using CL 3.1.5667. I am currently wondering if H80 firmware update worked for others via a CLCC. If this worked for you it would be good to know. Knowing the situation for an H100 should also provide some insight.

I could try again updating the firmware via the CLCC, but am reluctant to do the experiment for obvious reasons.

The main reason I am wondering this is that CL 3.2.5676 totally fails to report any of the hardware I have attached via my old commander , so I am wondering if I will ever be able to use the old commander with new CL releases. I know the hardware is OK as CL 3.1.5667 reported it before I updated and SIV also still reports it.

Only the H80 and H100 (V1 protocol) are of interest as the H100i and H80i use the V2 protocol. Note the old commander also uses a V1 protocol but the CLCC uses the V2 protocol.

I have only ever had an issue with the H80 and CLCC when doing the firmware update. I currently have 2 x H80 connected via a CLCC and the hardware works well.

Attached Images
File Type: png H80 Firmware Update.png (6.7 KB, 809 views)

Last edited by red-ray; 08-01-2015 at 04:41 AM. Reason: Typo
Reply With Quote


Reply

Tags
failure, firmware, h80, recovery, update

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 04:33 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.