ESP32-S3 DevKitCN8R8 + Display

[tonyrodrigues]

Hello,
I have an ESP32-S3 DevKitC N8R8 (I have already tested it and it is compatible with the DevKitC_N8R2 release).
I also have an MPI3508 display (http://www.lcdwiki.com/3.5inch_HDMI_Display-B) that I would like to use in the same way as the Waveshare 4.3" platform.
Would that be possible?

[Builty]

Hi Tony.
That display requires HDMI. This is beyond the capabilities of the ESP32 (actually beyond most small embedded processors.)
I don't think it will be possible to use that one.

[tonyrodrigues]

Thanks for the clarification.
Could recommend another model? I live in Brazil and the Waveshare 4.3B is expensive after the exchange rate.

[Builty]

Check out here: https://github.com/Builty/TonexOneController/blob/main/HardwarePlatforms.md

There are currently 5 supported platforms. 3 of them have LCD displays.
Is there some other brand that is more available/cheaper in Brazil than Waveshare and M5Stack?

[tonyrodrigues]

Confira aqui: https://github.com/Builty/TonexOneController/blob/main/HardwarePlatforms.md

Atualmente, há 5 plataformas suportadas. 3 delas têm telas LCD. Existe alguma outra marca que seja mais disponível/barata no Brasil do que Waveshare e M5Stack?

There is no low-cost display in Brazil, we usually buy in China in dollars + 90% in taxes, which makes it very difficult. If there were a low-cost and compatible 4.3" display, that would be my solution.

[Builty]

I haven't seen too many other ones that are common. I have used a lot of Waveshare as they are widely available.
If you had some other suggestions, I can investigate.

[bakarasche]

I made a controller with a Freenove ESP32S3 board (clone of DevKitC) and an inexpensive 2.8inch touch LCD.

I modified the UI for 240x320 resolution and modified the code to support SPI I/F for
display driver: ili9341
touch driver: xpt2046

The touch buttons are small and a little difficult to touch at this size, but I think I can manage to use it.
There is still a problem that some screen updates do not work due to SPI errors when updating screen displays,
and there is also a problem with unnecessary “>” at the beginning of the Preset Description when entering a Preset Description, so debugging is required.

The touch display system of ili9341+xpt2046 combination is used in many ESP32 boards, so I am glad to have more freedom of choice in terms of availability and size.

DevkitCw28LCD-.mp4

[Builty]

That looks great.

[mchbrk]

Awesome! I think I have some screen like this one, will check, if I have I will definetely build one and design a housing 😎😇

[bakarasche]

Hi
Since I have no experience in microcontroller software development and am not used to modifying code, I had a lot of trouble changing the touch LCD control to SPI I/F.
Memory management is very difficult.

I have a few questions and suggestions.

1. In the control_set_user_text function in control.c, I initialized it by adding
   　message.Text[0] = '\0';　 before strncat(message.Text, text, MAX_TEXT_LENGTH - 1);.

• • On my Platform, without this initialization, an indefinite value is added to the beginning of message.Text.

2. In the declaration of PropertyAnimation_0 in display.c, I got a build error if I did not add static.

static lv_anim_t PropertyAnimation_0;

3. I think the idea of ​​the location of the effect icon in the UI changing according to the order of the effects is great.
   However, in the case of a portrait display LCD, there may be more than two rows of icons, so how about making it two-dimensional to allow more flexible control over the placement?

Example of modifying updateIconOrder in display.c (for my portrait display)

// const int16_t offsets[8] = {-275, -205, -135, -65, 0, 65, 135, 205};
const int16_t offsets_x[8] = {-60, -20, 20, 60, -60, -20, 20, 60};
const int16_t offsets_y[8] = {-19, -19, -19, -19, 16, 16, 16, 16};

for (uint8_t i = 0; i<8; i++)
{
lv_obj_t *icon = icons[i];
// int16_t offset = offsets[i];
// lv_obj_set_x(icon, offset);

int16_t offset_x = offsets_x[i];
lv_obj_set_x(icon, offset_x);
int16_t offset_y = offsets_y[i];
lv_obj_set_y(icon, offset_y);
}

These may be issues specific to my environment (DevkitC, VSCODE+ESP-IDF5.4).

Sorry for talking about an unsupported LCD device.

[Builty]

Hi. The current releases have been using ESP IDF 5.1. I have spent time over the last few days moving to 5.4.1.

Issue 1: I haven't seen myself, but yes you are correct. Doing a string concatenation with an uninitialised string is bad practise. I have fixed this now.

Issue 2: yes I also found this one. The compiler in 5.4 is more strict. This is fixed also.

Issue 3: yes this makes sense also. I could be done a few different ways, but yours is fine.

I've been committing the fixes for 5.4.1 but haven't built any releases yet. Note that I had a lot of trouble with the 4.3B touch screen and random crashes. Espesssif changed the I2C API and it seems the legacy API has bugs. I have now changed to the new API, which needed a lot of changes but is working well now.