Search the Community

DISCLAIMERS (PLEASE READ): Everything you can find in this thread (binaries, texts, code snippets, etc...) are provided AS-IS and are not part of official Armbian project. For this reason not people from Armbian project nor myself are responsible for misuse or loss of functionality of hardware. THIS POST explains very well the troubles with TV Boxes and why they are not suitable for everyone Please don't ask about support or assistance in other non-community forums nor in the official Armbian github repository, instead post your questions in this thread, in the TV Boxes forum section (hardware related) or in the Peer-to-peer support section (general linux/software related). Following the recent thread on LibreElec forum about an unofficial image for rk3229 devices, I would like to make public the work made by me and @fabiobassa about bringing rk322x support to armbian. The project is now in -> mainline Armbian <- development fork -> here <- This first page and the last 3 or 4 pages of the thread are enough to get up to date with recent developments. Many useful experiences are scattered through the thread, but the most important things are collected here in the first page, so please read it carefully! Mainline kernel is fully supported and will receive most support in the future. Legacy kernel 4.4 is deprecated, but is kept around only for special purposes. What works: Should boot and work flawlessy on all boards with RK3228a, RK3228b and RK3229, with either DDR2 and DDR3 memories. Mainline u-boot Proprietary OPTEE provided as Trusted Execution Environment (needed for DRAM frequency scaling) All 4 cores are working Ethernet Serial UART (configured at 115200 bps, not 1.5Mbps!) Thermals, CPU and DRAM frequency scaling OTG USB 2.0 port (also as boot device!) EHCI/OHCI USB 2.0 ports MMC subsystem (including eMMC, SD and sdio devices) Hardware video acceleration NAND is available only on legacy kernel. To fully boot from NAND, use the Multitool and its steP-nand installation (instructions are below) Various WIFI over SDIO are supported (SSV6051P, SSV6256P, ESP8089, Realtek chips, etc...), ssv6256p driver is available only on legacy kernel Full GPU acceleration U-boot boot order priority: first the sdcard, then the USB OTG port and eventually the internal eMMC; you can install u-boot (and the whole system) in the internal eMMC and u-boot will always check for images on external sdcard/USB first. Unbrick: Technically, rockchip devices cannot be bricked. If the internal flash does not contain a bootable system, they will always boot from the sdcard. If, for a reason, the bootable system on the internal flash is corrupted or is unable to boot correctly, you can always force the maskrom mode shorting the eMMC clock pin on the PCB. Here there is the procedure, but you can also google around if you get stuck on a faulty bootloader, the technique is pretty simple and requires a simple screwdriver. There are however some unfortunate cases (expecially newer boards) where shorting the eMMC clock pin is difficult or impossibile, like eMMC or eMCP BGA chips with no exposed pins. In those cases pay double attention when burning something on the internal eMMC/eMCP and always test first the image from the sdcard to be sure it works before burning anything on eMMC/eMCP. Some useful links with pins, pads or procedures for some boards: Generic procedure for boards with non-BGA eMMC MXQPRO_V71 - eMCP H20 - eMCP ZQ01 - eMCP NAND vs eMMC vs eMCP difference: RK3228 and RK3229 tv boxes comes with three different flash memory chips: eMMC, NAND and eMCP. It does not depend upon the market name of the tv box and neither the internal board; manufacturers put whatever they find cheaper when they buy the components. NAND chip is just the non-volatile memory eMMC chip contains both the non-volatile memory plus a controller. eMCP chip contains the non-volatile memory, a controller for the non-volatile memory (like eMMC), but also contains a bank of DDR SDRAM memory on the same physical chip. The difference is very important, because eMMC and eMCP are far easier to support at various levels: the controller deals with the physical characteristics of the non-volatile memory, so the software has no to deal with. NAND chips instead are harder to support, because the software is required to deal with the physical characteristics and non-standard things that depends upon the NAND manufacturer. If you have a NAND chips you're unlucky because mainline kernel currently cannot access it, but also because you need special care and instructions explained later. You can discover if you have a NAND, eMMC or eMCP chip looking on the board are reading the signature on the flash memory chip. The Multitool (see later) also can detect which chip you have onboard: the program will warn you at startup if you have a NAND chip. NAND bootloader upgrade: IMPORTANT: don't do this is you have an eMMC or eMCP; skip this paragraph if you are unsure too! For very expert people who are having issues when (re)booting images, there is the chance to upgrade the bootloader on NAND. The NAND bootloader is nothing else than a regular idbloader (see official rockchip documentation) but contains some bits to correctly access the data on your flash memory. Upgrading requires to erase the existing flash content, in the worst case will require you to follow the Unbrick procedure above or restore an older but more compatible bootloader. If you are not mentally ready to overcome possible further issues, don't do this! The detailed instructions and the binaries are available at this post Multimedia: Mainline kernel: 3D acceleration is provided by Lima driver and is already enabled. Hardware video decoding: https://forum.armbian.com/topic/19258-testing-hardware-video-decoding-rockchip-allwinner/ Deprecated legacy kernel: multimedia features, like OpenGL/OpenGL ES acceleration, hardware accelerated Kodi, ffmpeg and mpv you can take a look to this post An effective tutorial from @Hai Nguyen on how to configure a box as a hi-quality music player using an USB audio card, and controlling it via remote control is available in this post Brief explanation about kernel naming: current kernel is the mainline LTS kernel version, most maintained and tested. This is the suggested version for production devices. If you don't know what to pick, pick this. legacy kernel (version 4.4) is provided by manufacturer; it is deprecated, unmaintained and not suggested. edge kernel is the development mainline kernel version, with experimental features and drivers; usually stable but perhaps suitable for production devices. You can switch from one kernel flavour to another using armbian-config or manually via apt. Installation (via SD card): Building: You can build your own image follow the common steps to build armbian for other tv boxes devices: when you are in the moment to choose the target board, switch to CSC/TVB/EOL boards and select "rk322x-box" from the list. Download prebuilt images from the following links: Archive builds (GPG-signed) - https://imola.armbian.com/dl/rk322x-box/archive/ SUGGESTED - Nightly built from trunk each week by Armbian servers (GPG-signed) - https://github.com/armbian/community Old images provided by me (unsigned and outdated) - https://users.armbian.com/jock/rk322x/armbian/stable Archived/older images: https://armbian.hosthatch.com/archive/rk322x-box/archive/ Multitool: The Multitool is a small but powerful tool to do quick backup/restore of internal flash, but also burn images and general system rescue and maintenance via terminal or SSH. Compressed images will be uncompressed on fly. Multitool - A small but powerful image for RK322x TV Box maintenance (instructions to access via network here) Quick installation instructions on eMMC: Build or download your preferred Armbian image and a copy of the Multitool; Burn the Multitool on an SD card; once done, place the Armbian image in images folder of the SD card NTFS partition; Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears; OPTIONAL: you can do a backup of the existing firmware with "Backup flash" menu option; Choose "Burn image to flash" from the menu, then select the destination device (usually mmcblk2) and the image to burn; Wait for the process to complete, then choose "Shutdown" from main menu; Unplug the power cord and the SD card, then replug the power cord; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt. On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run sudo rk322x-config and select your board characteristics to enable leds, wifi chips, high-speed eMMC, etc... Run sudo armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed and configured! Despite the procedure above is simple and reliable, I always recommend to first test that your device boots Armbian images from SD Card. Due to the really large hardware variety, there is the rare chance that the images proposed here may not boot. If a bad image is burned in eMMC, the box may not boot anymore forcing you to follow the unbrick section at the top of this post. Quick installation instructions on NAND: Build or download your preferred Armbian image and a copy of the Multitool; Burn the Multitool on an SD card; once done, place the Armbian legacy kernel image in images folder of the SD card NTFS partition; Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears; OPTIONAL: you can do a backup of the existing firmware with "Backup flash" menu option; Choose "Burn Armbian image via steP-nand" from the menu, then select the destination device (usually rknand0) and the image to burn; Wait for the process to complete, then choose "Shutdown" from main menu; Unplug the power cord and the SD card, then replug the power cord; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt. On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run sudo rk322x-config and select your board characteristics to enable leds, wifi chips, etc... Run armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed! Alternative: you can install the bootloader in NAND and let it boot from SD Card or USB: Download a copy of the Multitool and burn it on an SD card; Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears; RECOMMENDED: make a backup of the existing firmware with "Backup flash" menu option; Choose "Install Jump Start for Armbian" menu option: the Jump Start uses the internal NAND to boot from external SD Card or external USB Stick; Follow the general instructions to boot from SD Card below, skip the first erase eMMC step. Quick installation instructions to boot from SD Card: If you are already running Armbian from eMMC, skip to the next step. Instead if you are running the original firmware you need to first erase the internal eMMC; to do so download the Multitool, burn it on an SD Card, plug the SD Card and power the TV Box. Use "Backup flash" if you want to do a backup of the existing firmware, then choose "Erase flash" menu option. Build or download your preferred Armbian image; Uncompress and burn the Armbian image on the SD Card; Plug the SD Card in the TV Box and power it on; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt; On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run sudo rk322x-config and select your board characteristics to enable leds, wifi chips, high-speed eMMC or NAND, etc... Run armbian-config to configure timezone, locales and other personal options, or also to transfer the SD Card installation to internal eMMC; Congratulations, Armbian is running from SD Card! A note about boot device order: With Armbian also comes mainline U-boot. If you install Armbian or just the bootloader in the eMMC or the Jump Start on internal NAND, the bootloader will look for valid bootable images in this order: External SD Card External USB Stick in OTG Port Internal eMMC Installation (without SD card, board with eMMC) If you have no sd card slot and your board has an eMMC, you can burn the armbian image directly on the internal eMMC using rkdeveloptool and a male-to-male USB cable: Download your preferred Armbian image from Armbian download page and decompress it. Download the rk322x bootloader: rk322x_loader_v1.10.238_256.bin Download a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. Unplug the power cord from the tv box Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everything went well, run lsusb: you should see a device with ID 2207:320b Run sudo rkdeveloptool rd 3 (if this fails don't worry and proceed to next step) Run sudo rkdeveloptool db rk322x_loader_v1.10.238_256.bin Run sudo rkdeveloptool wl 0x0 image.img (change image.img this with the real Armbian image filename) Unplug the power cord Done! Installation (without SD card, board with NAND) If you are in the unfortunate case you can't use an SD card for installation and your board has a NAND chip, you still have an option to use the quick Multitool installation steps via USB. Obtain a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. Unplug the power cord from the tv box Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everyting went well, using lsusb you should see a device with ID 2207:320b Run sudo rkdeveloptool wl 0x4000 u-boot-main.img (download u-boot-main.img.xz , don't forget to decompress it!) Unplug the power cord Now you can follow the instructions on how to install on eMMC/NAND via SD card, just use instead an USB stick to do all the operations and plug it into the USB OTG port. Once you reboot, USB OTG port will be used as a boot device. NOTE: NAND users without SD slot may be unhappy to know that it will be difficult to do extra maintenance with Multitool in case something breaks in the installed Armbian system: installing u-boot-main.img makes the installed system unbootable because it is missing the NAND driver. Alternative backup, restore and erase flash for EXPERTS: These backup, restore and erase flash procedures are for experts only. They are kept here mostly for reference, since the Multitool is perfectly able to do same from a very comfy interface and is the suggested way to do maintenance. Backup: Obtain a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. If you prefer, you can compile it yourself from the sources available at official rockchip repository Unplug the power cord from the tv box Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everyting went well, using lsusb you should see a device with ID 2207:320b change directory and move into rkbin/tools directory, run ./rkdeveloptool rfi then take note of the FLASH SIZE megabytes (my eMMC is 8Gb, rkdeveloptool reports 7393 megabytes) run ./rkdeveloptool rl 0x0 $((FLASH_SIZE * 2048)) backup.data (change FLASH_SIZE with the value you obtained the step before) once done, the internal eMMC is backed up to backup.data file Restore: first we have to restore the original bootloader, then restore the original firmware. Running rkdeveloptool with these switches will accomplish both the jobs: ./rkdeveloptool db rk322x_loader_v1.10.238_256.bin Downloading bootloader succeeded. ./rkdeveloptool ul rk322x_loader_v1.10.238_256.bin Upgrading loader succeeded. ./rkdeveloptool wl 0x0 backup.data Write LBA from file (100%) Download here: Erase the flash memory: clearing the internal eMMC/NAND memory makes the SoC look for external SD Card as first boot option. If there isn't any suitable SD Card, the SoC enters maskrom mode, which can then be used for full eMMC/NAND access using rkdeveloptool. This is perfectly fine if your box has an eMMC flash memory. NOTE: In case you have a NAND flash memory this option is however discouraged. The original bootloader contains some special parameters to correctly access the data. Clearing the flash memory will probably garbage the NAND data and restoring the bootloader may require some special instructions. Obtain a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. If you prefer, you can compile it yourself from the sources available at official rockchip repository Unplug the power cord from the board Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everyting went well, using lsusb you should see a device with ID 2207:320b run ./rkdeveloptool ef and wait a few seconds once done, the internal eMMC is erased and the device will boot from the sdcard from now on Partecipation and debugging: If you want to partecipate or need help debugging issues, do not hesitate to share your experience with the installation procedure of the boxes. In case of issues and missed support, provide as many as possible of these things is very useful to try and bring support for an unsupported board: some photos of both sides of the board. Details of the eMMC, DDR and Wifi chips are very useful! upload the device tree binary (dtb) of your device. We can understand a lot of things of the hardware from that small piece of data; and alternative is a link to the original firmware (you can do a full backup with the Multitool); dmesg and other logs (use armbianmonitor -u that automatically collects and uploads the logs online) attach a serial converter to the device and provide the output of the serial port; Critics, suggestions and contributions are welcome! Credits: @fabiobassa for his ideas, inspiration, great generosity in giving the boards for development and testing. The project of bringing rk322x into armbian would not have begun without his support! Justin Swartz, for his work and research to bring mainline linux on rk3229 (repository here) @knaerzche for his great contribution to libreelec support and mainline patches @Alex83 for his patience in testing the NAND bootloader upgrade procedure on his board @Jason Duhamell for his generous donation that allowed researching eMCP boards and esp8089 wifi chip

