最近看到一个项目,名字叫 Dragonfruit。它干的事挺有意思:不是做一个 Palm OS 皮肤,也不是把几张 Palm 界面截图贴到墨水屏上,而是真的在 ESP32 设备上模拟一台68k Palm,更准确点说,它模拟的是 Motorola MC68EZ328,也就是当年 Palm IIIx 这类机器里面那颗 DragonBall EZ,一看这个名字就很有年代感。
Github地址:
https://github.com/megabytefisher/Dragonfruit
左边是真 Palm IIIxe,右边是 M5Paper。右边这个白色墨水屏设备里跑出来的 Launcher,不是图片,是 Palm OS 3.x 真启动后的界面。
这类项目最怕只做到“像”。图标像、字体像、外壳像,最后其实就是个怀旧主题。Dragonfruit 不是这个玩法,它更像是把一台 Palm 的硬件行为重新捏出来,然后让原版 Palm OS ROM 自己跑起来。

简单讲就是:ESP32 负责跑模拟器,PSRAM 放 Palm 的 RAM 和 ROM 镜像,墨水屏显示原有的Palm 的 160x160 黑白画面,触摸屏负责把手指/笔的位置变成 Palm 能理解的 pen event。
这个项目里几个主要器件挺关键。
第一个是 ESP32-D0WDQ6-V3。M5Paper 上这颗是双核 240MHz,纯解释器能跑,但速度不够舒服,所以设备端还做了 burst JIT,把热点 68000 ROM 代码翻译成 Xtensa 本机代码。JIT 编译器跑在第二个核上,不是随便拿个 ESP32 点亮屏幕。
第二个是 8MB PSRAM。Palm IIIx 的模拟 RAM 是 2MB,ROM 镜像也要放进去。README 里直接说了,没有外部 PSRAM 不行,像 ESP32-C3 那种单核、没 PSRAM 的芯片就别想了。
第三个是 IT8951 墨水屏控制器。M5Paper 是 960x540 的电子纸屏,而 Palm 原来是 160x160、1bit framebuffer。Dragonfruit 要把 Palm 的小黑白画面放大、旋转,再把 Graffiti 那块丝印区叠到下面。墨水屏刷新慢,所以显示这块不能当普通 LCD 随便刷。

第四个是 GT911 电容触控。Palm 原来是电阻屏和触控笔,M5Paper 是电容屏。
第五个是 SD 卡。Palm OS ROM 不随项目分发,因为有版权。你得自己从拥有的 Palm 设备里导出 ROM,放到 FAT32 SD 卡根目录,命名为 palm.rom。启动时固件读进 PSRAM。SD 卡里还可以放 PRC/PDB/PQA,让系统启动时安装;也可以放备份目录,把 Palm 数据库导出来。
上面这张图更有意思。M5Paper 上已经能跑 Graffiti 手写练习了。你看它不是只能进 Launcher,触控、手写区、按钮区这些都已经能跟 Palm OS 对上。
很多模拟器项目,启动系统那一刻最激动,后面就没下文了。Dragonfruit 反而是在这些小地方下功夫:首次启动向导、触控校准、国家/时间/日期设置、Graffiti 输入、Apps/Menu/Calc/Find 这些丝印按钮、睡眠和自动关机、数据库安装和备份。
觉得这个项目复古好玩,不是因为 Palm OS 多先进。现在看 Palm,那套东西当然很老了,160x160 黑白屏、Graffiti 手写、Date Book、Memo Pad,都是上个时代的东西。但它放在 M5Paper 上,突然又顺眼了。墨水屏本来就慢,Palm OS 本来也不追求花哨动画;Palm 的黑白 UI 碰上电子纸,反而比很多现代系统更合适。再加上 ESP32、PSRAM、JIT、触控映射、SD 卡这些嵌入式细节,整个项目就不是单纯怀旧,而是一次挺完整的“旧系统搬家”。
Recently I came across a project called Dragonfruit. What it does is quite interesting: it's not making a Palm OS skin, nor is it just slapping a few screenshots of the Palm interface onto an e-ink screen. Instead, it actually emulates a 68k Palm on an ESP32 device. More precisely, it emulates the Motorola MC68EZ328, which is the DragonBall EZ chip found in devices like the Palm IIIx from back in the day. Just hearing that name gives you a strong sense of retro nostalgia.
GitHub link:
https://github.com/megabytefisher/Dragonfruit
On the left is a real Palm IIIxe, and on the right is an M5Paper. The Launcher running on that white e-ink device on the right is not an image — it's the actual booted Palm OS 3.x interface.
Projects like this are most at risk of only achieving "looking alike." Icons look alike, fonts look alike, the shell looks alike, and in the end, it's just a nostalgia theme. Dragonfruit is not that kind of approach; it's more like reshaping the hardware behavior of a Palm, and then letting the original Palm OS ROM run on its own.

