Updating to the latest Picomite 6.02.01

PicoCalc
1

Hi - new poster here. Soft Eng for many years, just starting to get into the IoT and playing with voltages rather than just 1s and 0s in memory.

I have a PicoCalc which I’d like to update to the latest Picomite firmware (6.02.01 from Geoff’s projects) as I want to use some of the new features.

The readme for the picomite says that the firmware should just ‘go’ - detecting it’s attached to the PicoCalc environs, and set itself up. That hasn’t happened. So, I restored the firmware from the Clockwork site (6.00.02RC23), which woke everything back up again. I realized that the options for the firmware setup were being lost in the move, so I captured an ‘option list’ under the old regime, re-upgraded, and using the serial terminal put them back in again:

===
option platform “PicoCalc”

option system spi gp10,gp11,gp12
option system i2c gp6, gp7, slow

option lcdpanel ili9488P,portrait,gp14,gp15,gp13,invert
option lcdpanel console 1,rgb(0,255,0),0

option sdcard gp17,gp18,gp19,gp16
option audio gp26,gp27
option serial console com1,gp0,gp1,b

option display 26,40
option keyboard i2c

This has left me with an almost working system - I can load and run software from the serial terminal, and it appears on the screen, and I can use the keyboard and the screen on the device… mostly. But some of the keys aren’t working. Using the arrow keys in the editor doesn’t seem to work. Mostly they seem to be ignored, but left arrow seems to put the editor into search and replace mode, and neither Escape or Break seems to be doing their jobs, and CTRL seems to be absent as well.

Is there something simple I’m missing to re-enable the keyboard in full? More options to set, or perhaps a config file that needs to go somewhere in the flash or on the SD card? Or is there something special that needs to be done to get the PicoMite FW to recognise the PicoCalc infrastructure. (I tried Nuking the flash first).

I don’t mind typing, so even if it’s fairly long-winded (like setting options for all the key scan codes) I’d like to stick with the new firmware if I can. I’d even happily throw together some python to automate the process, and ease the springs for those coming after me.

TIA

2

Here’s the OPTION LIST from my PicoCalc. It looks like you’re missing
OPTION KEYBOARD PICOCALC.:

PicoMite MMBasic RP2350B V6.03.00RC6
OPTION SERIAL CONSOLE COM1,GP0,GP1,BOTH
OPTION LCD SPI GP10,GP11,GP12
OPTION SYSTEM I2C GP6,GP7, SLOW
OPTION BAUDRATE 19200
OPTION FLASH SIZE 16777216
OPTION LIBRARY_FLASH_SIZE  4D000
OPTION COLOURCODE ON
OPTION CASE UPPER
OPTION TAB 8
OPTION DEFAULT COLOURS  BLACK
OPTION KEYBOARD PICOCALC
OPTION PICO OFF
OPTION CPUSPEED (KHz) 384000
OPTION LCDPANEL CONSOLE ,, FFCC00
OPTION DISPLAY 26, 40
OPTION LCDPANEL ST7365P, PORTRAIT,GP14,GP15,GP13
OPTION BACKLIGHT LCD 96
OPTION SDCARD GP17, GP18, GP19, GP16
OPTION AUDIO GP26,GP27', ON PWM CHANNEL 5
OPTION RTC AUTO ENABLE
OPTION MODBUFF ENABLE  192
OPTION PLATFORM PicoCalc
OPTION PSRAM PIN GP47
3

Oooh, thanks for the quick response.

That’s had an effect - more of the keys are working, but my testing is shortened by the fact that the screen goes blank after a few seconds.

I notice I’ve got a different LCDPANEL setup to you as well. Have you upgraded, or are the kits sent out with different hardware sometimes?

I’ve just connected the serial port back in, and I’ve still got control there… I’ll continue having a tinker.

4

Did you upgrade the keyboard firmware to 1.6? I think the PicoMite firmware relies oin this to do the automatic configuration. It also requires a completely blank Pico so use the nuke S/W first.

5

The ST7365P came with my kit. It won’t hurt you to try it. The serial port is unaffected. Make sure you leave off INVERT since the 7365 doesn’t need it.

If it turns out worse, just use your serial connection to put it back the way you have it now.

TL