­DISCLAIMER (PLEASE READ): everything you can find in this thread (binaries, texts, code snippets, etc...) are provided AS-IS and are not part of official Armbian project. For this reason not people from Armbian project nor myself are responsible for misuse or loss of functionality of hardware. Please don't ask about support or assistance in other non-community forums nor in the official Armbian github repository, instead post your questions in this thread, in the TV Boxes forum section (hardware related) or in the Peer-to-peer support section (general linux/software related). Thank you! This thread is to give stable and mature long-term range support to rk3318/rk3328 found in many tv boxes in Armbian project as Community Supported Configuration (CSC). The current work is mainlined into Armbian project, but your mileage may vary; most recent developments live on my personal fork on github -> here <- Important notes: is just a personal opinion, but apparently widely supported, that rk3318 chip is not an official rockchip part. They probably are scrap rk3328 parts which have not passed conformance tests but are sold anyway to tv boxes manufacturers. They don’t reach the same operating frequency of the rk3328, have much higher leakage currents (and thus higher temperatures) and often the boards they are installed on are low quality with low quality components, in fact a very very common issue is the eMMC failure due to bad parts and bad soldering. So said, I personally suggest not to buy any rk3318 tv box, but instead find a properly supported SBC (Single Board Computer) if you need a reliable product. In the unfortunate case you already have such product, this thread may help you have some fun with them. What works: • Works on RK3318 and RK3328 TV boxes with DDR3 memories • Mainline u-boot • Mainline ATF provided as Trusted Execution Environment • All 4 cores are working • Ethernet • Serial UART (configured at stock 1.5Mbps) • Thermals and frequency scaling • OTG USB 2.0 port (also as boot device!) • EHCI/OHCI USB 2.0 ports and XHCI USB 3.0 ports • MMC subsystem (including , SD and sdio devices) • Hardware video acceleration (fully supported via RKMPP on legacy kernel, support via hantro and rkvdec kernel driver on mainline) • Various WIFI over SDIO are supported • Full acceleration on legacy kernel and mainline kernel • U-boot boot order priority: first the sdcard, then the USB OTG port and eventually the internal ; you can install u-boot (and the whole system) in the internal and u-boot will always check for images on external sdcard/USB first. Unbrick: Technically, rockchip devices cannot be bricked. If the internal flash does not contain a bootable system, they will always boot from the sdcard. If, for a reason, the bootable system on the internal flash is corrupted or is unable to boot correctly, you can always force the maskrom mode shorting the clock pin on the PCB. The procedure is explained here for rk322x, but for rk3318/28 is the same. In most of the rk3318/28 boards, shorting the clock pin is difficult or impossible because eMMC are BGA chips with no exposed pins. Pay double attention when burning something on the internal flash memory and always test first the image booting from the sdcard to be sure it works before burning anything in internal flash. This is a list of posts where forum users have been able to spot the eMMC clock pin to trigger the maskrom mode: H96 Max+ (board signature: RK3318_V1.4) by @Gausus X88 PRO 10 (board signature: X88_PRO_B) by @mathgaming Ninkbox N1 Max RK3318 by @enigmasphinx Partecipation and debugging: If you want to partecipate or need help debugging issues, do not hesitate to share your experience with the installation procedure of the boxes. In case of issues and missed support, provide as many as possible of these things is very useful to try and bring support for an unsupported board: some photos of both sides of the board. Details of the eMMC, DDR and Wifi chips are very useful! upload the device tree binary (dtb) of your device. We can understand a lot of things of the hardware from that small piece of data; and alternative is a link to the original firmware (you can do a full backup with the Multitool); dmesg and other logs (use armbianmonitor -u that automatically collects and uploads the logs online) attach a serial converter to the device and provide the output of the serial port; Multimedia: Mainline kernel: 3D acceleration is provided by Lima driver and is already enabled. Hardware video decoding: https://forum.armbian.com/topic/19258-testing-hardware-video-decoding-rockchip-allwinner/ Legacy kernel: If you need multimedia features, like OpenGL/OpenGL ES acceleration, hardware accelerated Kodi, ffmpeg and mpv you can take a look to this post Installation (via SD card): Building: You can build your own image follow the common steps to build armbian for other tv boxes devices: when you are in the moment to choose the target board, switch to /TVB/ boards and select "rk3318-box" from the list. Prebuilt images: Archived images - built by Armbian servers and GPG-signed: https://imola.armbian.com/dl/rk3318-box/archive/ Nightly stables - built from trunk by Armbian servers and GPG-signed: https://github.com/armbian/community Stables provided by me (unsigned): https://users.armbian.com/jock/rk3318/ Multitool: Multitool - A small but powerful image for RK3318/RK3328 TV Box maintenance. Download it from here Quick installation instructions on eMMC: Build or download your preferred Armbian image and a copy of the Multitool; Burn the Multitool on an SD card; once done, place the Armbian image in images folder of the SD card NTFS partition; Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears; OPTIONAL: you can do a backup of the existing firmware with "Backup flash" menu option; Choose "Burn image to flash" from the menu, then select the destination device (usually mmcblk2) and the image to burn; Wait for the process to complete, then choose "Shutdown" from main menu; Unplug the power cord and the SD card, then replug the power cord; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt. On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run rk3318-config to configure the board specific options Run armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed! Despite the procedure above is simple and reliable, I always recommend to first test that your device boots Armbian images from SD Card. Due to the really large hardware variety, there is the rare chance that the images proposed here may not boot. If a bad image is burned in , the box may not boot anymore forcing you to follow the unbrick section at the top of this post. Quick installation instructions to boot from SD Card: If you are already running Armbian from eMMC, skip to the next step. Instead if you are running the original firmware you need to first erase the internal flash; to do so download the Multitool, burn it on an SD Card, plug the SD Card and power the TV Box. Use "Backup flash" if you want to do a backup of the existing firmware, then choose "Erase flash" menu option. Build or download your preferred Armbian image; Uncompress and burn the Armbian image on the SD Card; Plug the SD Card in the TV Box and power it on; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt; On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run rk3318-config to configure the board specific options Run armbian-config to configure timezone, locales and other personal options, or also to transfer the SD Card installation to internal ; Congratulations, Armbian is running from SD Card! Tutorial - How to install Armbian on your TV Box (by @awawa) : https://www.hyperhdr.eu/2022/01/tv-box-mania-i-part-x88-pro-10.html A note about boot device order: With Armbian also comes mainline U-boot. If you install Armbian, the bootloader will look for valid bootable images in this order: External SD Card External USB Stick in OTG Port Internal The Multitool does not boot / How to burn image directly on eMMC: Some boards have the sdcard attached to an auxiliary (called also sdmmc_ext or external) controller which is not the common one. Forum findings declare that those boards are not able to boot from sdcard with stock firmware and they neither do in maskrom mode: the stock firmware always boots even if you put the multitool on sdcard. In such case, burning images directly on eMMC is the only way to have a working Armbian installation. You can follow these instructions by @fabiobassa to burn images directly on eMMC: https://forum.armbian.com/topic/17597-csc-armbian-for-rk3318rk3328-tv-box-boards/?do=findComment&comment=130453 Notes and special hardware: Script to change DDR memory frequency here Wireless chip AP2734, SP2734, HY2734C and similars: they are clones of AmPAK AP6334 which is combo wifi + bluetooth of broadcom BCM4334/B0 chips. You may need a special nvram file, instructions by @paradigman are here Critics, suggestions and contributions are welcome! Credits: @fabiobassa for his ideas, inspiration, great generosity in giving the boards for development and testing. The project of bringing rk3318 into armbian would not have begun without his support! @hexdump for his precious support in early testing, ideas and suggestions @MX10.AC2Nfor his patience in testing mxq-rk3328-d4 board support All the rockhip64 maintainers at Armbian project who have done and do most of the work to support the platform

Here is a serial log from the Bookworm 6.6.31 minimal release. Verbosity=7 this time. OPiPC2-uart.txt

I used python script with Orange pi zero 3 (Armbian_community_24.8.0-trunk.6_Orangepizero3_bookworm_current_6.6.31_minimal.img) Observation: 1) /dev/ttyS1 is actually Serial 2 as per pin diagram as per Orange Pi Zero 3 - Armbian web page 2) /dev/ttyS2 is actually Serial 5 as per pin diagram as per Orange Pi Zero 3 - Armbian web page 3) even if I set rtscts=True in crateing object ser in above script, there is no output on rts or cts pin. I am looking forward to have RTS pin remain high during transmission to easily integrate ic for RS485 communication. I was glad that Amrbian for Orange Pi Zero 3 has out of the box RTS CTS pin support which otherwise is a complicated matter for me. Please guide how to make the serial port work along with RTS pin to remain high during transmission of data. Regards

Hi guys, first of all I want to thanks for Nike efforts and care with all people. I Bought a Transpeed M98 plus and need your help. usually don't ask questions in topics, because almost always just have the answer in already posted in past messengers, but I read all the topic and tried everything relative to my box, but cant boot over SD Card ou USB stick. If I power on my box pressing the bottom behind the P2 jack, The led is just red and no image in screen, In Uart there are none this way. If I boot no pressing the bottom, the Uart shows the logo, but doesn't appear the box try to boot from SD, it starts directly from internal memory. I had same problem in a RK322x box and solved it installing a new loader in it, but I see no similar thing for the Transpeed M98 Plus. I miss anything? You or other could help me with ant tips? P.S. I'm Brazilian, and my English is not so good, sorry any mistake.

