Waveshare ESP32-P4-NANO dev board MIPI-DSI LCD issue

[RobCrown82]

The sample Arduino projects for the Waveshare ESP32-P4-NANO dev board don't properly initialize the MIPI-DSI LCD display. The display doesn't turn on (no backlight, black screen) so the code always jams in the panel_jd9365_init() function of the esp_lcd_jd9365.c file when it tries to read the LCD ID.

The panel does initialize properly if I load the waveshare sample projects using the ESP-IDF V5.4.1 directly (through VS code). I've examined their esp_lcd_jd9365.c file and there are some i2c commands being sent to the panel in the esp_lcd_new_panel_jd9365() function that are missing in the ESP32_Display_Panel Arduino library. Those commands are in some way responsible for turning on the display. Can you please advise on how to fix this issue in your library.

I've pasted the missing i2c code below.

i2c_config_t conf = {
.mode = I2C_MODE_MASTER,
.sda_io_num = 7,
.sda_pullup_en = GPIO_PULLUP_ENABLE,
.scl_io_num = 8,
.scl_pullup_en = GPIO_PULLUP_ENABLE,
.master.clk_speed = 100000,
};

i2c_bus_handle_t i2c0_bus = i2c_bus_create(I2C_NUM_1, &conf);
i2c_bus_device_handle_t i2c0_device1 = i2c_bus_device_create(i2c0_bus, 0x45, 0);

uint8_t data = 0x11;
i2c_bus_write_bytes(i2c0_device1, 0x95, 1, &data);
data = 0x17;
i2c_bus_write_bytes(i2c0_device1, 0x95, 1, &data);
data = 0x00;
i2c_bus_write_bytes(i2c0_device1, 0x96, 1, &data);
vTaskDelay(pdMS_TO_TICKS(100));
data = 0xFF;
i2c_bus_write_bytes(i2c0_device1, 0x96, 1, &data);

i2c_bus_device_delete(&i2c0_device1);
// i2c_bus_delete(&i2c0_bus);

vTaskDelay(pdMS_TO_TICKS(1000));

[DejanBukovec]

Hi,
JD9365 LCD Panel do not use I2C for comunication but use MIPI DSI. If you check Guition JC8012P4A1 issue thread which use 10.1 inch JD9365 LCD panel you will see example configurations for it... It also use GSL3680 touch panel which is not supported by this library...

There is no I2C configuration for JD9365. You need MIPI DSI and PWM_LED(Pin 29 in Guition example) for backlight and reset pin(Pin 23 in Guition example).

In case that your panel use GSL3680 touch panel then there is I2C configuration which use next 4 pins(In Guition example):
I2C_SDA 7
I2C_SCL 8
RST 22
INT 21
But probably your screen use different touch panel because use slower CLK speed(100kHz instead of 400kHz)...

[TiAmourze]

Hello, I have the same problem with the questioner when using "Waveshare ESP 32-P4-Nano Board MIPI-DSI LCD". When I tried to reproduce the "board_static_config" routine in the ESP_Display_Panel library on Arduino platform, "esp_panel_board_supported_conf" and "esp_panel_drivers_conf" were correctly configured, and all the steps were carried out according to "README".

But after compiling and burning to the development board, the above debugging information appears on the serial monitor, and the whole program stops : [D][Panel]esp_panel_lcd.cpp:0503: Refresh panel(@0x48001260) reset.

Go back to the root of the problem, trace back to the statements ( ESP_UTILS_CHECK_FALSE_RETURN(lcd_device->begin(), false, "LCD device begin failed");) in the file (esp_panel_board.cpp), then to the statements (ESP_UTILS_CHECK_ERROR_RETURN(esp_lcd_panel_init(refresh_panel), false, "Init panel failed");) in the file (esp_panel_lcd.cpp), and execute to the function (esp_lcd_panel_init(refresh_panel)), The whole program can't continue to execute, and the result in the figure appears.

[DejanBukovec]

Did you try set reset GPIO? Maybe is 23(Same as use Guition)...

[TiAmourze]

With reference to the. h configuration file in Guition JC8012P4A1 issue, setting reset GPIO still has the same problem. In the *panel_jd9365_init(esp_lcd_panel_t panel) function of esp_lcd_jd9365.cpp file, execute to ESP_RETURN_ON_ERROR(esp_lcd_panel_io_rx_param(io, 0x04, ID, 3), TAG, "read ID failed"); statement, that is, when obtaining the LCD ID, cannot be continued.