Simply put: the ESP32 handles running the emulator, the PSRAM holds the Palm's RAM and ROM images, the e-ink screen displays the original 160x160 black-and-white Palm display, and the touchscreen turns finger/stylus positions into pen events the Palm can understand.
A few key components in this project are particularly important.
The first is the ESP32-D0WDQ6-V3. The one on the M5Paper is a dual-core 240MHz chip. A pure interpreter can run, but the speed isn't comfortable enough, so the device side also implements burst JIT, translating hot 68000 ROM code into Xtensa native code. The JIT compiler runs on the second core — this isn't just some random ESP32 lighting up a screen.
The second is 8MB PSRAM. The simulated RAM for the Palm IIIx is 2MB, and the ROM image also needs to go in there. The README says it outright: external PSRAM is mandatory. Chips like the ESP32-C3, which are single-core and have no PSRAM, are out of the question.
The third is the IT8951 e-ink controller. The M5Paper has a 960x540 electronic paper display, whereas the Palm originally had a 160x160, 1-bit framebuffer. Dragonfruit has to scale up and rotate the Palm's small black-and-white image, then overlay the Graffiti silkscreen area at the bottom. E-ink refreshes slowly, so the display can't be treated like an ordinary LCD and refreshed casually.

The fourth is the GT911 capacitive touch controller. The Palm originally used a resistive screen and stylus, while the M5Paper uses a capacitive screen.
The fifth is the SD card. The Palm OS ROM is not distributed with the project because of copyright. You have to dump the ROM from a Palm device you own, put it on the root of a FAT32 SD card, and name it palm.rom. At boot, the firmware reads it into PSRAM. The SD card can also hold PRC/PDB/PQA files for the system to install at startup, as well as a backup directory for exporting Palm databases.
The image above is even more interesting. The Graffiti handwriting practice is already running on the M5Paper. As you can see, it's not just limited to the Launcher — the touch input, the handwriting area, and the button areas are all already synced up with Palm OS.
Many emulator projects give you the most exciting moment at system boot, and then nothing after that. Dragonfruit, by contrast, puts its effort into all the small details: the first-boot setup wizard, touch calibration, country/time/date settings, Graffiti input, the silkscreen buttons for Apps/Menu/Calc/Find, sleep and auto power-off, and database installation and backup.
The reason I find this project fun in a retro way is not because Palm OS is all that advanced. Looking at Palm now, that whole system is certainly very old — the 160x160 black-and-white screen, Graffiti handwriting, Date Book, Memo Pad, all relics of a bygone era. But when it's placed on an M5Paper, it suddenly looks good again. E-ink is inherently slow, and Palm OS never pursued flashy animations to begin with; Palm's black-and-white UI pairs with electronic paper in a way that actually suits it better than many modern systems. Add in the embedded details — ESP32, PSRAM, JIT, touch mapping, SD card — and the whole project stops being mere nostalgia and becomes a fairly complete "legacy system relocation."