c1570

m6569: c accesses half a cycle too late?

2

According to vic-ii.txt, the first c access in badlines happens in the second half of cycle 15, and the following cycles have gi accesses first, then c accesses. In m6569.h,...

PIO timing improvements and dual MCU demo

3

This makes the PIOs run in sync with the ARM cores and enables ClockDiv. This also adds a new demo program that runs two rp2040js instances with the two RP2040s...

UART write never blocks and doesn't actually write to GPIO pins

1

Writing to the UART never blocks at the moment: https://github.com/wokwi/rp2040js/blob/61e1d2cc9953eb049f7c45f8f0d3acc39c4c55e1/src/peripherals/uart.ts#L76 This also means that printf() using pico_stdio_uart is way faster in emulation than in reality quite often (basically whenever the...

apparently broken since 58cc97e

VIC-II/m6569 emulation issues (and fixes)

2

While working on https://github.com/c1570/Connomore64 I found some VIC-II emulation issues in chips. On the real VIC-II... - writing to D011/D012 can trigger a raster IRQ immediately (if no raster IRQ...

RP2350 support

7

Just as a pointer for anyone interested: https://github.com/c1570/rp2040js features some RP2350 support (RISC-V only).

People are trying to use this on a T48 programmer, which works, but orientation of the adapter is a caveat. E.g., see people [using it in the **wrong** orientation](https://www.forum64.de/index.php?thread/153046-xgecu-t48-eprom-programmierer-geeignet-f%C3%BCr-amiga-und-oder-c128dcr/&postID=2265731#post2265731). Perhaps...

Support more universal pinouts / 30 GPIOs

2

How about getting rid of the two UART pins (no need to waste those as they are only necessary for debugging)? Also, there are RP2040 boards that expose all GPIOs...