After commenting this statement (it has no effect on the following statements), the program can continue to execute. But continue to execute to the next for loop ESP_RETURN_ON_ERROR(esp_lcd_panel_io_tx_param(io, init_cmds[i].cmd, init_cmds[i].data, init_cmds[i].data_bytes), TAG, "send command failed"); statement, the above situation will still occur.

At first, the content of init_cmds was incorrect, but no difference was found after comparing with the driver library provided by waveshare. Change esp_lcd_panel_t *pane io (MIPI DPI panel @0x48001260 to another)，and there is still the same problem.

[RobCrown82]

Yes, I know the JD9365 LCD uses MIPI DSI for communication but the i2c bus is used to communicate with the touch panel GT9271 (GT911 like) which is supported by this library.

I don't believe this display uses a backlight or a reset pin. It's connections to the ESP32-P4 are only the MIPI DSI flex cable and a 2-pin header for power and ground.

This missing i2c code is important for the panel initialization. I'm not sure exactly what it does but it is responsible for turning the panel ON. I found this i2c code in the Waveshare sample projects. Without it, the LCD panel doesn't turn on and like I said the display library fails when trying to get the LCD ID.

I was able to add it to my sketch (using the i2c legacy driver) and once added, the panel does turn on and the sample Arduino projects do run properly. Can you please look into this.

add the following to your sketch file,

#include "driver/i2c.h"

#define I2C_NUM I2C_NUM_1
#define I2C_SDA_IO 7
#define I2C_SCL_IO 8
#define I2C_FREQ_HZ 100000
#define I2C_DEV_ADDR 0x45

void writeI2CRegister(uint8_t reg, uint8_t value) {
i2c_cmd_handle_t cmd = i2c_cmd_link_create();
i2c_master_start(cmd);
i2c_master_write_byte(cmd, (I2C_DEV_ADDR << 1) | I2C_MASTER_WRITE, true);
i2c_master_write_byte(cmd, reg, true);
i2c_master_write_byte(cmd, value, true);
i2c_master_stop(cmd);
i2c_master_cmd_begin(I2C_NUM, cmd, pdMS_TO_TICKS(100));
i2c_cmd_link_delete(cmd);
}

void initI2CLegacy() {
i2c_config_t config;
config.mode = I2C_MODE_MASTER;
config.sda_io_num = I2C_SDA_IO;
config.scl_io_num = I2C_SCL_IO;
config.sda_pullup_en = GPIO_PULLUP_ENABLE;
config.scl_pullup_en = GPIO_PULLUP_ENABLE;
config.master.clk_speed = I2C_FREQ_HZ;
config.clk_flags = 0;

i2c_param_config(I2C_NUM, &config);
i2c_driver_install(I2C_NUM, config.mode, 0, 0, 0);
}

void setup() {
Serial.begin(115200);

initI2CLegacy();
writeI2CRegister(0x95, 0x11);
writeI2CRegister(0x95, 0x17);
writeI2CRegister(0x96, 0x00);
delay(100);
writeI2CRegister(0x96, 0xFF);

Serial.println("Initializing board");
Board *board = new Board();
board->init();
assert(board->begin());
}

[DejanBukovec]

As Im write in previous post JD9365 do not have I2C comunication. Check documentation of JD9365 and you will see that in 220 pages of documentation there is nothing about I2C ...
Your I2C code is for touch panel GT9271. If your I2C configuration is wrong or driver do not support it fully then when you will call begin of board it will crash and your board will reboot ...
If you disable touch panel in config then your LCD(Without touchscreen) must init and work and board will not reboot...

[Y1hsiaochunnn]

You need to add i2c register control, refer to this section:https://github.com/waveshareteam/Waveshare-ESP32-components/blob/db328ea6b96e7a7523ee0a8e964bb2467b486b2e/display/lcd/esp_lcd_jd9365_10_1/esp_lcd_jd9365_10_1.c#L133-L144

[Y1hsiaochunnn]

As Im write in previous post JD9365 do not have I2C comunication. Check documentation of JD9365 and you will see that in 220 pages of documentation there is nothing about I2C ... Your I2C code is for touch panel GT9271. If your I2C configuration is wrong or driver do not support it fully then when you will call begin of board it will crash and your board will reboot ... If you disable touch panel in config then your LCD(Without touchscreen) must init and work and board will not reboot...

I don't deny your point, but the screen control should be supported by the manufacturer, during the process of making the screen, the waveshare guys added a single chip microcomputer, you need to write registers to control reset, backlight, etc. It is also mentioned in the waveshare Wiki