# UF2 Loader release

**URL:** <https://forum.clockworkpi.com/t/uf2-loader-release/18479>\
**Category:** PicoCalc\
**Created:** [July 8, 2025, 1:26pm UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479 "2025-07-08T13:26:49Z")\
**Posts on this page:** 20\
**Page:** 9

<div class="post-metadata">

**Author:** ![Marsupial](https://avatars.discourse-cdn.com/v4/letter/m/e9bcb4/32.png) [@Marsupial](https://forum.clockworkpi.com/u/Marsupial)\
**Post date:** [October 24, 2025, 12:08pm UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/163 "2025-10-24T12:08:10Z")

</div>

I’ve reinstalled bios 1.2 and got some results

Lua, lisp and Python works ok.

Wezterm still crash and reboot in a loop.

What would be the correct solution? A fresh rebuild with updated sdk?

I know for a fact wezterm works ok outside of the bootloader so the problem is in small details. It’s built in rust… 🤔

---

<div class="post-metadata">

**Author:** ![pelrun](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/pelrun/32/12323_2.png) [@pelrun](https://forum.clockworkpi.com/u/pelrun)\
**Post date:** [October 24, 2025, 12:45pm UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/164 "2025-10-24T12:45:39Z")

</div>

Looks like the flash library wezterm uses is using the old flash API. So short of modifying that it’s not easily made compatible with a partition table.

---

<div class="post-metadata">

**Author:** ![jblanked](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/jblanked/32/17438_2.png) [@jblanked](https://forum.clockworkpi.com/u/jblanked)\
**Post date:** [October 27, 2025, 12:30am UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/165 "2025-10-27T00:30:29Z")

</div>

> [@Marsupial](#):
>
> picoware firmware boot but are unresponsive.

Get the latest version! This is what I did to get it working:

> <https://github.com/jblanked/Picoware/commit/8db1a8777d965cfd7d1595f2c3de37c1e850efe7>

Before v1.4.9, the MicroPython version used a python implementation for the keyboard. I did some research and confirmed the latest MicroPython uses SDK v2.1.1, so when I switched to Blaire’s keyboard driver, I had to add `enable_interrupts` (as mentioned by pelrun earlier in this thread)

---

<div class="post-metadata">

**Author:** ![9a4db](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/9a4db/32/10642_2.png) [@9a4db](https://forum.clockworkpi.com/u/9a4db)\
**Post date:** [November 3, 2025, 8:54pm UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/166 "2025-11-03T20:54:56Z")

</div>

uf2loader 2.3 with:

uLisp 4.7b

or

uLisp 4.8f, both running but acting bit strange…. Anyone have better experience?

---

<div class="post-metadata">

**Author:** ![Escape\_Velocity](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/escape_velocity/32/14541_2.png) [@Escape\_Velocity](https://forum.clockworkpi.com/u/Escape_Velocity)\
**Post date:** [November 15, 2025, 5:16pm UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/168 "2025-11-15T17:16:48Z")

</div>

I just wanted to pop in and say a big thanks to @pelrun for all the work you’ve done on this awesome bootloader. I’ve just recently assembled my PicoCalc with a Pimoroni Pico + 2W and am having a blast learning the ins and outs. Tooling like this that allows flashing from the device/sdcard without a separate computer is such a game changer.

---

<div class="post-metadata">

**Author:** ![Geoff](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/geoff/32/14257_2.png) [@Geoff](https://forum.clockworkpi.com/u/Geoff)\
**Post date:** [November 17, 2025, 2:19pm UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/169 "2025-11-17T14:19:22Z")

</div>

100% agree with @Escape_Velocity. Thanks to @pelrun.

I’m trying to create my own program, and I may reload it half a dozen times in an hour. If this was using the USB port and the BootSel button I probably would have given up by now. Instead I’m slowly making progress _(_ _emphasis on slowly 😁_ _)_.

---

<div class="post-metadata">

**Author:** ![ohm69](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/ohm69/32/11926_2.png) [@ohm69](https://forum.clockworkpi.com/u/ohm69)\
**Post date:** [November 17, 2025, 9:44pm UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/170 "2025-11-17T21:44:46Z")

</div>

Dear @pelrun , I have problem making my software work with your uf2 loader on rp2350, maybe you could point me in the right direction?

My software is a ZX Spectrum emulator, [zx-picocalc](https://github.com/ohm69/zx-picocalc). The application itself works fine when loaded with uf2 loader, but it requires Spectrum software (games, 48BASIC programs) to work. Such a software packages consist of several .z80 image files glued together by a python script, which then executes picotool to load such a bin file into device memory. That works, but whenever I install another firmware using an UF2 loader, the games get erased ☹

There is another way of software distribution: merging application and games together. That’s what I put into release at my github project. But such a package doesn’t work with UF2 loader, “Unexpected error” gets displayed at the bottom of the screen".

I’m using a custom software, called uf2-append, made by someone else (included in my repo). I suspect that software has some problem as it was built for rp2040. I’m definitely not an expert in uf2 files and so I’m stuck. Could you please look at my zx-picocalc-2w.uf2 file - maybe that would be something trivial for you.

---

<div class="post-metadata">

**Author:** ![pelrun](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/pelrun/32/12323_2.png) [@pelrun](https://forum.clockworkpi.com/u/pelrun)\
**Post date:** [November 18, 2025, 6:40am UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/171 "2025-11-18T06:40:25Z")

</div>

Oh yeah, appending files together is a tricky business - you can have various mistakes that the pico rom doesn’t care about but will trip up uf2loader.

Obviously we can improve uf2-append or uf2loader, but that’s solving the wrong problem! The picocalc has an SD card, and that’s a much better place for an emulator to read from than bundling it into the flash.

---

<div class="post-metadata">

**Author:** ![Escape\_Velocity](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/escape_velocity/32/14541_2.png) [@Escape\_Velocity](https://forum.clockworkpi.com/u/Escape_Velocity)\
**Post date:** [November 20, 2025, 2:59pm UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/172 "2025-11-20T14:59:03Z")

</div>

Yeah, I’m sure it would be a heavy lift, but in the long run for this particular hardware it would probably be worth it to change the application to use the SD card to hold the z80 game images and load them into memory from there rather than from specified offsets in flash. From the end-user perspective it would be a much better experience to be able to just copy rom images to SD and have the application generate the list of available games from there.

---

<div class="post-metadata">

**Author:** ![pelrun](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/pelrun/32/12323_2.png) [@pelrun](https://forum.clockworkpi.com/u/pelrun)\
**Post date:** [November 20, 2025, 3:23pm UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/173 "2025-11-20T15:23:41Z")

</div>

Is it a heavy lift? There’s literally a complete working example in the uf2loader menu application 🙂

---

<div class="post-metadata">

**Author:** ![Escape\_Velocity](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/escape_velocity/32/14541_2.png) [@Escape\_Velocity](https://forum.clockworkpi.com/u/Escape_Velocity)\
**Post date:** [November 20, 2025, 8:13pm UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/174 "2025-11-20T20:13:47Z")

</div>

Maybe not, then 😉 I haven’t looked at the existing zx code so not sure how much work it would be to make such a change from the way it’s currently implemented.

---

<div class="post-metadata">

**Author:** ![ohm69](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/ohm69/32/11926_2.png) [@ohm69](https://forum.clockworkpi.com/u/ohm69)\
**Post date:** [November 22, 2025, 11:10pm UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/175 "2025-11-22T23:10:21Z")

</div>

The change wasn’t that hard and now the games may be loaded from an SD card. That version works with uf2loader, at least on 2350. Thanks for your help!

Btw, there is a snapshot size limitation on 2040. I know how to fix it but I don’t have enough time.

> **[Releases · ohm69/zx-picocalc](https://github.com/ohm69/zx-picocalc/releases)**
>
> RP2040 ZX Spectrum emulator ported to Picocalc by Clockwork Pi - ohm69/zx-picocalc

---

<div class="post-metadata">

**Author:** ![LomTuby](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/lomtuby/32/14747_2.png) [@LomTuby](https://forum.clockworkpi.com/u/LomTuby)\
**Post date:** [November 22, 2025, 11:28pm UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/176 "2025-11-22T23:28:20Z")

</div>

This is awesome thanks ohm69!

---

<div class="post-metadata">

**Author:** ![ohm69](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/ohm69/32/11926_2.png) [@ohm69](https://forum.clockworkpi.com/u/ohm69)\
**Post date:** [November 30, 2025, 10:12pm UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/177 "2025-11-30T22:12:11Z")

</div>

Hi,

I have found an interesting software package: **picocalc-wezterm** by wezterm. It’s a full-fledged SSH client for PicoCalc with Pico2\_w.

Unfortunately, when I tried to install it with uf2loader, I got reboot loop. The whole thing is implemented in Rust, which makes troubleshooting harder, for me at least, but once I figured out how to enable interrupts, it ran!

Or sort of ran, because when I’m trying to enter WiFi SSID/password, I get “Corrupted” error. WiFi parameters are stored in device flash, so that’s the most likely reason.

Anyway, other commands seem to work, so I have decided to share my fork:

> **[GitHub - ohm69/picocalc-wezterm: WezTerm for the PicoCalc compatible with uf2loader](https://github.com/ohm69/picocalc-wezterm)**
>
> WezTerm for the PicoCalc compatible with uf2loader

Maybe there’s someone here who knows Rust **and** 2350 flash structure and would be able to help in the “Corrupted” problem.

---

<div class="post-metadata">

**Author:** ![exoticatom](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/exoticatom/32/14118_2.png) [@exoticatom](https://forum.clockworkpi.com/u/exoticatom)\
**Post date:** [December 3, 2025, 4:46pm UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/178 "2025-12-03T16:46:29Z")

</div>

I’m running into a strange issue with pelrun/uf2loader v2.3 on a Pico 2W.

What I see:

1. Fresh Pico → flash wezterm-picocalc.uf2 → works without problems.

2. Then I flash UF2Loader → try to boot wezterm → the board goes into a reboot loop.

3. After that, flashing wezterm again does nothing. The UF2 file just stays in the USB folder and the board never installs it.

Other UF2 files still work normally.

I tested this on a second brand-new Pico 2W and can reproduce it every time. Once UF2Loader is on the device, wezterm UF2 never works again. Test with 2 different Pico 2W → confirmed.

So my question:  
Does UF2Loader leave something behind that can’t be cleaned?  
Is there a way to fully wipe/reset the Pico 2W back to real factory state?

edit: only way to return Pico 2W to factory state: [Release Version 1.0.1 · Gadgetoid/pico-universal-flash-nuke · GitHub](https://github.com/Gadgetoid/pico-universal-flash-nuke/releases/tag/v1.0.1) →universal\_flash\_nuke.uf2

---

<div class="post-metadata">

**Author:** ![ohm69](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/ohm69/32/11926_2.png) [@ohm69](https://forum.clockworkpi.com/u/ohm69)\
**Post date:** [December 3, 2025, 6:41pm UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/179 "2025-12-03T18:41:49Z")

</div>

I think [this post](https://forum.clockworkpi.com/t/uf2-loader-release/18479/135) would answer your question.

Btw, [this version of wezterm-picocalc](https://github.com/ohm69/picocalc-wezterm/releases/tag/20251130) doesn’t hang under uf2loader… but wifi cannot be configured, so ☹

---

<div class="post-metadata">

**Author:** ![jolephoto](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/jolephoto/32/9920_2.png) [@jolephoto](https://forum.clockworkpi.com/u/jolephoto)\
**Post date:** [December 6, 2025, 5:53pm UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/180 "2025-12-06T17:53:33Z")

</div>

hey @pelrun thanks for the great work on this loader

I’m wondering if you have Webmite u2f binairies that are patched for the loader? I only see the pico versions here but looks like the codebase has fixes for webmite. [Release UF2loader fixed build · pelrun/PicoMiteAllVersions · GitHub](https://github.com/pelrun/PicoMiteAllVersions/releases/tag/flash-fix-1)

---

<div class="post-metadata">

**Author:** ![pelrun](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/pelrun/32/12323_2.png) [@pelrun](https://forum.clockworkpi.com/u/pelrun)\
**Post date:** [December 7, 2025, 3:39am UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/181 "2025-12-07T03:39:05Z")

</div>

I fixed the build for webmite but people had issues with it and I took it back down. Haven’t had time for picocalc work since early October, but I’ll be on holiday in a week with nothing but my laptop and picocalc to play with over Christmas. Hopefully I can get a bunch of stuff sorted out then.

---

<div class="post-metadata">

**Author:** ![lamc\_coder](https://avatars.discourse-cdn.com/v4/letter/l/ce7236/32.png) [@lamc\_coder](https://forum.clockworkpi.com/u/lamc_coder)\
**Post date:** [December 11, 2025, 4:13pm UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/182 "2025-12-11T16:13:01Z")

</div>

@pelrun [Wi-Fi stability on MicroPython - #16 by lamc\_coder](https://forum.clockworkpi.com/t/wi-fi-stability-on-micropython/20711/16)

I can’t get WiFi to work in MicroPython when the UF2 is loaded using your loader. Do you know what might be causing this issue?

---

<div class="post-metadata">

**Author:** ![NightIsland](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/nightisland/32/15402_2.png) [@NightIsland](https://forum.clockworkpi.com/u/NightIsland)\
**Post date:** [January 22, 2026, 12:35pm UTC](https://forum.clockworkpi.com/t/uf2-loader-release/18479/183 "2026-01-22T12:35:01Z")

</div>

I’ve been pointed at this thread as I’m trying to upgrade my PicoCalc from a Pico-H to a Pico 2W.  
I can’t find a previously built .uf2 files, but the build instructions for this uf2loader have a line that I can’t find a reference for?

PICO\_SDK\_PATH=/path/to/pico-sdk cmake -DPICO\_BOARD=pico -B build -S .

I don’t know what pico-sdk is being referred to, or which version I might need, or where to get it.  
Can anyone ideally point me at a prior build of the uf2loader for a pico 2W, or point me at what I need for the pico-sdk, please?

[Previous page](https://forum.clockworkpi.com/t/uf2-loader-release/18479.md?page=8)

[Next page](https://forum.clockworkpi.com/t/uf2-loader-release/18479.md?page=10)
