c1570
commented
1 year ago dual_display is broken, see https://github.com/Wren6991/PicoDVI/pull/41 Moon is 1bpp so b/w is okay.
Red lines indicate the RP2040 lagging behind: https://github.com/Wren6991/PicoDVI/blob/51237271437e9d1eb62c97e40171fbf6ffe01ac6/software/libdvi/dvi.c#L210
Did you run cmake using -DPICO_COPY_TO_RAM=1 as indicated in the README?
Hello, everyone!
So I was planning to make a pull request adding support (a pinout description in the "common_dvi_pin_configs.h") for one of our boards - RP2040-PICO-PC (https://www.olimex.com/Products/MicroPython/RP2040-PICO-PC/).
But when tested with the provided examples from this repository it worked well with about half of them. Here is list of the behavior: Working fine: dht_logging, hello_dvi, mandelbrot, terminal, tiles, tiles_parallax Semi-working: colour_terminal (colors seem weird), moon (picture is visible but only black and white) Not working: bad_apple, christmas_snowflakes, dual_display (understandable since I tested with only 1 display), mandel-full, sprite_bounce, tiles_and_sprites, vista on all of these I see red screen and sometimes blinking lines somewhere on the screen Vista-Palette - not working at all - it gives me a message "Input signal out of range".
So I was wondering what could cause some of the examples to work fine, some of the others partially and the rest not working at all? I don't think it's pinout related since then none of the examples would have worked at all and thus I was thinking of making pull request but I decided to ask for this first. RP2040-PICO-PC_rev_C.pdf