picodvi VS pico-sdk

The RP2040 is a great MCU for playing with graphics as it can bit bang VGA and DVI/HDMI. There's some info on the DVI here: https://github.com/Wren6991/PicoDVI

I wrote a couple of articles on how to do bit banged VGA on the RP2040 from scratch: https://gregchadwick.co.uk/blog/playing-with-the-pico-pt5/ and https://gregchadwick.co.uk/blog/playing-with-the-pico-pt6/ plus an intro to PIO https://gregchadwick.co.uk/blog/playing-with-the-pico-pt4/

A few years back someone was bit banging DVI and 720p 30fps video straight off the RP2040 GPIO pins with just inline resistors between not and the HDMI cable.

https://github.com/Wren6991/PicoDVI

I have the Adafruit DVI board and have been hacking on it some. It's more fun than should be allowed.

There's a project to get this running using Rust[1]. Currently it outputs the blue channel with sync, but has trouble with the other two channels. I don't have a hardware lab with scope, logic analyzer, etc., so it's not easy for me to debug.

In the meantime, I've been doing some experiments in the C codebase as well[2], mostly in the direction of proportionally spaced bitmap text, using the fonts in the X11 distribution.

[1]: https://github.com/DusterTheFirst/pico-dvi-rs

[2]: https://github.com/Wren6991/PicoDVI/pull/48

There is even bit-banged DVI library for pico.

Apparently, there is a digital video output project for the RP2040 already out there [0]! As for why digital video is more rare, it is because the common digital video formats are higher bandwidth and require higher signal integrity.

[0] https://github.com/Wren6991/PicoDVI

I've seen people implement DVI with PIO, and I'm sure basic missile commands wouldn't be as bandwidth-intensive as that.

For example this guy (https://github.com/Wren6991/PicoDVI) essentially 'bit bangs' CML. Sure its not a completely compliant implementation, but it's pretty close... In his case using a push pull with 3.3V/0V. I don't know how he's getting a 0.8V swing.

In the Pico SDK repository, find the external/pico_sdk_import.cmake file

https://github.com/raspberrypi/pico-sdk/ links to a PDF about connecting to the interwebs with a pi pico.

micropython/micropython//ports/rp2/boards/RPI_PICO_W: https://github.com/micropython/micropython/tree/master/ports...

raspberrypi/pico-sdk /lib: btstack, cyw43-driver, lwip, mbedtls, tinyusb https://github.com/raspberrypi/pico-sdk/tree/master/lib

raspberrypi/pico-examples//pico_w/wifi/access_point/picow_access_point.c:

https://github.com/raspberrypi/pico-examples/blob/master/pic...

There's an iperf opkg pkg, or is it just netperf (which works with fluent)?

raspberrypi/pico-examples//pico_w/wifi/iperf/picow_iperf.c:

Relevant link: https://github.com/raspberrypi/pico-sdk/issues/979

There is an official sdk in C and C++ as well as a really thorough sdk guide, and a separate "getting started" guide which shows you how to upload files using command line and vs code.

Arch is using Gcc 13.0.1 and there's a bug fix that I had to manually apply so that uint16_t could be resolve. See https://github.com/raspberrypi/pico-sdk/pull/1318/files.

the LED of the W is hooked to the wireless chip. in the c sdk, the function to tell the chip to set it's gpio pin(s) is: cyw43_arch_gpio_put(CYW43_WL_GPIO_LED_PIN, 1); where CYW43_WL_GPIO_LED_PIN is the macro to the LED. (https://github.com/raspberrypi/pico-sdk/blob/master/src/rp2_common/pico_cyw43_arch/include/pico/cyw43_arch.h line 468)

The latest release of the Pico Software Developer Kit (SDK) version 1.5.0 is a significant milestone in that evolution. This new version includes many exciting features, the most notable of which is Bluetooth support. Read More - https://bit.ly/3Yyb0qi