Hello all, just got my PicoCalc. All seems good. Pico 2 is inside, works.
Now I wanted to update the keyboard firmware, using the most recent PicoCalc_Bios_v1.2.bin file.
I downloaded STM32CubeProgrammer (for Windows), put the dip switch 1 to on, connected with the programmer (it connects), selected the file and clicked download. The process starts, but then I get “Operation exceeds memory limits”. What am I doing wrong please?
Anyone please? It seems that the firmware i got is the old version as i cannot read the battery level via mmbasic - I get keyboard not responding
Thank you for the reply. I do not have a Linux computer. On windows I get this:
Is there maybe any other setting I should check?
I appreciate any ideas!
NO,things for flashing keyboard firmware is alway simple
just pull the DIP 1 on, and there you go
But compare these two screenshots
I noticed that , in the size input, mine is 0x10000,yours is 0x3227A
which is not normal
I don’t know why this happend
1 Like
Update: it seems the download file was corrupted. I downloaded again and now it works. Thank you!
1 Like
Maybe a stupid question: What does the update for the keyboard improve?
- Read battery percentage with charging status flag
- Read and set keyboard backlight
- Bug fix low_bat,add debounce to avoid false shutdown
- Depricated report_bat()
v1.2 updates maybe is useful for developers ,it’s like no difference to normal users
if any has inerests, also can check the example code to see how to talk to the keyboard through i2c:
5 Likes
I downloaded STM32CubeProgrammer on my Windows 11 desktop, but no COM port is detected via UART.
I tried another Windows 11 laptop, where COM4 and COM5 are available, but it still could not connect to PicoCalc.
I already set DIP1/ON, connected via USB-C, and launched STM32CubeProgrammer with administrator rights — but still no successful connection.
May I know what else I might be missing? Thanks!
1 Like
Does anybody have an alternative download link for STM32CubeProgrammer? I’ve been trying to download it all afternoon with no luck. It’s making me crazy.
For the PicoCalc,(unless you made my mod) you have to use USB, not UART to connect to the Cube Programmer.
Hi,
USB mode show “No DFU detected”.
Tried 5 different USB-C cables, also there’s has no hardware detected from Device Manager..
Re-installed the whole STM32Cube, take out batteries from Piocalc, tried everything but still cannot connect
Is there any driver that I am missing?"
Thanks!
This is how I just upgrade the firmware (from Windows 10):
- Open PicoCalc
- Turn on switch 1 (SW107) (just below the SD-card)
- Connect USB-C to the Computer
- Hold power button to turn on PicoCalc (Windows plays its ping-pong USB connected sound)
- Start STM32CubeProgrammer on the computer
- Select “UART” (light blue drop-down at the top right)
- Press “Connect” (green button at the top right)
- Press tab “Open file” and select “PicoCalc_BIOS_v1.2.bin”
- Press “Download” button
2 Likes
Oh, I missed the important step — “Hold the power button to turn on PicoCalc” 
I finally succeeded in flashing the v1.2.bin via the UART COM port.
No more errors when print mm.info(battery) now!!!
Thank you very much! 
2 Likes
Oops , I’m glad it worked for you.
I can’t get the bios upgrade to work.
I follow all the above instructions, STBCube says the download is complete.
But print mm.info(battery) gets a syntax error. And the screen is all wonky now too.
I’ve tried 1.2 and 1.4 with same bad results.
I do have the Pico2w version 6.002 as the basic load. Yes, I’m running a Pico2W.
Is there is p2 version of the bios firmware?
I’m quite frustrated, it seems like everyone else is have a nice easy time getting these update to work.
If you can even type “print mm.info(battery)” in means that the firmware upgrade worked. That it gives “syntax error” is because you’re probably still running a really old version of PicoCalc (yes, you need to upgrade both).
If your screen is “wonky” it has nothing to do with the bios firmware. It’s almost certainly because you damaged it while opening the case (or the cable isn’t correctly inserted into the connector, but that’s less likely.)
There are countless posts here from people who have done that (email alex@clockworkpi.com about a replacement) but there’s also a lot of information on how to protect the screen (tape it down, don’t put the screws in unless you know the lcd is seated properly, yadda yadda) which won’t help you if it’s already broken but will help you protect the next one.
Ok, thanks for the input & help.
I thought “generic” 6.00.02 was new enough but apparently not.
I just installed 6.00.02R23 and the mm.info is working.
I had just gotten word the my uConsole was shipping soon so I’m hoping Alex can pop a replacement display in the package.
Best Regards,
Michael Jones
SCSI Toolbox
303-972-2072
Version 06.00.03 final works even better than beta versions of 06.00.02.
Releases · madcock/PicoMiteAllVersions
I had been under the impression that when these posts mentioned “breaking” the display that they meant physically damaging, like cracking.
My display has no breaks or cracks, just some lines & some areas that are blank.
I started down this upgrade path because I was playing Zork and suddenly the text looked like it was going down off the bottom of the and was scrunching up at the top. Once this started (in Zork 2) it continued with everything.
Anyway hopefully I can replace the “broken” display, whatever “broken” means. Wonky.