PineDominator Posted July 12, 2012 Share Posted July 12, 2012 FIRST, I find that I am changing my upgrade files from upgrade-2.4.1.bin to upgrade.bin in order for the upgrade process to work. I keep a copy and a text file of MD5's and every time there is a new firmware or beta I have to go through this process. It would be nice if it just checked that the file was a .bin extension. Link to comment Share on other sites More sharing options...
Mr-Protocol Posted July 12, 2012 Share Posted July 12, 2012 When the firmware is downloaded from the website, it is named "upgrade.bin". I have multiple folders, one per firmware, with a txt file per firmware revision with MD5 for archival purposes in case and older version is needed for development. If you need/want and older revision you will need to edit the name of the .bin file to "upgrade.bin" Link to comment Share on other sites More sharing options...
Sebkinne Posted July 12, 2012 Share Posted July 12, 2012 This is actually a bug. You can already (since version 2.3.1) upload any file as long as it is in this form: upgrade*.bin. The problem currently is that we overlooked the md5sum check to not check for only upgrade.bin but for upgrade*.bin. That is the reason why when you do, you receive the MD5 error message. This will be fixed in the next bugfix release. Best, Sebkinne Link to comment Share on other sites More sharing options...
Sebkinne Posted July 12, 2012 Share Posted July 12, 2012 The fix has been committed onto our build server. It is definitely in the next firmware. Link to comment Share on other sites More sharing options...
PineDominator Posted July 12, 2012 Author Share Posted July 12, 2012 Thank you Seb:-) Link to comment Share on other sites More sharing options...
Recommended Posts