Orima

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.

Thank you very much for your answer. sudo apt install docker.io git clone https://github.com/armbian/build armbian cd armbian/ ./compile.sh In the configurator, I select the custom plate orangepizero3, and then the Trixie release. Then in the configurator, I select device-driver->graphic-support->drm->drm-panel-mipi-dbi-support Then I save the configuration under a custom name. Then exit, exit, exit, and load the configuration. When asked if I wanted to save the new configuration, I selected both options, but the result was always the same: the module wasn't compiled into the kernel.

I'm trying to build an abian trixie image with the CONFIG_DRM_PANEL_MIPI_DBI support module enabled in the kernel. However, no matter how many times I build, when checking the modinfo module, panel-mipi-dbi is not found. In the /boot/config(kernel) configuration, the line is commented out: #CONFIG_DRM_PANEL_MIPI_DBI is not set I set M to the panel-mipi-dbi kernel module parameter. I also set Y to the parameter. I also tried adjusting the .config file before running the image build. I used both Docker and non-Docker builds. I'm using Ubuntu 22.04.

@robertoj Thank you very much for your reply! I sincerely apologize for any misunderstanding. When I mentioned the 16-bit option, I was referring to the selection made when setting up the Armbian image. This option is located in the same menu as the mipi_panel_dbi support option. I mentioned this in my comment because I was a bit confused by the "but the greeter is not" part of your response. I probably just needed to enable the mipi_panel_dbi support parameter and continue building without adding any additional parameters. I use a screen with a red board on the ili9488 driver, the Chinese version for sure. I'd also like to clarify with someone who's already done this, whether I'm following all the steps correctly. If that's possible, please let me know within this forum thread. - I'm building a minimal image. - First, I use the DTS file from the thread you provided as a response. - After I see the image on the screen, if the colors are incorrect, I use the file provided by Pancake. Please forgive me again. In the thread you provided as a solution, I don't understand the sequence of actions and where I should start. Once again, I apologize for my meticulousness.

@robertoj OK. I managed to build Armbian, selecting mipi-panel-dbi support and booting to 16-bit. After setting it up and running the dts you provided, my screen still doesn't work. I'm probably doing something wrong, because although the screen glows white, it still shows barely noticeable backlight flickering. I also tried to do it according to Pancake's instructions, but I also didn't have any success. This log with Pancake's cat log.txt [ 1.623324] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 2.173154] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 2.242555] sdiohal:sdiohal_parse_dt adma_tx:1, adma_rx:1, pwrseq:0, irq type:data, gpio_num:0, blksize:840 [ 7.591150] systemd[1]: Starting systemd-backlight@backlight:backlight_gpio.service - Load/Save Screen Backlight Brightness of backlight:backlight_gpio... [ 7.652908] systemd[1]: Finished systemd-backlight@backlight:backlight_gpio.service - Load/Save Screen Backlight Brightness of backlight:backlight_gpio. user@orangepizero3:~$ hostnamectl Static hostname: orangepizero3 Icon name: computer Machine ID: a5f7b63422b54dc5a365def0a7294555 Boot ID: 4445f89ef8cb4b999e3fa684f292ca2a Operating System: Armbian-unofficial 26.02.0-trunk bookworm Kernel: Linux 6.16.8-edge-sunxi64 Architecture: arm64 And this log with DTS from you cat log.txt [ 1.623908] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 2.172898] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 2.242212] sdiohal:sdiohal_parse_dt adma_tx:1, adma_rx:1, pwrseq:0, irq type:data, gpio_num:0, blksize:840 But I'm very happy that I managed to build my first Linux, albeit in such a simple way. My pinout Displ OpiZ3 Vcc - out 3.3v Gnd - gnd Cs - ph9 Reset - pc14 Dc/rc - pc7 Sdi(mosi) - ph7 Sck - ph4 Led - 5v Sdo(miso) - ph8

@robertoj Hi I'm completely stuck. I'm trying to build an Armbian Trixie image, but I'm having trouble installing packages. I've tried changing the repository links to the ones closest to my location, but to no avail. I am completely unable to continue my research for assembling Armbian. This is how I collected Armbian ./compile.sh BOARD=orangepizero3 BRANCH=edge kernel-config CONFIG_DRM_PANEL_MIPI_DBI=m CONFIG_TOUCHSCREEN_EDT_FT5X06=m CONFIG_BACKLIGHT_GPIO=m CONFIG_BACKLIGHT_PWM=m ./compile.sh BOARD=orangepizero3 BRANCH=edge BUILD_DESKTOP=yes BUILD_MINIMAL=yes KERNEL_CONFIGURE=no RELEASE=trixie Also, with the configurator window open, I selected to enable panel_mipi_dbi Perhaps you still have an image of the assembled Armbian? I first built it on Ubuntu 22.04. Later, I built it on Debian Trixie. I change repo to: http://ftp.debian.org/debian And debian security http://ftp.debian.org trixie-security For armbian https://armbian.systemonachip.net/apt Its not work