or maybe something is missing from flash:
The RP2040 version has four targets, each of which create a similarly named UF2 file (e.g. doom_tiny.uf2). These UF2 files contain the executable code/data, but they do not contain the WAD data which is converted into a RP2040 Domom specific WHD/WHX format by whd_gen (for more see below). The WHD/WHX file must also be loaded onto the device at a specific address which varies by binary.
"super-tiny" refers to RP2040 Doom builds that use the more compressed WHX format, and required forDOOM1. WAD to run on a 2M Raspberry Pi Pico. "Non super-tiny" refers to RP2040 Doom builds that use the WHD format which is larger, but also is required for Ultimate Doom and Doom II WADs. These binaries are distinct as supporting both formats in the same binary would just have made things bigger and slower.
doom_tiny This is a "super tiny" version with no USB keyboard support. You can use SDL Event Forwarder to tunnel keyboard input from your host computer over UART. The WHX file must be loaded at 0x10040000.
doom_tiny_usb This is a "super tiny" version with additional USB keyboard support. Because of the extra USB code, the WHX file must be loaded at 0x10042000. As you can see USB support via TinyUSB causes the binary to grow by 2K (hence the move of the WHX file address) leaving less space for saved games (which are also stored in flash).
doom_tiny_nost This is a "non super tiny" version of doom_tiny supporting larger WADs stored as WHD. The WHD file must be loaded at 0x10048000
doom_tiny_nost_usb This is a "non super tiny" version of doom_tiny_usb supporting larger WADs stored as WHD. The WHD file must be loaded at 0x10048000
You can load you WHD/WHX file using picotool. e.g.
picotool load -v -t bin doom1.whx -o 0x10042000.
Statistics: Posted by gmx — Wed Nov 13, 2024 11:40 am