Hmmm, I dont think so, because Library -> Applications -> Custom only loads from picoware/apps, and is the only current way to run external Picoware python apps.
gosh darn it, try as i might i just cant get this piccoware to work.
Ive spent the morning setting a brand new virgin SD card but still most everything I try to do, run an app, download an app, retrieve app properties - 80% will fail. So frustrating because I really want this to work.
how exactly should i run an app? for instance the app store menu? cuz i went there, downloaded all 80 some apps successfully,. but then what? I tried View Python apps, click the forecast app, get "loading app details, and that errors out with a “failed to load app details”.
I hope someone can help this poor old tech dinosaur!
another example - I picking Applications/App Store and get “error starting view:name ‘_app_menu’ isnt defined”
huh?
Hey Mike, glad to hear from you again. Let’s walk through these one at a time
This is a reported backend issue that is being worked on. It’s not PicoCalc/Picoware related and should hopefully be fixed for the next release.
This issue was reported shortly after v2.4.1 was released and is fixed. The solution is included in the next release. That Dowloaded Apps option (within Library -> Applications -> App Store) simply lists the apps that were downloaded from the store. To access the actual apps refer to below ![]()
Custom/externals apps are in Library -> Applications -> Custom. Those are community built apps so some may have issues. You can create your own apps using the new IDE (in Library -> Utilities -> PicoIDE) following the Apps guide
Once the apps/scripts/programs are downloaded, you can use them right away. Leave the store, then scroll down and click C to run loaded C programs, Custom for python, JavaScript for mjs scripts, MMbasic for mmbasic programs, Games for community made python games, or Screensavers for community made python screensavers.
Thanks so much for putting up with me.
Ok, so I guess the only thing that’s supposed to work is the last point.
I tried all those things and none of them worked. All display the same type of thing, like I pick C and get a black screen with “C” underlined, a row of dots…then the black screen.
I tried within the App Store menu there’s the same sort of list of types like C, Custom,etc. they act the same way. So I think my fresh “download all” from the AppStore menu maybe didn’t really work, so to confirm that I tried to pick the Show All that sometimes came up, and it crashes. With “Error starting view name “=app=menu” isn’t defined, then a new error “Error stopping view: name “-app-menu” isn’t defined l”
BTW why do menu choices appear /dissapear randomly?
Anyway I think I’ll put it down again for a while and it will all work in a few weeks.
Thanks again for all your efforts
That would mean none of the apps/programs were downloaded to your SD card.
The individual options View All C, View All Python, etc, will list only those scripts available within the category. If you’re having trouble with the store, you should manually populate your SD card: Picoware/guides/Installation.md at main · jblanked/Picoware · GitHub
Which menu choices are appearing/disappearing randomly?
I think after I did an App Store Download All, when it finished the transfer, told me success…I think immediately when I hit back to back out to the menu that there was a choice of seeing or viewing all the new downloads. I may be wrong. I’m pretty tired of doing the download all thing but next time I do I’ll watch more carefully
Feature request: any chance of putting a “BOOTSEL” item into your Picoware menu (make it hard to accidentally request), that will put the PicoCalc into BOOTSEL mode? I’m doing a lot of flashing back and forth of various programs and it would be nice to have a software BOOTSEL instead of having to use a paperclip to press down the bootsel button on the Pico board while putting in the --USB connector. All of my programs use the tilde (“~”) key as a “backdoor” to get into BOOTSEL mode and it would be nice if PicoWare had an easy way to do it without the “paperclip method” haha
Hey, there’s one within Picoware currently. Go to Library -> System -> Bootloader ![]()
arrrghhh… I missed that. Sorry! and thanks!
Just as an FYI:
I had my PicoCalc plugged into my Windows laptop running my SDCard-over-USB program and I asked Claude AI to install Picoware to my D: drive (my RP2040) and it did it completely! It made the directories… it copied over all the apps and then it asked me to put it into BOOTSEL mode and copied over the PicoWare UF2 file and it all worked without a hitch! Fantastic!
NEW Picoware update v2.5.0 ![]()
This release adds support for 4 new devices (POOM, PicoDuo, Elecrow’s CrowPanel 2.01", and Waveshare’s ESP32-C6 OLED Touch Watch), 2 new apps (PGE Adventure and Sprite3D Editor), and many optimizations (game engine with a reduced memory footprint, audio driver with DMA and 10-bit PWM, multiple ESP32 crash fixes, and more).
Check out the full release notes here:
You’ve convinced me to upgrade my PicoCalc and, at 55, to give up MMBasic in favor of this mini OS. My PicoCalc has a hardware problem: the screen has 4 dead lines at the top, i.e. 40 dead pixels. Which OS file should I edit so that the display starts lower (the status bar with WiFi, BT, etc. 40 pixels below 0,0)? Thanks for your help.
Did your PicoCalc come that way or did it happen soon after you got it? If either one, email to get it replaced free.
Hey! Glad to hear you’re interested in Picoware ![]()
- change the following to
42in Picoware/src/MicroPython/picoware/gui/desktop.py at 566d2e59982091e3ae90f7a7bb5fc644ecf162c0 · jblanked/Picoware · GitHub - change the following to
42in Picoware/src/MicroPython/picoware/gui/desktop.py at 566d2e59982091e3ae90f7a7bb5fc644ecf162c0 · jblanked/Picoware · GitHub - change the
self.display.scale_y(5)toself.display.scale_y(45)Picoware/src/MicroPython/picoware/gui/desktop.py at 566d2e59982091e3ae90f7a7bb5fc644ecf162c0 · jblanked/Picoware · GitHub - change the
self.display.scale_y(5)toself.display.scale_y(45)Picoware/src/MicroPython/picoware/gui/desktop.py at 566d2e59982091e3ae90f7a7bb5fc644ecf162c0 · jblanked/Picoware · GitHub
As Toml suggested, reach out to alex@clockworkpi.com about a screen replacement. I think you have up to 6-months for a free replacement (though I’ve seen a person get one after buying through a third-party vendor that bought in early)
Hi, I started today with the latest version of the Picoware firmware on my Picocalc with the pico 2W installed. I’m still testing all the interesting functions but I’m really interested in using the picoide to create MMBasic programs. When I use the example hello.bas program and try to run in in MMBasic the screen flashes for a second and then there is nothing, only a black screen. The example clock program is working.
I’m I missing something or could it be a problem with my version of the firmware I installed.
Hey, thanks for checking out Picoware!
Could you point to where the hello.bas program comes from? The only example Picoware provides is the clock.bas program
I found the example on your github page ‘guides/MMBasic.md’. I entered the program with the picoedi app and tried to run it with the MMBasic app.
Ohh I see now. I think PRINT is supposed to print to serial/REPL.
This should do give the same result but show on screen:
CLS
COLOR RGB(white)
TEXT 0, 0, "Hello from MMBasic!",cm
TEXT 0, 10, "What is your name?",cm
INPUT "What is your name? ", name$
TEXT 0, 40, "Hi, " + name$,cm
END
I tried your code but I get an error message:
Error running view: memory allocation failed, allocating 32768 bytes
It seems that all graphical programs are working (eg the mand.bas program). As long as no ‘cls’ command is used the print command is also working. The ‘cls’ command blanks the screen and nothing is displayed anymore.
Hmm I’m assuming you’re using the Raspberry Pi Pico that shipped with the PicoCalc? I recommend using a Pico2w (that’s what I tested the above script on)
In a future release, I could look into moving some of the MMBasic buffers into PSRAM (we have about 7mb free). I did plan on moving the audio buffers into PSRAM too (which would free 32kb)