Graham Sanderson

Running these games currently experience the following problems below. None of the problems are particularly insurmountable, and I have a branch that hacks past them to make the games runnable;...

When we reboot into RAM we indicate this via ``` watchdog_hw->scratch[4] = 0xb007c0d3; watchdog_hw->scratch[5] = pc ^ -0xb007c0d3; watchdog_hw->scratch[6] = sp; watchdog_hw->scratch[7] = pc; ``` however on rebooting into flash...

Add dual mode examples when TinyUSB is updated

1

``` set(TINYUSB_FAMILY_PROJECT_NAME_PREFIX "tinyusb_dual_") add_subdirectory(${PICO_TINYUSB_PATH}/examples/dual tinyusb_dual_examples) ```

Don't know why this was never implemented. https://github.com/raspberrypi/pico-extras/blob/ccd88d320f6d759d102cf65a1345d06f1d730f32/src/rp2_common/lwip/lwip_arch.c#L12

This would set a bunch of build defines as an example of removing a bunch of runtime support you don't necessarily want when you are looking for every last ounce...

Make sure stack is 8 byte aligned in shared IRQ handlers

1

ARMv6m stack is supposed to be 8 byte aligned, but very few things (other than 64 bit vaargs care which is why this has gone unnoticed for so long).

Issue with reset interface with new stdio over use TinyUSB support

1

https://forums.raspberrypi.com/viewtopic.php?t=334842

filesystem support

4

maybe add some minimal stubs for common libraries like littlefs (i.e. make them trivial to use if the littlefs code is present)