and still NOSCROLL appears in the OPTION LIST. It looks like the default for PicoCalc is NOSCROLL but I can't change it back to anything else. Edited 2026-04-03 04:10 by toml_12953
Posted: 08:07pm 02 Apr 2026 Copy link to clipboard
Fede Newbie
In case it helps...
I've copied this from the manual:
'On displays where the framebuffer cannot be read, the firmware will automatically set the NOSCROLL option.'
Best regards.
Posted: 09:15pm 02 Apr 2026 Copy link to clipboard
phil99 Guru
That might be something Peter can fix.
If you want to make sure the PicoCalc display can be read from put an image on the screen and BLIT a portion to another location. If the result is a blank rectangle reading doesn't work.
Or try this command-line colour counter. It reads the colours back from a pixel.
> clear : dim a$(2)=(" Blues"," Greens"," Reds") : dim integer b, c, n > for b=0 to 2:n=0:for c=0 to 255:pixel 9,9,c<<b*8:if pixel(9,9)=c<<b*8 then:inc n:endif:next:?n;a$(b):next 32 Blues 64 Greens 32 Reds
Zeros would indicate it can't be read from. Edited 2026-04-03 07:31 by phil99
Posted: 09:56pm 02 Apr 2026 Copy link to clipboard
toml_12953 Guru
Thanks for that. This is weird. I get
2 Blues 2 Greens 2 Reds
Nowhere near what you get. What does that mean? I thought it should be a binary condition - either it can read from a framebuffer or it can't.
Posted: 10:06pm 02 Apr 2026 Copy link to clipboard
phil99 Guru
Perhaps the PicoCalc is using a RGB111 monochrome colour scheme . My test was on a regular Pico LCD with a ST7796S which uses RGB565. An ILI9488 would have returned 64, 64, 64 as it is RGB666.
Edit. Values greater than 1 at least show it can be read from so scrolling should be possible. All 1s would indicate just one returned colour matches what was sent to the screen, so it was really getting nothing back.
If the top left square gets copied faithfully then reading was successful . Edited 2026-04-03 08:49 by phil99
Posted: 04:03am 03 Apr 2026 Copy link to clipboard
toml_12953 Guru
Perhaps the PicoCalc is using a RGB111 monochrome colour scheme . My test was on a regular Pico LCD with a ST7796S which uses RGB565. An ILI9488 would have returned 64, 64, 64 as it is RGB666.
Edit. Values greater than 1 at least show it can be read from so scrolling should be possible. All 1s would indicate just one returned colour matches what was sent to the screen, so it was really getting nothing back.
If the top left square gets copied faithfully then reading was successful .
The reading was successful. All the colors are correct in the new square. I wonder why the OPTION command doesn't allow me to get rid of the NOSCROLL parameter, then.
Posted: 07:28am 03 Apr 2026 Copy link to clipboard
Mixtel90 Guru
Is the display SPI or parallel? If it's SPI then scrolling isn't recommended anyway. It's regarded as being too slow to use sensibly. That's why NOSCROLL was devised, so that SPI displays could be used for the console.
Posted: 08:25am 03 Apr 2026 Copy link to clipboard
matherp Guru
Lots of speculation and we don't even know what toml is running on or what version of the firmware. For the avoidance of doubt. The PicoCalc firmware built into MMBasic uses the ST7365P driver and writes in RGB565. The PicoCalc I tested on works perfectly with BLIT so reading from the framebuffer works. The display is in portatrait mode and uses H/W scrolling. I haven't got a PicoCalc available and have no idea what the OPTION list reports but NOSCROLL is irrelevant as H/W scrolling doesn't require to read from the framebuffer. To configure a PicoCalc correctly nuke the flash and load the latest firmware. It will then automatically configure itself corectly - nothing else should then be changed. Edited 2026-04-03 18:26 by matherp
Posted: 11:44am 03 Apr 2026 Copy link to clipboard
toml_12953 Guru
Lots of speculation and we don't even know what toml is running on or what version of the firmware. For the avoidance of doubt. The PicoCalc firmware built into MMBasic uses the ST7365P driver and writes in RGB565. The PicoCalc I tested on works perfectly with BLIT so reading from the framebuffer works. The display is in portatrait mode and uses H/W scrolling. I haven't got a PicoCalc available and have no idea what the OPTION list reports but NOSCROLL is irrelevant as H/W scrolling doesn't require to read from the framebuffer. To configure a PicoCalc correctly nuke the flash and load the latest firmware. It will then automatically configure itself corectly - nothing else should then be changed.
I figured since I posted into the V6.02.01 final thread everyone would know that that's what I'm running. Here's my OPTION LIST when I first load the firmware:
If I try to change the LCDPANEL CONSOLE line at all, NOSCROLL is added and nothing I can do will turn it off. Edited 2026-04-03 21:44 by toml_12953
Footnote added 2026-04-03 22:03 by toml_12953 The reason I want to change the LCDPANEL CONSOLE line is because I want to change the default foreground color to amber - RGB(255,191,0) and I can't do that via the OPTION DEFAULT COLOURS line. That line restricts me to the color names, none of which is amber. If OPTION DEFAULT COLOURS allowed RGB values, then I wouldn't need to mess with the OPTION LCDPANEL CONSOLE line.
Posted: 11:45am 03 Apr 2026 Copy link to clipboard
mozzie Senior Member
G'day Peter, Just for reference, can you please detail how the PicoMite firmware detects it is running in a PicoCalc?
Regards, Lyle.
Posted: 11:59am 03 Apr 2026 Copy link to clipboard
matherp Guru
If I try to change the LCDPANEL CONSOLE line at all, NOSCROLL is added and nothing I can do will turn it off.
The PicoCalc is a fixed config and isn't supposed to be changed. The code does not attempt to fully integrate the PicoCalc config with normal functionality.
Just for reference, can you please detail how the PicoMite firmware detects it is running in a PicoCalc?
For the 4 variants of the firmware that could be used on the PicoCalc iff no relevant options are set, as part of intialisation, the firmware tries to read the Pico battery level. If that returns without an I2C error then the PicoCalc is configured
Posted: 08:10pm 03 Apr 2026 Copy link to clipboard
Frank N. Furter Guru
Footnote added 2026-04-03 22:03 by toml_12953 The reason I want to change the LCDPANEL CONSOLE line is because I want to change the default foreground color to amber - RGB(255,191,0) and I can't do that via the OPTION DEFAULT COLOURS line. That line restricts me to the color names, none of which is amber. If OPTION DEFAULT COLOURS allowed RGB values, then I wouldn't need to mess with the OPTION LCDPANEL CONSOLE line.
Try "OPTION LCDPANEL CONSOLE 1,16760576,0" - that worked on my PicoCalc!
Frank
Posted: 11:21pm 03 Apr 2026 Copy link to clipboard
toml_12953 Guru
Footnote added 2026-04-03 22:03 by toml_12953 The reason I want to change the LCDPANEL CONSOLE line is because I want to change the default foreground color to amber - RGB(255,191,0) and I can't do that via the OPTION DEFAULT COLOURS line. That line restricts me to the color names, none of which is amber. If OPTION DEFAULT COLOURS allowed RGB values, then I wouldn't need to mess with the OPTION LCDPANEL CONSOLE line.
Try "OPTION LCDPANEL CONSOLE 1,16760576,0" - that worked on my PicoCalc!
Frank
After you did that, did you have NOSCROLL appear at the end of the line? On mine whenever I change OPTION LCDPANEL, I get NOSCROLL added, which I don't want. The PicoCalc LCD is fast enough to scroll the display rather than clearing it after every screen.
Posted: 12:07am 04 Apr 2026 Copy link to clipboard
toml_12953 Guru
Lots of speculation and we don't even know what toml is running on or what version of the firmware. For the avoidance of doubt. The PicoCalc firmware built into MMBasic uses the ST7365P driver and writes in RGB565. The PicoCalc I tested on works perfectly with BLIT so reading from the framebuffer works. The display is in portatrait mode and uses H/W scrolling. I haven't got a PicoCalc available and have no idea what the OPTION list reports but NOSCROLL is irrelevant as H/W scrolling doesn't require to read from the framebuffer. To configure a PicoCalc correctly nuke the flash and load the latest firmware. It will then automatically configure itself corectly - nothing else should then be changed.
I found a fix. In MM_Misc.c, line 5425 doesn't check for the display type ST7365P, which is what the PicoCalc has. I added a test for that and, voila! NOSCROLL is no longer added automatically. This is the change I made: