Orima

@Робертс I've been following this pinout from the very beginning, but I'm having trouble setting it up. I think I should wait for instructions from you, which you might create. I would be incredibly happy and grateful if you could provide a step-by-step description of the steps for setting up the Chinese ili9488 display and the OrangePi Zero 3 board.Maybe then I will understand where I am making a mistake.Thank you very much for your patience.

@Робертс My screen is constantly white. Here's my wiring diagram. Display-Orangepi zero 3 VCC-5v GND-GND CS-PH9(spi1) RST-PC14 D/C-PC7 SDI-PH7(mosi) SCK-PH4 BL-3.3v SDO-PH8(miso) Also, there might be a typo. The specified dc-gpio in your dts is described as PHC7. I don't quite understand, is it PC7 or PH7?

@robertoj Hello. I was able to get some DuPont wires and test them directly without soldering. The result was zero. I tried using ChatGPT to get it working.He suggests that my display isn't initializing. In some cases, it's either that the reset isn't working, or that the frequency is too high for a Chinese display. I tried using fbtft, but the result was zero. I followed your configuration and pinout. Are there any steps I might have missed?

@robertoj Could you post a step-by-step guide on setting up the Chinese ili9488 screen on a red board and OrangePi Zero 3? I think this forum will receive many thanks for your work.

@robertoj I apologize, perhaps you missed the message.

I'll try building the image again today with a new git clone, without changing anything except the userpatchers configuration. If I don't add the module this way, it won't be enabled in the text menu. I'll report back on my progress later.I created an image without changing the boardconfig. I used the default configuration for userpatches, which is used for compilation. I added one line, CONFIG_DRM_PANEL_MIPI_DBI=m, and the image built successfully. Afterwards, I booted and checked the kernel module with the command modinfo panel-mipi-dbi; the module is enabled. I also checked the configuration in /boot/config(umane); the module is enabled there too. I added DTS with the command sudo armbian-add-overlay , and also added the binary from the Pancake repo. After rebooting, the result didn't change at all; the screen was white. The output of dmesg | grep spi shows the same as in the previous post. I'm not sure about the pinout. Could you send me your pinout? What awg wires are you using? I use a combination of 28awg for VCC, DC, and GND, and 32awg for the rest.

I'll try building the image again today with a new git clone, without changing anything except the userpatchers configuration. If I don't add the module this way, it won't be enabled in the text menu. I'll report back on my progress later.

Thank you very much for your reply. That's exactly what I did. I have a custom Armbian image. When compiling, I selected my board for the 618 processor, as I couldn't find it in the standard section. I also found the panel-mipi-dbi parameter in the module selection menu. However, after compiling, writing the image to the flash card, and checking the module, the system didn't find it. I was able to build the image and include the module after correcting the boardconfig. It may have mistakenly listed the 616 processor, but I changed it to 618, and the image built successfully. After writing it to a flash drive and checking it in the system, I was finally able to find the required module. It was also displayed in the /boot/config(uname) configuration file.

I was able to get it out. I'm pretty good at Linux, but not at screens. Maybe I'm missing something?

Sorry, I've never done anything like this before. I tried setting it up according to instructions in various GitHub threads, but it always failed. You're the only person who helps me with advice, and thanks to you, I've only been able to build an image with the required kernel module. I haven't achieved anything else, except for the white screen.

Good afternoon. Thank you for your reply. Unfortunately, I haven't had a positive experience. My apologies for misleading you, but my motherboard originally had a 618 processor. I tried creating an image for the 616 many times until I noticed that my processor was a 618. After several attempts, I was able to create an image for the 618. After receiving an image for the 618 with the panel-mipi-dbi module, I tried connecting a screen with an ili9488 chip. I can say I've taken the first step toward implementing this project. Now I need to get the screen working with the resulting image.

So, here's what I had to do to successfully build the image. First, I corrected my board file in the config/board/orangepizero3.csc directory. The processor value was incorrect, it was 616, so I set it to 618. Menuconf suggested selecting a board with a 618 chip, but in the board file it was listed as family 616. Later, I copied my board file to the userpatches directory and added the value CONFIG_DRM_PANEL_MIPI_DBI=m. Then I ran the image build script with the menuconf viewer. I was surprised that the CONFIG_DRM_PANEL_MIPI_DBI parameter already had the value "m"; previously, it was empty. After all these manipulations, the build went smoothly. Thank you so much for your support.

Hi I was able to build an image with the panel-mipi-dbi module enabled. My previous image had the module disabled, so it took me a couple of days to figure it out. As I found out, for my version of the board, which uses the 618 chip, I needed to adjust a line in the bootconfig to build my board. It specified the 616 chip. But that's probably not the reason for the success. After I built the image, applied the binary, and dts, the screen was still white after rebooting. user@orangepizero3:~/v0_ips_touch_display$ cd user@orangepizero3:~$ sudo modinfo panel-mipi-dbi filename: /lib/modules/6.16.8-edge-sunxi64/kernel/drivers/gpu/drm/tiny/panel-mipi-dbi.ko license: GPL author: Noralf Trønnes description: MIPI DBI compatible display panel driver alias: of:N*T*Cpanel-mipi-dbi-spiC* alias: of:N*T*Cpanel-mipi-dbi-spi alias: spi:panel-mipi-dbi-spi depends: drm_mipi_dbi,backlight intree: Y name: panel_mipi_dbi vermagic: 6.16.8-edge-sunxi64 SMP preempt mod_unload aarch64 user@orangepizero3:~$ dmesg | grep spi [ 2.466658] sun6i-spi 5010000.spi: Error applying setting, reverse things back [ 2.467167] sun6i-spi 5011000.spi: cannot register SPI host [ 2.474140] sun6i-spi 5010000.spi: Error applying setting, reverse things back [ 2.474558] sun6i-spi 5011000.spi: cannot register SPI host [ 3.584770] panel-mipi-dbi-spi spi1.0: supply power not found, using dummy regulator [ 3.603713] panel-mipi-dbi-spi spi1.0: supply io not found, using dummy regulator [ 3.603960] panel-mipi-dbi-spi spi1.0: Direct firmware load for panel-mipi-dbi-spi.bin failed with error -2 [ 3.603975] panel-mipi-dbi-spi spi1.0: No config file found for compatible 'panel-mipi-dbi-spi' (error=-2) [ 3.603983] panel-mipi-dbi-spi spi1.0: probe with driver panel-mipi-dbi-spi failed with error -2 [ 12.001666] OF: /soc/spi@5011000/ads7846@1: Read of boolean property 'ti,swap-xy' with a value. [ 12.001860] ads7846 spi1.1: supply vcc not found, using dummy regulator [ 12.004761] ads7846 spi1.1: touchscreen, irq 77 [ 12.007680] input: ADS7846 Touchscreen as /devices/platform/soc/5011000.spi/spi_master/spi1/spi1.1/input/input10 [ 12.018707] spi-nor spi0.0: supply vcc not found, using dummy regulator [ 12.018953] spi-nor spi0.0: supply vdd not found, using dummy regulator

Are you sure you can't help me? I just need to add one line to add the module.

I'm using compile.sh without any arguments. Can I add the adra module argument to the command? How well will this work? For example, like this: ./compile.sh CONFIGURE_DRM_PANEL_MIPI_DBI=m I tried this, but I got a compilation error saying there was no such argument.