hexdump

Members
  • Content Count

    260
  • Joined

  • Last visited


Reputation Activity

  1. Like
    hexdump got a reaction from thanxx in Armbian for Amlogic S905X3   
    the legacy u-boot in those boxes is usually allocating away quite a bit of memory which you'll have to live with or your can try chainloading a mainline u-boot (which is what the u-boot.ext display hack is doing - on boxes where this is used there should be more memory available on average i guess)
     
    best wishes - hexdump
  2. Like
    hexdump reacted to Maker39 in CSC Armbian for RK322X TV Boxes   
    Since the changes from 10.04.2020 and the replacement of images on rk322x-box.
    Firmware replaced with new ones.
    LE_bootloader_Armbian_20.05.0-trunk_Rk322x-box_buster_current_5.5.16_minimal 2GB
    LE_bootloader_Armbian_20.05.0-trunk_Rk322x-box_buster_legacy_4.4.194_minimal 2GB
    LE_bootloader_Armbian_20.05.0-trunk_Rk322x-box_focal_legacy_4.4.194_desktop 4GB
    These are img from first post with Libreelec bootloader for boot without erase eMMC. Just insert a card and turn on power.
     
    Google Drive https://drive.google.com/open?id=1uoQvZUUFZyCWYFtatlTSJvJSSjUuJYLm
     
    26.06.2020
    Because at the moment, the firmware has lost its relevance. Deleted.
  3. Like
    hexdump got a reaction from Maker39 in CSC Armbian for RK322X TV Boxes   
    @Alessandro - you may try the following on a linux system, assuming your sdcard is in /dev/mysdcard (whichever device this might be in your case):
    "zcat working Librelec-xyz.img.gz | dd of=/dev/mysdcard bs=512 count=32768 status=progress"
    then use "fdisk /dev/mysdcard" to create a partition starting at sector 32768 (something like o, n, p, 1, 32768, enter, w, q - might be wrong - all off mind) and then dump the armbian image to it:
    "xzcat Armbian-xyz.img.xz | dd of=/dev/mysdcard bs=512 skip=8192 seek=32768 status=progress"
    and then try to boot that sd card - i think the armbian image uses an offset of 8192 sectors (@jock please correct me if i'm wrong here) - i never tried it this way, but in theory it should work and maybe be the fastest way to get libreelec boot and armbian rootfs combined
     
    good luck and best wishes - hexdump
  4. Like
    hexdump got a reaction from fabiobassa in Choice of TV box.   
    this is just a quick note that in my experience the amount of tv boxes with fake specs has grown quite a bit in the last months and that this is something to always have in mind when getting a box for a surprisingly cheap (i.e. quite a bit cheaper than usual or most of the other offerings) price - you might be lucky and it will be a bargain or you might hit one with fake specs. some examples i saw recently: a qplus 4g ram / 32g emmc ended up to be 2g ram and 16g nand, a h6 box sold as 4g ram / 32g emmc ended up as 2g ram / 16g emmc, a x96mini 2g ram / 16g emmc ended up at only 1g ram / 16g emmc, a r39 2g ram / 16g emmc with rockchip rk3229 ends up as 1g ram / 16g emmc and an allwinner h3 cpu and so on. the fake specs are not that easy to spot: in android they even fake the storage size shown in the storage settings and with a terminal installed even the "free" command tells you most of the time that the memory amount is proper. what usualy works for storage is "cat /proc/partitions" and watching for the device itself (for instance mmcblk0) - this also quickly shows you if its emmc (=mmcblk) or nand (=nand) and for memory "dmesg | grep -i mem" (do this immediately after booting android, otherwise the memory lines from the bootup might run out of the log buffer) - both of course called in a terminal app. booting one of balbes150's armbian images usually quickly shows you the real specs of the box too.
     
    good luck at not ending up with fake boxes and best wishes - hexdump
     
    p.s.: one thing to keep in mind is that allwinner h6 boxes always only can use 3g ram, even if they have 4g installed - this is a limitataion of the soc ...
  5. Like
    hexdump got a reaction from Nuno Cruz in Armbian for Amlogic S9xxx kernel 5.x   
    @Nuno Cruz - it is sometimes possible to extract some information from the original dtb and use it to adjust a mainline one, but its not easy and not always possible ...
  6. Like
    hexdump got a reaction from Nuno Cruz in Armbian for Amlogic S9xxx kernel 5.x   
    @Nuno Cruz - the original dtb is for android and most probably for another kernel version too, so there is no way to make it work without a lot of adaption work
  7. Like
    hexdump reacted to jock in CSC Armbian for RK322X TV Boxes   
    ahhh, right I remember that kernel config I had to disable the DMC devfreq config option because it was refusing to compile. Now it turned out that it was better to not have it.
    I'm going to publish new images with the dmc node disabled from the device tree, so there won't be any more issues.
  8. Like
    hexdump reacted to fabiobassa in CSC Armbian for RK322X TV Boxes   
    @hexdump

    thanks for replayng ;   you have a 3228 and not a 3229 , probabily a 3228b

    00000000  52 4b 23 82 the numbers 23 82 are 3228 in reverse mode
    so you must use trust os for 3228, the trust os for 3229 simply will not boot the board but this you already knew

    regarding the changing in code in kernel I did the following ( but no changes in code, maybe in make config ) : 

    in my long post linux on 3229  I used too the kernel 4.4.189 and it worked fine. I booted in 4.4.189 and take the config.gz and then recompile 4.4.194 with that same .config and it worked with SAME dtb .

    last info : I am pretty sure you have uart debug. At very early booting ( power on) what ddr it says ?

    ddr3 or ddr2 ? because ddr2 on 3228 HAVEN'T dmc ( ddr frequency scaling) so they will run at the speed that uboot set , probabily at 333 mhz ( all this infos thanks to @knaerzche that explained in his work on libreelec ).

    If you have ddr2 you must DISABLE dmc node in dtb


    boards with 3228b and ddr2..... well.... they are a bit slower than others


    EDIT:

    i realized the different behaviour from kernel 4.4.194 to 4.4.189

    in @jock config many thing are compiled as modules so then you must insert right modules under /lib/modules

    in 4.4.189 compilation many things are compiled IN kernel so they work  out of box, but yet you should check if have ddr2 or ddr3
     
  9. Like
    hexdump reacted to Alessandro in CSC Armbian for RK322X TV Boxes   
    Thanks so much @jock and of course @hexdump and @fabiobassa...
     
    I followed the @hexdump instruction about how to mix the LibreELEC for the mk809iv and one of the latest Armbian image from this page (the Armbian 20 05 0 trunk R329q bionic legacy 4.4.194 desktop). 
     
    it worked at first try... wired eth working. Imam checking all the other features.
     
    I‘ll keep you posted.
     
    thanks so much, Alessandro 

  10. Like
    hexdump got a reaction from jock in CSC Armbian for RK322X TV Boxes   
    @jock - thanks a lot - i'll give them a try soon ...
     
    update: i gave the 4.4 versions (both)  a try on the 2gb ram r39-4k and they hang at some point - retried the old kernel and that one still works (but only exposes 1gb ram) ... could this be the himem instability you mentioned?
     
    will have to check in more detail in the next days ... sadly without a working serial console its hard really see where it hangs (screen goes black and keyboard is dead)
     
    best wishes - hexdump
  11. Like
    hexdump got a reaction from MX_Master in Is Mali GPU driver available in Mainline for H3?   
    this xorg conf does not refer to the armsoc driver - here is a proven to be working example for an armsoc xorg.conf: https://github.com/hexdump0815/imagebuilder/blob/master/files/extra-files/etc/X11/xorg.conf.d.samples/01-armsoc.conf
  12. Like
    hexdump got a reaction from MX_Master in Is Mali GPU driver available in Mainline for H3?   
    maybe build your own kernel with lima disabled (i'm not sure, but i think it might conflict with the old mali driver even if the module is not loaded) ... make sure you apply those two patches:
    https://github.com/hexdump0815/linux-mainline-and-mali-generic-stable-kernel/blob/master/misc.av7/sunxi-drm-gem-cma-Export-with-handle-allocator.patch
    https://github.com/hexdump0815/linux-mainline-and-mali-generic-stable-kernel/blob/master/misc.av7/sunxi-drm-sun4i-Add-GEM-allocator.patch
     
    here are my own notes on getting this to work, which are verified to work up until v5.4 kernels:
    https://github.com/hexdump0815/linux-mainline-and-mali-generic-stable-kernel/blob/master/readme.av7-mali-sunxi
     
    good luck and best wishes - hexdump
  13. Like
    hexdump got a reaction from MX_Master in Is Mali GPU driver available in Mainline for H3?   
    another thing to keep in mind is that your user needs access to /dev/mali - usually granted via some udev rule and the video group (usermod -a -G video username) ... example udev rule: https://github.com/hexdump0815/imagebuilder/blob/master/files/extra-files/etc/udev/rules.d/50-mali.rules
     
    good luck and best wishes - hexdump
  14. Like
    hexdump got a reaction from jock in Is Mali GPU driver available in Mainline for H3?   
    another thing to keep in mind is that your user needs access to /dev/mali - usually granted via some udev rule and the video group (usermod -a -G video username) ... example udev rule: https://github.com/hexdump0815/imagebuilder/blob/master/files/extra-files/etc/udev/rules.d/50-mali.rules
     
    good luck and best wishes - hexdump
  15. Like
    hexdump got a reaction from sfx2000 in Choice of TV box.   
    this is just a quick note that in my experience the amount of tv boxes with fake specs has grown quite a bit in the last months and that this is something to always have in mind when getting a box for a surprisingly cheap (i.e. quite a bit cheaper than usual or most of the other offerings) price - you might be lucky and it will be a bargain or you might hit one with fake specs. some examples i saw recently: a qplus 4g ram / 32g emmc ended up to be 2g ram and 16g nand, a h6 box sold as 4g ram / 32g emmc ended up as 2g ram / 16g emmc, a x96mini 2g ram / 16g emmc ended up at only 1g ram / 16g emmc, a r39 2g ram / 16g emmc with rockchip rk3229 ends up as 1g ram / 16g emmc and an allwinner h3 cpu and so on. the fake specs are not that easy to spot: in android they even fake the storage size shown in the storage settings and with a terminal installed even the "free" command tells you most of the time that the memory amount is proper. what usualy works for storage is "cat /proc/partitions" and watching for the device itself (for instance mmcblk0) - this also quickly shows you if its emmc (=mmcblk) or nand (=nand) and for memory "dmesg | grep -i mem" (do this immediately after booting android, otherwise the memory lines from the bootup might run out of the log buffer) - both of course called in a terminal app. booting one of balbes150's armbian images usually quickly shows you the real specs of the box too.
     
    good luck at not ending up with fake boxes and best wishes - hexdump
     
    p.s.: one thing to keep in mind is that allwinner h6 boxes always only can use 3g ram, even if they have 4g installed - this is a limitataion of the soc ...
  16. Like
    hexdump got a reaction from mar0ni in [Development] RK3399 media script   
    @mar0ni - yes this is normal behaviour i think as there is some inefficient memory copying happening between the gpu and the x server and there is no proper 2d acceleration (used for such window moves) around ... but i guess @JMCC can explain it in more detail ...
     
    best wishes - hexdump
  17. Like
    hexdump got a reaction from OrangePee in Armbian on "M8S Plus W" (905W without microSD)   
    btw. i doubt that the initially mentioned box really has 2g/16g at this price - see my other posting about fake tv boxes here - i guess it will be 1g/8g maybe even nand instead of emmc if you are unlucky - all this with a hacked up android letting it look like 2g/16g so that a normal user will not recognize it ...
  18. Like
    hexdump got a reaction from TRS-80 in Armbian for TV box rk3328   
    @martos - some things which come to my mind:
    did you try my t9 dtb?  - see: most probably it will not work as your box does not seem to boot off sd card at all another thing worth trying is combined sd/usb booting - see this thread:  if all that does not work then you might have to flash it via usb (i think i have read that some tv boxes have the sd card connected to the wrong mmc port and are thus not sd card bootable at all) - see here and above and below it: good luck and best wishes - hexdump
  19. Like
    hexdump got a reaction from manuti in Choice of TV box.   
    this is just a quick note that in my experience the amount of tv boxes with fake specs has grown quite a bit in the last months and that this is something to always have in mind when getting a box for a surprisingly cheap (i.e. quite a bit cheaper than usual or most of the other offerings) price - you might be lucky and it will be a bargain or you might hit one with fake specs. some examples i saw recently: a qplus 4g ram / 32g emmc ended up to be 2g ram and 16g nand, a h6 box sold as 4g ram / 32g emmc ended up as 2g ram / 16g emmc, a x96mini 2g ram / 16g emmc ended up at only 1g ram / 16g emmc, a r39 2g ram / 16g emmc with rockchip rk3229 ends up as 1g ram / 16g emmc and an allwinner h3 cpu and so on. the fake specs are not that easy to spot: in android they even fake the storage size shown in the storage settings and with a terminal installed even the "free" command tells you most of the time that the memory amount is proper. what usualy works for storage is "cat /proc/partitions" and watching for the device itself (for instance mmcblk0) - this also quickly shows you if its emmc (=mmcblk) or nand (=nand) and for memory "dmesg | grep -i mem" (do this immediately after booting android, otherwise the memory lines from the bootup might run out of the log buffer) - both of course called in a terminal app. booting one of balbes150's armbian images usually quickly shows you the real specs of the box too.
     
    good luck at not ending up with fake boxes and best wishes - hexdump
     
    p.s.: one thing to keep in mind is that allwinner h6 boxes always only can use 3g ram, even if they have 4g installed - this is a limitataion of the soc ...
  20. Like
    hexdump got a reaction from jeanrhum in Choice of TV box.   
    this is just a quick note that in my experience the amount of tv boxes with fake specs has grown quite a bit in the last months and that this is something to always have in mind when getting a box for a surprisingly cheap (i.e. quite a bit cheaper than usual or most of the other offerings) price - you might be lucky and it will be a bargain or you might hit one with fake specs. some examples i saw recently: a qplus 4g ram / 32g emmc ended up to be 2g ram and 16g nand, a h6 box sold as 4g ram / 32g emmc ended up as 2g ram / 16g emmc, a x96mini 2g ram / 16g emmc ended up at only 1g ram / 16g emmc, a r39 2g ram / 16g emmc with rockchip rk3229 ends up as 1g ram / 16g emmc and an allwinner h3 cpu and so on. the fake specs are not that easy to spot: in android they even fake the storage size shown in the storage settings and with a terminal installed even the "free" command tells you most of the time that the memory amount is proper. what usualy works for storage is "cat /proc/partitions" and watching for the device itself (for instance mmcblk0) - this also quickly shows you if its emmc (=mmcblk) or nand (=nand) and for memory "dmesg | grep -i mem" (do this immediately after booting android, otherwise the memory lines from the bootup might run out of the log buffer) - both of course called in a terminal app. booting one of balbes150's armbian images usually quickly shows you the real specs of the box too.
     
    good luck at not ending up with fake boxes and best wishes - hexdump
     
    p.s.: one thing to keep in mind is that allwinner h6 boxes always only can use 3g ram, even if they have 4g installed - this is a limitataion of the soc ...
  21. Like
    hexdump got a reaction from balbes150 in Choice of TV box.   
    this is just a quick note that in my experience the amount of tv boxes with fake specs has grown quite a bit in the last months and that this is something to always have in mind when getting a box for a surprisingly cheap (i.e. quite a bit cheaper than usual or most of the other offerings) price - you might be lucky and it will be a bargain or you might hit one with fake specs. some examples i saw recently: a qplus 4g ram / 32g emmc ended up to be 2g ram and 16g nand, a h6 box sold as 4g ram / 32g emmc ended up as 2g ram / 16g emmc, a x96mini 2g ram / 16g emmc ended up at only 1g ram / 16g emmc, a r39 2g ram / 16g emmc with rockchip rk3229 ends up as 1g ram / 16g emmc and an allwinner h3 cpu and so on. the fake specs are not that easy to spot: in android they even fake the storage size shown in the storage settings and with a terminal installed even the "free" command tells you most of the time that the memory amount is proper. what usualy works for storage is "cat /proc/partitions" and watching for the device itself (for instance mmcblk0) - this also quickly shows you if its emmc (=mmcblk) or nand (=nand) and for memory "dmesg | grep -i mem" (do this immediately after booting android, otherwise the memory lines from the bootup might run out of the log buffer) - both of course called in a terminal app. booting one of balbes150's armbian images usually quickly shows you the real specs of the box too.
     
    good luck at not ending up with fake boxes and best wishes - hexdump
     
    p.s.: one thing to keep in mind is that allwinner h6 boxes always only can use 3g ram, even if they have 4g installed - this is a limitataion of the soc ...
  22. Like
    hexdump got a reaction from Tarzanus in TV Box A95X Z2 - RK3318   
    @Tarzanus - you might give this approach a try:
    best wishes - hexdump
  23. Like
    hexdump got a reaction from Tarzanus in TV Box A95X Z2 - RK3318   
    you need to dd the trust.img as well - just read the thread from the post i linked to onwards for the file and more info ...
     
    good luck - hexdump
  24. 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
  25. 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 ...