About Screen Selection #24

HalfSweet · 2023-03-13T10:42:17Z

HalfSweet
Mar 13, 2023

My screen is RGB666 and has a 3 line SPI initialization, can I also take the screen R[5:3],G[5:3],B[5:4] for connection.
But one more question, my screen needs an SPI initialization, where should I add it?

bwhitman · 2023-03-13T10:47:34Z

bwhitman
Mar 13, 2023
Maintainer

What screen is it? That may help understand how to get it working with Tulip.

If it needs SPI for setup but then hands off display to the RGB dot clock driver, add the setup in esp32s3_display.c's run_esp32s3_display.

If it's using SPI for display itself, there's a lot more work to do. Tulip is meant for a particular type of RGB TTL display, which allows it to have larger screen sizes at fast FPS.

4 replies

HalfSweet Mar 13, 2023
Author

No, it works under RGB, but it needs to give an initialization of SPI before the screen does send RGB signal, so I just add an initialization code that uses software emulation, thanks for your help.
As well as the format of the screen is RGB666, I thought maybe I could just take the high bits as well, not sure exactly how that would work.
Here is the link to buy the screen, maybe you can refer to it to come up with some valid information: https://item.taobao.com/item.htm?spm=a230r.1.14.16.641266eaIX2T38&id=582079489573&ns=1&abbucket=6#detail
I tried to rebuild a PCB for such a job, hopefully it works fine, thanks for your help

HalfSweet Mar 13, 2023
Author

Also, I saw that the esp idf's rgb lcd component supports the use of 8bit settings, and I thought maybe we could just set the unneeded pins to -1 to avoid taking up an extra IO

bwhitman Mar 13, 2023
Maintainer

That's neat. I can't see the display, it shows me a login page. But this sounds like it'll work.
We use RGB332 to also save CPU and memory, so 8-bit per channel color may be hard to get going.
I did get RGB565 to work on an earlier revision but could not get the FPS or RAM I needed for other things.

HalfSweet Mar 13, 2023
Author

No, I meant setting PIN_NUM_DATA8-15 to -1, which seems to work, so that we get a usable IO again, perhaps more convenient for expanding other applications.
Also you can refer to this link, which does not require login: https://item.taobao.com/item.htm?ut_sk=1.YpSfP3N9/ZUDANvJe6s7vfTd_21380790_1678706221322.Copy.1&id=582079489573&sourceType=item&price=102&suid=30470AFF-EC85-4E50-866F-1A2EB29A0F6E&shareUniqueId=20475927987&un=3385abe1161da1fc4501602a0955eade&share_crt_v=1&un_site=0&spm=a2159r.13376460.0.0&sp_abtk=gray_1_code_simpleios2&tbSocialPopKey=shareItem&sp_tk=RGo1WWQ4dUNXaTg%3D&cpp=1&shareurl=true&short_name=h.UJ7fJSy&bxsign=scdMVL3CamnTTaApxXHidFja44hkXVTTlaPGazIQ04DbJlcblk-z9ejVWVMcJ9aGvUERIv5uzSEPRYJUScIXUd2E81cBJBXm7ljBCAHcuIhiTNO4RNVhhfra_AgDjku7I23zX00SVEDo1uOiee9nQq27A&tk=Dj5Yd8uCWi8%20CZ3457&app=macos_safari

bwhitman · 2023-03-13T19:16:48Z

bwhitman
Mar 13, 2023
Maintainer

Oh yeah. I see. Yes, I am using it like this

#define PIN_NUM_DATA8          13 // B2
#define PIN_NUM_DATA9          13 // B1
#define PIN_NUM_DATA10         13 // B0
#define PIN_NUM_DATA11         13 // G2
#define PIN_NUM_DATA12         13 // G1
#define PIN_NUM_DATA13         13 // G0
#define PIN_NUM_DATA14         13 // R1
#define PIN_NUM_DATA15         13 // R0

In the code. we have maybe 7 or 8 free GPIO leftover I think. I want to use 3 for a joystick port.

1 reply

HalfSweet Apr 1, 2023
Author

Sorry ...... but I think I'm running into some problems that might need your help.
In my code I used IO45 48 and 38 to simulate the 9-bit SPI needed for the screen, and ported the approach from the https://github.com/moononournation/Arduino_GFX whole project.
This is the code I added to esp32s3_display.h

typedef enum
{
  BEGIN_WRITE,
  WRITE_COMMAND_8,
  WRITE_COMMAND_16,
  WRITE_DATA_8,
  WRITE_DATA_16,
  WRITE_BYTES,
  WRITE_C8_D8,
  WRITE_C8_D16,
  WRITE_C16_D16,
  END_WRITE,
  DELAY,
} spi_operation_type_t;

union
{
  uint16_t value;
  struct
  {
    uint8_t lsb;
    uint8_t msb;
  };
} _data16;



#define SPI_LL_DATA_MAX_BIT_LEN (1 << 18)

#define PAN_SPI_SDA 48
#define PAN_SPI_SCL 45
#define PAN_SPI_CS 38

void pan_spi_init();
void pan_spi_deinit();
void pan_spi_write(uint8_t data);
void pan_spi_write_command(uint8_t data);
void pan_spi_write_data(uint8_t data);
void pan_init();
void batchOperation(const uint8_t *operations, size_t len);

static const uint8_t st7701_type1_init_operations[] = {
    BEGIN_WRITE,
    WRITE_COMMAND_8, 0xFF,
    WRITE_BYTES, 5, 0x77, 0x01, 0x00, 0x00, 0x10,

    WRITE_C8_D16, 0xC0, 0x3B, 0x00,
    WRITE_C8_D16, 0xC1, 0x0D, 0x02,
    WRITE_C8_D16, 0xC2, 0x31, 0x05,
    WRITE_C8_D8, 0xCD, 0x08,

    WRITE_COMMAND_8, 0xB0, // Positive Voltage Gamma Control
    WRITE_BYTES, 16,
    0x00, 0x11, 0x18, 0x0E,
    0x11, 0x06, 0x07, 0x08,
    0x07, 0x22, 0x04, 0x12,
    0x0F, 0xAA, 0x31, 0x18,

    WRITE_COMMAND_8, 0xB1, // Negative Voltage Gamma Control
    WRITE_BYTES, 16,
    0x00, 0x11, 0x19, 0x0E,
    0x12, 0x07, 0x08, 0x08,
    0x08, 0x22, 0x04, 0x11,
    0x11, 0xA9, 0x32, 0x18,

    // PAGE1
    WRITE_COMMAND_8, 0xFF,
    WRITE_BYTES, 5, 0x77, 0x01, 0x00, 0x00, 0x11,

    WRITE_C8_D8, 0xB0, 0x60, // Vop=4.7375v
    WRITE_C8_D8, 0xB1, 0x32, // VCOM=32
    WRITE_C8_D8, 0xB2, 0x07, // VGH=15v
    WRITE_C8_D8, 0xB3, 0x80,
    WRITE_C8_D8, 0xB5, 0x49, // VGL=-10.17v
    WRITE_C8_D8, 0xB7, 0x85,
    WRITE_C8_D8, 0xB8, 0x21, // AVDD=6.6 & AVCL=-4.6
    WRITE_C8_D8, 0xC1, 0x78,
    WRITE_C8_D8, 0xC2, 0x78,

    WRITE_COMMAND_8, 0xE0,
    WRITE_BYTES, 3, 0x00, 0x1B, 0x02,

    WRITE_COMMAND_8, 0xE1,
    WRITE_BYTES, 11,
    0x08, 0xA0, 0x00, 0x00,
    0x07, 0xA0, 0x00, 0x00,
    0x00, 0x44, 0x44,

    WRITE_COMMAND_8, 0xE2,
    WRITE_BYTES, 12,
    0x11, 0x11, 0x44, 0x44,
    0xED, 0xA0, 0x00, 0x00,
    0xEC, 0xA0, 0x00, 0x00,

    WRITE_COMMAND_8, 0xE3,
    WRITE_BYTES, 4, 0x00, 0x00, 0x11, 0x11,

    WRITE_C8_D16, 0xE4, 0x44, 0x44,

    WRITE_COMMAND_8, 0xE5,
    WRITE_BYTES, 16,
    0x0A, 0xE9, 0xD8, 0xA0,
    0x0C, 0xEB, 0xD8, 0xA0,
    0x0E, 0xED, 0xD8, 0xA0,
    0x10, 0xEF, 0xD8, 0xA0,

    WRITE_COMMAND_8, 0xE6,
    WRITE_BYTES, 4, 0x00, 0x00, 0x11, 0x11,

    WRITE_C8_D16, 0xE7, 0x44, 0x44,

    WRITE_COMMAND_8, 0xE8,
    WRITE_BYTES, 16,
    0x09, 0xE8, 0xD8, 0xA0,
    0x0B, 0xEA, 0xD8, 0xA0,
    0x0D, 0xEC, 0xD8, 0xA0,
    0x0F, 0xEE, 0xD8, 0xA0,

    WRITE_COMMAND_8, 0xEB,
    WRITE_BYTES, 7,
    0x02, 0x00, 0xE4, 0xE4,
    0x88, 0x00, 0x40,

    WRITE_C8_D16, 0xEC, 0x3C, 0x00,

    WRITE_COMMAND_8, 0xED,
    WRITE_BYTES, 16,
    0xAB, 0x89, 0x76, 0x54,
    0x02, 0xFF, 0xFF, 0xFF,
    0xFF, 0xFF, 0xFF, 0x20,
    0x45, 0x67, 0x98, 0xBA,

    //-----------VAP & VAN---------------
    WRITE_COMMAND_8, 0xFF,
    WRITE_BYTES, 5, 0x77, 0x01, 0x00, 0x00, 0x13,

    WRITE_C8_D8, 0xE5, 0xE4,

    WRITE_COMMAND_8, 0xFF,
    WRITE_BYTES, 5, 0x77, 0x01, 0x00, 0x00, 0x00,

    WRITE_COMMAND_8, 0x21,   // 0x20 normal, 0x21 IPS
    WRITE_C8_D8, 0x3A, 0x60, // 0x70 RGB888, 0x60 RGB666, 0x50 RGB565

    WRITE_COMMAND_8, 0x11, // Sleep Out
    END_WRITE,

    DELAY, 120,

    BEGIN_WRITE,
    WRITE_COMMAND_8, 0x29, // Display On
    END_WRITE};

This is the code I added to esp32s3_display.h

void pan_spi_init()
{
    gpio_set_direction(PAN_SPI_CS, GPIO_MODE_OUTPUT);
    gpio_set_direction(PAN_SPI_SDA, GPIO_MODE_OUTPUT);
    gpio_set_direction(PAN_SPI_SCL, GPIO_MODE_OUTPUT);

    gpio_set_level(PAN_SPI_CS, 1);
}
void pan_spi_deinit()
{
    // gpio_reset_pin(PAN_SPI_SDA);
    // // gpio_reset_pin(PAN_SPI_SCL);
    // gpio_set_level(PAN_SPI_SCL, 0);
    // gpio_reset_pin(PAN_SPI_CS);
}
void pan_spi_write_command(uint8_t data)
{
    gpio_set_level(PAN_SPI_CS, 0);
    gpio_set_level(PAN_SPI_SDA, 0); // 命令
    gpio_set_level(PAN_SPI_SCL, 0);
    ets_delay_us(5);
    gpio_set_level(PAN_SPI_SCL, 1);
    ets_delay_us(5);

    for (int i = 0; i < 8; i++)
    {
        if (data & 0x80)
            gpio_set_level(PAN_SPI_SDA, 1);
        else
            gpio_set_level(PAN_SPI_SDA, 0);
        data <<= 1;
        gpio_set_level(PAN_SPI_SCL, 0);
        ets_delay_us(5);
        gpio_set_level(PAN_SPI_SCL, 1);
        ets_delay_us(5);
    }
    gpio_set_level(PAN_SPI_CS, 1);
}
void pan_spi_write_data(uint8_t data)
{
    gpio_set_level(PAN_SPI_CS, 0);
    gpio_set_level(PAN_SPI_SDA, 1); // 数据
    gpio_set_level(PAN_SPI_SCL, 0);
    ets_delay_us(5);
    gpio_set_level(PAN_SPI_SCL, 1);
    ets_delay_us(5);

    for (int i = 0; i < 8; i++)
    {
        if (data & 0x80)
            gpio_set_level(PAN_SPI_SDA, 1);
        else
            gpio_set_level(PAN_SPI_SDA, 0);
        data <<= 1;
        gpio_set_level(PAN_SPI_SCL, 0);
        ets_delay_us(5);
        gpio_set_level(PAN_SPI_SCL, 1);
        ets_delay_us(5);
    }
    gpio_set_level(PAN_SPI_CS, 1);
}

void pan_init()
{
    printf("pan_init \n");
    pan_spi_init();
    batchOperation(st7701_type1_init_operations, sizeof(st7701_type1_init_operations));
    pan_spi_deinit();

    printf("init done \n");
}

void CS_LOW()
{
    gpio_set_level(PAN_SPI_CS, 0);
}

void CS_HIGH()
{
    gpio_set_level(PAN_SPI_CS, 1);
}

void beginWrite()
{
    CS_LOW();
}

void endWrite()
{
    CS_HIGH();
}

void SPI_MOSI_LOW()
{
    gpio_set_level(PAN_SPI_SDA, 0);
}

void SPI_MOSI_HIGH()
{
    gpio_set_level(PAN_SPI_SDA, 1);
}

void SPI_SCK_LOW()
{
    gpio_set_level(PAN_SPI_SCL, 0);
}

void SPI_SCK_HIGH()
{
    gpio_set_level(PAN_SPI_SCL, 1);
}

inline void WRITE9BITDATA(uint8_t d)
{
    // D/C bit, data
    SPI_MOSI_HIGH();
    SPI_SCK_HIGH();
    SPI_SCK_LOW();

    uint8_t bit = 0x80;
    while (bit)
    {
        if (d & bit)
        {
            SPI_MOSI_HIGH();
        }
        else
        {
            SPI_MOSI_LOW();
        }
        SPI_SCK_HIGH();
        bit >>= 1;
        SPI_SCK_LOW();
    }
}

inline void WRITE9BITCOMMAND(uint8_t c)
{
    // D/C bit, command
    SPI_MOSI_LOW();
    SPI_SCK_HIGH();
    SPI_SCK_LOW();

    uint8_t bit = 0x80;
    while (bit)
    {
        if (c & bit)
        {
            SPI_MOSI_HIGH();
        }
        else
        {
            SPI_MOSI_LOW();
        }
        SPI_SCK_HIGH();
        bit >>= 1;
        SPI_SCK_LOW();
    }
}

void writeCommand(uint8_t c)
{
    WRITE9BITCOMMAND(c);
}

void writeCommand16(uint16_t c)
{

    _data16.value = c;
    WRITE9BITCOMMAND(_data16.msb);
    WRITE9BITCOMMAND(_data16.lsb);
}

void __write(uint8_t d)
{

    WRITE9BITDATA(d);
}

void write16(uint16_t d)
{

    _data16.value = d;
    WRITE9BITDATA(_data16.msb);
    WRITE9BITDATA(_data16.lsb);
}

inline void WRITE(uint8_t d)
{
    uint8_t bit = 0x80;
    while (bit)
    {
        if (d & bit)
        {
            SPI_MOSI_HIGH();
        }
        else
        {
            SPI_MOSI_LOW();
        }
        SPI_SCK_HIGH();
        bit >>= 1;
        SPI_SCK_LOW();
    }
}

inline void WRITE16(uint16_t d)
{
    uint16_t bit = 0x8000;
    while (bit)
    {
        if (d & bit)
        {
            SPI_MOSI_HIGH();
        }
        else
        {
            SPI_MOSI_LOW();
        }
        SPI_SCK_HIGH();
        bit >>= 1;
        SPI_SCK_LOW();
    }
}

inline void WRITE9BITREPEAT(uint16_t p, uint32_t len)
{
    if (p == 0xffff) // no need to set MOSI level while filling white
    {
        SPI_MOSI_HIGH();
        len *= 18; // 9-bit * 2
        while (len--)
        {
            SPI_SCK_HIGH();
            SPI_SCK_LOW();
        }
    }
    else
    {
        _data16.value = p;
        while (len--)
        {
            WRITE9BITDATA(_data16.msb);
            WRITE9BITDATA(_data16.lsb);
        }
    }
}

inline void WRITEREPEAT(uint16_t p, uint32_t len)
{
    if ((p == 0x0000) || (p == 0xffff)) // no need to set MOSI level while filling black or white
    {
        if (p)
        {
            SPI_MOSI_HIGH();
        }
        else
        {
            SPI_MOSI_LOW();
        }
        len *= 16;
        while (len--)
        {
            SPI_SCK_HIGH();
            SPI_SCK_LOW();
        }
    }
    else
    {
        while (len--)
        {
            WRITE16(p);
        }
    }
}

void batchOperation(const uint8_t *operations, size_t len)
{
    for (size_t i = 0; i < len; ++i)
    {
        uint8_t l = 0;
        switch (operations[i])
        {
        case BEGIN_WRITE:
            beginWrite();
            break;
        case WRITE_C8_D16:
            l++;
            /* fall through */
        case WRITE_C8_D8:
            l++;
            /* fall through */
        case WRITE_COMMAND_8:
            writeCommand(operations[++i]);
            break;
        case WRITE_C16_D16:
            l = 2;
            /* fall through */
        case WRITE_COMMAND_16:
            _data16.msb = operations[++i];
            _data16.lsb = operations[++i];
            writeCommand16(_data16.value);
            break;
        case WRITE_DATA_8:
            l = 1;
            break;
        case WRITE_DATA_16:
            l = 2;
            break;
        case WRITE_BYTES:
            l = operations[++i];
            break;
        case END_WRITE:
            endWrite();
            break;
        case DELAY:
            vTaskDelay(operations[++i]);
            break;
        default:
            printf("Unknown operation id at %d: %d", i, operations[i]);
            break;
        }
        while (l--)
        {
            __write(operations[++i]);
        }
    }
}

and modified some RGB screen parameters

#define DEFAULT_HSYNC_BACK_PORCH 50
#define DEFAULT_HSYNC_FRONT_PORCH 10
#define DEFAULT_HSYNC_PULSE_WIDTH 8
#define DEFAULT_VSYNC_BACK_PORCH 20
#define DEFAULT_VSYNC_FRONT_PORCH 10
#define DEFAULT_VSYNC_PULSE_WIDTH 8

#define DEFAULT_H_RES 480 
#define DEFAULT_V_RES 480

Then the pan_init function is added to main.c and the overall code looks like this

printf("Starting MIDI on core %d\n", MIDI_TASK_COREID);
    xTaskCreatePinnedToCore(run_midi, MIDI_TASK_NAME, MIDI_TASK_STACK_SIZE / sizeof(StackType_t), NULL, MIDI_TASK_PRIORITY, &midi_handle, MIDI_TASK_COREID);

    printf("Starting USB host on core %d\n", USB_TASK_COREID);
    xTaskCreatePinnedToCore(run_usb, USB_TASK_NAME, (USB_TASK_STACK_SIZE) / sizeof(StackType_t), NULL, USB_TASK_PRIORITY, &usb_handle, USB_TASK_COREID);

    pan_init();
    printf("Starting display on core %d\n", DISPLAY_TASK_COREID);
    xTaskCreatePinnedToCore(run_esp32s3_display, DISPLAY_TASK_NAME, (DISPLAY_TASK_STACK_SIZE) / sizeof(StackType_t), NULL, DISPLAY_TASK_PRIORITY, &display_handle, DISPLAY_TASK_COREID);

    //run_i2c();

    ft5x06_init();
    printf("Starting touchscreen on core %d \n", TOUCHSCREEN_TASK_COREID);
    xTaskCreatePinnedToCore(run_ft5x06, TOUCHSCREEN_TASK_NAME, (TOUCHSCREEN_TASK_STACK_SIZE) / sizeof(StackType_t), NULL, TOUCHSCREEN_TASK_PRIORITY, &touchscreen_handle, TOUCHSCREEN_TASK_COREID);

    printf("Starting Alles on core %d\n", ALLES_TASK_COREID);
    xTaskCreatePinnedToCore(run_alles, ALLES_TASK_NAME, (ALLES_TASK_STACK_SIZE) / sizeof(StackType_t), NULL, ALLES_TASK_PRIORITY, &alles_handle, ALLES_TASK_COREID);

    printf("Starting MicroPython on core %d\n", TULIP_MP_TASK_COREID);
    xTaskCreatePinnedToCore(mp_task, TULIP_MP_TASK_NAME, (TULIP_MP_TASK_STACK_SIZE) / sizeof(StackType_t), NULL, TULIP_MP_TASK_PRIORITY, &tulip_mp_handle, TULIP_MP_TASK_COREID);

    printf("Starting joystick\n");
    init_esp_joy();

But something is not right, I see in the log output of the serial port

Starting display on core 0␍␊
setting duty to 4000␍␊
ft5x06 device create successed␍␊
Starting touchscreen on core 1 ␍␊
Starting Alles on core 1␍␊
Start���oystick␍␊
I'm renderer #0 on core #1 and i'm handling oscs 0 up until 32␍␊
I'm renderer #1 on core #0 and i'm handling oscs 32 up until 64␍␊

Desync warning: past 101 frames desync 1: 38.24 FPS. free time 26148uS. bounce time per is 237uS, 45.32% of max (522uS). bounce_count 5049␍␊

I noticed that it doesn't seem to start micropython and there is no output on the screen, I don't know what I should change, I hope I can get your help, thanks a lot

bwhitman · 2023-04-01T15:54:45Z

bwhitman
Apr 1, 2023
Maintainer

As far as the serial port log, that looks correct. We do not show any Micropython prompts over serial in Tulip -- it all gets redirected to the screen. The desync warning is also ok as long as you don't see hundreds of them.

I would first make sure you can get anything at all to show up on the screen. Does the screen work with the same wiring on other (non-Tulip, non-Micropython) projects? I am not qualified to comment on the SPI setup as i'm not familiar with this screen. If you can get it going outside of Tulip it'll make it a lot easier to debug.

4 replies

HalfSweet Apr 1, 2023
Author

But normally I should see a log like this Starting MicroPython on core 1, but it doesn't seem to appear
I'm trying to build a new esp-idf project to see if it works

bwhitman Apr 1, 2023
Maintainer

I wouldn't take too much faith in what you see on the logs on boot. It's a TODO for us to make logging better, but for now we basically spam STDERR / UART with a lot of messages at once during startup and they all overwrite each other. My (100% working) Tulip looks like this:

ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x1 (POWERON),boot:0x18 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
Octal Flash Mode Enabled
For OPI Flash, Use Default Flash Boot Mode
mode:SLOW_RD, clock div:1
load:0x3fcd0108,len:0xe34
load:0x403b6000,len:0x9e8
load:0x403ba000,len:0x2c08
entry 0x403b61d4
Starting MIDI on core 0
UART MIDI running on core 0
Starting USB host on core 1
Starting display on core 0
usb_host_install: 0
usb_host_client_register: 0
setting duty to 4000
ft5x06 device create successed
Starting touchscreen on core 1 
Starting Alles on core 1
Starting MicroPython on il 32
I'm renderer #1 on core #0 and i'm handling oscs 32 up until 64
New device address: 1
speed: 1 dev_addr 1 vMaxPacketSize0 8 bConfigurationValue 1
USB boot keyboard ready```

HalfSweet Apr 1, 2023
Author

Let me think about ...... the module I am using is ESP32-S3-WROOM-1-N16R8, it uses 16M NOR Flash and 8M SPI PSRAM, do I need to change the menuconfig?

HalfSweet Apr 1, 2023
Author

After several attempts ...... I found that it works in esp-idf's native project and works well. But the screen never works under this project, the background is constantly shown in black.
I don't know what's the reason for this, I guess maybe it's the idf version? I tested with idf 5.1, if you think it will help you to find the problem, I can give you a copy of my screen test project

HalfSweet · 2023-04-01T18:18:51Z

HalfSweet
Apr 1, 2023
Author

I found something interesting. When I set panel_config.data_width to 8, the whole program doesn't seem to work properly, but when I set it to 16, it runs fine. I measured it with an oscilloscope and found that the data pin did not have any waveform.
But if panel_config.data_width is set to 16, it works fine.

0 replies

HalfSweet · 2023-04-01T18:29:02Z

HalfSweet
Apr 1, 2023
Author

RGBTest.zip
You can refer to this project, I think it may be a little help to solve the problem

4 replies

bwhitman Apr 1, 2023
Maintainer

Can you tell me the model name of the display? The two links you've shared both require logins to taobao, I can't see it. If you give me the model name i can look it up myself.

It does seem like you're setting the bit width to 16 and the display is expecting RGB666 (18 bits)

    WRITE_C8_D8, 0x3A, 0x60, // 0x70 RGB888, 0x60 RGB666, 0x50 RGB565

Tulip only uses RGB332 and is only 8-bit width. I don't know what your display is accepting of. It may not want to receive RGB332.

HalfSweet Apr 1, 2023
Author

It doesn't have a searchable model number, but I can give you the manual for it.
The reason it is set to RGB666 mode is because the screen is pinned like this - although I wanted to set it to RGB888, unfortunately it doesn't pin out
Here is the schematic of the screen part of my hardware design, I don't think there is anything wrong with it

HXR040W..3).pdf

HalfSweet Apr 1, 2023
Author

I tried again, using an oscilloscope to measure the waveform on each pin, and it seems to be working, but for some reason the screen is still not showing.
I think maybe I need to purchase a RGB888 screen, the same as you are using is best, that might help me find the final problem.
I wonder if it would be convenient to add your private instant social software so that our communication might be a bit smoother, like twitter or telegram?

bwhitman Apr 2, 2023
Maintainer

I wish you luck finding a screen that works with Tulip! I can't really help more with your particular issue as I don't have the screen you're having trouble with. I only test / use Tulip on the screen I recommend -- the HOTMCU 10.1" panel. https://www.hotmcu.com/101-inch-1024x600-tft-lcd-display-with-capacitive-touch-panel-p-215.html

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

About Screen Selection #24

{{title}}

Replies: 5 comments 13 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

About Screen Selection #24

HalfSweet Mar 13, 2023

Replies: 5 comments · 13 replies

bwhitman Mar 13, 2023 Maintainer

HalfSweet Mar 13, 2023 Author

HalfSweet Mar 13, 2023 Author

bwhitman Mar 13, 2023 Maintainer

HalfSweet Mar 13, 2023 Author

bwhitman Mar 13, 2023 Maintainer

HalfSweet Apr 1, 2023 Author

bwhitman Apr 1, 2023 Maintainer

HalfSweet Apr 1, 2023 Author

bwhitman Apr 1, 2023 Maintainer

HalfSweet Apr 1, 2023 Author

HalfSweet Apr 1, 2023 Author

HalfSweet Apr 1, 2023 Author

HalfSweet Apr 1, 2023 Author

bwhitman Apr 1, 2023 Maintainer

HalfSweet Apr 1, 2023 Author

HalfSweet Apr 1, 2023 Author

bwhitman Apr 2, 2023 Maintainer

HalfSweet
Mar 13, 2023

Replies: 5 comments 13 replies

bwhitman
Mar 13, 2023
Maintainer

HalfSweet Mar 13, 2023
Author

HalfSweet Mar 13, 2023
Author

bwhitman Mar 13, 2023
Maintainer

HalfSweet Mar 13, 2023
Author

bwhitman
Mar 13, 2023
Maintainer

HalfSweet Apr 1, 2023
Author

bwhitman
Apr 1, 2023
Maintainer

HalfSweet Apr 1, 2023
Author

bwhitman Apr 1, 2023
Maintainer

HalfSweet Apr 1, 2023
Author

HalfSweet Apr 1, 2023
Author

HalfSweet
Apr 1, 2023
Author

HalfSweet
Apr 1, 2023
Author

bwhitman Apr 1, 2023
Maintainer

HalfSweet Apr 1, 2023
Author

HalfSweet Apr 1, 2023
Author

bwhitman Apr 2, 2023
Maintainer