Purchase Link This should be a fun one. Bought the 4GB/128GB variant. AP6330 Wifi Stock software is a really, really bad Android TV port. Looks like a Google Pixel 5 image that has had RK3528 support hacked into it. Some parts report the device as Pixel 5, others MX10. RKdumper wouldn't work. Wifi is hardcoded to China region in the kernel commandline, so wifi doesn't work in North America. Boots into a setup wizard that can't be closed, and forces an internet connection. Since wifi is broken out of the box, had to use ethernet to get past the setup wizard. Transpeed does not have a website or offer stock firmware. The vendor I purchased it from refused to supply a stock image. Image was pre-rooted, so used ethernet+adb to adb pull the entire flash chip. Unfortunately the Android partitions appear to be encrypted and only show gibberish directory names. Was able to use extract-dtb on one of the raw binary partitions to get the stock DTB, which is all I cared about anyway. It is pretty close to an existing one in Armbian (rk3528-demo1-lp4-v10) Located and soldered the tiny UART pads without destroying the box. Tried my different garbage clone USB UART adapters to find one that could handle RockChip 1.5 megabit over serial, fake CH340G did the job, fake CP2102 would not. May the best fake product win! Followed @Hqnicolas guidance from this thread and used the hinlink-h28k trunk release with 5.10 kernel as a base, and changed the dtb referenced in armbianenv to the stock android DTB extracted from the device, and of course it would not boot. Lots of errors, kernel panics on UART, errors from SD reader. Changed to Kernel 6.1 base hinlink-h28k image, and tried rk3528-demo1-lp4-v10.dtb, that one almost boots but doesn't see the SD card so can't mount root filesystem. Began DTB surgery, added pieces of the SD card initialization from the factory DTB to the rk3528-demo1-lp4-v10.dtb, got it to boot. Black USB port dead, Blue USB port working. No HDMI output on console (only UART) but does load XFCE when the GUI autostarts. Will keep slicing and dicing DTB to gain functions. Will need to drop in proper NVRAM file to get AP6330 working as I've had to do on other boards. //rk3528-demo1-lp4-v10.dts SD Not Detected mmc@ffc30000 { compatible = "rockchip,rk3528-dw-mshc\0rockchip,rk3288-dw-mshc"; reg = <0x00 0xffc30000 0x00 0x4000>; interrupts = <0x00 0x85 0x04>; max-frequency = <0x8f0d180>; clocks = <0x02 0x198 0x02 0x197 0x7a 0x01 0x7a 0x02>; clock-names = "biu\0ciu\0ciu-drive\0ciu-sample"; fifo-depth = <0x100>; resets = <0x02 0x2a9>; reset-names = "reset"; rockchip,use-v2-tuning; status = "disabled"; phandle = <0x10e>; }; //Factory DTB - SD reader stuck Busy, can't select voltage etc. mmc@ffc30000 { compatible = "rockchip,rk3528-dw-mshc\0rockchip,rk3288-dw-mshc"; reg = <0x00 0xffc30000 0x00 0x4000>; interrupts = <0x00 0x85 0x04>; max-frequency = <0x8f0d180>; clocks = <0x02 0x198 0x02 0x197 0x68 0x01 0x68 0x02>; clock-names = "biu\0ciu\0ciu-drive\0ciu-sample"; fifo-depth = <0x100>; resets = <0x02 0x2a9>; reset-names = "reset"; rockchip,use-v2-tuning; //status = "disabled" status = "okay"; bus-width = <0x04>; cap-mmc-highspeed; cap-sd-highspeed; disable-wp; pinctrl-names = "default"; pinctrl-0 = <0x6d 0x6e 0x6f 0x70>; rockchip,default-sample-phase = <0x5a>; supports-sd; sd-uhs-sdr12; sd-uhs-sdr25; sd-uhs-sdr50; sd-uhs-sdr104; phandle = <0xff>; }; //Combo that works enough to boot mmc@ffc30000 { compatible = "rockchip,rk3528-dw-mshc\0rockchip,rk3288-dw-mshc"; reg = <0x00 0xffc30000 0x00 0x4000>; interrupts = <0x00 0x85 0x04>; max-frequency = <0x8f0d180>; //clocks = <0x02 0x198 0x02 0x197 0x7a 0x01 0x7a 0x02>; clocks = <0x02 0x198 0x02 0x197 0x68 0x01 0x68 0x02>; clock-names = "biu\0ciu\0ciu-drive\0ciu-sample"; fifo-depth = <0x100>; resets = <0x02 0x2a9>; reset-names = "reset"; rockchip,use-v2-tuning; //status = "disabled"; //from stock dtb status = "okay"; bus-width = <0x04>; //cap-mmc-highspeed; //cap-sd-highspeed; disable-wp; pinctrl-names = "default"; pinctrl-0 = <0x6d 0x6e 0x6f 0x70>; //rockchip,default-sample-phase = <0x5a>; supports-sd; //sd-uhs-sdr12; //sd-uhs-sdr25; //sd-uhs-sdr50; //sd-uhs-sdr104; //end from stock dtb phandle = <0x10e>; }; rk3528-transpeed-8k-ultra-hd-mx10.dts

Refer to https://debug.armbian.de to get full-fledged debug logs via UART. @amazingfate can you confirm vendor doesnt work properly?

Hello Armbian Team I have one banana pi r2 pro board(https://wiki.banana-pi.org/Banana_Pi_BPI-R2_Pro). I used Armbian_community_24.5.0-trunk.667_Bananapir2pro_bookworm_current_6.6.31_minimal.img(https://github.com/armbian/community/releases/download/24.5.0-trunk.667/Armbian_community_24.5.0-trunk.667_Bananapir2pro_bookworm_current_6.6.31_minimal.img.xz) . I want to use 4 serial port. But when I tried to "cat" command, it gives Input/output error. I tried to screen too but it terminated immediately. it can see there is 7 uart interface ,but only ttyS2 works, for terminal how can I use other uart interfaces. :~# ls -l /dev/ttyS* crw-rw---- 1 root dialout 4, 64 May 24 14:17 /dev/ttyS0 crw-rw---- 1 root dialout 4, 65 May 24 14:17 /dev/ttyS1 crw------- 1 root tty 4, 66 May 24 14:22 /dev/ttyS2 crw-rw---- 1 root dialout 4, 67 May 24 14:17 /dev/ttyS3 crw-rw---- 1 root dialout 4, 68 May 24 14:17 /dev/ttyS4 crw-rw---- 1 root dialout 4, 69 May 24 14:17 /dev/ttyS5 crw-rw---- 1 root dialout 4, 70 May 24 14:17 /dev/ttyS6 crw-rw---- 1 root dialout 4, 71 May 24 14:17 /dev/ttyS7 Thanks, Best regards

My problem seems to have nothing todo with hardware at all. None of my problems have their source in the hardware. My Idea was that "Armbian" and "sunxi" sounds like a solution to get my project running, but as longer as I'm trying it gets clearer and clearer that it isn't a solution, it's the source of the problems. "community support" should get renamed to "no support", you are at you own. I've tried a year before and it was impossible to ad a 2nd uart running with that overlay mechanism, but X11 worked and ethernet worked. Now a year later the uart works but other things are broken. The documentation isn't better as before, you get hundrets of outdated hints or websites with dead links. Sorry, if I have to investigate all things myself w/o documentation or any help from other users or the developers, I could use FreeBSD where I'm familiar with., but there are still other linuxes to try, plain debian and openwrt. I'm giving up here, that stuff is simply unusable like it was a year before. Regards, Holm

Hello. I received today a "H20 4K Ultra HD Quad Core CPU" Android box, with a board labeled H20-221-V1.8-B in one sticker and H20_221_V1.8_230925 on the PCB mask. The machine has 2GB of RAM and 16GB of FLASH, on a eMCP H9TQ64AAETAC from Hynix. I can boot just fine on the multitool currently available on the main thread, and I've backed up the original Android 7.0 image (available here) and cleared the internal memory, but I cannot boot from any of the Armbian images from the SD. I've tried so far: Armbian_21.02.1_Rk322x-box_buster_current_5.10.12_minimal.img.xz Armbian_24.2.5_Rk322x-box_bookworm_current_6.6.22_minimal.img.xz Armbian_community_24.8.0-trunk.6_Rk322x-box_bookworm_current_6.6.31_minimal.img.xz To no avail. This board does not seem to have UART headers so I cannot provide more detailed information about why is that the case. All I can tell is the HDMI output is dead even after waiting for a significant amount of time (10 minutes), and the blue LED that lights up with Android stays dead (with both multitool and Armbian), only having a dimly lit red one instead.

I noticed today that there was no build created yet for Radxa Rock 3C. I found the Rock 3A config file at build/config/boards/rock-3a.conf : # Rockchip RK3568 quad core 1-8GB SoC GBe eMMC USB3 BOARD_NAME="Rock 3A" BOARDFAMILY="rk35xx" BOOTCONFIG="rock-3a-rk3568_defconfig" KERNEL_TARGET="legacy,current,edge" FULL_DESKTOP="yes" BOOT_LOGO="desktop" BOOT_FDT_FILE="rockchip/rk3568-rock-3a.dtb" BOOT_SCENARIO="spl-blobs" WIREGUARD="no" BOOT_SUPPORT_SPI="yes" BOOT_SPI_RKSPI_LOADER="yes" IMAGE_PARTITION_TABLE="gpt" BOOTFS_TYPE="fat" And copied it to build/boards/rock-3c.conf . Then modified it to # Rockchip RK3566 quad core 1-8GB SoC GBe eMMC USB3 BOARD_NAME="Rock 3C" BOARDFAMILY="rk35xx" BOOTCONFIG="rock-3c-rk3566_defconfig" KERNEL_TARGET="legacy,current,edge" FULL_DESKTOP="yes" BOOT_LOGO="desktop" BOOT_FDT_FILE="rockchip/rk3566-rock-3c.dtb" BOOT_SCENARIO="spl-blobs" BOOT_SUPPORT_SPI="yes" BOOT_SPI_RKSPI_LOADER="yes" IMAGE_PARTITION_TABLE="gpt" BOOTFS_TYPE="fat" And was pleasantly surprised when it was able to build an image! 🙂 However, the booting was not so successful I get this on the UART (1500000 bps 8N1): DDR Version V1.10 20210810 ln ddrconfig:0 LP4 MR14:0x4d LPDDR4, 324MHz BW=32 Col=10 Bk=8 CS0 Row=17 CS=1 Die BW=16 Size=4096MB tdqss: cs0 dqs0: 361ps, dqs1: 289ps, dqs2: 313ps, dqs3: 217ps, change to: 324MHz PHY drv:clk:38,ca:38,DQ:30,odt:0 vrefinner:41%, vrefout:41% dram drv:40,odt:0 clk skew:0x58 change to: 528MHz PHY drv:clk:38,ca:38,DQ:30,odt:60 vrefinner:16%, vrefout:41% dram drv:40,odt:0 clk skew:0x78 change to: 780MHz PHY drv:clk:38,ca:38,DQ:30,odt:60 vrefinner:16%, vrefout:41% dram drv:40,odt:0 clk skew:0x5c change to: 1056MHz(final freq) PHY drv:clk:38,ca:38,DQ:30,odt:60 vrefinner:16%, vrefout:29% dram drv:40,odt:80 vref_ca:00000068 clk skew:0x3f cs 0: the read training result: DQS0:0x3b, DQS1:0x3d, DQS2:0x3d, DQS3:0x38, min : 0x9 0xa 0xc 0x9 0x1 0x2 0x5 0x2 , 0x8 0x9 0x5 0x1 0xb 0xd 0xf 0x9 , 0xd 0xb 0xc 0x8 0x4 0x1 0x4 0x6 , 0xb 0x6 0x6 0x1 0xf 0xe 0xd 0xe , mid :0x28 0x29 0x2b 0x28 0x1f 0x21 0x23 0x21 ,0x26 0x27 0x22 0x1f 0x29 0x2b 0x2c 0x27 , 0x2b 0x2a 0x29 0x27 0x22 0x1f 0x21 0x23 ,0x28 0x23 0x23 0x1f 0x2b 0x2b 0x29 0x2b , max :0x48 0x49 0x4b 0x47 0x3e 0x40 0x42 0x41 ,0x45 0x45 0x40 0x3e 0x47 0x49 0x4a 0x46 , 0x4a 0x49 0x46 0x46 0x41 0x3e 0x3f 0x41 ,0x45 0x41 0x40 0x3d 0x48 0x48 0x46 0x49 , range:0x3f 0x3f 0x3f 0x3e 0x3d 0x3e 0x3d 0x3f ,0x3d 0x3c 0x3b 0x3d 0x3c 0x3c 0x3b 0x3d , 0x3d 0x3e 0x3a 0x3e 0x3d 0x3d 0x3b 0x3b ,0x3a 0x3b 0x3a 0x3c 0x39 0x3a 0x39 0x3b , the write training result: DQS0:0x6f, DQS1:0x66, DQS2:0x69, DQS3:0x5c, min :0x95 0x97 0x99 0x97 0x8f 0x92 0x94 0x94 0x94 ,0x88 0x88 0x86 0x83 0x8d 0x8e 0x8e 0x8d 0x89 , 0x92 0x91 0x8e 0x8e 0x89 0x87 0x8a 0x8e 0x8d ,0x86 0x85 0x83 0x7f 0x8a 0x8a 0x88 0x8c 0x85 , mid :0xb2 0xb4 0xb6 0xb3 0xab 0xad 0xaf 0xae 0xae ,0xa6 0xa5 0xa1 0x9e 0xaa 0xaa 0xa9 0xa9 0xa6 , 0xaf 0xae 0xab 0xaa 0xa5 0xa1 0xa3 0xa9 0xa9 ,0xa4 0xa1 0xa0 0x9b 0xa7 0xa7 0xa5 0xa8 0xa2 , max :0xd0 0xd1 0xd3 0xcf 0xc7 0xc9 0xcb 0xc9 0xc9 ,0xc4 0xc3 0xbd 0xba 0xc7 0xc7 0xc5 0xc5 0xc3 , 0xcd 0xcb 0xc8 0xc6 0xc2 0xbc 0xbc 0xc4 0xc6 ,0xc2 0xbd 0xbd 0xb8 0xc5 0xc5 0xc2 0xc5 0xc0 , range:0x3b 0x3a 0x3a 0x38 0x38 0x37 0x37 0x35 0x35 ,0x3c 0x3b 0x37 0x37 0x3a 0x39 0x37 0x38 0x3a , 0x3b 0x3a 0x3a 0x38 0x39 0x35 0x32 0x36 0x39 ,0x3c 0x38 0x3a 0x39 0x3b 0x3b 0x3a 0x39 0x3b , CA Training result: cs:0 min :0x3d 0x35 0x37 0x2d 0x37 0x2c 0x38 ,0x3f 0x34 0x37 0x2c 0x37 0x2a 0x3c , cs:0 mid :0x78 0x79 0x71 0x70 0x71 0x6f 0x63 ,0x79 0x77 0x71 0x6f 0x70 0x6e 0x67 , cs:0 max :0xb3 0xbd 0xab 0xb3 0xab 0xb3 0x8e ,0xb4 0xbb 0xac 0xb2 0xaa 0xb2 0x92 , cs:0 range:0x76 0x88 0x74 0x86 0x74 0x87 0x56 ,0x75 0x87 0x75 0x86 0x73 0x88 0x56 , out U-Boot SPL board init U-Boot SPL 2017.09-armbian (Jun 10 2023 - 09:59:15) unknown raw ID phN unrecognized JEDEC id bytes: 00, 00, 00 Trying to boot from MMC2 ## Verified-boot: 0 ## Checking atf-1 0x00040000 ... sha256(5938a9cdfc...) + OK ## Checking uboot 0x00a00000 ... sha256(d801f0f359...) + OK ## Checking fdt 0x00b2e6f8 ... sha256(3ccee0dc53...) + OK ## Checking atf-2 0x00068000 ... sha256(0965dc8022...) + OK ## Checking atf-3 0xfdcd0000 ... sha256(be991af043...) + OK ## Checking atf-4 0xfdcc9000 ... sha256(695349eb36...) + OK ## Checking atf-5 0x00066000 ... sha256(315a4195a9...) + OK Jumping to U-Boot(0x00a00000) via ARM Trusted Firmware(0x00040000) Total: 237.208 ms INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-167-g81e0b993a-dirty:xsf NOTICE: BL31: Built : 11:20:08, Sep 6 2021 INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: pmu v1 is valid INFO: dfs DDR fsp_param[0].freq_mhz= 1056MHz INFO: dfs DDR fsp_param[1].freq_mhz= 324MHz INFO: dfs DDR fsp_param[2].freq_mhz= 528MHz INFO: dfs DDR fsp_param[3].freq_mhz= 780MHz INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0xa00000 INFO: SPSR = 0x3c9 U-Boot 2017.09-armbian (Jun 10 2023 - 09:59:15 +0200) Model: Radxa ROCK3 Model C PreSerial: 2, raw, 0xfe660000 DRAM: 4 GiB Sysmem: init Relocation Offset: ed34a000 Relocation fdt: eb9f63c0 - eb9fecc8 CR: M/C/I Using default environment failed to find reset-gpios property no mmc device at slot 1 dwmmc@fe2b0000: 1 (SD), dwmmc@fe2c0000: 2, sdhci@fe310000: 0 Bootdev(atags): mmc 1 MMC1: Legacy, 52Mhz PartType: EFI No misc partition boot mode: None FIT: No boot partition No resource partition No resource partition Failed to load DTB, ret=-19 Failed to get kernel dtb, ret=-19 I2c0 speed: 100000Hz vsel-gpios- not found! Error: -2 vdd_cpu init 900000 uV PMIC: RK8090 (on=0x40, off=0x00) vdd_logic init 900000 uV vdd_gpu init 900000 uV vdd_npu init 900000 uV io-domain: OK Model: Radxa ROCK3 Model C rockchip_set_serialno: could not find efuse/otp device CLK: (sync kernel. arm: enter 816000 KHz, init 816000 KHz, kernel 0N/A) apll 816000 KHz dpll 528000 KHz gpll 1188000 KHz cpll 1000000 KHz npll 1200000 KHz vpll 24000 KHz hpll 24000 KHz ppll 200000 KHz armclk 816000 KHz aclk_bus 150000 KHz pclk_bus 100000 KHz aclk_top_high 300000 KHz aclk_top_low 200000 KHz hclk_top 150000 KHz pclk_top 100000 KHz aclk_perimid 300000 KHz hclk_perimid 150000 KHz pclk_pmu 100000 KHz No misc partition Net: eth1: ethernet@fe010000 Hit key to stop autoboot('CTRL+C'): 0 failed to find reset-gpios property Device 0: unknown device switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot.scr reading /boot.scr 3252 bytes read in 2 ms (1.6 MiB/s) ## Executing script at 00c00000 Boot script loaded from mmc 1 reading /armbianEnv.txt 151 bytes read in 1 ms (147.5 KiB/s) reading /uInitrd 21588378 bytes read in 1795 ms (11.5 MiB/s) reading /Image 29331968 bytes read in 2437 ms (11.5 MiB/s) ** Unable to read file /dtb/rockchip/rk3566-rock-3c.dtb ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Default at 0xeb9f63c0 ** Unable to read file /dtb/rockchip/overlay/rk35xx-fixup.scr ** Unknown command 'kaslrseed' - try 'help' Fdt Ramdisk skip relocation No misc partition ## Loading init Ramdisk from Legacy Image at 0a200000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 21588314 Bytes = 20.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ERROR: Did not find a cmdline Flattened Device Tree Could not find a valid device tree SCRIPT FAILED: continuing... MMC error: The cmd index is 0, ret is -110 mmc_init: -110, time 4 starting USB... Bus dwc3@fcc00000: CTRL-A Z for help | 1500000 8N1 | NOR | Minicom 2.8 | VT102 | Offline | ttyUSB0 And no output on the HDMI. Any hints on what direction to dig for getting it closer to booting would be appreciated? / Kenneth

Hi everyone, i have uptabte armbian from 23.05 to 24.1 (stable relase update) in my nano pi neo air, but arter update i cant connect to device via com port from micro usb. (no avalible devices, when i connect nanopi to my PC) How i can fix it? Armbian-config? P.S. I also soldering external usb-uart and to the nano and i see that update was sucsessful, device steel working.

Hi, I've build an SD card image with in a buildroot myself, used the stable branch as suggested. "For stable branch use --branch=v23.11"..and that all worked good so far. I'm no linux guy at all and begun some investigations, installed packages and configured the system, this was an desktop variant with xfce. Somewhere in the middle of work I've got the message that a security update is available and I should do an apt upgrade..done that. Interresting for me was, that I've got an Update to Armbian 24.2.1 jammy.. ok ..then this is so. I've noticed later that I don't have any video output from X11 anymore, after the login prompt the screen gets black with an cursor above left and later is shut off entirely, but the Xserver is still running, [pre] 1125 tty7 Ssl+ 0:06 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/ru n/lightdm/root/:0 -nolisten tcp vt7 -novtswitch [/pre] xrandr output: [pre] xrandr Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 16384 x 16384 DVI-I-0 disconnected primary (normal left inverted right x axis y axis) DVI-I-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 59.95*+ 1920x1080 60.00 59.93 1680x1050 59.95 1600x1200 60.00 1440x900 74.98 59.89 1280x1024 75.02 72.00 60.02 1024x768 75.03 70.07 60.00 800x600 75.00 72.19 60.32 640x480 75.00 72.81 65.99 59.94 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DVI-D-0 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 521mm x 293mm 1920x1080 60.00*+ 50.00 1680x1050 59.95 1600x900 60.00 1440x900 59.89 1280x1024 75.02 60.02 1280x800 59.81 1280x720 60.00 50.00 1152x864 75.00 1024x768 75.03 70.07 60.00 800x600 75.00 72.19 60.32 56.25 720x576 50.00 720x480 59.94 640x480 75.00 72.81 59.94 DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) [/pre] I've fiddeled around with some commands, but I'm unable to restore the Xserver Output on the DVI Output of the Cubieboard2. I have an DVI to VGA Connector plugged in and an TFT Display with the VGA Input to the converter. I'm unable to use the vga output that is provided at the DVK521 Board (WaveShare) too and already had planned to ask here how I can switch between the Video connectors with an actual Armbian. The last thing I've done where some entries in the armbianEnv to get an 2nd uart and the 1wire Interface enabled, that worked so far, but I was logged in with ssh from my host and haven't seen the X-Display from the Cubieboard2 since the monitor was switched to DVI which is connected to the host as 2nd monitor. I don't think that there is something wrong: [pre] armbianEnv: verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 rootdev=UUID=42951d58-2c17-42a5-af83-c6eaf7357967 rootfstype=ext4 overlay_prefix=sun7i-a20 overlays=uart3 w1-gpio param_uart2_rtscts=1 param_w1_pin=PB10 param_w1_pin_int_pullup=1 #extraargs=video=HDMI-A-1:1920x1080M@60 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u [/pre] The commented out extraargs line was from Igor suggested in another thread for a problem w/o connected monitor..but changed nothing. Can someone help me please? I hadn't much todo with Xserver setup in the last years..I'm tapping around pretty much in the dark.. Kind Regards, Holm

Hi all, I'm new here and somewhat new to "modern Linux"..I'm more a BSD Guy... I'm using, administering and programming on unices since approx 1992, using FreeBSD (mostly) at home, my wife has a Laptop using Mint installed by me, but I haven't put much effort into my Linux experiences since systemd came up... Ok, approx 2 years before I've got a bunch of more or less unusual embedded HW..Beaglebone, Olinuxino with an A10, some Intel based thingy and something from AnalogDevices if I remember correctly. All of them are more or less old. Now I want to build a kind of a home automation appliance that is reading out data from 2 solar Inverters over a serial line and should process them (MQTT, PostgreSQL etc). I've decided to use an Cubiebord2 that was in the Bunch of Hardware I got, Pollin Elektronik here in Germany sold an DVK521 Kit for that board lately for cheap, so I've bought 3 pcs, the kit contains a 7" LCD with touch, but I don't want to use that (at first). My search for an more modern os brought 2 different possibilities to the daylight: 1. Using FreeBSD, 2nd Using armbian. I've decided to use the later one since the gpio capabilities seems to be more adult at was FreeBSD has. I've downloaded an Image with 6.1.30 kernel and startet experimenting. In the meantime I've set up an Ubuntu 20.4 in a Virtualbox VM and the armbian build environment, I've successfully created images that are booting and running more or less flawlessly. Bot there are loose ends in Software and Documentation. Most websites are outdated. For example I'm currently trying to bring up a 2nd serial interface (to connect the Inverters to). I kno that is should be an 2 stage process, first defining the GPIO Ports and second enabling the uart in the kernel. so far so good. Adding an overlays=uart1 to armbianEnv.txt is doing just nothing..because of the boot process on the cubieboard2. In the NAND flash resides the original u-boot with an old android version (as far as I remember) and the sd-card contains build image. The system boots, bot it seems not to read the environment from /boot at all. The armbianEnv.txt contains: [code] verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 overlay_prefix=sun7i-a20 overlays=uart1 rootdev=UUID=7d96085b-9f51-46ed-aee9-c5873b39d28c rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u [/code] ..but while booting "Loading Environment from FAT, unable to use mmc 0:1" (from my memory, not from a log). ...there is no FAT. I think to remember that I saw a FAT partition on the SD Card with some other disk image.. but not here.. and the "official" Image with 6.1.30 kernel is also not containing a FAT partition. What I'm doing wrong here? I need to enable some drivers, want I2C, OneWire und an uart.. It shouldn't be necessary to use a FAT partition? Regards, Holm

Linux cubieboard2 6.1.63-current-sunxi #1 SMP Mon Nov 20 11:52:19 CET 2023 armv7l armv7l armv7l GNU/Linux is build and runs good so far (stable version, jammy). ..at the moment I'm fighting with the keyboard mapping, got an german keyboard w/o the "<>|" key.. Tomorrow I'll look if I can enable the 2nd uart.. Regards, Holm

I've seen this question asked quite frequently here and all the posts end before there is a solution. I think it's time we had a crystal clear discussion on how it can be done. Not just for my curiosity, but for the people who've asked before and for the people who will ask in the future. The reason: Many hats/shields designed for RaspberryPi would otherwise be compatible with OrangePi if Armbian/u-boot didn't direct the debug output to UART0. UART0 is the most commonly used serial connection for hats/shields designed for RaspberryPi. OrangePi has multiple UART gpio so it would make sense for the O.S. (Armbian) to use the one that least impacts the users ability to actually use their hardware. Debug output is important but not so much so that the user cannot easily disable it.

Using a different UART is not really practical with a hat/shield designed to use UART0... It would be better for the system to use one that isn't commonly required by hats/shields to be the debug interface. I'll keep looking around.

@madeofstown I'd guess it is good to leave the default serial uart console running there as otherwise if things goofs, you may have no means to login onto the board. with the serial console, you can connect a usb-uart serial dongle and login to Armbian on the board. but if you insist you can nevertheless try going into /usr/lib/systemd/system look for those *getty* (e.g. ls *getty*), it would be one of those services. but that for debug output I'm not sure about that though, a google search I'd guess would get some leads e.g. https://superuser.com/questions/351387/how-to-stop-kernel-messages-from-flooding-my-console https://wiki.archlinux.org/title/working_with_the_serial_console I'd suggest to browse that same Orange Pi Zero 3 thread and figure out how to use a different serial uart port, there are probably more than a single uart port available on Orange Pi Zero 2W or Orange Pi Zero 3. using a different serial comm (uart) port is the correct solution in your case and you won't need to be bothered about console messages as they won't be there.

finally bluetooth is working with such config: &uart0 { status = "okay"; uart-has-rtscts; bluetooth { pinctrl-names = "default"; compatible = "brcm,bcm43438-bt"; max-speed = <4000000>; clocks = <&rk805 0x01>; clock-names = "extclk"; shutdown-gpios = <&gpio1 RK_PC5 GPIO_ACTIVE_HIGH>; host-wakeup-gpios = <&gpio1 RK_PD2 GPIO_ACTIVE_HIGH>; }; }; firmware from android partition: sha256sum BCM4343B0.hcd 2252534aa755ab2857eb9765c55eb1d917e77992b5ee2ff701955cdcda9a8c9a BCM4343B0.hcd

