Jump to content

RetroFan90

  • Posts

    45
  • Joined

  • Last visited

Reputation Activity

  1. Like
    RetroFan90 reacted to pakos96 in CSC Armbian for RK3318/RK3328 TV box boards   
    Hi,
    thanks for your reply. Sorry but I can only reply to the topic once a day. I've installed the minimal version and it's ok. No problem so far. I sent the links in the previous message in the hope that you can find something useful. I hope so
    I don't want to get the idea that I complained that it was "lagging" but it was just to be able to provide more information about my tv box and help in some way with the development.
    These are the double-sided photos of the card (if it can help):


    I am currently using the limited 1.1GHz version (although in reality the max speed is 1.01GHz), I have installed pi-hole and unbound and have not noticed any problems at the moment.
    Thanks again!
  2. Like
    RetroFan90 reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    @pakos96 Ookay, got it! Glad to hear everything is fine
    Thanks for the photos, they are always useful to inspect the board!
  3. Like
    RetroFan90 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.
       
    Stable images:
    Nightly stables - built from trunk by Armbian servers and GPG-signed: https://github.com/armbian/community Stables provided by my (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 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 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 ; 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
     
     
    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
     
     
  4. Like
    RetroFan90 reacted to usual user in CSC Armbian for RK3318/RK3328 TV box boards   
    I don't know what requirements Kivy places on the graphics stack, but since Panfrost achieves OpenGL ES 3.1 conformance on Mali-G52, it certainly makes sense to read this to understand what to expect from a lima-driven GPU. I still remember very well times when my GPU only reached almost 2.0 and the performance was quite moderate. With now 3.1 it's a big difference for daily desktop use, although my GPU isn't yet declared fully compliant. But since this is bleeding edge development, at least the current mesa mainline release is required in any case. If not even the main branch to use just implemented extentions. Kernel driver wise everything necessary should already be available and therefor mesa is where you are looking for GPU support improvements.
  5. Like
    RetroFan90 reacted to pakos96 in CSC Armbian for RK3318/RK3328 TV box boards   
    Hi,
    thank you for your work! I've tried the latest image with mainline kernel Ubuntu Hirsute on my android box bought on Amazon Italy called "Bqeel TV Box R2 PLUS 4GB +64GB CPU RK3318" (https://www.amazon.it/gp/product/B07VXMTD78).
    I installed the image on the eMMC and tried a bit to see how the performance was. It starts up correctly but it lags enough. I have created with "armbianmonitor -u" a log that maybe can help you.
    This is the specification: RK3318, 4GB RAM, 64GB ROM, WIFI AP6330.
    This is the link of the log: ix.io/3zSk (verbosity 7)
    This is the link for download the original Android ROM: https://mega.nz/file/AYlDhA7L#y7vW7S3arW995X_m5c8URa3UGVTzxm0KDrC1-aNplGw.
     
    Unfortunately I don't know how to use the soldering iron and I don't have the skills to connect a serial cable.
    Hope it can help you somehow. 
    Cheers
  6. Like
    RetroFan90 reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    Nope, it looks like there is nothing really interesting. Maybe it's just the mesa Lima driver which is just too old.
    I sorted out the display problems, but then other issues regarding the i2s bus with kernel 5.14 came up.
    I think I can build a couple of fresh images with the 5.10 kernel which is good enough for now.
  7. Like
    RetroFan90 reacted to AlwinLub in CSC Armbian for RK3318/RK3328 TV box boards   
    Thanks for the correction. I've generated a new log, http://ix.io/3zQZ
     
    Edit; I also got my Xorg log here, but i didn't see anything interesting.
     
  8. Like
    RetroFan90 reacted to AlwinLub in CSC Armbian for RK3318/RK3328 TV box boards   
    If you need someone for testing, let me know. I'm happy to test it out.
  9. Like
    RetroFan90 reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    Update!
     
    Images with mainline kernel have been updated to Debian Bullseye (minimal) and Ubuntu Hirsute (xfce desktop) with kernel 5.10.68.
    Kernel is the same major version as previous mainline images, but Bullseye and Hirsute should provide significant newer software packages (including new Mesa libraries for those interested in graphics).
  10. Like
    RetroFan90 reacted to AlwinLub in CSC Armbian for RK3318/RK3328 TV box boards   
    I've got my armbianmonitor -u log here, if it helps; http://ix.io/3zGJ. Thanks for the quick reply as always.
     
  11. Like
    RetroFan90 reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    Hmm, actually I built an newer image with kernel 5.14 and hirsute and the Lima driver is not playing nice at all.
    I tried both the stock mesa coming with Hirsute and latest development mesa and both of them cause the login screen to appear just as you describe: black screen and the cursor.
    Lima driver is somehow complaining with these lines in dmesg:
    [ 39.136659] [drm:lima_sched_timedout_job [lima]] *ERROR* lima job timeout [ 39.136801] lima ff300000.gpu: fail to save task state from Xorg pid 1654: error task list is full [ 39.136818] lima ff300000.gpu: gp task error int_state=0 status=a so I got to investigate this issue too...
     
    edit: uff... ok it seems that the issue is due to the missing operating points in the device tree. I always fall into every time there is a new kernel
  12. Like
    RetroFan90 reacted to Wester_Minsk in CSC Armbian for RK3318/RK3328 TV box boards   
    Logs complete
    Android.log Armbian eMMC.log Armbian sdcard.log
  13. Like
    RetroFan90 reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    @Wester_Minsk thanks for the logs.
    I extracted the ddrbin from the backup you posted above and made an image with that. The ddrbin is the thingy that initializes the DDR memory, an initialization with bad timings may be harmful for the system stability, so give a shot to this experimental image (it's a debian bullseye with command line only):
     
    https://users.armbian.com/jock/rk3318/Armbian_21.11.0-trunk_Rk3318-box_bullseye_current_5.10.64_minimal.img.xz
     
    edit: if you try this on sdcard, be sure to erase the eMMC completely first!
  14. Like
    RetroFan90 reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    Nope, not yet, I'm a bit busy with rk3288 at the moment, but here you go: ddrbin_v1.16.bin
  15. Like
    RetroFan90 reacted to hexdump in CSC Armbian for RK3318/RK3328 TV box boards   
    @jock - do you have this extracted ddrbin somewhere in your repos already? i was not able to find it yet ...
  16. Like
    RetroFan90 reacted to Wester_Minsk in CSC Armbian for RK3318/RK3328 TV box boards   
    https://disk.yandex.by/d/RYIADV5cMwpOmA





  17. Like
    RetroFan90 reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    @Wester_Minskthanks for the firmware and photos. I had a quick look into the device tree and it looked quite standard to me: no particular hardware like Power Management ICs or other significant differences from regular tv boxes.
    I will take a deeper look and check other compatibility things soon!
  18. Like
    RetroFan90 reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    @curse
    Sorry for the late answer, but I just spot the post edit right now.
     
    wlan and bluetooth, despite being on the same chip, are connected to the SoC in different ways: wlan is connected via high-speed sdio bus, bluetooth via common UART; also they are physically different chip parts that just share some things (the radio part), so it may happen that one work and the other does not.
     
    Since rk3318-config correctly reports the right chip, it is attached to the right sdio bus.
    Now there there may be some board peculiarities that does not make it work.
     
    In the first post of this thread there are some good things that help in debugging, in particular if you can provide photos of the board and the original firmware or the original dtb I can inspect it and try solve the issue.
    If you can spot some marking/signatures on the board, you can see if there is a match in rk3318-conf when it asks for "led/gpio configuration".
     
    At the moment there are just two supported boards: YK_RK3328 (found on my HK1 Max) and X88_PRO_B ( @lucky62's box); maybe yours is a different one that require some minor adjustment to make wifi work.
  19. Like
    RetroFan90 reacted to curse in CSC Armbian for RK3318/RK3328 TV box boards   
    Sweet. I'll do some testing and get back to you. 
     
    Edit
    Testing done. 
    Most things seem to work. 
    Ethernet OK
    HDMI Video out OK
    HDMI Audio Ok
    Bluetooth Audio OK
     
    However, I don't seem to be able to connect to WiFi. Odd since Bluetooth and WiFi is the same chip. Armbian-Config and nmcli see it, it also shows the available networks but when trying to connect. No luck. 
    rk3318-config says that I have a Broadcom BCM4335/AmPac AP6334 chip. 
    Somehow the WiFi times out after 90 seconds and after it has asked me twice for the password, which I know is correct. 
    Also, no network settings icon is visible near the clock where the sound and Bluetooth icons are. 
    No Web Browser seems to be installed, though the menu item for Web Browser is there. No problem since I had ethernet and could install a Web Browser (and without ethernet or wifi, there is no need for a browser) 
    So... H96 Max plus (written with a '+'). RK3328. 4GB RAM and 64GB eMMC. Confirmed mostly working. 
     
    Next edit
    The version I tried was: Armbian 21.08 - Ubuntu Focal desktop [xfce] - mainline kernel 5.10.41 - Build date: 2021-05-30
  20. Like
    RetroFan90 reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    Yeah, you're right: the thread title is a bit misleading, because rk3318 and rk3328 are fundamentally the same chip.
    It is so because I have no rk3328 to work on, so can't guarantee and test anything on that. People reported that the images works as well on rk3328 boards, so you're invited to try and report if it works for you.
    There are good chances that the images works fine, and ap6330 is well supported in mainline kernel, including bluetooth!
  21. Like
    RetroFan90 reacted to curse in CSC Armbian for RK3318/RK3328 TV box boards   
    I had missed this thread thinking it was only about RK3318 devices, but do I understand it correctly if I say it's for RK3328 devices as well? 
    I have a H96 Max Plus RK3328 4/64 box that I've been fighting with for a while. I mostly have had problems with the WiFi.
    Reading through this thread seems to show that the ap6330 WiFi I have isn't impossible after all. I've mostly had problems finding a good dtb, that includes it. 
    Would there be a chance that this would work on my box? 
  22. Like
    RetroFan90 reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    AFAIK there is no such tool for rk3188
  23. Like
    RetroFan90 reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    In the previous post you stated your box is an rk3188 box, this is the thread for rk3318.
    If your box is an rk3318, please provide as many as possible of the things described in the first post (logs, photos, original dtb), otherwise it is impossible to help.
    HDMI issues are common if cable is cheap, or the monitor less non usual resolution (like 1920x1200, for example)
     
  24. Like
    RetroFan90 reacted to camsaway in CSC Armbian for RK3318/RK3328 TV box boards   
    I have now tried a new Class 10 SD card and the same problem still persists. I am using the original power supply as well and there are no power issues.
    Any suggestions?
  25. Like
    RetroFan90 reacted to camsaway in CSC Armbian for RK3318/RK3328 TV box boards   
    Hi,
     
    Newbie here. I have an old CloudGate TV Box. It's an RK3188 based unit that I want to try an repurpose for Home Automation.
     
    I downloaded the multitool image, used BalenaEtcher to burn it to an SD Card. Popped the SD Card into the TV Box and turned it on.
     
    Unfortunately it just booted into the standard Android OS not the multitool. If I use the file explorer on the box it can see the SD Card and the files on it.
     
    Am I missing a step? Or is there something I need to do to boot from SD?
     
    thanks.
×
×
  • Create New...