STM32 Firmware Binaries are Source Code, not Binaries? #44
Description
Thank you all very much for supporting the Picocalc the way you do. I recently received an "H" version Pico with all the older, yet working, factory installed apps. The kit comes with screen tape "stickers" now, so that is a standard practice right out of the box.
I upgraded my Pico to a newer Pico 2W. I managed to track down and install the correct UF2Loader and Picomite version for my Pico 2W. I was dismayed to find I couldn't upgrade my SD Card higher than 32GB, but it should work for now.
I read everywhere that I need to upgrade my STM32 Motherboard Firmware to the latest version "1.4". So, I managed to track down the correct USB-C Data Cable and current version f "STM32CubeProgrammer. I Flipped the little SW107 (Position 1) switch. Now I can connect to my Windows 10 version of STM32CubeProgrammer with my USB-C cable no problem. I downloaded the latest "Picocalc_BIOS_v1.4.bin" file from the /BIN directory here on GITHUB. It appears to download correctly and is sitting on my desktop.
When I try to "download" it to my Picocalc, STCubeProgrammer always-always-always comes back with "Error: Operation Exceeds Memory Limits". There is a thread here: https://forum.clockworkpi.com/t/unable-to-update-keyboard-firmware/17683 that illustrates the problem well.
My issue, I think, is that possibly the wrong file versions were committed to this GITHUB directory. In the forum thread listed above, user "Nick_Stevens" has the same problem as me. Further down, user "guu" shows his screen shot of the download completing properly on Linux. He notices the difference in size between the two files. His is "x01000" and Nicks is "x03227", three times larger.
What I notice is that Nick's file - and the ones I get currently from from GITHUB - look like ASCII files, yet they have the "BIN" extension. If they were indeed source code files, they would be three times larger than compiled binaries. "guu"s files look like proper random hex characters.
This issue occurred in May of last year, around the time that version "1.2" was released. I'm guessing something similar happened then and was corrected. When the new version "1.4" was committed to GITHUB, did anyone test the contents of the BIN files?
Is it possible the Source Code files got uploaded to GITHUB with the wrong extensions on them? If they are, then a lot of others besides me will have the same issue. Can someone please check on this and re-post the correct files?
Thanks very much in advance if you find the solution to this issue.