Armbian 24.5.0 Bookworm images (linux-6.1/linux-6.6) for TVBoxes: Vontar KK MAX / HK1 RBOX R2 / HK1 RBOX R3 (the same dts/dtb should work for these TVBoxes) Here is a dts and dtb files, working reworked for mainline: hk1-rbox-r3-profile-kernel-6.1-6.6.zip (original dts and dtb from TVBox rk-kernel-orig.zip) Checked the following: HDMI - works (need to check hot plugging) HDMI sound - works USB 2.0 - works USB 3.0 - works SPDIF - should work (I cannot to check) SD-Card booting and detection - works eMMC install on it (/sbin/nand-sata-install) and detection - works RKDevTool installing and loading images on/from eMMC - works GPU (bugs/frizzes on mainline are not canceled) - works Hardware video acceleration(except for browsers) - works Dualboot if you flash new bootloader (SD-Card boot high priority) - works Here are the compiled Armbian images (Bookworm only) with integrated dtb: https://www.mediafire.com/file/4dwf7ce922x7obq/Armbian-unofficial_24.5.0-trunk_Hk1-rbox-r3_bookworm_current_6.1.87_cinnamon_desktop.img.xz/file https://www.mediafire.com/file/fjwtxb5gjzip341/Armbian-unofficial_24.5.0-trunk_Hk1-rbox-r3_bookworm_current_6.1.87_minimal.img.xz/file https://www.mediafire.com/file/iuz4uijgjh5ry1r/Armbian-unofficial_24.5.0-trunk_Hk1-rbox-r3_bookworm_current_6.6.28_cinnamon_desktop.img.xz/file https://www.mediafire.com/file/kofyqabr5k6qxm8/Armbian-unofficial_24.5.0-trunk_Hk1-rbox-r3_bookworm_current_6.6.28_minimal.img.xz/file The one of this box itself is HK1 RBOX R3, the photo shows the pins for short to go to the Maskrom bootloader and UART pins: A working bootloader(supports dualboot) on this hardware for RKDevTool tool just in case: Loader.zip Please note that RKDevTool flashing utility only needs to flash the .img file with the bootloader, i.e. you need to unpack the .xz archive somewhere first (for ex. you can use 7-zip). -- Recommendations for installation on eMMC ---------------------------------------------------- For those who want to build Armbian themselves, here are the instructions: UPD: Added to images "f2fs-tools" package, added loader to support dualboot without touching the original Android(or other OS) image on eMMC - priority is given to SD-Card. Boot will be from SD-Card if there is on boot partition exist folder and file \boot.scr or extlinux\extlinux.conf - uboot(both: original Android and compiled for Armbian) searches for this path and file if it found this file, it will load from device which contains this file. mmc1(SD-Card) - first, mmc0(eMMC) - second. For correct priority loading it is necessary to replace the main bootloader which is in the archive Loader.zip - if you have an Android it is enough to flash only this bootloader as Loader at 0x0 offset using RKDevTool utility, the rest of the eMMC part should not be touched if the OS and settings we need are there. U-boot on eMMC must be original or Armbian and preinstalled at offset 0x4000. Instructions: (remember, uboot must be on eMMC (even the original Android or Armbian, i.e. if you erase the eMMC - the boot will not work) and this is relevant if you have installed the original MiniLoaderAll.bin, which does not support booting from SD-Card, but only from eMMC. Some TVBoxes may already have a bootloader that supports SD-card booting.). Feel free to test...

@helix afaik, no tool for that. phandles are the way how kernel navigates the device tree. BTW, you may wish to try to enable box-wlan-ap6330 or box-wlan-ap6334 device tree overlay in /boot/armbianEnv.txt and see if you advance in getting bluetooth: broadcom chips have the need for some bits in the device tree to load the driver and attach the communication "bus" (which is usually a simple UART port). Also they are very similar chips. the driver is usually capable of handling the detection of features despite you declare a different chip in device tree. You can see the source of the ap6330 overlay here And yes, you definitely need to enable the led-conf3 because the dtb declares that your board definitely has a rk805 PMIC: that's why the photo of the board is heavily suggested in the first page to get help.

Hi Werner, thanks a lot for your recommendations. I finally found some time to go back to the issue. I bought a CP2102 USB UART Adapter as you recommended in your video. The Odroid h1 has a Molex 5268-04a coonncetor mounted on its PCB. In the "ODROID Port description of UART Connector" (https://wiki.odroid.com/accessory/development/usb_uart_kit) the pins are described like follows. However, on the board itself the pins are not marked. I would not want to destroy anything here. Do you know which is which? _____UART____ |Pin 4 - VCC| |Pin 3 - RXD| |Pin 2 - TXD| |Pin 1 - GND| \___________| BTW: In the manual (https://magazine.odroid.com/wp-content/uploads/odroid-xu4-user-manual.pdf#page=7) the baud rate is specified with 115200.

Iperf3 performance using my 8821cu drivers peaked at ~135 Mbps. For experiments I bought a Fenvi AX1800 adapter. Speed with this adapter reaches 220 Mbps with Iperf3. I would have expected better, but can see the following: It seems the adapter does not connect USB3, but USB2 speed, so that might be an explanation. G root@orangepi5-2:~# iperf3 -c 192.168.1.80 Connecting to host 192.168.1.80, port 5201 [ 5] local 192.168.1.169 port 47482 connected to 192.168.1.80 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 28.4 MBytes 238 Mbits/sec 0 3.45 MBytes [ 5] 1.00-2.00 sec 24.5 MBytes 206 Mbits/sec 0 3.71 MBytes [ 5] 2.00-3.00 sec 26.6 MBytes 223 Mbits/sec 0 4.11 MBytes [ 5] 3.00-4.00 sec 25.9 MBytes 217 Mbits/sec 0 4.11 MBytes [ 5] 4.00-5.00 sec 25.9 MBytes 217 Mbits/sec 0 4.66 MBytes [ 5] 5.00-6.00 sec 26.0 MBytes 218 Mbits/sec 0 4.66 MBytes [ 5] 6.00-7.00 sec 26.0 MBytes 218 Mbits/sec 0 6.49 MBytes [ 5] 7.00-8.00 sec 25.8 MBytes 216 Mbits/sec 0 6.49 MBytes [ 5] 8.00-9.00 sec 25.6 MBytes 215 Mbits/sec 0 7.66 MBytes [ 5] 9.00-10.01 sec 26.9 MBytes 224 Mbits/sec 0 7.66 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.01 sec 262 MBytes 219 Mbits/sec 0 sender [ 5] 0.00-10.06 sec 259 MBytes 216 Mbits/sec receiver iperf Done. root@orangepi5-2:~# lsusb -t /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 480M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M |__ Port 001: Dev 002, If 0, Class=Vendor Specific Class, Driver=mt7921u, 480M /: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M /: Bus 005.Port 001: Dev 001, Class=root_hub, Driver=ohci-platform/1p, 12M |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 001: Dev 002, If 1, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 006.Port 001: Dev 001, Class=root_hub, Driver=ehci-platform/1p, 480M /: Bus 007.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 480M /: Bus 008.Port 001: Dev 001, Class=root_hub, Driver=xhci-hcd/1p, 5000M root@orangepi5-2:~# root@orangepi5-2:~# iwconfig lo no wireless extensions. end0 no wireless extensions. wlx90de80d68879 IEEE 802.11 ESSID:"yyyyyy" Mode:Managed Frequency:5.18 GHz Access Point: xx.xx.xx.xx.xx.xx Bit Rate=720.6 Mb/s Tx-Power=3 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=55/70 Signal level=-55 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:4 Missed beacon:0 root@orangepi5-2:~#

@Deoptim You have UART debug TTL and SD Card reader? lets see what you have I think you will find better support when found people with the same board

What about "Ubuntu 24.04 LTS with Rockchip Linux 6.1" anyone try to launch ubuntu-24.04-preinstalled-desktop-arm64-orangepi-3b.img.xz or ubuntu-24.04-preinstalled-desktop-arm64-radxa-zero3.img.xz image? I tried launch images on hk1-rbox-r3 TVBox with modified dtb, but no luck. UART Boot log hungs on: ... ... systemd[1]: Started systemd-journald.service - Journal Service.