W1CY wrote: ↑Sun Oct 25, 2020 7:41 pm
Second time was a charm... I tried it again today, but instead of using the standalone firmware loader I used the new 10/24 CPS. It worked fine and the radio is operational. Not sure whether it was a coincidence or whether using the CPS loader made a difference or not. The bottom line is that everything is working now. Thanks again for your support.
FYI.
Its a long boring story about the change to the release method and the CPS, but just to explain in more detail
Originally the CPS and the Standalone downloader, "Screen scrape" the Github Releases page, searching for specific things on the web page, specifically a version code that looks like a release , e.g. R2020.10.10 or a development release e.g. D2020.09.27
However to support displaying a list, using screen scraping was no longer practical.
So my first attempt at building a list of releases, was by using the RSS feed available on Github, and I spend several hours battling with this data format, only to discover that it didn't actually contain the release version (aka release_tag) . This was an arrrghh moment, as I'd just wasted over 3 hours on this.
I then found Github also has an API download , which does contain this data
https://api.github.com/repos/rogerclark ... 7/releases
So I had to then rewrite all my code to use this data forum instead. Probably around 2 hours work.
Just to complicate matters, I then found that the Micosoft built in data parser for the API data format (called JSON), is not compatible with Linux , so the Standalone installer could not be used on Linux...
Yet another aarggghh moment.
Luckily, I found a third party plugin (DLL), that could parse JSON format, and was also compatible with the build process that Daniel F1RMB uses to make the Linux version of the standalone firmware loader.
But, here's the kicker as they say...
When I looked at the list of release names using the new loader in the CPS I noticed that the older releases didn't have proper names and I'd simply put the release version in the Release Title.
But when I corrected this on Github by editing the title on the old releases. Github decided that these old releases now needed to be displayed above the newer releases, on the Releases web page, which the Standalone Loader still uses.
IMHO, this is a bug on Github, as editing some text about a release should not make it the latest release.
I partially fixed this, by re-editing the newer releases to change the title to include the year "2020" but I think somehow the old Firmware loader is still incorrectly detecting some old releases as if they are new releases
So, as you can see, nothing is ever as simple as it looks!