You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pico9918 is fantastic, and I've been using a modified version of it in a couple of different projects. Namely, CoPicoVision, a ColecoVision clone that uses a Pi Pico module for the display, and a small BASIC computer running my own BASIC interpreter natively on a Pi Pico, which uses the 9918 emulation and VGA engine from pico9918 for it's native text/graphics display/terminal emulator (in this case, the "bus interface" is not using PIO, but rather a native interface using shared memory buffers and the multicore FIFO to communicate from the BASIC side to the display side).
In order to facilitate the hardware differences from the base pico9918 module, I've added some hooks to the pico9918 build system to make it easier to make the necessary configuration tweaks without having to modify pico9918 directly. The config parameters are placed into a CMake file:
that parameterizes:
- board type
- product name
- disabling clock outputs
- interrupt polarity
- RGB signal / color pin origins
...and consult the config file for these parameters that already existed:
- scanlines yes/no
- SCART yes/no/mode
Addresses issue visrealm#28.
pico9918 is fantastic, and I've been using a modified version of it in a couple of different projects. Namely, CoPicoVision, a ColecoVision clone that uses a Pi Pico module for the display, and a small BASIC computer running my own BASIC interpreter natively on a Pi Pico, which uses the 9918 emulation and VGA engine from pico9918 for it's native text/graphics display/terminal emulator (in this case, the "bus interface" is not using PIO, but rather a native interface using shared memory buffers and the multicore FIFO to communicate from the BASIC side to the display side).
In order to facilitate the hardware differences from the base pico9918 module, I've added some hooks to the pico9918 build system to make it easier to make the necessary configuration tweaks without having to modify pico9918 directly. The config parameters are placed into a CMake file:
...and this config file is used like so:
The text was updated successfully, but these errors were encountered: