aprayoga

  • Posts

    135
  • Joined

  • Last visited

1 Follower

Profile Information

  • Gender
    Male
  • Location
    Indonesia

Contact Methods

  • Github
    aprayoga

Recent Profile Visitors

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

aprayoga's Achievements

  1. Hi all, you could download the SATA firmware update at https://cdn-kobol-io.s3-ap-southeast-1.amazonaws.com/Helios64/SATA_FW/Helios64_SATA_FW_update_00021_200624.img.xz Instruction: 1. Download the sd card image 2. Flash the image into a microSD card 3. Insert microSD card into Helios64 and power on. Helios64 should automatically boot from microSD. If Helios64 still boot from eMMC, disable the eMMC 4. Wait for a while, the system will do a reboot and then power off if firmware flashing succeed. If failed, both System Status and System Fault LEDs will blink 5. Remove the microSD card and boot Helios64 normally. See if there is any improvement. Our officially supported stock firmware can be downloaded from https://cdn-kobol-io.s3-ap-southeast-1.amazonaws.com/Helios64/SATA_FW/Helios64_SATA_FW_factory_00020_190702.img.xz. If there is no improvement on newer firmware, please revert back to this stock firmware. SHA256SUM: e5dfbe84f4709a3e2138ffb620f0ee62ecbcc79a8f83692c1c1d7a4361f0d30f *Helios64_SATA_FW_factory_00020_190702.img.xz 0d78fec569dd699fd667acf59ba7b07c420a2865e1bcb8b85b26b61d404998c5 *Helios64_SATA_FW_update_00021_200624.img.xz
  2. It could be caused by power supply failure. Could you check the following thread ?
  3. ## Executing script at 09000000 Bad Linux ARM64 Image magic! @scottf007, it could be filesystem corruption or something wrong during update and kernel symlink was not updated to correct file. If you have access to Linux PC, you can use recovery button to enter UMS mode and do fsck or fixed the symlink. @wurmfood, it is not a problem. Rockchip loader expect the storage to be partitioned and formatted in certain way but it also can load using raw offset. Armbian does not use GPT, so the loader will print such errors.
  4. @SIGSEGV @clostro the service is triggered by udev rules. @wurmfood, I didn't realize the timer fill the the log every 20s. Initial idea was one time timer, poweroff after 10m of power loss event. Then it was improved to add polling of the battery level and poweroff when threshold reached. Your script look good, we are considering to adapt it to official release. Thank you
  5. Thank you for the report. The error code is different compared to the one reported here, which already fixed on this PR. We will investigate this issue
  6. bus-width 4 because of microsd card, not eMMC. As we already put warning note on our wiki, it is not supported out of box, because it could break the system. There are several cards that are not compatible and show error during the test. When those card used as boot drive (for the test, Helios4 boot from USB drive), it won't boot. Too risky to be included out of box. IMO, the card and the host controller should try to use lower/normal speed if higher one failed. but we don't see such case during our test.
  7. @jbergler could you modify /boot/armbianEnv.txt and add/modify following lines: verbosity=7 console=serial extraargs=earlyprintk ignore_loglevel It should make the serial console more verbose and output the systemd services to serial. Could you also post a step by step to set up and reproduce the crash? maybe also the detail of ZFS pool and HDD model and size.
  8. @antsu Could you post a step by step to set up and reproduce the crash? maybe also the detail of ZFS pool and HDD model and size.
  9. @crosser please modify /boot/armbianEnv.txt and add/modify following lines: verbosity=7 console=serial extraargs=earlyprintk ignore_loglevel It should make the serial console more verbose. mortomanos is referring to Armbian Device Tree Overlays
  10. The bootloader (u-boot) is configured to try loading OS from SD card first, then if it failed, it will try internal eMMC. You need to remove the jumper just before Linux initialized, otherwise the eMMC would not be detected. More info on our wiki.
  11. @kabo is this new fresh sd card image? I assume it is not, looking on u-boot build date that is quite old. Did you recently update & upgrade the Armbian? You can try my instruction on following thread:
  12. @JMCC Thanks for the hint. i'll take a look.
  13. @qrthi it seems something wrong during writing to eMMC. Your log show these lines Wrong image format for "source" command SCRIPT FAILED: continuing... How did you write the image? We recommend to use Etcher because it has write verification. The boot mode jumper only needed if for some reason the bootloader corrupted and to fix it you need to completely bypass the boot device. If the bootloader (u-boot) just fine, it will load Armbian from the sdcard first. The "Card did not respond to voltage select" is because you removed the sdcard. If you put Armbian sdcard, the lines would be Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3185 bytes read in 6 ms (517.6 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 My suggestion, 1. Download latest Armbian image. 2. Since you already have u-boot on your eMMC, no need to download and write the helios64_sdcard_u-boot-only.img.xz into sdcard. 3. Power on and enter UMS recovery mode 4. Write the image using Etcher. No need to extract the image. Etcher can handle it just fine. 5. Reboot Helios64.
  14. What do you mean? Have you managed to get serial console working? Have you checked our wiki?
  15. @apocrypha, theoretically Helios4 could support USB gadget since the SoC support USB OTG at one of the USB controller, i forgot which one, upper or lower. Unfortunately, Helios4 does not have circuitry to support this operation. Both of the USB is USB Host only. If you're referring to the micro usb port, it is not part of the USB controller of the armada 388. it using external USB to Serial converter IC