MX10.AC2N

  • Posts

    65
  • Joined

  • Last visited

Reputation Activity

  1. Like
    MX10.AC2N reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    No, it is led: Light Emitting Diode. The infrared receiver is not emitting anything, hence it is not a led.
    Probably there are other variants of your board which have a led that must be react on remote controller activity.
    Your board hasn't this led, but the chinese guy that wrote the dtb thought that the ir node may be left there.
     
    That's not possible: /sys is a virtual filesystem exported by kernel itself.
    Files in that directory does not really exist on partition but are generated by kernel.
     
    This is what I get on my board (with a keyboard attached):
    root@rk3318-box:~# cd /sys/class/leds/ root@rk3318-box:/sys/class/leds# ls input0::capslock input0::numlock input0::scrolllock working  
     And this is the content of working directory:
    root@rk3318-box:/sys/class/leds# cd working root@rk3318-box:/sys/class/leds/working# ls brightness device max_brightness power subsystem trigger uevent root@rk3318-box:/sys/class/leds/working# cat trigger none usb-gadget usb-host kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock usbport disk-activity disk-read disk-write ide-disk mtd nand-disk heartbeat cpu cpu0 cpu1 cpu2 cpu3 [mmc2] mmc1 activity default-on panic mmc0 mmc3 rfkill-any rfkill-none rc-feedback bluetooth-power hci0-power rfkill0 rfkill1 stmmac-1:00:link stmmac-1:00:100Mbps stmmac-1:00:10Mbps  
  2. Like
    MX10.AC2N reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    Sorry it was not 4 leds, but 3 leds in the original dtb:
    leds { compatible = "gpio-leds"; power-green { gpios = <0xfb 0x00 0x00>; linux,default-trigger = "none"; default-state = "off"; mode = <0x23>; }; net-green { gpios = <0xfb 0x01 0x00>; linux,default-trigger = "none"; default-state = "off"; mode = <0x05>; }; ir { gpios = <0xa5 0x12 0x00>; linux,default-trigger = "ir"; default-state = "off"; mode = <0x00>; }; };  
    0xfb is the phandle to rk805 node and 0xa5 is the phandle to gpio2 node.
     
    This instead is the content of the led-conf3:
    &gpio_led { pinctrl-names = "default"; pinctrl-0 = <&ir_led>; working { gpios = <&rk805 1 GPIO_ACTIVE_LOW>; default-state = "on"; linux,default-trigger = "mmc2"; mode = <35>; }; net { gpios = <&rk805 0 GPIO_ACTIVE_LOW>; linux,default-trigger = "eth0"; default-state = "off"; mode = <5>; }; ir { gpios = <&gpio2 RK_PC2 GPIO_ACTIVE_LOW>; linux,default-trigger = "ir"; default-state = "off"; mode = <0>; }; };  
    The two leds controller by rk805 are working (net-green on old dtb) and net (power-green). Working and net already match the order in the dtb you just sent me, so they should already fit your need.
    Moreover there is the specification of this other ir led, which I don't know if it is present on your board or it isn't.
     
    From what I can see, working and net are pointing to the same rk805 device and pins in both mine, yours and original dtbs, so they should work with led-conf3.
     
    Maybe triggers are not exactly what you want, but they should not be changed in the dtb: it is expected you change them for your needs using /sys/class/leds filesystem objects at startup.
    I have proposed a boot script to armbian developers to stash led state at shutdown and restore it as startup, so once you configure the leds for your tastes, they will be automatically restored at boot and there will be no hassle to do that manually.
  3. Like
    MX10.AC2N got a reaction from fabiobassa in CSC Armbian for RK3318/RK3328 TV box boards   
    Hi all,
    Little feedback, I tried installing CasaOs, CasaOS - A simple, easy-to-use, elegant open-source Family Cloud system
    it works..
    It may be useful for some of you.
    Thank you to the entire IceWhale team for this sharing..
     
    https://github.com/IceWhaleTech/CasaOS
     
     
  4. Like
    MX10.AC2N reacted to Elmojo in CSC Armbian for RK3318/RK3328 TV box boards   
    Now that is something I may be interested in! Thanks for the ideas!
  5. Like
    MX10.AC2N got a reaction from mkultra in CSC Armbian for RK3318/RK3328 TV box boards   
    You can try YUNoHost, it's cool I use it on my beelink gt-king pro with armbian-meson64 works fine and have many apps.
    Today I try install of Swizzin, on my RK3328 box that's work ( install process need root user "su -" )
    it's another possibility..
    https://github.com/swizzin/swizzin
    https://swizzin.ltd/getting-started/
  6. Like
    MX10.AC2N got a reaction from mkultra in CSC Armbian for RK3318/RK3328 TV box boards   
    You can try YUNoHost, it's cool I use it on my beelink gt-king pro with armbian-meson64 works fine and have many apps.
    Today I try install of Swizzin, on my RK3328 box that's work ( install process need root user "su -" )
    it's another possibility..
    https://github.com/swizzin/swizzin
    https://swizzin.ltd/getting-started/
  7. Like
    MX10.AC2N reacted to curse in CSC Armbian for RK3318/RK3328 TV box boards   
    My French is not the best but for me it seems like the folders named "/boot/dtb-5.14.13-rockchip64/rockchip", "/boot/dtb-5.14.13-rockchip64/rockchip/overlay" and "/var/lib/initramfs-tools" are missing and the packages "bison" and "flex" needs to be installed.
  8. Like
    MX10.AC2N reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    @MX10.AC2N
     
    As @curse noticed, probably you need the bison and flex packages to install headers. But you don't really need headers in case you don't want to compile kernel modules by yourself.
  9. Like
    MX10.AC2N reacted to jock in Testing hardware video decoding (rockchip, allwinner?)   
    Hello, recent upgrades to armbian are regarding kernel 5.15.
    I noticed that many v4l2 fixes and enhancements went into this release, so I decided to compile ffmpeg using LibreELEC patched version and mpv over it.
    mpv turns out to be statically linked with ffmpeg, so I propose it here for people who is interested in cutting edge kernel and wants to do some tests.
     
    This has been tested on Debian Bullseye and Ubuntu Hirsute on following platforms:
    Rockchip RK3228/9 (kernel 5.10, 5.14) Rockchip RK3288 (kernel 5.14) Rockchip RK3318/28 (kernel 5.15)  
    It should work on allwinner platforms too, but I didn't test it there.
    Binaries are built by me on developing boards.
     
    The binary for armhf is available here
    The binary for aarch64 is available here
     
    Dependencies for Debian Bullseye and Ubuntu Hirsute:
    apt install libass9 libbluray2 librubberband2 libsdl2-2.0-0 libva-drm2 libva-wayland2 libva-x11-2 libva2 libvdpau1 libx264-160 libx265-192 libxss1 libxv1 libfdk-aac2  
    I have had issues with dependencies on Debian Buster/Ubuntu Focal, in particular libx264-160 and libx265-192 are not available there.
    I Solved the issue downloading the packages from Debian Bullseye web page and manually installing them.
    There may be the need for some other dependency depending upon your actual installation.
     
    Run mpv in a virtual terminal (videos up to 4K) with this CLI:
    mpv --vo=gpu --hwdec=drm --gpu-hwdec-interop=drmprime-drm --drm-draw-plane=overlay --drm-drmprime-video-plane=primary <video.mp4>  
    Mpv can be run in X11 with this other CLI, but due to buffer copying it requires a good CPU - rk3228 and rk3328 won't even play 720p, rk3288 do 720p fine:
    mpv --vo=gpu --hwdec=auto-copy --gpu-context=x11egl --gpu-hwdec-interop=drmprime-drm <video.mp4>  
    This is an experiment and your mileage may vary a lot:
    H.264 codec should be well supported around the boards; H.265 has more limited support VP8 should be generally supported VP9 seems to still require some work.
  10. Like
    MX10.AC2N reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    Update!
     
    New testing minimal and xfce desktop debian images are available on first page!
    Latest kernel 5.15: plenty of fixes and upgrades for hardware video decoding Initial (and untested) support for boards with sdcard on external controller U-boot v2021.07, should make USB2 boot more reliable To test hardware video decoding capabilities follow this link to a tutorial with prebuilt mpv binary and instructions on how to use it.
  11. Like
    MX10.AC2N got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    Hi all, So I started from scratch, everything works fine without any overlays but this morning I tried adding overlays=rk3318-box-led-conf3 in armbianEnv.txt and the box freezes at startup

  12. Like
    MX10.AC2N got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    At moment, I have system just on sd-card..
    I switched to verbosity = 10 but then it scrolls too fast on the screen, suddenly I tried to film it and bring out some photos but hey it's not super easy ..
    It gives a lot of image very blurry finally I did the best, at the end I only have 5 lines with the rest of the black screen .. Hope that can help you ..
  13. Like
    MX10.AC2N got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    copy of dmesg without rk3318-box-cpu-hs and rk3318-box-led-conf3 => https://paste.yunohost.org/ogasoqumeq.vbs
  14. Like
    MX10.AC2N got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    Thank again @jock
    So on the emmc I still have the armbian bulleyes system from the station-m1 image
    So I replaced the rk3318-box.dtb file (yours is slightly heavier 63761 bytes against 62913 for the dtb already present in the image) here is the new dmesg => https://paste.yunohost.org/alatoyakud.md
  15. Like
    MX10.AC2N got a reaction from jock in CSC Armbian for RK3318/RK3328 TV box boards   
    Hi @jock and thank you for these explanations it enlightens my knowledge a little more, suddenly I left the emmc as it is and tried adding overlays, it works I was able to put led-conf3 and cpu-hs without problem here is the copy of dmesg => https://paste.yunohost.org/ewutojutal.md
     
    However I come back to your explanations, you indicate that ATF would be useful for DRM rights, suddenly this attracts my interest because I am looking for a solution to be able to read the amazon prime videos and unfortunately I still have this damn message missing drm rights .. do you know a parade with this problem? I looked a lot on Github, I even tried a few installs but nothing convincing, often the problem is that we are under arm64 (no drm rights under arm64) because with armhf apparently there will be solutions .. Y -will there be a way to build a multiarch arm64 / armhf image or maybe just an armhf image ..? For the moment I am in the idea of using a docker like https://github.com/HenningThiemann/docker-chromium-armhf ..
     
    Thanks again, apparently the problems seem to be solved, I will go back to 1.3GHz.
  16. Like
    MX10.AC2N reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    Glad to hear everything is back to normal.
    About the Amazon DRM etc... I don't know anything about. I see that libreelec is downloading chrome and extracting the widewine DRM binary to let some plugins work, but I did not ever try Amazon Prime and don't know what are the requirements for that.
    The proprietary ATF may provide a "secure" application of some sort for DRM, but this is a guess. I never digged into what in reality there is. I may guess that "secure" ATF software is tailored with some other userland software which I'm not aware of that may lie in the Android image, but this is all purely guessing
  17. Like
    MX10.AC2N got a reaction from jock in CSC Armbian for RK3318/RK3328 TV box boards   
    Hi @jock and thank you for these explanations it enlightens my knowledge a little more, suddenly I left the emmc as it is and tried adding overlays, it works I was able to put led-conf3 and cpu-hs without problem here is the copy of dmesg => https://paste.yunohost.org/ewutojutal.md
     
    However I come back to your explanations, you indicate that ATF would be useful for DRM rights, suddenly this attracts my interest because I am looking for a solution to be able to read the amazon prime videos and unfortunately I still have this damn message missing drm rights .. do you know a parade with this problem? I looked a lot on Github, I even tried a few installs but nothing convincing, often the problem is that we are under arm64 (no drm rights under arm64) because with armhf apparently there will be solutions .. Y -will there be a way to build a multiarch arm64 / armhf image or maybe just an armhf image ..? For the moment I am in the idea of using a docker like https://github.com/HenningThiemann/docker-chromium-armhf ..
     
    Thanks again, apparently the problems seem to be solved, I will go back to 1.3GHz.
  18. Like
    MX10.AC2N reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    Ahhh ok, we got the right explanation.
    Now the message is properly gone from dmesg.
     
    The problem is this: the box always boots from eMMC because there is a valid bootloader there. The bootloader is in reality composed of many parts executed one after another.
    The station-m1 bootloader contains a thing that is called ATF (Arm Trusted Firmware). This piece of software is like a protected sandbox, something that runs outside the kernel or, if you prefer, above the kernel. It can whatever do it wants, can even stop the linux kernel. In fact it controls some very low level things, like system reset, core initialization, standby/resume, and so on...
     
    It also controls the RAM frequency scaling, so memory can switch from 300 Mhz up to 800 Mhz and more.
     
    Now there are two "flavours": the proprietary rockchip ATF (compiled by rockchip with their own customizations) and the public one provided by ARM.
    The proprietary ATF is fully-fledged, but actually we don't really know what is inside: it's a blob provided by rockchip.
    The public opensource ATF has just basic features, but we know it is harmless.
     
    When I say harmless I want to stress out the fact that the ATF can peek his nose everywhere in the system, in fact it is widely used to implement DRM (Digital Rights Management) and HDCP (HDMI Copy Protection) features in tv boxes, to prevent piracy and restrict user rights in some form.
     
    A proof of some harmful behaviour (not yet fully understood) is the fact that if I run rk3318 boards with proprietary ATF, the system crashes when cpu frequency is > 1.1Ghz. 1.1Ghz is the advertised speed for the rk3318 chip.
    When I run the opensource ATF, rk3318 boards runs happy at 1.3 Ghz or even above.
     
    Now this behaviour is a bit suspect: I don't want to state that the rockchip ATF is crashing the system on purpose to limit the frequency speed of the chip, but if we consider the final effect, it is so.
     
    All this long explanation is to say that maybe the bootloader installed in the eMMC may cause headaches of some sort. I don't know if there are limiting behaviours on rk3328 too, but as we are used to say in Italy, the wolf loses the hair but does not lose the vice (ie: what they do once, they can do again)
     
    It would be wise to clean the eMMC bootloader. If you're not afraid to lose the eMMC installation, you could erase the eMMC with blkdiscard.
    If you don't want to lose it, you may make a backup of the first megabyte of the eMMC on the sdcard, zero-fill the first megabyte of the eMMC, and finally reboot.
    Otherwise leave it as-is and just and see what happens with led-conf3 overlay again.
     
  19. Like
    MX10.AC2N got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    ju@rk3328-mx10-TvBox:~/Téléchargements/deb_upgrade$ sudo apt --fix-broken install Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait Correction des dépendances... Fait Les paquets supplémentaires suivants seront installés : bison flex libsigsegv2 libssl-dev m4 Paquets suggérés : bison-doc flex-doc libssl-doc m4-doc Paquets recommandés : libfl-dev Les NOUVEAUX paquets suivants seront installés : bison flex libsigsegv2 libssl-dev m4 0 mis à jour, 5 nouvellement installés, 0 à enlever et 3 non mis à jour. 1 partiellement installés ou enlevés. Il est nécessaire de prendre 3 442 ko dans les archives. Après cette opération, 12,5 Mo d'espace disque supplémentaires seront utilisés. Souhaitez-vous continuer ? [O/n] o Réception de :1 http://deb.debian.org/debian bullseye/main arm64 libsigsegv2 arm64 2.13-1 [34,7 kB] Réception de :2 http://deb.debian.org/debian bullseye/main arm64 m4 arm64 1.4.18-5 [199 kB] Réception de :3 http://deb.debian.org/debian bullseye/main arm64 bison arm64 2:3.7.5+dfsg-1 [1 084 kB] Réception de :4 http://deb.debian.org/debian bullseye/main arm64 flex arm64 2.6.4-8 [431 kB] Réception de :5 http://deb.debian.org/debian bullseye/main arm64 libssl-dev arm64 1.1.1k-1+deb11u1 [1 693 kB] 3 442 ko réceptionnés en 1s (3 536 ko/s) Sélection du paquet libsigsegv2:arm64 précédemment désélectionné. (Lecture de la base de données... 173316 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../libsigsegv2_2.13-1_arm64.deb ... Dépaquetage de libsigsegv2:arm64 (2.13-1) ... Sélection du paquet m4 précédemment désélectionné. Préparation du dépaquetage de .../archives/m4_1.4.18-5_arm64.deb ... Dépaquetage de m4 (1.4.18-5) ... Sélection du paquet bison précédemment désélectionné. Préparation du dépaquetage de .../bison_2%3a3.7.5+dfsg-1_arm64.deb ... Dépaquetage de bison (2:3.7.5+dfsg-1) ... Sélection du paquet flex précédemment désélectionné. Préparation du dépaquetage de .../flex_2.6.4-8_arm64.deb ... Dépaquetage de flex (2.6.4-8) ... Sélection du paquet libssl-dev:arm64 précédemment désélectionné. Préparation du dépaquetage de .../libssl-dev_1.1.1k-1+deb11u1_arm64.deb ... Dépaquetage de libssl-dev:arm64 (1.1.1k-1+deb11u1) ... Paramétrage de libsigsegv2:arm64 (2.13-1) ... Paramétrage de libssl-dev:arm64 (1.1.1k-1+deb11u1) ... Paramétrage de m4 (1.4.18-5) ... Paramétrage de bison (2:3.7.5+dfsg-1) ... update-alternatives: utilisation de « /usr/bin/bison.yacc » pour fournir « /usr/bin/yacc » (yacc) en mode automatique Paramétrage de flex (2.6.4-8) ... Paramétrage de linux-headers-edge-rockchip64 (21.11.0-trunk) ... Compiling headers - please wait ... Traitement des actions différées (« triggers ») pour libc-bin (2.31-13+deb11u2) ... Traitement des actions différées (« triggers ») pour man-db (2.9.4-2) ... Traitement des actions différées (« triggers ») pour doc-base (0.11.1) ... Traitement de 1 fichier de documentation ajouté… ju@rk3328-mx10-TvBox:~/Téléchargements/deb_upgrade$ sudo dpkg -i *.deb (Lecture de la base de données... 173818 fichiers et répertoires déjà installés.) Préparation du dépaquetage de linux-dtb-edge-rockchip64_21.11.0-trunk_arm64.deb ... Dépaquetage de linux-dtb-edge-rockchip64 (21.11.0-trunk) sur (21.11.0-trunk) ... Préparation du dépaquetage de linux-headers-edge-rockchip64_21.11.0-trunk_arm64.deb ... Dépaquetage de linux-headers-edge-rockchip64 (21.11.0-trunk) sur (21.11.0-trunk) ... Préparation du dépaquetage de linux-image-edge-rockchip64_21.11.0-trunk_arm64.deb ... ls: impossible d'accéder à '/var/lib/initramfs-tools': Aucun fichier ou dossier de ce type Dépaquetage de linux-image-edge-rockchip64 (21.11.0-trunk) sur (21.11.0-trunk) ... dpkg: concernant linux-u-boot-edge-rk3318-box_21.11.0-trunk_arm64.deb contenant linux-u-boot-rk3318-box-edge : linux-u-boot-rk3318-box-current entre en conflit avec armbian-u-boot linux-u-boot-rk3318-box-edge fournit armbian-u-boot et doit être installé. dpkg: erreur de traitement de l'archive linux-u-boot-edge-rk3318-box_21.11.0-trunk_arm64.deb (--install) : paquets en conflit - linux-u-boot-rk3318-box-edge non installé Paramétrage de linux-dtb-edge-rockchip64 (21.11.0-trunk) ... Paramétrage de linux-headers-edge-rockchip64 (21.11.0-trunk) ... Compiling headers - please wait ... Paramétrage de linux-image-edge-rockchip64 (21.11.0-trunk) ... update-initramfs: Generating /boot/initrd.img-5.14.13-rockchip64 update-initramfs: Converting to u-boot format Des erreurs ont été rencontrées pendant l'exécution : linux-u-boot-edge-rk3318-box_21.11.0-trunk_arm64.deb ju@rk3328-mx10-TvBox:~/Téléchargements/deb_upgrade$  
  20. Like
    MX10.AC2N got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    @jock I try upgrade via deb. There is some errors => https://paste.yunohost.org/dirafakuve.erl
  21. Like
    MX10.AC2N got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    No worries, I'm only in the testing phase so nothing important ..
    Too bad it didn't work ..
    Hoping that my feedback can help,
    Thank you again for everything you do .. Great @jock
  22. Like
    MX10.AC2N reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    ­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 in early stages, it may or may not work for you; if and when it will be considered mature enough, it will be hopefully merged into Armbian master, but in the meantime it lives 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
        • 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 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.
       
    Development images:
    Armbian 21.11 - Debian Bullseye desktop [xfce] - mainline kernel 5.15.2 - Download from here - Build date 2021-11-12 Armbian 22.02 - Debian Bullseye minimal - mainline kernel 5.15.16 - Download from here - Build date: 2022-01-20 Armbian 21.11 - Ubuntu Hirsute desktop [xfce] - mainline kernel 5.14.14 - Download from here - Build date: 2021-10-22 Armbian 21.05 - Debian Buster minimal - legacy kernel 4.4.213 - Download from here - Build date: 2021-04-16 (not available)  
    Manual kernel upgrade:
    In case you want to upgrade to the latest kernel on a existing installation, deb packages are available here.
    Download all the deb packages in an empty directory and then install with the following command:
    sudo apt install ./*.deb  
    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 FAT 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 Run apt-mark hold linux-image-edge-rockchip64 linux-dtb-edge-rockchip64 to avoid the upgrade of kernel with the armbian official one, since it still does not contain rk3318 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; 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 ; Run apt-mark hold linux-image-edge-rockchip64 linux-dtb-edge-rockchip64 to avoid the upgrade of kernel with the armbian official one, since it still does not contain rk3318 Congratulations, Armbian is running from SD Card!  
    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
     
     
    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
     
     
  23. Like
    MX10.AC2N reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    @MX10.AC2N @curse That's true, the only way to update currently is to start from scratch and the reason is exactly the one hiphotesis by @curse is right: since the whole thing is not yet into mainline armbian, upgrading via apt is not possible. Even worse: upgrading via apt will install official armbian packages, and it would just break the installation because it would remove the existing dtbs.
     
    I'm going to add the .deb packages in the first page along the pristine images for manual upgrade, in the hope it will not break existing installations
  24. Like
    MX10.AC2N got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    Hi all,
    So I continue my feedback on a TvBox MX10 with rk3328 I tried adding overlays to have 1.4GHz and 1.5GHz but none will have allowed to use these max values in armbian-config via CPU governor (I still have 1.3GHz as the max value). Pity..
    Another thing I always try via armbian-config the docker install, it did not finish correctly and I had to be able to install docker use the method described in https://alexbacher.fr/unixlinux/installer-docker-debian/
    I tried to install docker-chromium-armhf in order to be able to have chromium with DRM rights (amazon, netflix, ...) because no DRM lib in ARM64 ..
    https://github.com/HenningThiemann/docker-chromium-armhf
    So I was able to start Chromium-armhf but unfortunately once I arrived in my Amazon primevideo account, streaming is not allowed due to lack of DRM rights
    I also attempted the construction of https://github.com/gort818/qtwebflix it works but again and again this problem of DRM lib .. If someone has found a solution I am well interested..
    @jockI see you updated but, do we have to reflash ?
    Have a nice day..
  25. Like
    MX10.AC2N reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    Update!
     
    Images on first page have been updated to kernel 5.14.13