• Content Count

  • Joined

  • Last visited

About rmoriz

  • Rank

Recent Profile Visitors

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

  1. rmoriz

    Armbian for TV box rk3328

    Thanks for the tip! Using the identical image with the same UUID on SD and USB the system boots. First part of the boot process reads from the SD card but later mounting rootfs from USB (both devices are required to boot successfully). Ethernet works and I can access the internal eMMC. (nand-install and boot does not work on the first try, at least requires manual partitioning and bootloader installation. Will try later this week). Sadly WiFi and SD-Card seem not to work. Update: Booting with SD+eMMC (both required) works for me now (no USB stick) after: - used cfdisk to dump partition layout of my USB stick (select DUMP) - cfdisk --zero /dev/mmcblk1 (press L, load file from step above) to restore layout to eMMC (will delete all data on emmc!) - in cfdisk re-created ext4 partition to extend size to emmc + saved - changed `nand-sata-install` script to use /dev/mmcblk1 - executed nand-sata-install, without errors - after finish: change UUID of ext4 emmc partition to UUID of (inaccessible) SD ext4 partition. - sudo tune2fs /dev/mmcblk1p2 -U <UUID> - reboot
  2. rmoriz

    CSC Armbian for RK3288 TV Box boards (Q8)

    How one can backup the existing bootloader? Where does "rk3288_ubootloader_v1.01.06.bin" come from?
  3. rmoriz

    Armbian for TV box rk3328

    They are not the same, as my 64GB version has another radio chipset. There are at least two hardware versions out there, and there are different android firmware releases. One is "SSV6051_RTL8189" the other one is "HS2734".
  4. rmoriz

    Armbian for TV box rk3328

    H96 Max+ (4/64) (Original Posting) - UART (see Image) - serial output default booting android firmware: https://gist.github.com/rmoriz/6b01009ea62edfa9e58c5b9729eeabd2 I've found some stock firmware upgrade files, trying to squeeze some usable stuff using "binwalk".
  5. rmoriz

    Armbian for TV box rk3328

    Hi, got a H96 Max+ with 4GB and 64GB eMMC today (https://www.banggood.com/H96-Max-Plus-RK3328-4GB-RAM-64GB-ROM-Android-8_1-USB3_0-5G-WIFI-TV-Box-Support-HD-Netflix-4K-Youtube-p-1335810.html?ID=533601). It's booting Android 8.1 with a kernel 4.4.120, build date 2018-12-18. I opened it using a GB-5A opening tool. Attached are some pictures. 1. PCB is labelled as "RK3328_8D4_V1.1" with date "20180703" 2 .Wifi/BT chip seems to be: HS2734A V15628 98MA 3. eMMC seems to be Samsung: SEC525 B031 (unreadable due to QA marks) I flashed Armbian_5.68_Rk3328-tv_Ubuntu_bionic_default_4.4.154_20190110.img from your mega account to an microSD card. Tried all rk3328 FDTs in extlinux.conf # Result: LABEL=ROOTFS does not exists + drop to busybox rk3328-box-trn9.dtb rk3328-box-z28.dtb rk3328-box.dtb rk3328-evb-100m.dtb rk3328-evb.dtb rk3328-mx10.dtb rk3328-roc-cc.dtb rk3328-rock64-android.dtb rk3328-rock64.dtb rk3328-rockbox.dtb # Result: black screen/crash? rk3328-box-liantong.dtb rk3328-evb-android.dtb rk3328-t9-android.dtb Thanks Roland
  6. Happy New Year! Just built and tried Armbian_5.75_Orangepizeroplus2-h5_Debian_stretch_next_4.19.20.img using U-Boot 2019.01 but had no luck. Still hanging after "Trying to boot from MMC2"
  7. @martinayotte custom built Armbian_5.74_Orangepizeroplus2-h5_Ubuntu_bionic_next_4.19.17.img with U-Boot 2019.01 sadly hangs at the same point as the 2018.11 release: U-Boot SPL 2019.01-armbian (Jan 30 2019 - 13:08:51 +0000) DRAM: 512 MiB Trying to boot from MMC2 @Igor I've contacted "zhao_steven" via mail today at 13:05 UTC providing a screenshot of my AliExpress order and a summary of the thread including a link.
  8. I think this is the eMMC: upper side just for reference (says V 1.0) Thanks!
  9. I've built a custom image using the docker method (result was named Armbian_5.73_Orangepizeroplus2-h5_Ubuntu_bionic_next_4.19.17.img), etched it to SD, booted and installed it to eMMC. Result: U-Boot SPL 2018.11-armbian (Jan 28 2019 - 23:02:45 +0000) DRAM: 512 MiB Trying to boot from MMC2 (hangs, no LED, serial output) compared to the behaviour of the release image (as mentioned in my opening post already) U-Boot SPL 2018.05-armbian (Jan 12 2019 - 18:49:16 +0100) DRAM: 512 MiB Trying to boot from MMC2 (looping) "Synchronous Abort" handler, esr 0x8a000000 elr: 0000000000016895 lr : 0000000000016895 x 0: 0000000000017718 x 1: 0000000000000500 x 2: 0000000000000001 x 3: ffffff80ffffffc8 x 4: 0000000000000001 x 5: 000000000000004a x 6: 000000004fdffba8 x 7: 000000000000000a x 8: 0000000000000044 x 9: 800303d600000000 x10: 9419820400000000 x11: 000000000000000c x12: 4028177e0007fffe x13: 02042420a1fe8820 x14: 1c4401836c41c200 x15: 0012010004200000 x16: 102520254a2c0844 x17: 0c03fc405001bb46 x18: 000000004fdffe80 x19: 0000000000000022 x20: 00000000ffffffc8 x21: 000000004fdff0f0 x22: 000000000001717b x23: 000000000001717b x24: 000000004fdff0b0 x25: 000000004fdff5f1 x26: 000000004fdff0b1 x27: 0000000000000030 x28: 5e0f2289281c052c x29: 000000004fdff410 Resetting CPU ... resetting ... (/looping) PS: Yes, I've set verbosity=7 and console=both as before, by manually mounting the emmc filesystem and chaging /boot/armbianEnv.txt. There is sadly no change in outcome/output.
  10. Did you remove the SD card? Does it boot without the SD-Card?
  11. I know, I posted a lot, so I'll summarize it quickly for you: The remaining issue with Armbian is the "CPU reset" loop after a nand-sata-install immediately after power-up. There is no need to increase kernel verbosity because the kernel gets never loaded. U-Boot is broken.
  12. I did that ~25 times using 4 different Armbian builds without success however the year old OrangePI Ubuntu image does successfully install to eMMC *and* boot after. After checking the eMMC integrity successfully, there are two possibilities left: A. It never worked with Armbian B. It worked in an old Armbian release which is not available anymore. C. something changed in BROM (or whatver this is called with Allwinner) with my late 2018 board. This is very unlikely because the year old OrangePI image works. If A): Ok, I'll accept and stop If B): Tell me which version worked so I can do a bisect manually and debug. Thanks
  13. If you read this thread, you already see that I put some effort into it. Given that there is no documentation about the source of the overlay and u-boot files in Armbian, there is little to debug. It should be easy for you to tell me e.g. which u-boot patches your image uses or at least which git ref you build
  14. But this does not deliver an exact version build. I have many builds that don't work, another one will not help me. That's why I'm asking for exact versions.
  15. I already did a full eMMC test