Jump to content

caruso

Members
  • Posts

    8
  • Joined

  • Last visited

Posts posted by caruso

  1. 7 hours ago, pinder said:

    no luck with anything.

    i tried 4.4 image  and dtb as told by @caruso and dd trust.img and uboot.img. Nothing on the screen.

    even i copied trust.img and uboot.img to the uboot directory. 

     

     

    Please help i have a95x z2 2gb/16gb 5 pieces in which i want to install linux. 

     

    i must be missing something.

    @balbes150 please any help is appriciated.

     

     

  2. 8 hours ago, pinder said:

    huge applaud to really great preole out there.

     

    I have a95x z2 rk3318 2gb Ram 16gb Rom model.

    i have tried @hexdump dtb, trust.img from @caruso 

    and used 'armbian_20.02.0-rc1.038_rk3328-tv_bionic_current_5.5.0-rc6_desktop_20200205.img.xz'  from the firrst link

    I get nothing but unsupported on my hdmi monitor.

    please help with the file selection.

    Especially @Tarzanus as you got the same device, in 4gb ram model

    Try images with kernel 4x. You can also try my dtb which works with libreelec and have remote, diode, wifi working.

    rk3318-t9_remote_diode_wifi_110.dtb

  3. 2 hours ago, hexdump said:

    update: i think i have found another problem - as we are using the trust.img we have to unmap the trust memory area from the kernel, otherwise it will panic whenever it will try to access memory in that region. this can be done with a reserved memory region in the dtb:

    
    /* seems to be required to not touch the trust area - see:
       - https://forum.manjaro.org/t/rockpro64-kernel-panics-caused-by-firmware/117900
       - https://lore.kernel.org/linux-arm-kernel/006d3ee0-2711-1b4e-d8cf-6a226fcad0e4@arm.com/
    */
            reserved-memory {
                    #address-cells = <2>;
                    #size-cells = <2>;
                    ranges;
    
                    tee@0x8400000 {
                            reg = <0x0 0x8400000 0x0 0x2400000>;
                            no-map;
                    };
            };
    

    after this the box finally seems to run completely stable now (this might be of interest for @caruso and @Tarzanus too most probably). attached are updated mainline dts/dtb files with this inside (beware, those files is for mainline and not the 4.4 rockchip kernel).

     

    @Amoren - better wait a bit before using all this stuff as it is still quite a bit in the move.

     

    best wishes - hexdump

    rk3318-h96max.dts 11.67 kB · 1 download rk3318-h96max.dtb 33.34 kB · 1 download

    @hexdump Thanks for sharing, I was playing with different dtbs and sometimes I had kernel panic.

    Did you managed to have working ir remote?

    I was also playing with LibreElec with manual:

    https://forum.libreelec.tv/thread/20813-step-by-step-tutorial-libreelec-on-h96-max-also-ir-remote-support/

    and I successfully run with rk3318, by analogy (dding trust.img, removing >1.1 GHz frequencies from cpu section of dts and recompile dtb)

     

     

  4. 13 hours ago, Amoren said:

    Hello, I have the h96max rk3318 box. I extracted the  Armbian_19.11.3_Rk3328-tv_eoan_legacy_4.4.154_desktop_20191126 onto sd card (i rememeberd to make changes to the conf and env files) then I inserted to my box but it wont boot at all. only when i remove the sd card it reboots again to android.

    Any help to boot from sd card? Thanx...

    dding of trust.img and copy of 3318.dtb is needed also, check my description. You can execute dd command from virtual machine (i.e virtual box), linux machine, or even in terminal on the same box when it's booted to android, you must check only name of target sdcard device.

    You can extract trust.img or use attached one in this thread.

     

     

  5. 14 minutes ago, hexdump said:

    @caruso - the dtb is not relevant here, as it still fails in u-boot ... here is the full boot log:

    
    DDR version 1.16 20190713                                                             
    ID:0xFFF                                                                               
    In                                                                                    
    DDR3                                                                                   
    333MHz                                                                                 
    Bus Width=32 Col=11 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=2048MB                   
    ddrconfig:2                                                                           
    OUT                                                                                   
    Boot1 Release Time: May 13 2019 17:34:36, version: 2.50                               
    ChipType = 0x11, 232                                                                   
    mmc2:cmd19,100                                                                         
    SdmmcInit=2 0
    BootCapSize=2000
    UserCapSize=15028MB
    FwPartOffset=2000 , 2000
    mmc0:cmd5,20
    SdmmcInit=0 0
    BootCapSize=0
    UserCapSize=15279MB
    FwPartOffset=2000 , 0
    StorageInit ok = 169710
    Raw SecureMode = 0
    SecureInit read PBA: 0x4
    SecureInit read PBA: 0x404
    SecureInit read PBA: 0x804
    SecureInit read PBA: 0xc04
    SecureInit read PBA: 0x1004
    SecureInit ret = 0, SecureMode = 0
    atags_set_bootdev: ret:(0)
    GPT 0x337a9f0 signature is wrong
    recovery gpt...
    GPT 0x337a9f0 signature is wrong
    recovery gpt fail!
    LoadTrust Addr:0x4000
    No find bl30.bin
    Load uboot, ReadLba = 2000
    Load OK, addr=0x200000, size=0xa2ad8
    RunBL31 0x10000
    NOTICE:  BL31: v1.3(release):0e7a845e
    NOTICE:  BL31: Built : 16:24:22, Apr 29 2019
    NOTICE:  BL31:Rockchip release version: v1.3
    INFO:    ARM GICv2 driver initialized
    INFO:    Using opteed sec cpu_context!
    INFO:    boot cpu mask: 1
    INFO:    plat_rockchip_pmu_init: pd status 0xe
    INFO:    BL31: Initializing runtime services
    INFO:    BL31: Initializing BL32
    INF [0x0] TEE-CORE:init_primary_helper:337: Initializing (1.1.0-221-gda2bcfdc #137 Mon Jun 17 03:00:04 UTC 2019)
    INF [0x0] TEE-CORE:init_primary_helper:338: Release version: 1.4
    INF [0x0] TEE-CORE:init_teecore:83: teecore inits done
    INFO:    BL31: Preparing for EL3 exit to normal world
    INFO:    Entry point address = 0x200000
    INFO:    SPSR = 0x3c9
    
    U-Boot 2019.10-armbian (Nov 29 2019 - 09:50:19 +0300)
    
    Model: Rockchip RK3328 EVB
    DRAM:

    could you maybe post yours too for comparision?

     

    best wishes - hexdump

     

    Yes, sure - please find in attachment.

     

    teraterm.log

  6. 2 hours ago, hexdump said:

    @caruso - i can confirm that your trust.img approach ist bringing the boot forward and the main part of u-boot is properly loaded, but for my box (2gb) sadly hangs quite early on:

     

    ...

    U-Boot 2019.10-armbian (Nov 29 2019 - 09:50:19 +0300)

    Model: Rockchip RK3328 EVB
    DRAM:

     

    looks like a memory timing issue to me ( @jernej - maybe any idea here too, although this is rockchip?). @caruso - on you website you have a file write_dd.txt in which you are writing more than just the trust.img - i assume that was just some intermediate step of your tries maybe?

     

    best wishes - hexdump

     

    Regarding write_dd.txt - indeed, there were many trials but I was able to reproduce working scenario with minimum dd'ing trust.img only.

    My box is 4GB/64GB, not sure maybe some changes are needed in dts/dtb for 2GB versions.

    Maybe post whole log up to hang moment.

     

  7. 12 hours ago, hexdump said:

    @caruso - do you have a download link for the rk3318_9.0_hcy_20191114_v002 firmware?

     

    update: ok - found it - how did you extract its contents? all linux cmdline tools to unpack the update.img file seem to fail for me ...

    @hexdump

     

    I think I took firmware from: https://www.h96tvbox.com/content/6-Firmware-upgrade

     

    I've unpacked with img_unpack and afptool tools available in git repo: https://github.com/TeeFirefly/rk2918_tools.git

    I took instructions from http://wiki.t-firefly.com/ROC-RK3328-CC/fw_pack_unpack.html

     

    unzip rk3318_9.0_hcy_20191114_v002.zip to update.img
    git clone https://github.com/TeeFirefly/rk2918_tools.git
    cd rk2918_tools
    make
    sudo cp afptool img_unpack img_maker mkkrnlimg /usr/local/bin

    Unpack update.img, which creates img folder with update.img and loader.img

     

    img_unpack update.img img
    rom version: 9.0.0
    build time: 2019-11-14 13:59:46
    chip: 33323248
    checking md5sum....OK

     

    Unpack update.img

     

    cd img
    afptool -unpack update.img update
    Check file...OK
    ------- UNPACK -------
    package-file    0x00000800      0x000002C0
    Image/MiniLoaderAll.bin 0x00001000      0x0002E94E
    Image/parameter.txt     0x00030000      0x00000372
    Image/trust.img 0x00030800      0x00400000
    Image/uboot.img 0x00431000      0x00400000
    Image/misc.img  0x00831800      0x0000C000
    Image/baseparameter.img 0x0083E000      0x00100000
    Image/dtbo.img  0x0093E800      0x00000133
    Image/boot.img  0x0093F000      0x01E81000
    Image/recovery.img      0x027C0800      0x0285E800
    Image/system.img        0x0501F800      0x78DBA0E8
    Image/vendor.img        0x7DDDA000      0x08DAB064
    Image/oem.img   0x86B85800      0x0002704C
    Image/vbmeta.img        0x86BAD000      0x00001000
    RESERVED        0x00000000      0x00000000
    UnPack OK!

     

    rk3318-t9.dtb dtb based on rk3328-t9.dtb with removed cpu freqencies > 1.1GHz

    rk3318-t9.dts - text version for above

     

    device-tree-copy.tar.gz - taked from running android environment

    rk3318_org_android.dts - dts for above

    rk3318_org_android.dtb - dtb for above - for me this version doesn't work, which was strange for me

    trust.img - extracted trust.img from firmware update

     

  8. Hi everyone,

     

    I would like to share my work which leads to boot from sdcard device based on RK3318 to desktop armbian.

     

    I've was using Armbian_19.11.3_Rk3328-tv_eoan_legacy_4.4.154_desktop_20191126.img and end up with booting to desktop

    What doesn't work for me:

    • onboard wifi (usb dongle works, old tp-link tl-wn725N)
    • onboard bluetooth

    My box is same as picture below:

    h96-max-rk3318-review-s03-min.jpg

    https://androidpctv.com/review-h96-max-opinion/

     

    I've burned image with rufus on windows and my first boot trial finished with boot hang up:

     

    bl31.PNG

     

    I've solved this issue by invoking following code where /dev/mmcblk0 is sdcard device in linux, and trust.img was extracted from rk3318_9.0_hcy_20191114_v002 updage image.

     

    dd if=trust.img of=/dev/mmcblk0 seek=24576
    sync
    

    After that boot sequence went further. I'm not sure but I guess that debug vs release version of bl31 might be problem here.

     

    bl31_release.PNG

     

    Also, I've used rk3318-t9.dtb file prepared based on rk3328-t9.dtb posted in this thread, with removing cpu freqencies > 1.1GHz, as box was unstable with such high frequencies.

     

    I didn't find option here to attach file so temporaraly you can find my modified file here rk3318-t9.dtb and other useful files here:

    https://freeshell.de/~tiloc/armbian/

     

    I hope it will be useful for somebody :)

     

     

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines