1. Display Anomaly Troubleshooting

Completely dark (no backlight):

1. Use a multimeter to verify the supply voltage is 3.3V;
2. After power-on, wait 700 ms for the TR2S chip to finish initializing before sending the backlight command;
3. Check that the corresponding interface is configured correctly (e.g., SPI/QSPI/8080_8B/8080_16B mode) and that the IM0/IM1 pins are set correctly — see (2. How to Switch Between QSPI/SPI/8080_8B/8080_16B Interfaces);
4. Confirm that the backlight-enable command has been correctly written to register 0x20.

White screen (backlight on but no image):

1. When sending commands (such as 0x20, 0x2A, 0x2B, etc.), wait until the busy pin goes high to ensure the previous command has finished executing. If the busy pin is not connected, you can add a delay between commands to ensure they execute correctly — refer to the table below for specific timings:

Chip	Resolution	0x2A (μs)	0x2B (μs)	0xAD (μs)	0x20 (μs)
TR230S	1024×600	6.08	5.72	12.84	12.88
TR220S	480×800	16.3	17	31.7	34

2. Confirm that image data was sent correctly via register 0x2C and that the data volume is sufficient (matching the display area set by 0x2A and 0x2B);
3. Send 0x2A/0x2B before every frame to set the display area;
4. The interval between two frames should be 20-30 ms, because the TR2S chip takes time to push the image to the screen — avoid sending data too fast, which can cause packet loss.

Garbled/distorted image:

1. Use the self-test command (0x12) to check whether the screen displays normally;
2. Check whether the SPI/QSPI/8080_8B/8080_16B clock frequency is too high; try lowering the CLK frequency. If the host and screen are connected with Dupont wires, set the CLK frequency below 100k first and check whether the display is correct;
3. Confirm that the data format (RGB565/RGB888) matches the configuration;
4. Confirm that the MSB/LSB order of the image data being sent is correct;
5. Check that the wiring is secure, especially whether any data lines have cold solder joints or poor contact.