OPTION COLOURCODE ON to activate color coded in the editor. [20250401_170419]
A little benchmark with the Lorenz attractor prog :
default cpuspeed (150Mhz) : 10 sec
cpuspeed 396Mhz : 4 sec
Not bad
How does one get wifi working on pico 2 w
Thereās no easy way, at present. Youāll need to create and build the firmware yourself and create whatever applications you need.
You could use the Arduino IDE to create your own custom firmware for the device. Someone started working on that here:
I havenāt played with the uLisp port, but itās possible it might support wifi functionality. Someone built it for the Pico 2.
Edit (download links for firmware):
Similarly Fuzix might support wifi, but I havenāt played with it yet either. Doesnāt seem like anyone has really been using it much, since the folks interested in Linux have seemed to gravitate toward the Luckfox Lyra (which also doesnāt have wifi, except by hardware mods).
I havenāt seen anyone porting MicroPython/CircuitPython to the Pico/Pico2 for PicoCalc, but that could be a possibilty as well. I might take a look at that myself soon since I already started looking at it for the Waveshare ESP32-S3 Pico module.
Edit (display works, but keyboard doesnāt on CircuitPython):
I suppose you could ask @guu about it, but sounds like heās busy with other things (and he already did the inital ports of these firmwares), so Iām guessing the community efforts will probably produce something faster.
So I guess the TL;DR is: wait a few months and see what develops, or jump in and try to get something working yourself. Thatās kind of the general rule for all Clockwork devices, which can be either exciting, or frustrating, or both, depending on your needs and patience.
I do have images available; a few minor issues, but itās pretty usable.
There is wifi support in uLisp at least, but I havenāt tried it yet. Will report back later.
Nice! Thanks for sharing the link. Also, itās cool youāre documenting your journey with Lisp on the PicoCalc.
I noticed the Pico 2W @ 250MHz link on your website is dead, but since it wasnāt listed in your performance stats, maybe it was a planned release that didnāt happen?
I plan to play around with your firmware for the Pico 2W, though I have to admit I wasnāt overjoyed with lisp years ago as an undergrad. I struggled to wrap my head around it. Not sure if that will have improved or worsened with age but Iāll give it a go. A friend of mine who is really interested in Scheme has tried to bring me over to that world, but so far hasnāt managed to do it, but maybe the PicoCalc will push me in that direction.
Thanks for the catch! It was a misnamed file, which Iāve pushed up and it should be available now.
FYI, uLisp is a Lisp-1 (like Scheme) with Common Lisp function names, and itās pretty extensible (Iāve added some of my own functions and extensions already). But Lisp is definitely not everyoneās cup of tea!
Does anyone know what the issue is here i keep getting Not enough memory. Is there a way to clear memory? So i have tried the commands CLEAR and or CLR seems to do something but i still get the not enough memory error.
um, thatās an NES rom meant for an emulatorā¦
It looks like you have the (default) PicoMite firmware loaded on your PicoCalc, the only thing that is capable of RUNning is MMBasic programs (.bas files).
Iām guessing you need an NES emulator firmware for a .nes file.
Best wishes,
Tom
Lol i thought it wasntoo big
just curious: why did you try to run binary nes file in basic interpreter? what did you expect to happen?
I am totaly newbie to all this and trying to take the baby steps to learning lol. Though i have learned a few commands now for picomite.
no shame there, I wish you the very best on you journey!
Are the āfew monthsā over, yet, @adcockm?
Seriously, I just got my very own PicoCalc today and swapped the stock Raspberry Pi Pico for a Raspberry Pi Pico 2W. Booting with the original SD card gives a blank screen, obviously (but a green power LED ā yayyy).
Iād love to be able to program the PicoCalc in Python (Micro- or Circuit-) and being able to fully use the screen, keyboard, audio, SD-card, GPIO ports etc.
Where should I look for the latest developments on that frontier?
But BASIC (PicoMite? MMBasic? Terminology?) would be fine for a start, too. Where would I look for the latest developments for the Pico 2W here?
As you said it quite well, @adcockm, the support from Clockwork seems to be a bit ābareboneā. Thatās too bad. But if the community is eagerly working on porting stuff for the PicoCalc thatās based on a Pico 2W (or even totally different but socket-compatible boards) that awesome!
Cheers!
Stefan.
If you want to be adventurous, I would suggest taking a look at Forth on the PicoCalc. There is a thread here about running zeptoforth on the PicoCalc (disclaimer: I am its primary author), which is detailed at FORTH on the PicoCalc - #5 by tabemann. While the PicoCalc support is still beta per se as it is not in a formal release yet, it is already very functional. Currently you can configure zeptoforth to support the PicoCalcās display and keyboard, FAT32 filesystems* in on-board flash, and WiFi with zeptoIP; with a bit of work you can also set up support for FAT32 filesystems* in the SD card in the PicoCalc.
Also, there are tools available such as zeptoed for editing files in FAT32 filesystems and tools for transferring files to and from your PC. Also, there is an NTP client available for zeptoIPv4 for synchronizing your Raspberry Pi Pico 2 Wās Always-On Timer with an NTP server (currently zeptoIPv6 is not supported for this, but adding zeptoIPv6 support should only require a minor modification to the NTP client). Last but not least, if you choose to invest in a Pimoroni Pico Plus 2 or Pico Plus 2 W, there is support for PSRAM and putting FAT32 filesystems in PSRAM as a RAM disk.
* Note: there is currently no support for long file names nor is there plans to ever support them.
Yes, you can use the Pico 2W on PicoCalc. I do. Just go to Madcockās website, download the file and install as usual.
The current version is RC25 but I only see RC24 there. Madcock should update the website soon although the difference between RC24 and RC25 is minimal. RC25 just fixes a couple minor bugs in the editor.
As far as I could tell, the RC25 only affects PicoMite running on HDMI displays with a mouse (it was an issue with the mouse cursor), so it shouldnāt have any noticable affect on the PicoCalc build. But I updated it to keep things in sync.
Update posted:
If itās like other Clockwork hardware (take the Gameshell, for instance), eventually people will move on and no active development or projects will be appearing, but we donāt seem to be anywhere near that point yet, thankfully!
What comes on the SD card with the device only works with the Pico. The Pico 2W can either use the PicoMite build for Pico2 or the Webmite build for Pico2. You wonāt be able to access wifi features with the PicoMite build, but youāll have a bit more memory free, and some other PicoMite features. I donāt think thereās a good list of the differences between versions, but if you donāt mind sifting through a lot of information itās in the PicoMite manual. Thereās no updated manual for 6.00.02 builds yet, but I think most, if not all of the functionality is backwards compatible with that release, and itās just some extra commands, maybe some extra parameters and options, and some bugfixes that come with 6.00.02. The changes are listed in all the (many) posts on TheBackShed, but hopefully the docs will be updated when the new version is officially released. Right now itās just RCs, but people (including me, mostly out of curiosity) seem to want the latest so itās there at the link below.
I havenāt kept up with the MicroPython development, but last I looked it was quite active. Documentation was slim, and Iād recommend reading everything you can about it on the forums here, since it sounded like some of the information posted on teh github was incorrect and people had to do things differently to get it fully working, but it was discussed in the forums.
There are at least 3 different version, I think. The first was for an ESP32 based WalnutPi, but zenodanteās seemed to replace it with a more robust (but maybe not documented well?) version. And Laika adapted it or created a new one too, I think?
Best to ready everything at these two threads to catch up. Iād have to do the same as I have no idea what the current ābest procedureā is to install MicroPython on a Pico2 with the PicoCalc. Iām guessing itās zenodanteās, but I could be wrong.
Kinda sucks that the only way to find out about whatās going on is to sift through months of posts, but thatās kind of how things have always worked around here.
See the link I posted in the message above this. Itās my own fork of the official PicoMite repo. Originally it just included the adaptations made by guu for the PicoCalc hardware (mostly display and keyboard), but itās seen a number of bugfixes, rewrites, and even benefitted from a compelte display rewrite that was done from teh official sources to support a very similar display to ours. Keyboard stuff was a bit of a mess in the old version too. And the version that shipped on the SD was for a much older version of PicoMite, without any options for Webmite or wifi access.
Forth was already metnioned above, and while i havenāt tried it myself, it seems like theyāve been making a lot of progress. The uLisp folks have made considerable progress too, and I think it may be the first āofficially supported portā project for the PicoCalc as it sounded like the uLisp maintainers brought the changes into their own project. Iām not a Lisp enthusiast though, so canāt really comment on it beyond knowing that it exists and has made progress.
I think those are the main languages that people have worked on for the PicoCalc so far. The other big thing (which I still need to dig into more for PicoMite) is the SD Bootloader to avoid the need to flash firmware as often. Currently, itās only usable if the firmware is rebuilt to support it. Guu posted a version that incorporates a PicoMite build and the Bootloader into one firmware, but itās only for the Pico and only for that specific version of the code. Iām hoping to dig into it again at some point and replicate that for the Pico2 and also get it building in a way that can be synced and kept up to date with changes in teh mainline PicoMite code. Iām also considering breaking it out compeltely (as teh bootloader was originally intended) and using the work guu has done to have ābootloader friendlyā builds for the PicoMite variations. Thing is, the SD_Boot developer already has plans to enhance it so it coudl theoretically use firmware as it is, without having to be rebuilt. If that happens, then all this extra work will be unnecessary. So partly this is an issue of figuring out where it makes sense to spend time.
Iāve got a few other things planned for the PicoMite build though, like setting the display brightness from mmBASIC, and cleaning up the existing code that allows for setting the keyboard backlight, among other things.
Itās also worth noting there are developers who have been using the PicoCalc as an arduino platform, and git has several examples of working drivers for the PicoCalc hardware, as different people ahve independently figured out how to do it and built their own libraries. Itās unclear which of those is the ābestā, but thereās plenty of stuff to sift through and adapt or get ideas from. Iād recommend doing a search on github for āpicocalcā and plenty of stuff will pop up. Iām not sure what that āpicocalc sd formatterā thing is, but it seems like some kind of AI generated garbage and considering the useless and frequent updates to it, it could be malware.
If youāre interested in using a different module, the Luckfox Lyra is an impressive option instead of the Pico2w. It can run actual Linux, has considerably more memory and processor power, but still fits in the Pico module slot. The downsides are some soldering is required to get sound working, and you wonāt be able to benefit from any of the other software/language work being done for the PicoCalc, but since itās Linux you can pretty much build and run whatever you want, assuming it can run via a Linux terminal, and doesnāt do anything too fancy in terms of graphics, though SDL has been supported so things like Doom and even retroarch can run, though they have limited performance.
Sorry for the long reply, but that was my attempt to try to summarize things that have been happening around here. Hopefully some of it helps!