All the examples work and the basis is solid connections, do spare time to make them (it takes many hours, but without it nothing will work).

Of course, you can use the factory ones, but do not separate the wires from the band, just group them according to purpose.

If you think that you will get it on a test board, you are wrong, such connections may work by accident, but any interference will destroy it irretrievably. The connections should be made straight from A to B with the wires in the protective sleeves, as in the factory, and then it will work.

Touch Screen Desktop for Raspberry pi pico.

(no overclocked examples)

• https://www.youtube.com/watch?v=2_8hvvxUR1c
• https://youtu.be/4ENcbCUJWro canvas1 overlaid 320x240 PIO SPI 64K
• https://youtu.be/IN8qoKfxF0M canvas1 overlaid 320x240 PIO SPI 256K
• https://youtu.be/PHK2owDnlNk canvas3 buffered 320x240 PIO SPI 64K
• https://youtu.be/49iehFhhrsU canvas3 buffered 320x240 PIO SPI 256K
• https://youtu.be/Pa9H-aLCpmY canvas3 buffered 480x320 PIO 8BITP 64K
• https://youtu.be/E2C1jvAtG-U canvas3 buffered 480x320 PIO 8BITP 256K
• https://youtu.be/UUobwTMtHng canvas3 buffered 480x320 GPIO 8BITP 64K
• https://youtu.be/-yLM6ibkhxQ canvas1 overlaid 480x320 GPIO 8BITP 64K
• https://youtu.be/gJZjT5y9lvY resistive touch 480x320 GPIO 8BITP

• Resistive touch was misinterpreted

• Touch over PIO SPI

• More sensitive touch for Arduino SPI (taken from pico-sdk)

• Touch rotation has been finally mastered. One of the touch_??? procedure from Touch.hh is responsible for touch rotation. If none of the available procedures work properly, we have two options:

  1. if one of the procedures could be suitable but has the same deviation in all 4 cases, we can correct it using the TOUCH_REV parameter.
  2. Define another routine for touch rotation.

• Resistive touch for RP2040 GPIO 8BITP, ATTENTION: pinout changed

• Chunks in PIO

• A new protocol: RP2040 GPIO 8BITP write/read (enable LCD_RD pin)

• RP2040 PIO SPI RAED finally works with RP2040 PIO SPI WRITE protocol

• RP2040 PIO 8BITP Write protocol, developed for buffered writing and speed now

• Writing by PIO and reading by SPI work now together in Arduino only, the touch needs to be commented out

• User setups in setup folder

• Buffered canvas - see canvas3 example

• New repository https://github.com/rspber/TSD_Fonts

• New repository https://github.com/rspber/TFT_eSPI_light

• TFT write/read and touch protocols were separated from each other and from gfx

• A new RP2040 PIO SPI WRITE protocol

• Available TFT drivers:

  • GC9A01
  • HX8357
  • ILI9341
  • ILI9481
  • ILI9486
  • ILI9488
  • R61581
  • RM68140
  • SSD1963
  • ST7789
  • ST7796

• Overlaid objects

  GFXButton's objects can 'flow' over others thanks to setOverlaid property. The method is to remember the background when drawing the object 'draw' and recreate it when hiding the object 'hide'. See examples canvas1 and canvas2. It is an uresolved problem when several overlaid objects overlap.

• TSDesktop

  • easy way to place objects on the screen: all examples
  • integrated touch screen: almost all examples
  • scroller: see examples: scroll1, menu1, menu2, menu3

• TFT Stack (TSD_GFX -> TSD_SCREEN -> TFT_SCREEN(TFT_API) -> TFT_Protocol -> TFT_DRIVER -> Display) to easy implement protocols and drivers for tft

• Modified gamma for ILI9341 to reflect better color vibrancy.

• 565/666 color support

• Gradient with percentage

  • see examples: canvas1, menu3, checkboxes

• Flexible font format

  • visit https://github.com/rspber/TSD_Fonts repository

• UTF-8/Unicode Support

  Although utf-8/unicode fonts are not included, see https://github.com/rspber/TSD_Fonts for more details.

  When the correct font with UTF-8 encoding is included in the code, use the following scheme to deliver utf-8 text:

    display.drawText(x, y, "\xc4\x85\xc4\xb2", FontName);
  

  or

    textBtn.setStaticText("\xc4\x85\xc4\xb2");
  

  and for unicode:

    const uint16_t buf[] { 0x4E00, 0x3007, 0 };
    display.drawText(x, y, buf, FontName);
  

  or

    textBtn.setStaticText(buf);
  

  remember to end the construction with a 0.

• Thickness parameter for lines, rectangles, triangles and circles

1. No other libraries are required,

2. Install CMake (at least version 3.13), and GCC cross compiler

• Fedora

  sudo dnf install cmake gcc-c++ arm-none-eabi-gcc-cs-c++ arm-none-eabi-newlib
  

• Ubuntu

  sudo apt install cmake g++ gcc-arm-none-eabi libnewlib-arm-none-eabi libstdc++-arm-none-eabi-newlib
  

3. Install pico-sdk:

• download or git clone https://github.com/raspberrypi/pico-sdk.git

• Set PICO_SDK_PATH to the SDK location in your environment

4. download or git clone this repository

5. Resolve links

6. Install VS Code

7. In VS Code:

• Install extensions: C/C++ Extension Pack, CMake Tools

• File / Open Folder ... select location to /tsdesktop/pico-sdk

• In the bottom panel:

  • CMake : [Scan for kits], select: GCC X.X.X arm-none-eabi, Release

  • Build

8. Use bootselBoot tool to upload *.uf2 examples

1. Tested on Arduino 1.8.19, Arduino 1.8.5 should works too,

2. In Arduino:

• File / Preferences / Settings

  Additional boards manager URLs: https://github.com/earlephilhower/arduino-pico/releases/download/global/package_rp2040_index.json

  • Hit OK to close the dialog.

• Tools / Board / Boards Manager ...

  • Type "pico" in the search box, you should see: Raspberry Pi Pico/RP2040, and select "Install"

• Tools / Board / Raspberry Pi RP2040 Boards / select your board

• If after upgrading system to new version of eabi e.g. to 10.x.x, Invalid -march:armv6-m error occures, it's time to upgrade this library too.

3. download or git clone this repository

4. Resolve links to tsdesktop directories in Arduino/libraries

5. No other libraries are required

6. Copy Arduino/examples to Arduino's Sketchbook directory

7. For linux users:

• In Arduino:

  • Tools / Port / /dev/ttyACM0

• In console:

  • for one-time access:

    sudo chmod a+rw /dev/ttyACM0
  

  • for permanent access:

    sudo usermod -aG dialout $USER
    sudo reboot
  

8. If you want to use SerialUSB in/for tft pio debugging you must comment #include "Arduino.h" in packages/rp2040/hardware/rp2040/2.7.1/cores/rp2040/SerialUSB.h, similarly with SerialUART.h and SerialUART.cpp where you need to add #include "api/Common.h", "hardware/gpio.h", "pins_arduino.h" and copy/paste __bitset from Arduino.h wherever it appears instead.

1. If incidental touch pressed or not calibrated touch illusion occures, try reduce touch speed first

2. If not all colors are displayed, try reduce tft speed first