You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I would like to mention that the handling of firmware uploads that include the MD5 digest is not really very intuitive. You don't even know whether it's considering the digest.
If it's not too much effort, I'd like to suggest trying to improve the UX in this scenario, e.g. as follows:
After uploading the MD5, you could mention something like "Ok, digest received, now upload BIN". And then, when the BIN has been received, and the MD5 matches, you could issue "Great, MD5 matches, proceeding to flash now..."
Just an idea... And only if the effort is very, very minimal...
(Currently it shows MD5: , but the MD5 shown is the MD5 hash computed over the uploaded MD5 file, not the hash included in the file... This seems pretty useless...)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
From ralfbergs on Discord:
Hi, I would like to mention that the handling of firmware uploads that include the MD5 digest is not really very intuitive. You don't even know whether it's considering the digest.
If it's not too much effort, I'd like to suggest trying to improve the UX in this scenario, e.g. as follows:
After uploading the MD5, you could mention something like "Ok, digest received, now upload BIN". And then, when the BIN has been received, and the MD5 matches, you could issue "Great, MD5 matches, proceeding to flash now..."
Just an idea... And only if the effort is very, very minimal...
(Currently it shows MD5: , but the MD5 shown is the MD5 hash computed over the uploaded MD5 file, not the hash included in the file... This seems pretty useless...)
All reactions