• Content Count

  • Joined

  • Last visited

Reputation Activity

  1. Like
    jock got a reaction from hetao in rk3328 vs rk3318 which one should I choose?   
    Theoretically rk3318 is a cheap version of rk3328. We don't know yet perfectly what rockchip means with "cheap version", what is stripped down and what has been removed from rk3328 that makes it less expensive because there is no datasheet, no official launch and no technical documents about.
    It's just my guessing that maybe they reduced the video encoding/decoding media features, but some other people said that the rk3318 has a bit more powerful GPU than rk3328, and on par with s905x (which is a bit strange, because rk3318 should be the cheaper version...)
    edit: ah, rk3328 has support from armbian and mainline kernel, 3318 in theory is exactly the same but still does not appear officially anywhere
  2. Like
    jock got a reaction from suberimakuri in Start looking at 5.3.y   
    Hello, I managed to bump the rockchip-dev kernel to 5.3.y on my fork. After removing a couple of redundant patches and updating two or three of them I'm able to compile with no problems. The new kernel also boots fine on my rk3288.
    Don't know if anyone is already working on this (maybe @Igor or @TonyMac32), if my work can ease someone's else fatigue I can make a merge request from my repo to main armbian repo for code review (the single commit is here) documenting the steps I did.
  3. Like
    jock reacted to Salvador Liébana in Wayland on ARM SBCs   
  4. Like
    jock got a reaction from manuti in Recommend me a TV Box   
    About point #3, your Orange PI PC is not stuck at kernel 3.0.
    H3 chip is not the fastest nor the newest, but currently is one of the best supported in mainline kernel. There is an enduring work-in-progress for hardware decoding on mainline kernel which is progressing nicely.
    It looks like LibreElec will soon include some official H3 support. All the main peripherals are working well and 3D acceleration is available.
    As for desktop replacement, the problem with the H3 is the lacking of the thermal driver, so frequencies of the SoC are set in a conservative fashion in armbian. The experience may suffer from this.
    You may think to use a small heatsink and drive the SoC to its rated 1.4Ghz and see if it satisfactory for you. IMHO it is not powerful enough for a decent desktop replacement, but you may try and see if it suits your needs.
  5. Like
    jock reacted to NicoD in Raspberry Pi 4 Released - From $35 USD   
    Here my view on the Raspberry 4b.
    It's a high performance board, unmatched by any other qua-core. But with some issue's.
    Undevoltage still there with non RPi PSU's. sd-card is now the biggest bottleneck of it all. Tho it has doubled in speed to 40read and 20write. That's not enough for a powerful system as this.
    It's no more a pure IoT board, but more a cross-over to pc. Plenty of power, dual HDMI. Up to 4GB lpddr4 ram.
    Here my video about it.
    And here some of my test results.

    Raspberry Pi4B -------------- Raspbian Buster --------------- Blender results Default clock 1.5Ghz No fan Tinker heatsink : 1h57m23s 3v fan Tinker heatsink : 1h29m07s OC clock 1.75Ghz 3V fan : 1h19m25s 1.85Ghz 3V fan : 1h14m05s 2.00Ghz 3V fan : 1h10m24s 2.00Ghz 3V fan : 1h09m39s gpu_freq=600 sbc-bench Ubuntu arm64 ------------ default clock 3v fan Tinker heatsink : 1h21m05s 1.75Ghz 3v fan : 1h08m42s 2Ghz 3v fan : 1h00m12s sbc-bench Temperatures ------------ Big Tinker heatsink no fan idle : 58°C maxed out : 83°C heavy throttle to 1000Mhz after about 3 minutes 3V fan idle : 37°C maxed out : 50°C OC 1.75Ghz 3V fan maxed : 55°C OC 1.85Ghz 3V fan maxed : 57°C Power consumption ----------------- Default idle no wifi : 0.64A Default idle with wifi : 0.7A Default maxed : 1.3A 2Ghz over voltage 4 GPU 600Mhz idle : 0.8A maxed : 1.85A (2A with fan) Issues ------ Governor again shows falls frequency numbers. vcgencmd measure_clock arm <- show the real ferquency Undervoltage problem is still there. It requires +5.15V or it's undervolting and clocked to 600Mhz OC -- over_voltage=2 arm_freq=1750 over_voltage=4 arm_freq=2000 gpu_freq=600 SoC : Broadcom BCM2711B0 quad-core A72 1.5Ghz (up to 2Ghz) GPU : VideoCore VI @ 500Mhz RAM : LPDDR4-2400 SDRAM HDMI : dual micro HDMI 4K 60Hz + 1080p or 2x 4K 30Hz USB : 2x USB 3.0 / 2x USB 2.0 Ethernet : Gigabit Ethernet  
  6. Like
    jock got a reaction from Jens Bauer in Raspberry Pi 4 Released - From $35 USD   
    Ignoring support and documentation from the board manifacturer, GPIO pins and peripheral buses access, expandability, warranty, construction and international safety certifications... Looking just at the basic horsepower, tell us what tv box can you buy that provides 4 out-of-order A72 cores for 35$?
  7. Like
    jock reacted to erew in Installation Guide and your questions answered for TV Boxes   
    Since I originally wrote this post Ive re-written bits and included quick videos to guide you through the steps (My original post is still below).
    As Im writing other posts on other topics related to Armbian, but not relevant to install/setup, Im keeping them all on my new site, so all my updates will be on there. Id welcome any feedback (drop me a comment on here or on Also, if anyone has any specific topics they want me to take a look at, let me know. 
    As always, thanks to balbes150 for his work getting Armbian on ARM boxes.
    Index of Articles
    Youtube playlist for the videos 
    (The videos are quite quick, but are designed to go with the articles below) 
    - Hardware you need
    - Software/Downloads Installation 
    - Steps to image your SD Card/USB stick from a Windows PC
    - First boot setup
    - Updating the system, changing hostname and RDP setup
    - Includes 2 x videos showing the whole process and the extra optional steps Troubleshooting Amlogic Boot
    - What to do if your system wont even boot at all
    - Includes 1 x video showing the whole process uEnv.ini and extlinux.conf configuration
    - Editing the files and picking the right DTB.
    - What do these 2 files do and why cant I boot off emmc internal ram?
    - What should the files look like? Installing to emmc
    - Performing the install
    - What files/folder and other issues can cause problems with booting off emmc Bricked device recovery
    - How to figure whats happened when your device no longer boots
    - How to recover your device back to factory/working condition Using Clonezilla to make a compressed backup of your TF card/USB stick -
    - How to create a bootable Clonezilla USB
    - How to make a small file sized backup using Clonezilla
    - How to restore using Clonezilla
    - Includes 1 x video showing the whole process Making a Backup of your emmc via the GUI
    - What you will need
    - All the commands/screens to perform this
    - Includes 1 x video showing the whole process Making a Backup of your emmc via Command line
    - What you will need
    - All the commands/screens to perform this
    - Includes 1 x video showing the whole process Remote access/administration SSH, RDP and Webmin
    - Not Armbian specific, however very handy for those who want simple remote access or administration of their systems.
    - SSH - Setup/Use (Remote control via a command line)
    - RDP - Setup/Use (Remote control direct to the desktop of Armbian)
    - Webmin Setup/Use (Webpage based administration, setup, configuration, diagnostics, terminal access, backups, settings for just about everything etc etc etc)  
    Ive not yet written anything on fully troubleshooting a linux/armbian system that was working but now fails to boot (TS card damaged/power cut or something like that happened), though these things do happen from time to time. If you are performing a lot of configuration, it took you a long time to setup your system or you want to make a major change to your system, I highly recommend taking a look at the backup videos/instructions Ive done. 
    OnDROID is a new thing for me... and Armbian OS install is my first topic/guide on there, so if anyone wants to give me feedback or support you're welcome to drop me a message on here or OnDROID. 
    Its based on setting up the Armbian that balbes150 created (Thanks @balbes150) and all the things I picked up/learned along the way/had to hunt around the forums to try understand. 
    I use Amlogic based systems (905, 912 etc etc).... I assume things are pretty similar for Rockchip etc, but if anyone wants to post other useful information in this post!
    Contents of this post:
    Contents of this post Intro

    Example of setting up a system Example Setup on a MeCool M8S PRO w (Change your DTB file in uEnv.ini and extlinux.conf for other boxes).
    - Hardware you need
    - Software/Downloads Setting it up
    - Steps to image your SD Card/USB stick from a Windows PC
    - Installing onto the MeCool M8S PRO w (Or any other box assuming youve changed the DTB) Congratulations - If you reach here you will have a working Armbian server.

    Booting Problems and getting your system to boot Booting off SD/USB problems. uEnv.ini and extlinux.conf (Required for booting Armbian)
    - Editing the files and picking the right DTB.
    - What do these 2 files do and why cant I boot off emmc internal ram?
    - What should the files look like? Installing onto emmc/NAND - The internal hard drive of the TV box. LOST.DIR, System Volume Information and Android folders cause problems booting off eMMC/NAND.

    What to do if you brick your device. Ive done something and now my box wont boot/stuck on a splash screen/is a brick what do I do?
    - Getting the system recovered - notes
    - Doing the recovery
    I had written a previous article just over 1 year ago and things have moved on and its now far simpler/more efficient to do this… between 20 to 40 minutes depending on your speed. To get a basic working Armbian server, you only need to follow this guide. The example setup is for a MeCool M8S PRO w (4x cores, 2GB ram), though the procedure and information in here is relevant for all TV boxes.
    To be clear, on the MeCool M8S PRO w, you have to plug it in via a network cable and run the OS off an SD card or USB stick. The Bluetooth and WiFi dont (at this moment) work. So, if that is a limitation for you, either keep an eye on the Armbian forum looking for later OS builds that may work, or on there you can also find other Android TV boxes that will work. (side note, I think there are 2 revisions of the MeCool M8S Pro w.. one you can install to emmc/NAND and one you cant).
    Example Setup on a MeCool M8S PRO w

    Hardware you will need:
    MeCool M8S Pro W (or box of your choice…after researching which ones work). A Windows PC/Laptop. A micro SD card OR USB memory sick (16GB or larger recommended)  A way to plug that SD card into your Windows computer to image the Armbian OS onto it. A Cat 5 LAN cable to plug it into your Router/Switch/Network port.  
    NOTE - It looks like you will only see the option to install Armbian to eMMc memory, within Armbian Config, if you are running from an SD Card, NOT a USB stick. (As mentioned, you cannot do this with this MeCool M8S PRO w anyway, but you can with other boxes like the Beelink GT1 Mini).
    As an additional note, if you want to UPS protect your device from power outages etc, most (Im not claiming all) of these Android TV boxes (and I assume maybe Pi’s but Ive never tested so research that before you try it) support being powered from the USB ports (and the main power socket simultaneously too if you like). The RAVPOWER RP-PB078 is a battery pack for charging USB devices like phones etc. Its special trick, is that it is like an online UPS style device, meaning it can be both charging and powering your device at the same time. So, if the power cuts out, it will keep powering your device through the USB port (or you can buy a USB to 5v adapter cable if you like and use the main power port). I dont know how long for sure, but my rough estimation is this will give you about 5 to 9 hours run-time on the battery pack without any problems, plenty for small power outages.
    Armbain from here (Armbian_5.88_Aml-s905_Ubuntu_bionic_default_5.1.0_desktop_20190611) (Later builds should work fine!!)
      Win32DiskImager from here  
    Setting it up
    Steps to image your SD Card/USB stick from a Windows PC:
    Download the above files. Unzip/Extract with Armbain image file (Use WinRAR or 7Zip). Install Win32DiskImager . Insert your micro SD card or USB Stick into your PC. Run Win32DiskImager as an Administrator. In Win32DiskImager , click the folder Icon and select your Armbian Image file. Check the Device field is pointing at your SD card/USB stick you just inserted and click the Write button. Wait about 5 minutes while the SD card/USB is imaged. (takes about 2 minutes at USB3 speed)  
    The MeCool M8S PRO w and other Amlogic boards are often set to boot from external media first, however there is a simple process I will add at the bottom of this document to show you how to change the boot order if needed. The fix (as far as I know) only works on Amlogic based chipsets 905, 912, 922 etc. If you use a system based on Rockchip or something else, you will need to research the Armbian forums, which I would do ahead of time anyway if you decide to use an alternate TV Box.
    For different Android TV boxes (other than the MeCool M8S PRO w), you may need to edit the uEnv.ini and extlinux.conf file on the SD card/USB stick, to choose a different DTB file. The DTB files are effectively for choosing what hardware drivers are needed when loading the OS and different Android TV boxes will have different chipsets e.g 905, 905X2, 912, RK3399 etc. I would suggest using Notepad++ for editing this file on a Windows computer, as the file is in UNIX file format, so much easier to read with Notepad++. I will add a short explanation of uEnv.ini and extlinux.conf at the bottom of this document (though they dont need changing with the above Armbian image, when used on the MeCool M8S PRO w.
    Installing onto the MeCool M8S PRO w (Or any other box assuming youve changed the DTB)
    Place the SD card or into your MeCool box’s SD card slot, plug in a monitor, network cable to your switch/router, keyboard and mouse and then the power. Your Armbian box should now boot and will prompt you at a text command prompt to type in the Username and Password (default are root and 1234) . After this is done, it will ask you once again to type in the root password 1234 and change the root password to something else more secure. You will now be asked to create a user account, other than the root account. I created a user called openhab with a password. For the “Name” I called it openhab , ignore the other questions, leaving them blank and when asked if this is correct, say Y and press enter. (You will see references in here a user openhab, this is just the account I created. You can use any name you like)

               NOTE - if it doesnt boot to Armbian and you have the box I suggest, or an Amlogic based chipset, read the note at the bottom of this document.
      The box will now load the GUI, asking you for the password of the user account you created . Log in and you will now be at the Armbian desktop.

      From here, we want to open the Application menu at the top left > Settings > Armbian Config. Type in your password when prompted.

      In the config system that opens up, we are going to perform a few tasks pretty quickly. Setup our system keyboard locale, change the name of this computer on the network, setup SAMBA file sharing, setup Microsoft RDP for remote control access to the system.

    NOTE - On this build of Armbian with this MeCool box, Ive had a situation where it sometimes doesnt like detecting my monitor correctly when it boots, at the point it switches from the text boot to the GUI interface, meaning, you can get a black screen. So ensure RDP is enabled on your 1st boot, then you can always RDP from a windows machine to get to the GUI desktop OR, boot it with no monitor attached and after about 5 minutes, you can plug the monitor in and it usually works… As I say, only on THIS build of Armbian and THIS MeCool box, hence setting up RDP.

    You can use the keyboard cursor keys, TAB key to move around each screen and Escape will move you back a screen.

      With your cursor keys, go down to the Personal menu, select Timezone and choose your region. then back and select Keyboard and select your correct keyboard layout.

      Still on the Personal menu select Hostname. This allows you to change the name of the computer to whatever you want to call it on your network (Default is aml). After this, go back to the main Armbian Config main menu. Back at the main menu, select Software and scroll down to RDP - Enable remote desktop from windows and select it. (THIS IS OPTIONAL) This will allow you to use Remote Desktop (mstsc) to this computer ON your LOCAL network from a Windows computer by connecting to the server’s network name or local network IP address. It will not be internet accessible via RDP unless you create a rule in your router/firewall for port 3389 to point to your server, which, please research security concerns if you want to go down the route of allowing the internet to RDP your server. Exit back out of Armbian config and............

            (Yes, I know my screen grab says disable, I had already installed RDP)
    CONGRATULATIONS - You now have a working Armbian Server.
    BOOTING OFF SD/USB PROBLEMS - (ALL the Below sections all cover boot problems)
    If you cant boot an Amlogic based system off external media
    Once you have completed steps 1 through to 8, of the Installing onto the MeCool M8S PRO w at the top of this guide. Boot your Amlogic based system into the Android OS that is installed on the box. When you are booted in to Android, plug in your newly created Armbian SD card or USB stick to the system. Somewhere in the Android interface, perhaps the applications folder, you will find a program called Update OR Update&Backup (you can also hunt the Settings menu and find an update in there). Open this application.

      It should give you the choice to update OTA (Over the Air) or from a Local File. Select Local and browse to your SD card/USB stick. You will find a file called select that and confirm the upgrade. The system should reboot, most likely twice. After which it may either boot into your Android OS or it may start booting into Armbian. Its also possible it may just do the reboots and then sit at a splash screen for a while. In short, if its not booting an OS within 3 minutes, give it 2 more minutes, then pull the power and try rebooting (with your SD card/USB stick in). If it doesnt work (meaning it doesnt boot Armbian off your SD card/USB stick), try again with this process and also check you are using the right DTB files in uEnv.ini (as below) as they can cause a system to hang at a splash screen.  
    To explain what is doing..... The file is from here:

    What it does, is tell the boot partition of the Android TV box, that it has multi-boot (can boot from any device, internal/external) and sets external devices as being the 1st thing to try booting off.
    If youve copied your Armbian OS to the emmc/NAND chip and it wont boot off the internal memory, read up below on uEnv.ini and extlinux.conf as that may be the problem… though some boxes just cant/wont boot off emmc/NAND
    uEnv.ini and extlinux.conf 
    When you set up Armbian on a Android TV box, you need to tell Armbian what drivers/setup to use for the chipset in your box. This is done through matching the best DTB file to your TV Box’s hardware. To do this, there are 2 files on the SD card or USB stick you create.
    In the root of the BOOT partition, you will find uEnv.ini and in /extlinux directory, you will find extlinux.conf.
    Editing the files and picking the right DTB
    These files are best edited in Notepad++ on Windows, or some program that happily edits Unix format text files.
    If you just use Windows Notepad, they wont look correct when edited (as shown below) and you can screw the formatting up, resulting in your system NOT booting. Use Notepad++ or a Unix text file editor!!
    Within these files you will specify a DTB file, from the dtb folder on the BOOT partition.. Your TV Box might be a 905x2 chipset, or an 912 etc, so you need to find the DTB that works for your chipset. Lets say you have an S912 based system, you can look in the DTB folder and you will see various DTB files with 912 in their name, you can try each one of those, one at a time and see which one works, though not all DTB files are labeled as clearly as this. As an example, I have a Beelink GT1 Mini which is based on the 905x2 chipset, and for that unit, the X96 DTB file is recommended, though I only found that out through hunting the forums/finding out what other people had used.
    In short, look at the Armbian forums to find the best one, or just pick one that you think, list it in the uEnv.ini and extlinux.conf, see if the box will boot (try a different DTB file if not) and see if all the hardware works (Try a different DTB file if not, or some boxes its possible to find there is no bluetooth driver or something. Best to research the Armbian forums first to see what boxes people have success with. 
    There is no harm in just trying different DTB files, one at a time. Your box will either boot or not boot and either some or all of the features of your box will work.
    If you are just at a stage of testing your booting process from an SD card or USB stick, you only need to edit the uEnv.ini file for now, as your system will boot from that, however, when you find the DTB you want to use, update the extlinux.conf file too, so you can install to emmc/NAND.
    What do these 2 files do and why cant I boot off emmc internal ram?
    My understanding is that uEnv.ini takes care of the boot information when you are booting off SD card or USB Stick and the extlinux.conf takes care of the boot sequence if you load the OS onto the internal eMMC memory (the internal hard drive ram chip thing).
    So long and short… if you boot off external media, transfer the OS to the internal eMMC and you HAVNT updated the extlinux.conf, dont expect it to boot off the internal eMMC, it will just sit at the box’s spashscreen. (though you can boot off an external SD/USB and edit those files).

    In short… just update BOTH files to ensure you can boot off external SD card/USB stick and internal emmc (if you copy the OS over).
    What should the files look like?
    NOTE - If they dont look/arent formatted like this when you open them, you arent using a Unix file editor like Notepad++
    bootargs=root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes net.ifnames=0
    LABEL Armbian
      LINUX /zImage
      INITRD /uInitrd
      FDTDIR /dtb
    #  FDT /dtb/meson-gxl-s905x-khadas-vim.dtb
      APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes net.ifnames=0 
    You would be replacing meson-gxl-s905x-khadas-vim.dtb with the DTB file that matches your box, in BOTH these files.
    Also, DONT delete the # out of the extlinux.conf file, its meant to be there!
    Installing onto emmc/NAND - The internal hard drive of the TV box.
    This is pretty simple to do, though its worth re-mentioning not every box will support this, for one reason or another. If you want to try however:
    Boot your system from your Armbian OS SD Card (I think it HAS to be an SD card, or at least the menu option wont show up in my tests using a USB stick, only on SD card). Make sure you have edited BOTH your uEnv.ini AND extlinux.conf files as above. In the OS, go to Armbian config (Step 5 onwards from Installing onto the MeCool M8S PRO w above). Go into the system option. In there, the first option should be Install to SATA, emmc, NAND or USB and select that. It will now copy over your files (wiping your Android OS off your box). This takes 3 to 8 minutes approximately. While this is copying, read the section below LOST.DIR, System Volume Information and Android and follow that process if needed. Assuming you configured your extlinux.conf file with the correct DTB, you can shut your system down, take out your SD card, switch it back on, and it should boot.  
    You can always boot off your SD card again, to edit the BOOT_NAND (on the desktop.. I think its called that) which is the copied over boot volume, where you can find the extlinux.conf file, to update the DTB file it uses.
    Worst case, check through the bits in this document and the forums. I dont know much about Rockchip based systems and how they differ (most of what Ive put in here was based on my Amlogic chipset TV boxes), Id assume its pretty similar.
    LOST.DIR, System Volume Information and Android folders cause problems booting off eMMC/NAND.
    If your SD card or USB stick had been in an Android or Windows box BEFORE you copied your OS over to eMMC/NAND, you may find out that your system WONT boot off the eMMC/NAND memory, but will still boot off your external card. These folders, as far as I can tell ONLY interfere with booting from the internal emmc/NAND and seem to cause no problem when booting from an SD card/USB stick.... but of course, if you copy Armbian to emmc/NAND, they seem to then cause a problem booting from emmc/NAND.
    I dont know why these folders seem to create an issue, but in my tests, deleting them before you copy over to your eMMC/NAND, OR after you have copied the OS over to eMMC/NAND, boot the system off your original SD Card/USB stick and on the Desktop of your system, go to the BOOT_EMMC drive, delete the folders LOST.DIR, System Volume Information and Android (or whichever combination of those 3 exist), shutdown the system and try booting again from eMMC.

    I tested multiple times on a system and after I had deleted those folders.... my system suddenly started booting correctly (with the occasional corruption occurring and having to re-copy the OS to eMMC/NAND again,  but if you do this, you can delete the folders before attempting to boot next time).
    To be clear, at time of writing this document, on your boot volume, there should be maybe 20 files in the root of the boot partition and only 3 folders ("dtb," "dtb-XXX-aml-XXX "and "extlinux"). (the XXX's will be some number)
    Ive done something and now my box wont boot/stuck on a splash screen/is a brick what do I do?
    If this happens, it usually means your onboard emmc/NAND storage area has become trashed somehow OR if you have your SD Card/USB stick, thats trashed somehow. To figure which, take your SD card/USB stick out and see if it boots look at these 2 options:
    OPTION A - if it boots without the SD Card/USB stick in, then its your SD Card/USB stick. Quick fix is to check you are using the correct DTB and edited uEnv.ini and extlinix.conf correctly (maybe try a different DTB if its never booted).  If it was booting off the SD card/USB stick, then re-image the SD card/USB stick with Armbian and make sure you have the right DTB and all should be good again.
    OPTION B - It wont boot without the  SD Card/USB stick in then the emmc/NAND area on your tv box is trashed in some way and its therefore not multibooting. So you need to re-flash the internal memory with the correct ROM/image for your box.
    Getting a system recovered - notes
    So for example, with an Amlogic based box, lets say the MeCool M8S Pro w box (Amlogic based box) you would find an original ROM for that system via a google hunt and download it (expect about a 1GB to 2GB download). You would also need the Amlogic USB Burning tool. Id recommend version or later as it starts up in English (though you can find a language menu and select English on older versions).  Install this on a Windows based computer.
    You will will need a USB cable that will plug into both the USB port of your computer AND the USB port of your Amlogic based TV Box. This is how it will communicate to re-image the emmc/NAND.
    On the TV boxes, there is usually a reset button. but this could be:
    a tiny hole in which you need to stick a paperclip or something to press the reset button. you might need to open the box and connect 2 jumpers or short out 2 points on the board (on the MeCool M8S Pro w, its like this) Some systems, you can power on and hold down/press a button on the supplied remote AS you are powering on the box.   
    Doing the recovery
    Lets pretend you have method 1 from above, the paperclip version.
    For an Amlogic based system (Other makes will have their own software, but it will be a variation on doing this).
    Install the USB Burning tool to your Windows machine. Open the USB Burning tool and go to File > Import Image, then select the image file you have downloaded (Unzip or Unrar the file if its compressed).  DONT power your TV box from the supplied mains adapter!! (The Amlogic boards arent expecting that it appears, so dont go into recovery mode on mains power. It wont hurt your box, it just wont go into recovery). - Plug one end of your USB cable into your Windows PC. - Push down the reset button (or whichever method you need to use) with the paperclip on the TV Box and at THAT point, plug in the USB cable. This should now power on the box, but it may display a blank screen.

              On some TV boxes, it appears ONLY 1 of the multiple USB ports they have will be usable/activate for the flashing process. As such, try your other ports if it doesnt appear in your flashing software. 
      - You should hear a ding/chime or something from your Windows PC and the Amlogic USB Burning tool should now say something like HUB Connected. - In the USB Burning tool you should have it set at "Normal Erase" but Ive also done "Full Erase" before.... I dont quite know the difference... but Normal Erase seems to be fine, try Full if if doesnt work on Normal. - Press the start button and wait about 5 minutes until the USB Burning tool says 100% success. Wait about another 20 seconds. Press Stop and unplug your TV Box. Next time you power on the box, it should start booting into Android.   
    Now you are back at a working box and can start your install procedure as per this guide... so setup multiboot with etc....
    Hopefully all this helps someone figure things out.... if you cant find the answer here.... Im sure someone in the forums will give an answer!
    erew (the OP for this topic)
  8. Like
    jock got a reaction from pro777 in CSC Armbian for RK3288 TV Box boards (Q8)   
    @Sergei Steshenko Apparently the purple line and audio issues with HDMI are gone in kernel 5.1! Here is an experimental image (Armbian 5.88 + Kernel 5.1.7) if you want to give it a chance.
  9. Like
    jock reacted to maxlinux2000 in Add undetected hdmi resolution to X11/Xorg   
    Mini tutorial
    I am putting here some notes for posterity
    In the current version of armbian (testing H6) I use X11 / Xorg only reaches 1024x768, but my display reaches 1440x900.
    To add this new resolution to the list of Settings/Display you have to give these commands:
    # xrandr --listmonitors
    (this command serves to see what it's called, the hdmi output)
    # cvt 1440 900
    # 1440x900 59.89 Hz (CVT 1.30MA) hsync: 55.93 kHz; pclk: 106.50 MHz
    Modeline "1440x900_60.00"  106.50  1440 1528 1672 1904  900 903 909 934 -hsync +vsync )
    # xrandr --newmode "1440x900_60.00" 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vsync
    # xrandr --addmode HDMI-1 1440x900_60.00
    # xrandr --output HDMI-1 --mode 1440x900_60.00
    If it works then modify Xorg with:
    # sudo mcedit /etc/X11/xorg.conf.d/40-monitor.conf
    Section "Monitor"
    Identifier "HDMI-1"
    Modeline "1440x900_60.00" 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vsync
    Option "PreferredMode" "1440x900"
    # reboot
  10. Like
    jock reacted to Myy in The VPU driver   
    You should like my Wayland example, then :3
    Anyway, I see that Ezecquiel Garcia is currently pushing patches to adapt the V4L2 patches from Ayaka, into something that works with V4L2 (and a few modifications) without the MPP layer in-between.
    He pushed support for MPEG-2 decoding support... I'll see if he pushes support for H264 this week.
    If not, I'll try to adapt Ayaka's patches.
  11. Like
    jock reacted to Staars in Proof of concept - Realtek 1295   
    Just a tiny update. Booting from SSD works as expected:
    It is not completely free of error messages, but it is quite okay'ish.
    I will try to update my first post in order to gather the most recent information there. 
  12. Like
    jock reacted to TonyMac32 in RK3288 Media Script (TinkerBoard)   

    So, this has @Myy's work with the patchset that got dropped on the mailing list for vdec, I've gotten everything building properly (minus a wireless driver and we don't have 1.7 and 1.8 GHz opps)
    I ran the media script ans installed everything.
    I'm watching a 1080p mp4 at fullscreen, here is my armbianmonitor -m:
    Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 05:41:25: 1608MHz 1.00 20% 3% 16% 0% 0% 0% 51.7°C 0/11 05:41:30: 1608MHz 0.92 20% 3% 17% 0% 0% 0% 50.4°C 0/11 05:41:35: 1608MHz 0.92 21% 3% 17% 0% 0% 0% 50.4°C 0/11 05:41:40: 1608MHz 0.93 19% 3% 15% 0% 0% 0% 51.2°C 0/11 05:41:45: 1608MHz 0.93 20% 3% 17% 0% 0% 0% 50.4°C 0/11 05:41:50: 1608MHz 0.94 21% 5% 16% 0% 0% 0% 51.7°C 0/11
    As for functionality, gstreamer does not seem to want to work, so I would guess the vdec isn't operational yet, or something isn't quite right.  In any case, there is hope, perhaps.  ;-)
  13. Like
    jock got a reaction from TonyHCM15 in Miqi board RK3288   
    I don't have a MiQi, but AFAIK armbian-config should already do what you ask
  14. Like
    jock got a reaction from TonyMac32 in USB Serial Support not working   
    I can confirm that latest armbian with next kernel (4.19) on rk3288 works flawlessy with prolific USB-to-serial adapters:
    15567.072909] usb 2-1: new full-speed USB device number 2 using dwc2 [15567.281604] usb 2-1: New USB device found, idVendor=067b, idProduct=2303, bcdDevice= 3.00 [15567.281616] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [15567.281623] usb 2-1: Product: USB-Serial Controller [15567.281630] usb 2-1: Manufacturer: Prolific Technology Inc. [15567.318362] usbcore: registered new interface driver pl2303 [15567.323408] usbserial: USB Serial support registered for pl2303 [15567.323550] pl2303 2-1:1.0: pl2303 converter detected [15567.327312] usb 2-1: pl2303 converter now attached to ttyUSB0 I use it daily with Arduino IDE to develop and push things to ESP8266 and works without issues.
  15. Like
    jock reacted to Staars in Proof of concept - Realtek 1295   
    after reading the very entertaining thread regarding the BPI-W2 and the following opening of the bsp-kernel on github, I became curious and when prices dropped for the Lake-1-TV-Box, I decided to play around with it.
    Without very much documentation there was a bunch of trial and error and still many things are not absolutely clear to me, but finally I could boot an armbian build today:
    _ _ _ | | __ _| | _____ / | | | / _` | |/ / _ \ | | | |__| (_| | < __/ | | |_____\__,_|_|\_\___| |_| Welcome to ARMBIAN 5.68 user-built Ubuntu 18.04.1 LTS 4.9.119-rtd1295 System load: 1.49 0.74 0.31 Up time: 3 min Memory usage: 4 % of 1631MB IP: CPU temp: 46°C Usage of /: 11% of 7.2G [ General system configuration (beta): armbian-config ] New to Armbian? Check the documentation first: Thank you for choosing Armbian! Support:  
    This is still connected over the serial port and completely untested. I had to use the strange chained double-u-boot and load kernel and dtb manually (from raw sd card sectors), so it is not even close to alpha. But it seems, that this can be improved. 
    I plan to make a repeatable build config, but do not expect some really usable stuff anytime soon.  The situation with the lack of mainline support was already discussed in the other thread and the future does not look very bright here.
    This is more or less a personal playground at the moment. But if anyone is interested, you can leave comments or questions here.
    Sticky part (updated 03-03-2019):
          Tested: Lake 1 Home Cloud TV Box
          Untested: Beelink SEA 1, Zidoo X9s, Zidoo X8, Zidoo X10,  Probox2 AVA, WD My Cloud Home, ...
    All development and tests thus far have been done on the Lake-1-TV-Box. It can not be ruled out, that the other boxes have other u-boot-versions/-configurations.
    Serial connection soldered to the PCB (to reach the u-boot-shell) and a suitable terminal software. Further information here: (I can not confirm that „SD rescan“ does not work. Only „fatls“ and „fatload“ never worked for me, that’s why raw sector reads are used.)

    Access to a Windows-PC, a USB-male-to-male-cable and the knowledge to re-flash the device by yourself.
    If you are not comfortable in doing this, DON’T DO IT!!! YOU CAN BRICK YOUR DEVICE FOREVER !!
    Current installation process (booting from SD-Card):
    Build a full-OS-image with armbian selecting „lake1“ from this fork: This will create an image with kernel image and dtb written to sectors before the root partition. The u-boot-build of armbian is not used. Write the image (using etcher) to an SD-card. For the moment we will not touch the eMMC of the target device and therefore will work as non-destructive as possible. This might change in the future and it should be no problem to implement a eMMC-only solution, but at the moment there is no solution in sight, that would let you dual-boot Android and Linux. Create a terminal connection to the serial pins of your target device and intercept the boot process immediately after power up to reach the first u-boot-shell. Now we have to edit the BOOTCMD the following way: env edit bootcmd sd read $kernel_loadaddr 800 954a; sd read $fdt_loadaddr a440 5d; env set bootargs earlycon=uart8250,mmio32,0x98007800 console=ttyS0,115200 noinitrd root=/dev/mmcblk0p1 rootfs=ext4  init=/sbin/init; b2ndbc; bootr env save  
               This is a relatively harmless operation and can be reversed with the insertion of 'bootr' in step 2.
               The Android-installation on the eMMC stays untouched.
       4. Now at every boot the device will initialize the SD (which can fail!!), load the image and dtb, change the bootargs and call the second u-boot, which then will (hopefully) boot the kernel. 
    At the moment u-boot will be build, but not used. Because of bootloader encryption this will likely stay that way. We can build the fsbl-parts, but without the proper encryption the boot stops, when the first part (hw_setting) is loaded. 
    A separated u-boot-fork at is used for the armbian build, but that does not really matter. We must use the vendor-u-boot and we can not do real scripting (no RUN-command) but only chaining of commands.
    The starting point from Sinovoip was labeled 4.9.119, but this is very likely not the whole story. Some parts are even newer and some are probably older, given the fact that git-cherry-picking showed possible updates when used with the stable linux-4.9-branch below tag:4.9.119.
    The additional phoenix drivers were partly integrated in the kernel-fork on as an extra folder to keep them in one place.
    If there should be really an adoption of this platform in the future, it might be a good idea to go the other way around and merge the soc-specific parts into a generic linux-4.9.-fork. This is a bit of work, but it should be possible.
    The fork is currently patched to 4.9.174
    New kernel fork started at (not 4.20 because of LTS) and armbian build config updated.
    This is a minimal changed version for the banana-pi w2. 

    I do not really know if this (audio firmware?) is useful outside of Android. It is written to the SD-Image (directly behind the DTB), but not loaded.
    What works:
    -SATA-port (incl. booting with /root on SSD with bootarg 'root=/dev/sataa1')
    -WLAN (onboard 8821AU), but there are very short freezes every few seconds
    -simple software install (i.e. OMV)
    -reboot/restart works, but can take some time
    What does NOT work:
    Things to do:
    -waiting for someone, who confirms, that this is repeatable on other setups
    -working on the DTS/DTB
    -test Ethernet, USB
    -HDMI-in/-out or graphics in general (very low priority for me)
    -eMMC-only-install (must check first, where it is safe to write data)
    -test 4.19 (functional regression expected)
  16. Like
    jock got a reaction from lanefu in Is Mali GPU driver available in Mainline for H3?   
    The answer is yes, it can be done, but you need a bit of knowledge about compiling kernel modules.
    I made it on an Orange PI PC (Allwinner H3) to test my armsoc drivers and it worked, although Mali-400 MP2 embedded into H3 was quite slow.
    You should be able to take everything you need (both the kernel driver and the userland EGL+OpenGL ES drivers) from
    Kernel and userland libraries should match their versions to be sure that they work correctly together: if you use r6p2 kernel driver, use r6p2 for userland too.
    Instructions are easy but here are some hints:
    You need the kernel headers package installed, you won't get far without this; you should be able to use apt-get to install the appropriate package for your armbian version You can compile the kernel driver on your very same board (I strongly suggest this), so you don't need to export the CROSS_COMPILE environment variable export the KDIR env variable to point to your kernel headers. Typically: export KDIR=/lib/modules/$(uname -r)/build export INSTALL_MOD_PATH env variable to point to your kernel modules:. Typically: export INSTALL_MOD_PATH=/lib/modules/$(uname -r)/kernel follow the instructions as described, but expect some patch won't work or compile fail. Just don't be scared to get your hands dirty, it is common that you may need to do some little manual adjustments (a missing kernel file here, a missing header there...) Once the driver is compiled and installed, you should be already able to modprobe it.
    Follow the instructions to install the userland EGL and OpenGL ES libraries too.
    If you are using the X server, you need the x11_dma_buf flavour and you also need to compile this armsoc driver too (maybe you can try the already compiled version I published on this post, it should work for your SoC too. Ignore the media script part which is for rockchip socs).
    If you don't use X you can use the fbdev flavour, in this case add extraargs=drm_kms_helper.drm_fbdev_overalloc=200 to /boot/armbianEnv.txt as per-instructions.
  17. Like
    jock got a reaction from Tido in Integrate WireGuard into kernel   
    Yeah you can integrate wireguard into the kernel, but you can also use DKMS framework to let it being recompiled each time a new kernel is installed.
    Wireguard already comes with a small configuration file for DKMS, just follow a tutorial on how to install and setup DKMS on your machine (which is quite easy, just few steps) and register wireguard module and you're done.
  18. Like
    jock got a reaction from chwe in Integrate WireGuard into kernel   
    Yeah you can integrate wireguard into the kernel, but you can also use DKMS framework to let it being recompiled each time a new kernel is installed.
    Wireguard already comes with a small configuration file for DKMS, just follow a tutorial on how to install and setup DKMS on your machine (which is quite easy, just few steps) and register wireguard module and you're done.
  19. Like
    jock got a reaction from manuti in CSC Armbian for RK3288 TV Box boards (Q8)   
    Hello guys, I'm proud to say that the Q8 boards are now in mainline Armbian as CSC supported boards!

  20. Like
    jock got a reaction from pro777 in CSC Armbian for RK3288 TV Box boards (Q8)   
    Hello guys, I'm proud to say that the Q8 boards are now in mainline Armbian as CSC supported boards!

  21. Like
    jock got a reaction from Igor in CSC support for discontinued rk3288 tv box?   
    Well, another solution is to patch brcmfmac kernel module to add ap6330 chip and revision. It's a very small patch, just adding another item to the list:
    diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c index a907d7b06..ec71996c7 100644 --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c @@ -619,13 +619,17 @@ BRCMF_FW_DEF(4354, "brcmfmac4354-sdio"); BRCMF_FW_DEF(4356, "brcmfmac4356-sdio"); BRCMF_FW_DEF(4373, "brcmfmac4373-sdio"); +/* AMPAK */ +BRCMF_FW_DEF(AP6330, "brcmfmac-ap6330-sdio"); + static const struct brcmf_firmware_mapping brcmf_sdio_fwnames[] = { BRCMF_FW_ENTRY(BRCM_CC_43143_CHIP_ID, 0xFFFFFFFF, 43143), BRCMF_FW_ENTRY(BRCM_CC_43241_CHIP_ID, 0x0000001F, 43241B0), BRCMF_FW_ENTRY(BRCM_CC_43241_CHIP_ID, 0x00000020, 43241B4), BRCMF_FW_ENTRY(BRCM_CC_43241_CHIP_ID, 0xFFFFFFC0, 43241B5), BRCMF_FW_ENTRY(BRCM_CC_4329_CHIP_ID, 0xFFFFFFFF, 4329), - BRCMF_FW_ENTRY(BRCM_CC_4330_CHIP_ID, 0xFFFFFFFF, 4330), + BRCMF_FW_ENTRY(BRCM_CC_4330_CHIP_ID, 0xFFFFFFEF, 4330), + BRCMF_FW_ENTRY(BRCM_CC_4330_CHIP_ID, 0x10, AP6330), BRCMF_FW_ENTRY(BRCM_CC_4334_CHIP_ID, 0xFFFFFFFF, 4334), BRCMF_FW_ENTRY(BRCM_CC_43340_CHIP_ID, 0xFFFFFFFF, 43340), BRCMF_FW_ENTRY(BRCM_CC_43341_CHIP_ID, 0xFFFFFFFF, 43340), This will let brcmfmac look for brcmfmac-ap6330-sdio.bin and brcmfmac-ap6330-sdio.txt firmware files, so there is no need for alternative paths. As long as brcmfmac only discriminates among Chip ID and Chip Revision, there is the drawback case where all those devices which have ID:0x4330 and REV:0x4 will be considered as AP6330.
    After googling around for "BCM4330/4" (a string the driver produces in dmesg), all the sensible results always bind it to AP6330.
    Although this looks tidier, my preference goes to the former solution because it seems "safer" (no id/revision clashing)
  22. Like
    jock reacted to PiotrO in s905w boot process?   
    I think we need to distiguish booting from sd and _unattended_ booting from sd.
    In case of my hw (tx3-mini) I think unattended boot from sd is NOT possible without erasing[modifying] eMMC bootloader.
    I think so as IPL by default is passing control to eMMC.
    So if we want unattended boot from SD - we MUST:
    1\ change eMMC content
    2\ modify IPL
    As IPL is in ROM (I think) -  only option 1\ is choice.
    Reasonably written IPL should have fall-back to SD[USB] if SPL from eMMC fails (i.e. for case when flash ageing leading to data rot). In such case IPL should offer recovery by booting from SD and refresh eMMC SPL.
    So I agree with initial @jock answer as IMHO his intention was to describe what needs t be done to have tv-box _unattended_ boot from sd
  23. Like
    jock got a reaction from TonyMac32 in CSC support for discontinued rk3288 tv box?   
    My plan is to reset the kernelconfigs from common base and enable brcmfmac and IR (and ancillary config options) as modules when possible.
    Devfreq support and other things were just test bits that can be left out.
    If AP6330 firmware binaries could make into armbian firmware repository I can remove the copy work in rockchip.conf - I can arrange a pull request myself for that.
  24. Like
    jock got a reaction from chwe in CSC support for discontinued rk3288 tv box?   
    My plan is to reset the kernelconfigs from common base and enable brcmfmac and IR (and ancillary config options) as modules when possible.
    Devfreq support and other things were just test bits that can be left out.
    If AP6330 firmware binaries could make into armbian firmware repository I can remove the copy work in rockchip.conf - I can arrange a pull request myself for that.
  25. Like
    jock reacted to JMCC in RK3288 Media Script (TinkerBoard)   
    Finally, the version 2.0 for Armbian Bionic is out! Check the OP for documentation and download link.
    Updated all necessary packages to work with Ubuntu Bionic Updated versions of MPV and Kodi Added the GL4ES wrapper, to provide OpenGL support (thanks @jock for the tips). In order to use it, you must launch your app from command line using the wrapper "glrun" RELEASE NOTES:
    I'm not sure whether the Widevine library is still working with newer versions of Chrome, and I don't have access to Netflix anymore to test it. Some feedback on this point is welcome. I'm still including the old cgminer as OpenCL example. If you want to try more recent algorithms and experiment with GPU mining just for fun, I recommend you to have a look to this sgminer for from the ODROID community (it works also with RK3288): As I said, just for learning, curiosity or fun. Trying to get money with a Tinkerboard is a waste of time. Plus, I think the whole crypto-mining idea is absurd, basing the value of a currency on wasting as much electricity as possible  Remember you need a default (4.4.y) kernel for HW video acceleration to work. It is not yet implemented in mainline (4.14.y).