hexdump

  • Content Count

    350
  • Joined

  • Last visited

Reputation Activity

  1. Like
    hexdump got a reaction from balbes150 in Armbian for TV box rk3328   
    i think i got it stable finally - i built u-boot for it myself (v2020.01) and did the following:
    loaderimage --pack --uboot ./u-boot-dtb.bin uboot.img 0x200000 # loaderimage on x86 dd if=uboot.img of=/dev/sdx seek=16384 the dd of trust.img as described above is required still. booted this way the box seems to run quite stable. i guess the u-boot i used before was setting a too advanced memory timing and my self build evb-rk3328 u-boot seems to have a more conservative memory timing which is ok for the box. i'll tomorrow upload a readymade dd'able u-boot here in case someone else wants to give it a try.
     
    i also tried to dd the spl/tpl idbloader.img and u-boot.itb too following https://github.com/u-boot/u-boot/blob/master/doc/README.rockchip but it looks the box initally boots off the emmc and only uses the u-boot on the sd-card, so the spl/tpl on the sd card were ignored.
     
    best wishes - hexdump
  2. Like
    hexdump got a reaction from Werner in h6 allwinner tv box need help!!!!   
    @jernej - success! finally ... it was the atf - i now built the atf myself (v2.2) and just emptied the axp probing function (so that it does nothing anymore and just returns an error back, i.e. no axp) and voila: it boots ... with the mainline u-boot it still resets dozens of times until it finally continues to boot, but it always does at some point in time after a few seconds or minutes (with the libdram version it boots absolutely reliable) ... so we are back to trying to improve the dram setup and timing to maybe get rid of the resets - please let me know in case you have any idea what else to maybe test ...
     
    a lot of thanks for all you help and support and best wishes - hexdump
     
    ... resetting ... U-Boot SPL 2020.01-rc3-00007-g8d8ee47e03-dirty (Jan 10 2020 - 16:34:14 +0100) DRAM:PLL = b0003500 DRAM PHY PGSR0 = 20003d DRAM PHY DX0RSR0 = 0 DRAM PHY DX1RSR0 = 0 DRAM PHY DX2RSR0 = 0 DRAM PHY DX3RSR0 = 0 Error while initializing DRAM PHY! resetting ... U-Boot SPL 2020.01-rc3-00007-g8d8ee47e03-dirty (Jan 10 2020 - 16:34:14 +0100) DRAM:MBUS port 0 cfg0 0100000d cfg1 00640080 MBUS port 1 cfg0 06000009 cfg1 01000578 MBUS port 2 cfg0 0200000d cfg1 00600100 MBUS port 3 cfg0 01000009 cfg1 00500064 MBUS port 4 cfg0 20000209 cfg1 1388157c MBUS port 5 cfg0 00640209 cfg1 00200040 MBUS port 6 cfg0 00640209 cfg1 00200040 MBUS port 8 cfg0 01000009 cfg1 00400080 MBUS port 11 cfg0 01000009 cfg1 00640080 MBUS port 14 cfg0 04000009 cfg1 00400100 MBUS port 16 cfg0 2000060d cfg1 09600af0 MBUS port 25 cfg0 0064000d cfg1 00200040 MBUS port 26 cfg0 20000209 cfg1 1388157c MBUS port 37 cfg0 01000009 cfg1 00400080 MBUS port 38 cfg0 00640209 cfg1 00200040 MBUS port 39 cfg0 20000209 cfg1 1388157c MBUS port 40 cfg0 00640209 cfg1 00200040 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.2(debug):v2.2-dirty NOTICE: BL31: Built : 16:17:47, Jan 10 2020 NOTICE: BL31: Detected Allwinner H6 SoC (1728) NOTICE: BL31: Found U-Boot DTB at 0xc07ad38, model: Eachlink H6 Mini INFO: ARM GICv2 driver initialized NOTICE: PMIC: Probing AXP805 <=== this is actually not doing anything in this version INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for 855873 was applied INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 U-Boot 2020.01-rc3-00007-g8d8ee47e03-dirty (Jan 10 2020 - 16:34:14 +0100) Allwinner Technology CPU: Allwinner H6 (SUN50I) Model: Eachlink H6 Mini DRAM: 2 GiB MMC: mmc@4020000: 0, mmc@4022000: 1 Loading Environment from FAT... Unable to use mmc 1:1... In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 1103 bytes read in 5 ms (214.8 KiB/s) 1: Armbian Retrieving file: /initrd.img-5.4.7-stb-ah6+ 11947280 bytes read in 1201 ms (9.5 MiB/s) Retrieving file: /Image-5.4.7-stb-ah6+ 21233672 bytes read in 2131 ms (9.5 MiB/s) append: root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyS0,115200 console=tty0 no_console_suspend cons0 Retrieving file: /dtb-5.4.7-stb-ah6+/sun50i-h6-eachlink-h6mini.dtb 21044 bytes read in 7 ms (2.9 MiB/s) ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 4949b000, end 49fffd10 ... OK Loading Device Tree to 0000000049492000, end 000000004949a233 ... OK Starting kernel ... Booting Linux on physical CPU 0x0000000000 [0x410fd034] Linux version 5.4.7-stb-ah6+ (root@eachlink) (gcc version 7.4.0 (Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)) #1 SMP 0 Machine model: Eachlink H6 Mini ...  
  3. Like
    hexdump got a reaction from amirul in Armbian for TV box rk3328   
    a little update regarding my rk3318 box - at my last try it was hanging at u-boot -> see:
    i finally got it booting by dd'ing the u-boot from this image: xenial-minimal-rock64-0.5.15-136-arm64.img.xz from https://github.com/ayufan-rock64/linux-build/releases/tag/0.5.15 to my sd-card and afterwards dd'ing the trust.img from:
    on top of it ... not really straight forward, but works at least
     
    best wishes - hexdump
  4. Like
    hexdump got a reaction from balbes150 in Single Armbian image for RK + AML + AW (aarch64 ARMv8)   
    hi @balbes150, i can confirm that your last image (1228) boots and runs well on a qplus h6 box ...
     
    best wishes and get well into the new year - hexdump
  5. Like
    hexdump got a reaction from Redferne in Since Tanix TX6 can boot from the SD card   
    @Redferne - try to add mem=2048M to the kernel cmdline - the eachlink h6 mini otherwise detects the memory wrong as 3gb although only 2gb are useable - thus it will crash as soon as it tries to access the part of the memory which does not really exist
     
    best wishes - hexdump
  6. Like
    hexdump got a reaction from balbes150 in Since Tanix TX6 can boot from the SD card   
    @balbes150 - one other thing: try to add "mem=2048M video=HDMI-A-1:e" to your kernel cmdline - some boxes (like my eachlink h6 mini) fail to detect the memory size properly and/or fail to enable the hdmi port otherwise ...
     
    best wishes - hexdump
  7. Like
    hexdump got a reaction from balbes150 in Since Tanix TX6 can boot from the SD card   
    hi @balbes150 - here is my dtb in source and binary and to make it complete also the other patches i use against the current megous 5.4 tree (just in case there is anything interesting in them for you). to my surprise the frequency scaling hack i was using with an adjusted opp table and fake vcccpu and dcdcc does not seem to work anymore in v5.4 (it only runs at fixed 900mhz again now) - i'll have to investigate why ...
     
    best wishes - hexdump
    emmc-fix.patch h6-ac200-eth-and-local-changes-v5.4.patch h6-ac200-eth-new-files.patch sun50i-h6-eachlink-h6mini.dts sun50i-h6-eachlink-h6mini.dtb
  8. Like
    hexdump got a reaction from balbes150 in Since Tanix TX6 can boot from the SD card   
    hi @balbes150, i think the attached one should be it (just dd it to the sd card with bs=512 skip=1 seek=1 to save the partiton table) - please let me know in case it should not work. i'll also attach my kernel config - maybe it helps you to figure out what is the problem with your generic one.
     
    good luck and best wishes - hexdump
    boot-h6_tv_box-aarch64.dd config-h6
  9. Like
    hexdump got a reaction from Werner in h6 allwinner tv box need help!!!!   
    its not a trivial problem (i usually get serial consoles working easily) - i tried close to all speeds etc. ... its either that the connectors are not for the serial console (but they really look like: 4 connectors, one is mass, another seems to be vcc and the other two in the middle go directly to the soc chip), there are maybe some electrical components missing to make it work properly or u-boot output is somehow scrambled (never seen something like this so far) ... these are at least my guesses ...
     
    best wishes - hexdump
  10. Like
    hexdump got a reaction from oneminute in A5x max - rk3328 help booting from emmc   
    @oneminute - maybe give this dtb a try for booting form sd card only:
     
  11. Like
    hexdump got a reaction from jernej in Since Tanix TX6 can boot from the SD card   
    @jernej - good news: this patch seems to fix the emmc problem - on the eachlink i can now read and write the emmc in a stable way and on the qplus - where it was hanging on boot with emmc enabled in dtb - it does not hang anymore on boot and i can also read and write the emmc
  12. Like
    hexdump got a reaction from kissste in Pine H64 model A - emmc boot stuck - sunxi-mmc 4022000.mmc: data error, sending stop command   
    @kissste - there is a good chance, that this patch will fix your problem too - for me it fixed the emmc problems - see
     
  13. Like
    hexdump got a reaction from jernej in Since Tanix TX6 can boot from the SD card   
    @jernej - bisecting in progress - 14 rounds, so it will take a while
  14. Like
    hexdump got a reaction from armar in Armbian for TV box rk3328   
    @armar - yes with the -I or -O fs options you can also use a device tree structure as input or output for the dtc command - it then works exactly like a dtb file with the -I or -O dtb options.
     
    @Sico - your edited dts file looks right - the last easy option is see would be to set the dmc-opp entry (memory voltage and frequency scaling) for opp-600000000 and opp-800000000 from disabled to okay like in your dts, but i guess it will not help much neither. opp-hz should not really differ between the dts files, except for the higher disabled clocks by me.
     
    if all that does not help, i would suggest you get some pl2003 usb to serial adapter and solder a serial console to your board (only gnd, rx and tx - usually tx from the board to rx of the adapter and the other way around). this way you will be able to see the bootup messages and get an idea about what really is the problem. one thing to be aware is that the baud speed of the serial console is 1500000 for rockchip devices instead of the usual 115200.
     
    good luck - hexdump
  15. Like
    hexdump got a reaction from armar in Armbian for TV box rk3328   
    hi @armar - the above device-tree-copy.tar.gz is the android dtb, just in another format and read from the system in an easier way
     
    @Sico - your hardware is definitely different from the 4g/32g t9 hardware - atttached is the resulting android dts file for your box - what you can do is: take my rk3328-t9.dts file from above and change all the opp-microvolt* values in the various sections to the values in your dts file and then build your dtb from it on a linux machine with the command "dtc -I dts -O dtb your-modified-rk3328-t9.dts > rk3328-t9-2g.dtb" and try this dtb then. you might need to install the "device-tree-compiler" package on your linux system for this.
     
    good luck and let me know about the result and post the resulting rk3328-t9-2g.dts and rk3328-t9-2g.dtb files here in case it works.
     
    hexdump
    t9-2g.dts
  16. Like
    hexdump got a reaction from Qooerr in Armbian for TV box rk3328   
    with this diff against rk3328-evb.dtb for the 4.4 rockchip kernel i got mmc, serial console and the usb2 port working for a t9 rk3328 box (4/32g) and i think the h96max+ is similar, so maybe it will work there too - the resulting rk3328-t9.dtb and .dts are attached as well. @balbes150 if it works for others too it might be worth to include it into future rk3328 tv box images maybe.
    rk3328-t9-dtb.diff
    rk3328-t9.dtb
    rk3328-t9.dts
  17. Like
    hexdump got a reaction from ole1105 in Armbian for TV box rk3328   
    with this diff against rk3328-evb.dtb for the 4.4 rockchip kernel i got mmc, serial console and the usb2 port working for a t9 rk3328 box (4/32g) and i think the h96max+ is similar, so maybe it will work there too - the resulting rk3328-t9.dtb and .dts are attached as well. @balbes150 if it works for others too it might be worth to include it into future rk3328 tv box images maybe.
    rk3328-t9-dtb.diff
    rk3328-t9.dtb
    rk3328-t9.dts