LANBON L10

[parody1]

I've acquired a Lanbon L10. It's a really nice quality, larger screen version of the L8.

I've been trying to get it working, so far with no luck. It uses a ESP32S3-WROOM-1U. Here's a board-info dump

espflash board-info
[2025-11-10T21:19:49Z INFO ] Serial port: '/dev/cu.usbserial-A50285BI'
[2025-11-10T21:19:49Z INFO ] Connecting...
[2025-11-10T21:19:49Z INFO ] Using flash stub
Chip type:         esp32s3 (revision v0.2)
Crystal frequency: 40 MHz
Flash size:        16MB
Features:          WiFi, BLE, Embedded Flash
MAC address:       dc:b4:d9:07:d9:5c

Security Information:
=====================
Flags: 0x00000000 (0)
Key Purposes: [0, 0, 0, 0, 0, 0, 12]
Chip ID: 9
API Version: 0
Secure Boot: Disabled
Flash Encryption: Disabled
SPI Boot Crypt Count (SPI_BOOT_CRYPT_CNT): 0x0

From viewing the logs of a stock firmware boot I can see it is a GT911 and ST7701
boot.log

Here is a board image:

Given the similar hardware I tried the esp32-s3-4848s040 image but had no luck with booting. I've also tried some GPIO tests but can't seem to fire the screen up. The log mentions "Initialize IO expander" so not sure if that has something to do with it.

Can anyone give any pointers? I've heavily modified some of the other images, and not afraid to poke around, but I'm at a bit of a loss on the hardware side.

[fvanroie]

Nice, it is probably very similar like the other 480x480 screens, but the pin-out is most likely unique to this PCB revision.
So, because there is no pin-out, you'll need to whip out the multi-meter in continuity mode and probe the ESP32 pins vs the LCD connector FCP1 pins. Make a spreadsheet or table on paper with ESP32 pin# <-> FCP pin#. This should give a good starting point.

While you're at it, also probe the P1 header for ESP32 connectivity to get the serial/replay pins.

[parody1]

Nice, it is probably very similar like the other 480x480 screens, but the pin-out is most likely unique to this PCB revision. So, because there is no pin-out, you'll need to whip out the multi-meter in continuity mode and probe the ESP32 pins vs the LCD connector FCP1 pins. Make a spreadsheet or table on paper with ESP32 pin# <-> FCP pin#. This should give a good starting point.

While you're at it, also probe the P1 header for ESP32 connectivity to get the serial/replay pins.

Great, I've ordered a FCP breakout to make testing easier. Will come back with the results.

[parody1]

@fvanroie

Here are the results of the continuity tests:

FPC PIN #	ESP PIN #	ESP PIN
1	1 & 40	GND
2	2	3V
3	-
4	11	IO18
5	12	IO8
6	1 & 40	GND
7	1 & 40	GND
8	39	IO1
9	38	IO2
10	35	IO42
11	34	IO41
12	33	IO40
13	33	IO40
14	32	IO39
15	31	IO38
16	18	IO10
17	19	IO11
18	20	IO12
19	21	IO13
20	22	IO14
21	23	IO21
22	24	IO47
23	25	IO48
24	26	IO45
25	26	IO45
26	16	IO46
27	15	IO3
28	27	IO1
29	17	IO9
30	-
31	-
32	-
33	-
34	-
35	-
36	2	3V
37	1 & 40	GND
38	1 & 40	GND
39	1 & 40	GND
40	-

And here is the P1 (I've already connected and flashed without issue):

P1 PIN	P1 PIN #	ESP PIN #	ESP PIN
RX	1	36	RXD0
TX	3	37	TXD0
5V	5
K1	7
K2	9
GND	11	1 & 40	GND
IO0	2	27	IO0
CF	4
3V	6	2	3V
HUMI	8
BP	10
K3	12

[parody1]

Any advice @fvanroie ?

[fvanroie]

The list only makes sense to me if you reverse the FPC pin numbers (40->1 instead of 1->40).
Please check the yellow ribbon cable of the display that should also have a 1 and 40 labels (in white) on it.
The label number on the yellow ribbon cable are leading, maybe there is a reverse/mismatch with the PCB-FPC numbering...
Maybe take a picture with the display ribbon connected to the PCB to verify.
You need to map ST7701S pin functions (SDA, VSYNC, DBxx, etc) to ESP32 pin numbers.

[parody1]

I agree. I wondered that, it looked to me like they should be reversed but I used the numbers on the breakout header pins to take the notes.

So these will be used for TOUCH_SDA etc? Do you think I can use the esp32-s3-4848s040.ini as a starting point and adjust? Do you have the ESP32 to FPC map for that so I can reverse engineer it?

[fvanroie]

Yes, there are several ST7701S ini files that you can use as a template and adapt to this device.
I usually create a visual aid like this.
But a detailed table with ESP32 Pin numbers <-> display functions mapping should work fine too.

[markjsmith]

I just got one of these, very clean compared to the old L8.

Did you manage to create a working .ini file?

[fvanroie]

I haven't seen one for the L10 yet, no. It should be possible to start from a similar device and adapt the ini file accordingly.
If you can compile firmware locally, that's the way to test and iterate.

[parody1]

I didn't get to it yet, but it's very much on my list to get to. As soon as I make some progress I'll update, unless someone beats me to it.