chinhhut

  • Posts

    34
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

chinhhut's Achievements

  1. @jock For my RK3318 box, everything works well but recently there is always error message during starting up. The message is "[FAILED] Failed to start Resets System Activity Logs.", Here is the detail status of this service: root@mybox:~# systemctl status sysstat.service ● sysstat.service - Resets System Activity Logs Loaded: loaded (/lib/systemd/system/sysstat.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2021-11-25 12:10:54 +07; 26min ago Docs: man:sa1(8) man:sadc(8) man:sar(1) Process: 698 ExecStart=/usr/lib/sysstat/sa1 --boot (code=exited, status=2) Main PID: 698 (code=exited, status=2) CPU: 38ms Warning: journal has been rotated since unit was started, output may be incomplete. So I just confused how to fix this one. Thank you.
  2. https://github.com/home-assistant/os-agent/tree/main#using-home-assistant-supervised-on-debian @tv4you2016you can try this tutorial. Please note you should run the following command to see the detail log of installing process: journalctl -f -u hassio-supervisor.service You can post the log of your problem and others can suggest you more detail solution.
  3. 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.
  4. That's good idea but I don't know how to modify the .iso file while keep the files system consistency. I need to install a lot of applications and library such as docker etc.
  5. @jock I have an idea as follow to clone an Armbian box to new one and will try this weekend if reasonable. For instance, we have H96 max with 64GB flash. If making full backup of 64G flash and restore, it takes a lot of time. Here are major steps: Step 1: Install the Armbian according to your guide from page 1 (only take 1 minute to finish) to the box 1. Step 2: Boot Armbian from box 1 and using partition tool to divide the eMMC flash into 2 partitions,: partition 1 from beginning to 5GB. Partition 2 is remaining space Step 3: Make the backup of partition 1 by rkdeveloptool or similar partition tool to the PC Step 4: Install the fresh armbian to the box 2 like Step 1(only take 1 minute to finish) Step 5: boot the box 2 and make 2 partitions like Step 2. Step 6: using rkdevelopetool or similar to to restore the backup from Step 3 to partition 1 of box 2 I don't have much experience with partition tool on Linux and this is just idea. Please give us your any comments if any. Thank you.
  6. I've tried your way by decompressing the backup.gz file first then the extracted file is very big (the size is 16GB equal to the original eMMC size) and it takes much time to fully restoring. So is there a way to reduce the size of extracted image to save the restoring time? For example, the original size of eMMC is 16GB then the extracted image is also 16GB but the actual data size is only around 2-3GB. My idea is how to keep the data size only in the image and remove the blank data of the backup image. That might help to reduce the backup image even after decompressing.
  7. @jockI've tried but not success, may be I'm not lucky man :D. By the way, is there a way to restore the backup.gz from multitool to new box using "rkdeveloptool wl 0X0 yourimage.img" command? I mean change yourimage.img file with backup.gz.
  8. I used Etcher to flash the Armbian image to the SD card as usual but it is unable to boot from SD card.
  9. 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.
  10. @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.
  11. @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.
  12. @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
  13. 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.
  14. I already tried to push reset button in the AV hole while plugging the power but got same issue. Actually I've upload new firmware (android 9) to the box via Male to male cable using Rkdevtool 2.5.8 on windows 10. But the box is stucked at the splash screen after flashing (may be the Android firmware is not compatible). I will try to to connect the box with Ubuntu PC .
  15. So according to your hint, there should be a solution to install the customized u-boot to the Android firmware then try to boot from USB port, right? If so, could you give me the suggestion to do? I have some experience with ADB and some Linux/shell command like dd to extract/replace the bootloader before. Thank you.