chinhhut

  • Posts

    34
  • Joined

  • Last visited

Reputation Activity

  1. Like
    chinhhut reacted to Igor in How to build for an unsupported board (Pine64 Quartz64)?   
    Officially no. Too many hardware is seeking for very low time and expertise.
     

    Example of first start
    https://github.com/armbian/build/commit/3c4b69650e9f98edbf7f0a934add1dd19eb14772
    Yes, it might looks complicated, but we are working on to improve the procedure. That is generally more useful for us.
     
     
    Documentation - start there first:
    https://docs.armbian.com/Developer-Guide_Build-Preparation/
    https://docs.armbian.com/Process_Contribute/
    ... and do small steps.
     

    That kernel is shipped with the chip, while path to modern kernel is long, hard and expensive:
    https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one
     
     
    Armbian framework help yes, while for hardware related features - we can't finance hardware vendor business.
  2. Like
    chinhhut reacted to balbes150 in Board Bring Up Station P2 rk3568, M2 rk3566   
    Update version 20211124 with legacy kernel.
     
     
    p.s. Now I am testing a new image with a 5.16.rc2 kernel, in which HDMI and USB work. After all checks are completed, new versions of images with a new kernel will be available. 
  3. Like
    chinhhut reacted to fabiobassa in CSC Armbian for RK3318/RK3328 TV box boards   
    @Elmojo
    I know is not fine answer to a question with another question but in this case
     
    comes very natural ask  : why did you modded it ??? Just for fun ? You didn't have a defined purpose in trying linux ?

    Anyway, just to answer , in my personal study case I have done on it:
    voip pbx ( asterisk)
    network nas
    network firewall
    pihole dns firewall
    openvpv, wireguard and tinc vpn
    home assistant
    volumio
    special ip cam monitoring and data acquisition

    and I guess I could experiment more..... if only I would study more potential applications
  4. Like
    chinhhut reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    @callegar Thanks for spotting it out.
    Actually it is my fault the package installs things in /usr/local/bin.
    I will change that to install in /usr/sbin which is probably more appropriate
     
    @chinhhut It could work, but it couldn't
    The problem is shrinking the partition, you don't just need to reduce the partition size, you also need to shrink the filesystem appropriately otherwise you lose data and possibly the partition does not get mounted when restored.
    Enlarging the partition (and the filesystem) is easy and almost cheap, shrinking can be painful. But you can try indeed! (And maybe realize that losing some time to restore the wholly 64Gb eMMC is better than a headache )
  5. Like
    chinhhut reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    @chinhhut Actually armbian provides a way to introduce user-level patch files which can modify the behaviour of the installed system.
    It means that you can, to some extent, launch sudo ./compile.sh and finally produce an image customized for your needs.
     
    Armbian documentation will help you further.
  6. Like
    chinhhut reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    First page, github repository has always been public
  7. Like
    chinhhut got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    I will study more how to patch some additional files but could you share the source code to build RK3318 image?
    Thank you so much for your support.
  8. Like
    chinhhut got a reaction from ghoul in RK3566 and Armbian   
    Personally, we still hope our hero @jock will take a look on rk3566 soon in near future. For now, I feel happy with my 3318 box.
  9. Like
    chinhhut reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    @chinhhut @curse
    The backup made by multitool (and rkdeveloptool) is per nature a full backup of all the physical eMMC sectors. It has no knowledge of the abstract structures like filesystem and files.
    The compression gives back a more manageable file which is not the entire size of the eMMC, but up to a few gigabytes, depending on how much data is stored on the eMMC and how much compressible it is.
     
    Indeed if you decompress it, you get the whole size of the eMMC, it is expected and it is advisable too. If it is not so, it means the backup process didn't went right.
     
    Now should be clear there is a problem about the "blank" part: how we can know if a part is "blank" and not, for example, a piece of a file which just contains a long string of 0x00 bytes? This is crucial: if you say that you skip those parts which are, supposedly, blank, you may (and probably will) fail to restore files that contains long string of 0x00 bytes. You won't get 0x00s in those places, but you will instead find there the contents of the unwritten eMMC sectors.
     
    So a full restore of all sectors is essential to restore the exact previous condition when doing a full backup.
     
    One helpful thing that may be helpful here is to use the native page erase feature of eMMCs, which is the thing blkdiscard program do and is at the bottom of the famous TRIM feature: flash memories are divided into "pages", ranging from several kilobytes to few megabytes usually.
    Erasing those pages using the discard command is very fast, much faster than zero-filling. You can erase all the pages of a whole eMMC in a few seconds, while zero-filling all the pages would require dozens of minutes.
     
    Doing an erase with blkdiscard and then restoring the backup skipping the blank parts now becomes sensible!
    There is an issue though: discarding pages does not fill them with 0x00 bytes, but with 0xff bytes, so the real blank parts now are not those which contains string of 0x00s but those which contains strings of 0xff bytes. Those may or may be not so common. Surely they are common in non-programmed sectors, but results may vary.
     
    As a conclusion: restoring the whole count of eMMC sectors, despite being slower, is surely the simplest and most reliable way!
  10. Like
    chinhhut reacted to curse in CSC Armbian for RK3318/RK3328 TV box boards   
    I noticed the same when I was trying to restore my backup. It got stuck at around 20-25 percent and I thought it might work better if I uncompress it first.
    Oups, I have a 64GB eMMC, and the SD card I had at the time was only 16 or 32 GB. 
    The backup is a raw disk image of the eMMC, and it will always be the same size as the eMMC until it's compressed, and "removing the blank data" is part of the compression process. 
  11. Like
    chinhhut reacted to balbes150 in Armbian for TV box rk3328   
    For everyone, in order to avoid problems and have a guaranteed working device with a desktop (DE XFCE \ Mate\Lxde\KDE\IceWM etc), I recommend using proven models. Now full-fledged devices are available that can completely replace the PC. Entry-level device Firefly Station M1 (rk3328). For those who need maximum performance Firefly Station P1 (rk3399). For these models, there are versions of ArmbianTV Armbian LibreELEC (there are versions with HW acceleration).
     
    https://www.stationpc.com/
     
     
    P.S. I have both models available, you can draw conclusions yourself ....
  12. Like
    chinhhut reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    Well, since the sd controller on his board is swapped I don't think it will ever work.
    But sometimes is true, more expensive cards are not always better.
  13. Like
    chinhhut reacted to curse in CSC Armbian for RK3318/RK3328 TV box boards   
    And perhaps try with different SD cards. I first used some expensive recommended 64GB SanDisk card and nothing worked then I tried a "no-name" cheap 8GB card and it worked perfectly. I think it's up to luck when it comes to the SD cards. The recommended expensive cards might work more often than the cheap ones, but sometimes it's the other way around. 
  14. Like
    chinhhut reacted to fabiobassa in CSC Armbian for RK3318/RK3328 TV box boards   
    @chinhhut
    Will try to explain you what loader is with an analogy: in normal pc you have bios and master boot record. Well, maskrom is bios and is contained in the soc itself, loader is a sort of master boot record and it enables the emmc and ddr.
    You can have a look here
    http://opensource.rock-chips.com/wiki_Boot_option

     

    I did extract it by a working firmware using a tool that unpacked the whole firmware. Try to google for RK3xxx_firmware_tools_5.23.1_by_SergioPoverony.zip and leave alone that github since it is just one piece of the puzzle. The detailed infos how to get a working loader are in the rockchip instructions

     

    Of course and the command would be rkdeveloptoo rl 0x0 etc etc etc ( try rkdeveloptool -h to get the help)
    But if you are lucky that works multitool, well that is the easiest way to clone and clone back
  15. Like
    chinhhut reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    That's true, because the sdcard controller is not where u-boot and kernel are told by device tree to look for.
     
    Adapting the device tree for the kernel is easy, but u-boot dtb requires a recompilation.
     
    When armbian is installed, u-boot is totally responsible for the boot process. It scans the devices to find a valid bootable system and the order is first sdcard, then USB and finally internal eMMC.
    If you have a lucky USB stick, you could try to put the Multitool on a USB stick and see if boots from there. I say "lucky USB stick" because u-boot USB code is buggy and does not always work.
     
    All kind of regular images (armbian, multitool, libreelec if available too...) can be burnt on USB stick or USB external hard drive: u-boot should prefer booting from there (if the buggy code doesn't kick in).
     
     
  16. Like
    chinhhut reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    Maybe with another USB stick or drive it may work. Also consider to use all the USB ports of the board, since they are not all the same. u-boot is picky.
     
    About the backup, indeed you can burn the multitool backup with rkdeveloptool. You just need to decompress it first.
  17. Like
    chinhhut got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    @fabiobassa @jock @hexdump 
    Thank you once again for your support.
     
    By the way, I still confused how to get the MiniLoaderAll.bin as you suggested.
    That file is built by yourself or pick up from here:
    https://github.com/rockchip-linux/rkbin/tree/master/bin/rk33
     
    As I checked, from the official Rockchip repo, there are several boodloader files related to RK3328 and I don't know how to choose the correct one.
     

  18. Like
    chinhhut got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    @jockI have one more question. Is there a way to dump the whole eMMC to .img file then using "./rkdeveloptool wl 0X0 file.img" to clone to new box. It looks similar to the backup and restore function from your Multitool. 
    That's great if we can use some function of Multitool under Linux.
     
    THank you.
  19. Like
    chinhhut got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    Thank you for detail explanation in a basic way.  I can understand the logic of booting process now.
     
    After booting from eMMC successfully, I try to boot from SD card again to try the multitool but not success. At current, my box still only can boot from eMMC.
     
    I guess using rkdevelopertool to backup will create the .img file that could be restored using "rkdeveloptool wl 0X0 yourimage.img" command, right?
    I will try to backup the entire eMMC using rkdevelopetool and report the result later. 
  20. Like
    chinhhut got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    I used Etcher to flash the Armbian image to the SD card as usual but it is unable to boot from SD card. 
  21. Like
    chinhhut got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    I'm going to follow your guide but I just want to confirm about the whole story from your idea.
    According to your guide, the MiniLoaderAll.zip contain the u-boot of the box? After flashing it to the eMMC successfully, the box may support to boot from USB and unable to boot from Android anymore? 
     
    One more question, how to get the MiniLoaderAll.zip as your attachment? You extract it from similar Rk3328 box or that's built manually by yourself.
    Thank you once again for detail suggestion.
  22. Like
    chinhhut got a reaction from RetroFan90 in CSC Armbian for RK3318/RK3328 TV box boards   
    @fabiobassa @jock I've followed your guide and got success. Thank you so much.
    root@mybox:~/rkdeveloptool# ls 99-rk-rockusb.rules Makefile.in RKComm.h RKImage.h RKScan.h cfg configure.ac main.cpp CMakeLists.txt Property.hpp RKComm.o RKImage.o RKScan.o config.h.in crc.cpp main.o DefineHeader.h RKBoot.cpp RKDevice.cpp RKLog.cpp Readme.txt config.ini crc.o parameter_gpt.txt Endian.h RKBoot.h RKDevice.h RKLog.h aclocal.m4 config.log gpt.h rkdeveloptool Makefile RKBoot.o RKDevice.o RKLog.o autom4te.cache config.status license.txt Makefile.am RKComm.cpp RKImage.cpp RKScan.cpp boot_merger.h configure log root@mybox:~/rkdeveloptool# ./rkdeveloptool ld DevNo=1 Vid=0x2207,Pid=0x320c,LocationID=101 Loader root@mybox:~/rkdeveloptool# ./rkdeveloptool rd 3 Reset Device OK. root@mybox:~/rkdeveloptool# ./rkdeveloptool db MiniLoaderAll.bin Opening loader failed, exiting download boot! root@mybox:~/rkdeveloptool# ./rkdeveloptool db /root/MiniLoaderAll.bin Downloading bootloader succeeded. root@mybox:~/rkdeveloptool# ./rkdeveloptool wl 0X0 /root/Armbian_21.11.0-trunk_Rk3318-box_bullseye_edge_5.14.14_minimal.img Write LBA from file (100%) root@mybox:~/rkdeveloptool# ./rkdeveloptool ---------------------Tool Usage --------------------- Help: -h or --help Version: -v or --version ListDevice: ld DownloadBoot: db <Loader> UpgradeLoader: ul <Loader> ReadLBA: rl <BeginSec> <SectorLen> <File> WriteLBA: wl <BeginSec> <File> WriteLBA: wlx <PartitionName> <File> WriteGPT: gpt <gpt partition table> WriteParameter: prm <parameter> PrintPartition: ppt EraseFlash: ef TestDevice: td ResetDevice: rd [subcode] ReadFlashID: rid ReadFlashInfo: rfi ReadChipInfo: rci ReadCapability: rcb PackBootLoader: pack UnpackBootLoader: unpack <boot loader> TagSPL: tagspl <tag> <U-Boot SPL> ------------------------------------------------------- root@mybox:~/rkdeveloptool# ./rkdeveloptool ld DevNo=1 Vid=0x2207,Pid=0x320c,LocationID=101 Maskrom  
  23. Like
    chinhhut reacted to hexdump in CSC Armbian for RK3318/RK3328 TV box boards   
    @chinhhut - this might be some interesting reading too regarding boxes, which cannot boot from sd card: https://github.com/hexdump0815/u-boot-misc/issues/2
     
    best wishes - hexdump
  24. Like
    chinhhut reacted to fabiobassa in CSC Armbian for RK3318/RK3328 TV box boards   
    @chinhhut
    Glad you got success .
    Don't forget to put a like that helps @jock and myself in community reputation
     
     
     
  25. Like
    chinhhut reacted to jock in CSC Armbian for RK3318/RK3328 TV box boards   
    @chinhhut