You are reading a single comment by @Andrewmk and its replies.
Click here to read the full conversation.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Andrewmk
Fri 2020.01.10
Hi Andrew @Andrewmk maybe a computer ordering vs human visible ordering issue?
It's likely this was the starting page:
from which page may be found:
Beneath 'Find a Binary' DDL the specific firmware update for the desired board type may be selected.
The change log may be found at:
Further complicating things is that the order of the firmware changes is by a unique GUID assigned index and not the release date. This means to find a build from December 2019, one will need to hunt down the page for the release date:
When one aligns decimal numbers, one may view the difference between how computers would sequence, in comparrison to how humans logically sequence. Remember the trailing zero (invisible) place holders to the right of the decimal in any base numbering. A trailing zero is not considered a significant figure:
Tons of articles on version numbering conventions:
2v04.294
2v04.84
0So, using the firmware updates you provided, shows that 840 is a larger value than 294 further proving the cutting edge build is more recent than the firmware installed on your device.
Searching down that page, one may see that there were two releases of the latest cutting edge build today:
2v04.81
7001b3adf8e1e2882d99df5cbdb8a08d3bead589/ 2020-01-10 16:14
2v04.84
63587f2b6c01456461401ba503e1c936de2573cc/ 2020-01-10 16:30
It would take some trial and error Hi-Lo date estimating to locate the actual date for the 2v04.294 version.