Search the Community

After booting up armbian 23.02.2 on my orange pi 4 LTS, cpu temp goes up to 95 deg celcius when stress testing (no heatsink or fan installed at all) and the device reboots shortly afterwards. I ran `armbianmonitor -m` when stress testing and found out that some of the cores are not throttling. I examined the default trip point settings coming with the image in the file /boot/dtb/rockchip/rk3399-orangepi-4-lts.dtb: trips { cpu_alert0 { temperature = <0x14c08>; hysteresis = <0x7d0>; type = "passive"; phandle = <0x5a>; }; cpu_alert1 { temperature = <0x17318>; hysteresis = <0x7d0>; type = "passive"; phandle = <0x5b>; }; cpu_crit { temperature = <0x186a0>; hysteresis = <0x7d0>; type = "critical"; phandle = <0xf3>; }; }; These temperature settings do not match the vendor images' settings, and I changed them to match the vendor images' settings as follows: trips { cpu_alert0 { temperature = <0x11170>; hysteresis = <0x7d0>; type = "passive"; phandle = <0x5a>; }; cpu_alert1 { temperature = <0x14c08>; hysteresis = <0x7d0>; type = "passive"; phandle = <0x5b>; }; cpu_crit { temperature = <0x1c138>; hysteresis = <0x7d0>; type = "critical"; phandle = <0xf3>; }; }; After making this change, I no longer have any reboots caused by overheating and `armbianmonitor -m` shows that the cpu is correctly throttled at 85 deg celcius when stressing testing without heatsink or fan. Is this the right way to solve this issue? If so, can someone make a PR for this? Thanks.

Hello folks! I was experimenting with all ARM images (Manjaro, Fedora, Arch, etc) i could find to test with the Orange Pi 4 LTS SBC board, and when i was about to return to armbian, it didnt boot anymore, not even from the SD card flashed with a proper image. I' currently using UART USB to TTL debug device to see whats happening with the board and it returns this: NOTE: [At the moment of this screenshot the board was with a SD card flashed with the default orange pi debian server image] Does anyone know how to reset this board and get it booting again from any ARM images? Would really appreciate any help on this to discover what i did mess up... Thanks in advance

Hello everyone, I somehow managed to brick my OrangePi 4 LTS. I had the Armbian running on it and decided to try the newest install in a minimal format so no desktop. Installed it, made all the setup and restarted. Since then no other image works, neither the official orangepi images nor any other armbian image. I tried booting off without the SD Card, trying to flash another OS with the SD card and read out the TTL and this is what I get: DDR Version 1.25 20210517 In channel 0 CS = 0 MR0=0x18 MR4=0x2 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x2 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! change freq to 416MHz 0,1 Channel 0: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB Channel 1: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB 256B stride channel 0 CS = 0 MR0=0x18 MR4=0x2 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x18 MR4=0x2 MR5=0x1 MR8=0x10 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done change freq to 856MHz 1,0 ch 0 ddrconfig = 0x101, ddrsize = 0x40 ch 1 ddrconfig = 0x101, ddrsize = 0x40 pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD ddr_set_rate to 328MHZ ddr_set_rate to 666MHZ ddr_set_rate to 928MHZ channel 0, cs 0, advanced training done channel 1, cs 0, advanced training done ddr_set_rate to 416MHZ, ctl_index 0 ddr_set_rate to 856MHZ, ctl_index 1 support 416 856 328 666 928 MHz, current 856MHz OUT After this, nothing happens. Red light still on, no HDMI image, nothing. I don't know what to do from here. Not even sure if I can reset it. I tried another SD card and nothing works. Any tips?

Hello, I'm having issues with my Orange Pi 4 LTS. I cannot get any HDMI output at the moment. Neither with the Debian flashed on the eMMC, or with Armbian running of the SD card. In both cases I can SSH into the Orange and run commands normally. The HDMI worked just a day before, but in the meantime I was flashing different systems and it stopped working. I tried different monitors and cables. Any ideas what can I do?

I've compiled mainline kernel 6.6 which runs well on my OrangePi/RK3399. The only problem left is getting H.264 decoding working. Unfortunately, when I query /dev/video1 which is the node created by the hantro-vpu driver, only MPEG2 and VP8 are shown as supported codecs for decoding. No H.264, even though I've read many places that the mainline hantro driver supports H.264. Has anyone else had this problem? Is there something else I need to do to get this working?

