jock

  • Posts

    940
  • Joined

  • Last visited

Reputation Activity

  1. Like
    jock got a reaction from fabiobassa in CSC Armbian for RK3318/RK3328 TV box boards   
    @MX10.AC2N Great, happy that we're very close to the solution
    To get 1.3Ghz, just add rk3318-box-cpu-hs overlay.
    If I read the dtb correctly, also the wifi is attached to the extra sdio bus on your board, so you'd better add rk3318-box-wlan-ext overlay too!
     
    Reboot and you should get these two other things.
     
    BTW: you can also use rk3318-config to do all the necessary overlay configuration with the comfy menu interface. Just need to manually edit armbianEnv.txt before rebooting and set rk3318-box-led-conf3 in place of any other led-conf (there must be only one led-conf overlay). In the next update I will add the led-conf3 to rk3318-config so coming people with boxes like yours will find the recipe ready-made
  2. Like
    jock reacted to MX10.AC2N in CSC Armbian for RK3318/RK3328 TV box boards   
    Great, I did find 1300MHz as the maximum value for the CPU, for the wifi I will have to look because I use the box connected by wire (and then it's an SV6051P chip ..)
    thanks again, and again
  3. Like
    jock reacted to MX10.AC2N in CSC Armbian for RK3318/RK3328 TV box boards   
    Hi and Thanks again,
    so here is dmseg => https://paste.yunohost.org/vawijabuga.erl
    system diagnosis information => http://ix.io/3C6s
    the option to choose the CPU governor is functional again (well seen ..) on the other hand I still only have 1000MHz as max value ..
    Thank you again @jock you are great..
  4. Like
    jock got a reaction from MX10.AC2N in CSC Armbian for RK3318/RK3328 TV box boards   
    @MX10.AC2N Here it is another attempt, last one for today
     
    I rewrote the overlay and double checked anything I could simulate on my board.
    If the system boots, please send back a dmesg log!
    rockchip-rk3318-box-led-conf3.dtbo
  5. Like
    jock got a reaction from MX10.AC2N in CSC Armbian for RK3318/RK3328 TV box boards   
    @MX10.AC2Nwell at least some error is showing up: Failed to register regulator: -517
    I will try to find what's wrong with that.
  6. Like
    jock got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    Look at the post edit I made a little after, clarifies why the thing can't work on our tv boxes.
     
    I learned things are and there on the internet, could not find a proper guide.
    Anyway google reports this forum thread, which is a good starting point:
     
    Yeah, undervolting is cool, but results vary a lot depending on the cpu sample.
    GPU can be tweaked too. RAM can't be tweaked for three reasons:
    the dmc (dram memory controller) node in the dtb is disabled the dmc driver in the kernel is a bit broken the piece of code that does the dram frequency scaling is not present The dram frequency is fixed by a thing which is called ddrbin, and it is the very first thing that boots (even before u-boot).
    It is fixed to 330 Mhz currently, but probably I will push it to a higher yet safe value.
     
    You need to put together an idbloader, which is composed of ddrbin + u-boot SPL.
    You can inspect armbian sources for that, but if you're not an expert in compiling u-boot, I would rather suggest you to stay away from that to avoid lose mental sanity.
     
  7. Like
    jock got a reaction from fabiobassa in CSC Armbian for RK3318/RK3328 TV box boards   
    Look at the post edit I made a little after, clarifies why the thing can't work on our tv boxes.
     
    I learned things are and there on the internet, could not find a proper guide.
    Anyway google reports this forum thread, which is a good starting point:
     
    Yeah, undervolting is cool, but results vary a lot depending on the cpu sample.
    GPU can be tweaked too. RAM can't be tweaked for three reasons:
    the dmc (dram memory controller) node in the dtb is disabled the dmc driver in the kernel is a bit broken the piece of code that does the dram frequency scaling is not present The dram frequency is fixed by a thing which is called ddrbin, and it is the very first thing that boots (even before u-boot).
    It is fixed to 330 Mhz currently, but probably I will push it to a higher yet safe value.
     
    You need to put together an idbloader, which is composed of ddrbin + u-boot SPL.
    You can inspect armbian sources for that, but if you're not an expert in compiling u-boot, I would rather suggest you to stay away from that to avoid lose mental sanity.
     
  8. Like
    jock reacted to tommy in CSC Armbian for RK322X TV Boxes   
    I tested in terminal mode ,'$ sudo systemctl set-default multi-user" which has really good performance. Your cutting edge armbian can achieve PSX full 60fps speed in retroarch (however, in legacy, I use wrong parameter which seriously impact performance) and snes9x framerate improved. I really surprise it is faster than legacy in my case. Really great.
  9. Like
    jock got a reaction from tommy in CSC Armbian for RK322X TV Boxes   
    @tommy Here it is, the latest 5.14 kernel with Ubuntu Hirsute: https://users.armbian.com/jock/rk322x/Armbian_21.11.0-trunk_Rk322x-box_hirsute_edge_5.14.12_xfce_desktop.img.xz
     
    I didn't even test the image, I hope it boots!
  10. Like
    jock got a reaction from NicoD in armbian-gaming : A tool to install Box86, Box64 and Wine on Armbian Hirsute   
    Ahah cool! Congrats!
  11. Like
    jock reacted to tommy in CSC Armbian for RK322X TV Boxes   
    I am interest your new cutting edge armbian image. Could you provide me your links? Thank you in advance.
     
     
     
    Lakka image files for rk322x
     
    rk3228a-mxq4kpro <- I tested this image
    https://mega.nz/file/dJgDXIbB#7yOLyHmuptrP_8aswOCxKdk2aEffOQDUnH-9lIAg8jw
     
    rk3229-a95xr1
    https://mega.nz/file/hIwFHCrZ#nWeLsKnBCXcCwtsDp8_MklgYsqEF5r0N-a3iVQUeLXI
     
    Any images has dtb in first fat partion. You may edit extlinux/extlinux.conf to correct device. It has samba service that can upload game roms but in my case wifi driver not work, only LAN work for my tv box.
     
     
  12. Like
    jock got a reaction from tommy in CSC Armbian for RK322X TV Boxes   
    Can't remember if the upstream image has lima enabled in X11 or not.
    Anyway check /etc/X11/xorg.conf.d/40-serverflags.conf and in case Option "AccelMethod" is set to "none" change it to "glamor".
    It was set to none because X.org performance is very slow with older lima + mesa and software cursor.
    If you wish to try I can provide a cutting edge image with kernel 5.14 and Ubuntu Hirsute (=> much newer Mesa) and hardware cursor, which should radically change the experience.
     
    BTW: I'm pretty interested in trying retroarch just for fun; there is a "gaming on arm" club where you may give some hints or write down a tutorial on how to compile. Maybe @NicoD may give you some help.
  13. Like
    jock got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    Uhm, I see that you have and old full-hd monitor. It should not be an issue, but apparently it is.
    From the hints about your experiences (working on Android, working on multitool, not working with armbian), I guess you installed armbian with mainline kernel: there are some tweaks in the mainline kernel that alter the HDMI timings, thus they may be better with some monitors and worse with others. In your case it may be that your monitor does not like those timings.
    You may give a chance to the legacy kernel image, you can just put in on sdcard, plug the sdcard and boot: the box should automatically boot from sdcard, so you can easily test if HDMI is properly working with legacy kernel at least.
  14. Like
    jock reacted to hexdump in CSC Armbian for RK3318/RK3328 TV box boards   
    @jock - i can confirm that those old mx10 boxes were rk3328 and they were the only ones i saw, which had a proper cpu voltage control ... i once had one of those some time ago
     
    @Matteo Venturi - i think there are at least two versions of this box: an older rk3328 one which should work very nice out of the box (i have one of those) and a newer rk3318 one which might have a few surprises in it resulting in it no longer working that easily
     
    best wishes and good luck - hexdump
  15. Like
    jock got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    Read the instructions!! rk3318-config to configure it for 1.3 ghz !!
  16. Like
    jock got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    The cpu-hs overlay is responsible for the 1.3ghz clock. If it is causing you issues, then the cpu is not really happy running with that frequency
  17. Like
    jock got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    Need to check out the station m1 dtb though. Maybe your board has a dedicated PMIC to control the CPU voltage and not the common cheap PWM voltage regulation.
    It would be the first case for rk3318, but it could definitely could be.
    Or the other dtbs are just giving more voltage to the CPU, that could be also...
    I'm not having problems with lightdm right now; in the recent past lightdm-gtk-greeter caused some issues with hangs and crashes, but on arm64 it should be fine right now. Try to upgrade the package with apt (take care not to upgrade the kernel and dtbs though!)
     
  18. Like
    jock got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    You should also provide some detailed photos of the board, in particular report if you see a small chip with the rk805 printing on it.
    Also the device tree of the original firmware (or the original firmware itself) would be useful.
  19. Like
    jock got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    @MX10.AC2N Okay, so that's the reason your board works fine with Station M1 device tree.
    Your board seems to be better constructed than regular rk3318 boards, maybe is it rk3328? (rk3318-config will tell you)
    Another non-common thing is the GL850G USB2 hub chip, but that should not be a problem.
     
    I need a bit of time to study and prepare an appropriate overlay specific for your board, so you have to be patient...
  20. Like
    jock got a reaction from tommy in CSC Armbian for RK322X TV Boxes   
    @tommy
    I would say you to give a chance to the mainline kernel too. Lima driver has decent performance and you don't have to lose time around proprietary Mali OpenGLES-only drivers swapping links under the hood. (BTW for legacy kernel there is the media script link on first page that should install the libraries in the right places).
     
    For snes9x you should not need particular load on the GPU since it has just to render the framebuffer. Lima performances should suffice.
     
  21. Like
    jock got a reaction from tommy in CSC Armbian for RK322X TV Boxes   
    @tommy I Didn't ever try retroarch. I took a look on snes emulation on libreelec and surprisingly it was working quite well on rk322x. I tried once to compile snes9x for rk322x and also was working fairly well in X.org, but performance dropped when I tried any scaling 2X filter.
     
    That said, I would suggest to you, as @fabiobassa said, to try and see if you can avoid X.org, maybe trying to compile with GBM/DRM support so you get fullscreen without passing through the X server.
    Also you should tell which kernel are you using, it may be important.
  22. Like
    jock got a reaction from fabiobassa in CSC Armbian for RK322X TV Boxes   
    @dotbg Some boxes with rk3566/rk3568 are sold with 8GB (gigabytes) of RAM. That chip is capable to address such amount of ram, yet you have to trust the chinese manufacturers and vendors that they really put 8Gb of RAM in the box
     
    rk322x instead is not able to go above 2GB (gigabytes). Everything beyond on a rk322x is surely fake.
  23. Like
    jock got a reaction from tommy in CSC Armbian for RK322X TV Boxes   
    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!
     
    Following the recent thread on LibreElec forum about an unofficial image for rk3229 devices, I would like to make public the work made by me and @fabiobassa about bringing rk322x support to armbian.
    The project is now in -> mainline Armbian <- and the development fork will be available on github -> here <-
    Most of the love has been poured into supporting and bringing up the legacy rockchip 4.4 kernel, but in the near future the goal is to fully support the mainline kernel.
     
    What works:
    Should boot and work flawlessy on all boards with RK3228a, RK3228b and RK3229, with either DDR2 and DDR3 memories. Mainline u-boot OPTEE provided as Trusted Execution Environment All 4 cores are working Ethernet Serial UART (configured at 115200 bps, not 1.5Mbps!) Thermals and frequency scaling OTG USB 2.0 port (also as boot device!) EHCI/OHCI USB 2.0 ports MMC subsystem (including eMMC, SD and sdio devices) Hardware video acceleration (fully supported via RKMPP on legacy kernel, partial support via hantro kernel driver on mainline) NAND is available only on legacy kernel. To fully boot from NAND, use the Multitool and its steP-nand installation (instructions are below) Various WIFI over SDIO are supported (SSV6051P, SSV6256P, ESP8089, Realtek chips, etc...), but ssv6x5x drivers are available only on legacy kernel Full GPU acceleration on legacy kernel, mainline kernel has lima driver compiled in but X11 is very slow - you are still free to compile and install mali kernel driver on mainline yourself. U-boot boot order priority: first the sdcard, then the USB OTG port and eventually the internal eMMC; you can install u-boot (and the whole system) in the internal eMMC and u-boot will always check for images on external sdcard/USB first.  
    Unbrick:
    Technically, rockchip devices cannot be bricked. If the internal flash does not contain a bootable system, they will always boot from the sdcard. If, for a reason, the bootable system on the internal flash is corrupted or is unable to boot correctly, you can always force the maskrom mode shorting the eMMC clock pin on the PCB. Here there is the procedure, but you can also google around if you get stuck on a faulty bootloader, the technique is pretty simple and requires a simple screwdriver.
     
    There are however some unfortunate cases (expecially newer boards) where shorting the eMMC clock pin is difficult or impossibile, like eMMC or eMCP BGA chips with no exposed pins. In those cases pay double attention when burning something on the internal eMMC/eMCP and always test first the image from the sdcard to be sure it works before burning anything on eMMC/eMCP
     
    NAND vs eMMC vs eMCP difference:
    RK3228 and RK3229 tv boxes comes with three different flash memory chips: eMMC, NAND and eMCP.
    It does not depend upon the market name of the tv box and neither the internal board; manufacturers put whatever they find cheaper when they buy the components.
     
    NAND chip is just the non-volatile memory eMMC chip contains both the non-volatile memory plus a controller. eMCP chip contains the non-volatile memory, a controller for the non-volatile memory (like eMMC), but also contains a bank of DDR SDRAM memory on the same physical chip.  
    The difference is very important, because eMMC and eMCP are far easier to support at various levels: the controller deals with the physical characteristics of the non-volatile memory, so the software has no to deal with.
    NAND chips instead are harder to support, because the software is required to deal with the physical characteristics and non-standard things that depends upon the NAND manufacturer.
     
    If you have a NAND chips you're unlucky because mainline kernel currently cannot access it, but also because you need special care and instructions explained later.
    eMCP chips at the moment are not supported by stable images, do not burn Armbian image on eMCP internal flash or you risk of bricking the boards! Instead follow the "Boot from sdcard" procedure and post on the forum the results of armbianmonitor -u command for further help and possibly a customized image.
     
    You can discover if you have a NAND, eMMC or eMCP chip looking on the board are reading the signature on the flash memory chip.
    The Multitool (see later) also can detect which chip you have onboard: the program will warn you at startup if you have a NAND chip.
     
    NAND bootloader upgrade:
    IMPORTANT: don't do this is you have an eMMC or eMCP; skip this paragraph if you are unsure too!
    For fearless and bold people who wants to get all the things up-to-date, or are having issues booting images, there is the chance to upgrade the bootloader on NAND.
    The NAND bootloader is nothing else than a regular idbloader (see official rockchip documentation) but contains some bits to correctly access the data on your flash memory.
    Upgrading requires to erase the existing flash content, in the worst case will require you to follow the Unbrick procedure above or restore an older but more compatible bootloader.
    If you are not mentally ready to overcome possible further issues, don't do this!
     
    After the disclaimer above, there are some benefits although:
    You run the most recent rockchip blob code (ddrbin + miniloader) You will probably solve the reboot issue that some users with NAND memories are having Boards with DDR2 memories are booted at 330 MHz, so you may get a bit of improvement because older bootloaders boot them at 300 Mhz or 330 Mhz Boards with DDR3 memories are booted at 660 Mhz, here you get quite an improvement because older bootloaders boot them at 300 Mhz or 330 Mhz  
    The detailed instructions and the binaries are available at this post
     
    Multimedia:
    If you need multimedia features, like OpenGL/OpenGL ES acceleration, hardware accelerated Kodi, ffmpeg and mpv you can take a look to this post An effective tutorial from @Hai Nguyen on how to configure a box as a hi-quality music player using an USB audio card, and controlling it via remote control is available in this post  
    Installation (via SD card):
    Building:
    You can build your own image follow the common steps to build armbian for other tv boxes devices: when you are in the moment to choose the target board, switch to CSC/TVB/EOL boards and select "rk322x-box" from the list.
     
    Stable images:
    Stable images are certified and signed by Armbian and you have the guarantee to get the system updates when there is a new Armbian release.
    Images and installation instructions are provided in the Armbian RK322x download page: https://www.armbian.com/rk322x-tv-box/
     
    Development images:
    No development images for now, please download the stable images directly from above.
     
    Multitool:
    Multitool - A small but powerful image for RK322x TV Box maintenance  
    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 sudo rk322x-config and select your board characteristics to enable leds, wifi chips, high-speed eMMC, etc... 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 eMMC, the box may not boot anymore forcing you to follow the unbrick section at the top of this post.
     
    Quick installation instructions on NAND:
    Build or download your preferred Armbian image and a copy of the Multitool; Burn the Multitool on an SD card; once done, place the Armbian legacy kernel image in images folder of the SD card 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 Armbian image via steP-nand" from the menu, then select the destination device (usually rknand0) and the image to burn; Wait for the process to complete, then choose "Shutdown" from main menu; Unplug the power cord and the SD card, then replug the power cord; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt. On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run sudo rk322x-config and select your board characteristics to enable leds, wifi chips, etc... Run armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed!  
    Alternative: you can install the bootloader in NAND and let it boot from SD Card or USB:
    Download a copy of the Multitool and burn it on an SD card; Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears; RECOMMENDED: make a backup of the existing firmware with "Backup flash" menu option; Choose "Install Jump Start for Armbian" menu option: the Jump Start uses the internal NAND to boot from external SD Card or external USB Stick; Follow the general instructions to boot from SD Card below, skip the first erase eMMC step.  
    Quick installation instructions to boot from SD Card:
    If you are already running Armbian from eMMC, skip to the next step. Instead if you are running the original firmware you need to first erase the internal eMMC; to do so download the Multitool, burn it on an SD Card, plug the SD Card and power the TV Box. Use "Backup flash" if you want to do a backup of the existing firmware, then choose "Erase flash" menu option. Build or download your preferred Armbian image; Uncompress and burn the Armbian image on the SD Card; Plug the SD Card in the TV Box and power it on; Wait for 10 seconds, then the led should start blinking and HDMI will turn on. The first time the boot process will take a couple of minutes or more because the filesystem is going to be resized, so be patient and wait for the login prompt; On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run sudo rk322x-config and select your board characteristics to enable leds, wifi chips, high-speed eMMC or NAND, etc... Run armbian-config to configure timezone, locales and other personal options, or also to transfer the SD Card installation to internal eMMC; Congratulations, Armbian is running from SD Card!  
    A note about boot device order:
    With Armbian also comes mainline U-boot. If you install Armbian or just the bootloader in the eMMC or the Jump Start on internal NAND, the bootloader will look for valid bootable images in this order:
    External SD Card External USB Stick in OTG Port Internal eMMC  
    Installation (without SD card, board with eMMC):
    If you have no sd card slot and your board has an eMMC, you can burn the armbian image directly on the internal eMMC using rkdeveloptool and a male-to-male USB cable:
     
    Download your preferred Armbian image from Armbian download page and decompress it. Download the rk322x bootloader: rk322x_loader_v1.10.256.bin Download a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. Unplug the power cord from the tv box Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everything went well, run lsusb: you should see a device with ID 2207:320b Run sudo rkdeveloptool rd 3 (if this fails don't worry and proceed to next step) Run sudo rkdeveloptool db rk322x_loader_v1.10.256.bin Run sudo rkdeveloptool wl 0x0 image.img (change image.img this with the real Armbian image filename) Unplug the power cord Done!  
    Installation (without SD card, board with NAND):
    If you are in the unfortunate case you can't use an SD card for installation and your board has a NAND chip, you still have an option to use the quick Multitool installation steps via USB.
     
    Obtain a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. Unplug the power cord from the tv box Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everyting went well, using lsusb you should see a device with ID 2207:320b Run sudo rkdeveloptool wl 0x4000 u-boot-main.img (download u-boot-main.img.xz , don't forget to decompress it!) Unplug the power cord  
    Now you can follow the instructions on how to install on eMMC/NAND via SD card, just use instead an USB stick to do all the operations and plug it into the USB OTG port. Once you reboot, USB OTG port will be used as a boot device.
     
    NOTE: NAND users without SD slot may be unhappy to know that it will be difficult to do extra maintenance with Multitool in case something breaks in the installed Armbian system: installing u-boot-main.img makes the installed system unbootable because it is missing the NAND driver.
     
     
    Alternative backup, restore and erase flash for EXPERTS:
    These backup, restore and erase flash procedures are for experts only. They are kept here mostly for reference, since the Multitool is perfectly able to do same from a very comfy interface and is the suggested way to do maintenance.
     
    Backup:
    Obtain a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. If you prefer, you can compile it yourself from the sources available at official rockchip repository Unplug the power cord from the tv box Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everyting went well, using lsusb you should see a device with ID 2207:320b change directory and move into rkbin/tools directory, run ./rkdeveloptool rfi then take note of the FLASH SIZE megabytes (my eMMC is 8Gb, rkdeveloptool reports 7393 megabytes) run ./rkdeveloptool rl 0x0 $((FLASH_SIZE * 2048)) backup.data (change FLASH_SIZE with the value you obtained the step before) once done, the internal eMMC is backed up to backup.data file  
    Restore: first we have to restore the original bootloader, then restore the original firmware.
    Running rkdeveloptool with these switches will accomplish both the jobs:
    ./rkdeveloptool db rk322x_loader_v1.10.256.bin Downloading bootloader succeeded. ./rkdeveloptool ul rk322x_loader_v1.10.256.bin Upgrading loader succeeded. ./rkdeveloptool wl 0x0 backup.data Write LBA from file (100%) Download here: rk322x_loader_v1.10.256.bin
     
    Erase the flash memory: clearing the internal eMMC/NAND memory makes the SoC look for external SD Card as first boot option.
    If there isn't any suitable SD Card, the SoC enters maskrom mode, which can then be used for full eMMC/NAND access using rkdeveloptool. This is perfectly fine if your box has an eMMC flash memory.
    NOTE: In case you have a NAND flash memory this option is however discouraged. The original bootloader contains some special parameters to correctly access the data. Clearing the flash memory will probably garbage the NAND data and restoring the bootloader may require some special instructions.
     
    Obtain a copy of rkdeveloptool: a compiled binary is available in the official rockchip-linux rkbin github repository. If you prefer, you can compile it yourself from the sources available at official rockchip repository Unplug the power cord from the board Plug an end of an USB Male-to-male cable into the OTG port (normally it is the lone USB port on the same side of the Ethernet, HDMI, analog AV connectors) while pressing the reset microbutton with a toothpick. You can find the reset microbutton in a hole in the back of the box, but sometimes it is hidden into the AV analog jack Plug the other end of the USB Male-to-male cable into an USB port of your computer If everyting went well, using lsusb you should see a device with ID 2207:320b run ./rkdeveloptool ef and wait a few seconds once done, the internal eMMC is erased and the device will boot from the sdcard from now on  
    Critics, suggestions and contributions are welcome!
     
    Credits:
    @fabiobassa for his ideas, inspiration, great generosity in giving the boards for development and testing. The project of bringing rk322x into armbian would not have begun without his support! Justin Swartz, for his work and research to bring mainline linux on rk3229 (repository here) @knaerzche for his great contribution to libreelec support and mainline patches @Alex83 for his patience in testing the NAND bootloader upgrade procedure on his board
  24. Like
    jock got a reaction from fabiobassa in CSC Armbian for RK322X TV Boxes   
    @Willy Moto Yes, your observation is right: load average is broken on legacy kernel. For some reason, it idles with a value of 4.00, where instead mainline kernel correctly idles with a value of 0.00
  25. Like
    jock got a reaction from Willy Moto in CSC Armbian for RK322X TV Boxes   
    @Willy Moto Yes, your observation is right: load average is broken on legacy kernel. For some reason, it idles with a value of 4.00, where instead mainline kernel correctly idles with a value of 0.00