This is exactly what happened when I loaded the Webmite_PICORP2350 variant through the new uf2 bootloader application. I’m wondering where the OPTIONS data for configuring Picomite to the PicoCalc hardware is located? None of the USB or UART have connectivity to the picomite console. For all I know, the blank screen is just a consequence of not having the SPI and LCDPANEL Options set correctly for Picomite to talk to the hardware. If the OPTIONS are stored in flash, perhaps Picomite simply can’t find it where it’s expecting it to be?
After nuking the flash, I can reflash Webmite and the PicoCalc comes back to normal. I’m really looking forward to proper operation of the new bootloader!!!
When I loaded Picomite from the main Picomite website, the OPTIONS were absolutely necessary. There was no I2C, SPI, keyboard, no LCDPANEL setting, no console operation or default colors, until after I set all the OPTIONS in a particular order. Loading PicoMite from PicoCalc website may include all the settings necessary, but not every implementation of Picomite has these options preset.
I got a chance to compile the MMBasic source code, and now I see what you were trying to tell me. The compiled code takes care of setting up the OPTIONS so the PicoCalc can properly boot up.
Unfortunately, I still can’t get past the black screen when using the new bootloader. Is this an issue that has no resolution?
Thanks for your great contributions to the PicoCalc community!
I am only using the latest release from your github repo.
I think my previous post was too ambiguous. I should have said that the new bootloader loaded itself correctly and came up with the correct selection menu. After selecting the PicoMite and after the flash was erased and rewritten, the screen went black, until I power cycled with F1 held down. I could not get Picomite running.
Incidentally, on the RP2350W, when I tried to use the mass storage mode, as directed by your documentation, the PC complained with “USB Device not recognized”. The device manager confirmed there was a problem with that USB driver.
Hopefully, you’ve seen this before and can tell me where I’m going wrong!
I’ve never been able to get my PicoCalc (also a Pico2W) to be recognized as a USB storage device in Windows either. I’m (still) on WIndows 10, and I only ever remember seeing people reporting success with Linux and/or Mac, so it might be a Windows issue. And I’ve booted it up to the menu and waited before plugging it in, even waiting for several minutes just to see if that mattered.
Running the TurboDeck firmware from the loader always works fine though. If I had the time (which I haven’t yet), I’ve wondered if it would be possible to trim all the unnecessary stuff out of the TurboDeck firmware and try to get it to build as a noflash option. I’m not sure it would even be possible to fit it in the limited space that requires though. But it really doesn’t need to show a background image like it does, have any of that extra framework code that it uses, or even show anything on the screen at all, as long as the SD can be mounted via USB.
Not working for me. PicoCalc with Pico 2w. Already nuked. Running UF2 Loader 2.3. When I flash Webmite_pico2_w.uf2 file taken from @pelrun github PicoMiteAllVersions, I get a black screen for maybe 2 seconds and it returns to UF2 Loader menu…
That’s interesting. I had the same experience with a standard version of WebMite and UF2 bootloader. I actually loaded the @pelrun source files from his repo and compiled that to UF2. I did get some errors that I had to figure out… I had to comment out a gpio function “gpio_get_out_level_all64” in “External.c” because it was already defined elsewhere. I recall previously modifying a couple SDK files for PicoCalc builds, which are explained by @adcockm.
This device has great potential, but not for the casual user. Loading and swapping UF2 flies will not guarantee success, however the open-source community is incredibly talented and willing to share. If we want to get it working our way, it may be best to roll up our sleeves, get dirty and contribute to the cause. I am grateful for the efforts of the early adopters; they laid down a ton of groundwork!
That SDK modification was a terrible idea from Peter, and one of my fixes was to remove the need to do it. You should reset your copy of the pico-sdk to the official release rather than continuing to build using a modified version.
I thought it was an interesting approach and very hacky… I didn’t have alternatives at the time. I’ll probably wait until SDK 2.3 and start fresh with that… I can’t remember all the files I touched.
Incidentally, your WebMite source had some very minor build issues, however after addressing them, everything came together, compiled and I’m running it now! Thanks.
I’ve been moving house for the past couple of weeks and basically haven’t had my laptop out in that entire time. Will have to wait a bit longer I’m afraid