I've noticed that some system images will start the OrangePi with 4:2:2 output on HDMI instead of 4:4:4. This causes artifacts, especially when there's white text on a red background. What's the interface or method to change this? Does this have to be done via U-Boot or can it be done in userspace?

Hi all, reporting a regression in new Armbian 24.2.1 kernel version. New kernel is causing Orange Pi 4 LPS not to boot most of the time, when it boots, then there is no network. Kernel hangs with oops errors on the screen, and all debugging stuff. Sorry that I did not caught any of them on my phone, but it would have been incomplete anyway. How to reproduce: Install any 24.2.1 based system on Orange Pi 4 LTS Upon first boot, you will have issues. No Ethernet network. Second boot will most likely not succeed no matter what you do and system will brick permanently, by not booting at all (no video output), or booting and then showing kernel crash. I've tested: Armbian_24.2.1_Orangepi4-lts_jammy_current_6.6.16_xfce_desktop.img.xz (system booted into desktop only once, never managed to do it again. No network in first boot) Armbian_24.2.1_Orangepi4-lts_jammy_current_6.6.16.img.xz (kernel crash in terminal on second boot, no network on first boot) Armbian_23.8.1_Orangepi4-lts_bookworm_current_6.1.50.img.xz - here I installed older image, all was good, network good, reboots good, so I upgraded all packages, upon restart everything was broken again) Armbian_23.8.1_Orangepi4-lts_bookworm_current_6.1.50.img.xz - formatted the card again, got it working again, I went to armbian config tool and marked Armbian kernel packages to freeze, not going to upgrade them unless regression is confirmed to be gone. Notes: I've tested this with nothing connected to the board except for HDMI cable and some GPIO pins. Nothing on USB etc. New kernel 6.6.16. on Armbian 24.2.1 is experiencing this regression. Kind regards

New 6.x based kernels for OPI 4 LTS seems to be a hit or miss for HDMI monitors. Some work, and others especially TVs dont output video at all. Images with 5.15.x kernels dont have this issue.

I create a file 98-use-serial.rules under folder /etc/udev/rules.d . But symlink not created . My purpose is to fix USB port names, As COM1 COM2 COM3 This is the content of 98-usb-serial.rules: SUBSYSTEM=="tty",ATTRS{busnum}=="1",ATTRS{devnum}=="2",SYMLINK+="COM1" SUBSYSTEM=="tty",ATTRS{busnum}=="4",ATTRS{devnum}=="2",SYMLINK+="COM2" SUBSYSTEM=="tty",ATTRS{busnum}=="5",ATTRS{devnum}=="2",SYMLINK+="COM3" I used to fix the USB port on Asus Tinker S, Khada_VIM3 , all worked fine. I have no idea why Orange Pi 4 LTD not working.

Hello! I would like to connect orangepi-4-lts to ili9341. I have new blank Armbian. $ uname -a Linux orangepi4-lts 5.15.52-rockchip64 #22.05.4 SMP PREEMPT I did overlay based on allwinner: /dts-v1/; /plugin/; / { compatible = "rockchip,rk3399"; fragment@0 { target = <&gpio1>; __overlay__ { ili9341_pins: ili9341_pins { pins = "PC7", "PD0"; function = "gpio_out", "gpio_out"; }; }; }; fragment@1 { target = <&spi1>; __overlay__ { status = "okay"; cs-gpios = <&gpio1 10 1>; ili9341: ili9341@0 { compatible = "ilitek, ili9341"; reg = <1>; pinctrl-names = "default"; pinctrl-0 = <&ili9341_pins>; spi-max-frequency = <16000000>; rotate = <90>; bgr; fps = <25>; buswidth = <8>; reset-gpios = <&gpio1 23 1>; dc-gpios = <&gpio1 24 0>; debug = <0>; }; }; }; }; Setting /boot/armbianEnv.txt verbosity=1 bootlogo=true extraargs=systemd.unified_cgroup_hierarchy=0 overlay_prefix=rockchip fdtfile=rockchip/rk3399-orangepi-4-lts.dtb rootdev=UUID=ce86a0ca-f0e5-4dba-af37-15cc3fb2f4e0 rootfstype=ext4 param_spidev_spi_bus=1 param_spidev_spi_cs=0 user_overlays=ili9341 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Restart, TFT not turn on. I watch debugiing uart, no errors: ## Executing script at 00500000 Boot script loaded from mmc 1 320 bytes read in 4 ms (78.1 KiB/s) 16356833 bytes read in 696 ms (22.4 MiB/s) 30540288 bytes read in 1295 ms (22.5 MiB/s) 81458 bytes read in 14 ms (5.5 MiB/s) 1233 bytes read in 7 ms (171.9 KiB/s) Applying user provided DT overlay ili9341.dtbo 2698 bytes read in 9 ms (292 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 Moving Image from 0x2080000 to 0x2200000, end=3fc0000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 16356769 Bytes = 15.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f4f65000, end f5efe5a1 ... OK Loading Device Tree to 00000000f4ee8000, end 00000000f4f64fff ... OK Starting kernel ... Watching system boot log: grecha@orangepi4-lts:~$ sudo dmesg | grep spi [ 2.053302] rockchip-spi ff1d0000.spi: cs1 >= max 1 [ 2.053318] spi_master spi1: spi_device register error /spi@ff1d0000/ili9341@0 [ 2.053345] spi_master spi1: Failed to create SPI device for /spi@ff1d0000/ili9341@0 grecha@orangepi4-lts:~$ sudo dmesg | grep ili9341 [ 2.053318] spi_master spi1: spi_device register error /spi@ff1d0000/ili9341@0 [ 2.053345] spi_master spi1: Failed to create SPI device for /spi@ff1d0000/ili9341@0 Please, help me. Why is this overlay not working?

Well, I am trying to flash armbian to my board, but after I run upgrade_tool ef in mistake. I can't do anything via maskrom/loader at all wherever Windows or linux. Then I try to unbrick it via flash the "MiniLoaderAll.bin" via "upgrade_tool db" and "ul" but them don't work at all(Timeouted),How can I do with it?

I have owned numerous Raspberry Pi boards over the years, and I have always have ran Kodi on one of them. For years I have been wanting to upgrade my RPi 3 as it cannot play any of my H.265/HEVC videos. With all the shortages, and how old the Raspberry Pi 4 is getting, I made a rather spontaneous purchase for this Orange Pi 4 LTS board. Getting it all setup is easy enough, but of course, the video (even with H.264!) nearly maxes all 6 cores and the video is chunky as it's just doing everything without any video acceleration. Even navigating the menu seems slow and delayed. I have been scouring these forums and other sources for about 12 hours now, and I am still unsure which route to go. Just as a test, I ran Kodi as root and it was much smoother in the menu system and seemed to do H.264 (in software of course, so it was working really hard). But broke Pulseaudio, as Pulse is hardcoded to not accept connections from root when it's not setup as a system-wide service. Anyway, that's not an option. Kodi doesn't need to, and shouldn't run as root. I was very excited, then extremely let down when I found this post: A custom image with custom repositories? Plus, I don't want X11 or Wayland plus a window manager, I don't need it! Either way, it *seems* to be tied to a completely different chipset. I've been up all night working on this, and I am starting to go delirious, so any help would be appreciated.

Hello everyone, Thank you for stopping buy and reading this thread. I have Orange Pi 4 LTS with the latest Armbian Jammy image (Armbian_23.8.1_Orangepi4-lts_jammy_current_6.1.50). But I also want to mention that I've tried the same thing on the "official" Ubuntu image from OrangePi website and it was the same. I need to decode and show RTSP video stream, h264 encoded. First of all, I've tried gstreamer with v4l2 codecs. I was using v4l2slh264dec from gst_plugins_bad. This is the only hardware codec in gstreamer for my device (at least available by default) and it worked fine until I started encountering a strange bug when my video getting stuck into 0.5-1 second loop forever. Anyway, I thought that I could bypass this issue by building libav/FFmpeg with v4l2 features and using it instead. However, I couldn't, and this is my problem. I am building FFmpeg from source like this: First of all, I made sure that there is no FFmpeg on my system. Then: sudo apt install libv4l-dev libsdl2-dev -y git clone https://github.com/FFmpeg/FFmpeg.git cd FFmpeg/ ./configure --enable-libv4l2 --enable-libdrm No errors/warnings. h264_v4l2m2m is in "Enabled decoders". make -j6 sudo make install sudo ldconfig ffplay -vcodec h264_v4l2m2m rtsp://192.168.0.125:8554/stream It gives me the following error: If I do not specify v4l2m2m decoder - it works just fine, but with software decoding. Drivers are present: And I have no idea how to fix this issue I will appreciate a lot any help!

Hello community! Orange pi 4 LTS with Armbian 22.11 Jammy CLI, there is a problem with launching the screen with resolutions: 1024x600 - there is no image 1024x768 - the image is there, there are ripples 1920x1080 - everything is fine Tell me how to solve this problem. uname -a Linux orangepi4-lts 5.15.80-rockchip64 #22.11.1 SMP PREEMPT Wed Nov 30 11:12:47 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux /boot/armbianEnv.txt verbosity=1 bootlogo=false overlay_prefix=rockchip fdtfile=rockchip/rk3399-orangepi-4-lts.dtb rootdev=UUID=72cc3f82-2e76-4495-99fd-8cc46a4a21db rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Link: armbianmonitor 1024x600 Link: armbianmonitor 1024x768

Hi I want to use the I2S GPIO output pins ( 26 pins ) on Orange Pi4 LTS to connect multi channel DAC. Is it possible to overlay some pins?

Hello, I would like to know how they reduce the size of the images and then, when the microSD cards are inserted into a card, they expand to fill the entire space. In other words, the same thing that Armbian images do when we use them for the first time: they are small, and then they occupy all the storage space.

Hi, does anyone know how to get hardware video acceleration on orange 4 lts? I've looked around and I saw that rk3399's multimedia support can be enabled using the rk3399 legacy multimedia framework. But that requires a legacy buster image, which doesn't exist for the orange pi. I've tried to compile it myself, but it seems the compile script won't allow it. Is it really impossible to compile a legacy kernel for orange pi 4 lts?

I have recently purchased an Orange Pi 4 LTS and attempted to run Armbian 23.02 Cinnamon version on my board. However, I could only able to connect into the network with 2.4Ghz. Everytime when I connect to the 5Ghz Network, it failed with some authentication issues (such as WPA3). I am sorry I am new to Linux.May I ask if anyone now how can I resolve the problem?

I have a usb sound card on my sbc. Im only getting left channel audio. Ive tried a different usb sound card and different cable with no luck. I run the command below with no luck, only get audio through the left speaker. speaker-test -t wav -c 2 Any ideas how to fix this?

Hello! Recently i bought an Orange Pi 4 LTS. I choosen armbian for my os. I installed it to sd card, but I wanted more. I decided to flash the system to eMMc. It was a mistake. Instead armbian-config tool, i executed armbian-install, and flashed bootloader to eMMc 🤦‍♂️. After that, i was checking the sd card, reading the logs, nothing helped. I have official 5v 4a dc adapter, factory new sd card, but my board only shines with a red LED, and does not boot into the system.

Hi Team, Greetings. I am using OPi4 LTS Emmc with 16 GB version. kernel: Linux orangepi4-lts 5.15.93-rockchip64 #23.02.2 SMP PREEMPT Fri Feb 17 23:48:36 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux. installed Armbian in Emmc worked like charm. Issue: I connected the SSD WD SN570 and format with nand -sata-install on Armbian to boot and use SSD boot. then I got successful msg all done and ready to reboot. once after the reboot I got this msg. then I tried root it doesn’t work and control-d comes back to same screen. Troubleshooting with a gentleman's assistance: 1. Booted with SD card which has Manjaro. 2. Here are the results of fstab, lsblk, fdisk etc. Suspecting that the Armbian script is broken, I purchased the 1 TB SSD for productivity purposes; however, now either the EMMC or the SSD are starting up. Any help would be appreciated!!

Hi There, Details: Linux orangepi4-lts 5.15.93-rockchip64 #23.02.2 SMP PREEMPT Fri Feb 17 23:48:36 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux I got issues from the Armbian when with Opi 4 LTS. 1.USB 3.0 or USB C not working with the kernel with WD Blue SN570 1TB (1.00)SSD failed in OPI 4 LTS. only works when i connect in USB 2.0. HW is OK, but suspecting problem with drivers (kernel). Tried below options: 1. Tried different cable but no luck in USb 3.0 port or USB c type. 2. same cable works fine in Windows and USB 2.0 3. Only not working detected in USB 3.0 port hub. Attached screenshot. Tried various trouble shooting steps in the orange Pi forum, finally suggested by expert post here. Attached the chat we had on the OrgangePi telegram and few photos of the issue. messages.html

Hi all, After a restart and after a few days go by my My Orange Pi 4 LTS randomly loses its ability to make outbound network connections. I can ssh into the box, however for some reason the routing tables are empty: > ping 192.168.1.53 ping: connect: Network is unreachable > netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface The box is connected through an ethernet cable, configured to used DHCP, but I see no IPv4 address in the interface configuration: > ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 2a01:cb15:81c2:e500:6cba:b008:2761:e29a prefixlen 64 scopeid 0x0<global> inet6 2a01:cb15:81c2:e500:e971:fd8d:4d26:e65 prefixlen 64 scopeid 0x0<global> inet6 fe80::9935:bbd1:a503:c83a prefixlen 64 scopeid 0x20<link> inet6 2a01:cb15:81c2:e500:681d:5fa0:94fd:9e1a prefixlen 64 scopeid 0x0<global> ether 72:d7:a6:97:4b:cf txqueuelen 1000 (Ethernet) RX packets 195548 bytes 16128189 (16.1 MB) RX errors 0 dropped 13442 overruns 0 frame 0 TX packets 22932 bytes 2779612 (2.7 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 31 I am new to armbian, and not sure where to go to troubleshoot from there. /etc/networks/interfaces is empty, how is eth0 configured? I can resolve the issue by issuing > sudo ip link eth0 down && sudo ip link eth0 up ... and I have added a cron entry doing just that, but obviously I would like to understand where the issue is coming from. Here is some system information: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy Linux orangepi4-lts 5.15.76-rockchip64 #22.08.8 SMP PREEMPT Sun Oct 30 10:57:32 CET 2022 aarch64 aarch64 aarch64 GNU/Linux Thanks! Franck EDIT: here is what I find in journalctl, it looks like the eth0 interface goes down shortly (4mn) after a reboot and never comes back up correctly: Apr 17 06:17:28 orangepi4-lts NetworkManager[1626]: <info> [1681705048.7753] dhcp4 (eth0): state changed new lease, address=192.168.0.102 <normal network manager startup> Apr 17 06:17:28 orangepi4-lts NetworkManager[1626]: <info> [1681705048.8306] device (eth0): Activation: successful, device activated. ... Apr 17 06:17:29 orangepi4-lts nm-dispatcher[2142]: /etc/network/if-up.d/resolved: 12: mystatedir: not found Apr 17 06:17:32 orangepi4-lts kernel: rk_gmac-dwmac fe300000.ethernet eth0: Link is Down Apr 17 06:17:32 orangepi4-lts systemd[1]: systemd-fsckd.service: Deactivated successfully. Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.3960] device (eth0): carrier: link connected Apr 17 06:17:36 orangepi4-lts kernel: rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.3968] device (eth0): ip:dhcp4: restarting Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.4136] dhcp4 (eth0): canceled DHCP transaction Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.4138] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.4139] dhcp4 (eth0): state changed no lease Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.4144] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Apr 17 06:17:36 orangepi4-lts NetworkManager[1626]: <info> [1681705056.4305] dhcp4 (eth0): state changed new lease, address=192.168.0.102 <from this point on, outbound connections are failing, e.g. Apr 17 06:17:38 orangepi4-lts telegraf[1790]: 2023-04-17T04:17:38Z E! [agent] Error writing to outputs.influxdb_v2: failed to send metrics to any configured server(s) > Apr 17 06:17:42 orangepi4-lts systemd[1]: systemd-hostnamed.service: Deactivated successfully. Apr 17 06:17:46 orangepi4-lts systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Apr 17 06:18:28 orangepi4-lts NetworkManager[1626]: <info> [1681705108.9445] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Apr 17 06:18:28 orangepi4-lts NetworkManager[1626]: <info> [1681705108.9446] dhcp4 (eth0): state changed no lease Apr 17 06:18:58 orangepi4-lts systemd-resolved[794]: eth0: Bus client set search domain list to: home Apr 17 06:18:58 orangepi4-lts systemd-resolved[794]: eth0: Bus client set DNS server list to: 192.168.0.254, 2a01:cb15:81c2:e500:7ec1:77ff:fe90:48f0 Apr 17 06:18:58 orangepi4-lts systemd[1]: Starting resolvconf-pull-resolved.service... Apr 17 06:18:58 orangepi4-lts sh[2217]: /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf Apr 17 06:19:14 orangepi4-lts systemd-resolved[794]: eth0: Bus client set DNS server list to: 2a01:cb15:81c2:e500:7ec1:77ff:fe90:48f0

Hello, i just bought new display from orangepi. But i have problem get it work with armbian 23 jally with kernel 5.15. I try get files from orange pi os with no success. Does somebody have working dts for this type of display ? Orange Pi RK3399 10.1inch LCD Touch Screen & Display Panel screen - OP1102 DTS

Hi I am wondering if anyone has had any luck using a mini PCIe to SATA adapter with an Orange Pi 4 LTS to attach a SATA hardrive? If yes, which adapter did you use? I would like to throw the OPi 4 LTS and a hard drive in a box and make a mini fanless NAS box. thanks