Jump to content

zero

Members
 View Profile  See their activity

  • Posts

    19

  • Joined

  • Last visited

 Content Type 

Posts posted by zero

    Armbian for TV box rk3328

    in Rockchip CPU Boxes

    Posted

    On 2/10/2020 at 3:29 PM, balbes150 said:

    Unlike rk3328, the S905x2 does not have and does not know when HW will be used to speed up DE and full-screen video.

     

     

     

    On 2/4/2020 at 4:56 PM, srx said:

    I see that RK3328 in my A5X max is getting really hot.

    It is just touch under 50°C at idle.

     

    last  week i bought tanix tx3-min which has s905w not the s095x2...

    both rk and amlogic got nearly same temperature here, about 50 C on idle,

    comparing the heat sink, the tx3 have better material by default

    despite the high temp the rk seems to be stable so far, i use it for media server and web server,,

    have not do much yet on the s905...

     

    and about the fake tvbs, just FYI, they are a mainline on my county... harder to get the original one, the chip inside of it, not chip they are displayed..

    got rk3228a on a mxq rk3229 tvb,

    got allwinner H3 on a mxq s905w tvb,

    but it's not that bad, i think it's more challenging doing with this fakes, because they are cheap hahaha,,,

    0

    Since Tanix TX6 can boot from the SD card

    in Allwinner CPU Boxes

    Posted

    Got this msg from the very beginning of the boat log...

    is this really tell that the board is broken/hardware fault?

     

    boot emmc 

    [168]HELLO! BOOT0 is starting!
[171]boot0 commit : 8
[185]set pll start
[188]set pll end
[190]rtc[0] value = 0x00000000
[193]rtc[1] value = 0x00000000
[196]rtc[2] value = 0x00000000
[199]rtc[3] value = 0x00000000
[202]rtc[4] value = 0x00000000
[205]rtc[5] value = 0x00000000
[208]DRAM VERSION IS V2_78
[211]the chip id is 0x00000003
[214]the chip id is 0x00000003
[217]the chip id is 0x00000003
[220]the chip id is 0x00000003
[223]the chip id is 0x00000003
[226]chip id check OK
[229]DRAM CLK =648 MHZ
[231]DRAM Type =3 (3:DDR3,4:DDR4,6:LPDDR2,7:LPDDR3)
[236]DRAM zq value: 003b3bfb
[540]MP_PGSR0 IS = 0100017d
[543]BYTE0 GATE ERRO IS = 00000000
[546]BYTE1 GATE ERRO IS = 00000000
[550]BYTE2 GATE ERRO IS = 00000000
[553]BYTE3 GATE ERRO IS = 00000000
[556]IPRD=00710070--PGCR0=0100017d--PLL=b0003500
[561]DRAM initial error : 1 !
[564]initializing SDRAM Fail.

     

    boot sdcard (tx6 image) 

    [177]HELLO! BOOT0 is starting!
[181]boot0 commit : 92fbece68a08eb88ae0862889a59ae15d6963156

[199]set pll start
[202]set pll end
[204]DRAM VERSION IS V2_761
[508]MP_PGSR0 IS = 0040005d
[511]BYTE0 GATE ERRO IS = 00000002
[514]BYTE1 GATE ERRO IS = 00000002
[518]BYTE2 GATE ERRO IS = 00000002
[521]BYTE3 GATE ERRO IS = 00000002
[826]MP_PGSR0 IS = 0100017d
[829]BYTE0 GATE ERRO IS = 00000000
[832]BYTE1 GATE ERRO IS = 00000000
[835]BYTE2 GATE ERRO IS = 00000000
[839]BYTE3 GATE ERRO IS = 00000000
[842]scan dram size fail !
[845]initializing SDRAM Fail.

    is there anything i can do to resolve this issue?

    0

    Armbian for TV box rk3328

    in Rockchip CPU Boxes

    Posted

    1 hour ago, srx said:

    Thanks for pointing me to that. I have not read the whole thread and missed that bit.

    As I understand, I have to add that block to dtb?

    I decompiled dtb, added that bit, recompiled. I hope I got it right - at least it booted :)

     

    I am running unified image with 5.5 kernel now. It still crashed before dtb update. I hope it works better now. We will see in few days if it is stable or not.

     

    If that fix works I think it should be included in images. Saves a lot of trouble for many people.

    thanks to hexdump,,, hehe

    btw where did you get this "Armbian_19.11.3_Rk3328-tv_buster_legacy_5.3.0_20191216.img" image?

    is there any available link for download?? i want to try to put it on my fake rk3318

    i still stuck using 4.4.x 

    0

    Armbian for TV box rk3328

    in Rockchip CPU Boxes

    Posted

    2 hours ago, hexdump said:

    @zero - welcome to the wonderful world of fake tv boxes - they are getting more and more common nowadays - you cannot really trust that you'll find in the boxes what is printed on them - the cheaper they are the more likely it is that they are fake with a hacked up android letting it look like having more ram, more emmc and a faster soc than they really have in a way, so that a normal user will not recognize it ... see my other posting about fake tv boxes here

     

    @hexdump they wrote it clearly "TV Box Rockchip RK3328" on the shop!!!

    fist time i'm doubt about it when i installed cpu-z on the android...

    and then this morning,,, it's just take me to the  "wonderful world of fake tv boxes"
     

     

    2 hours ago, hexdump said:

    @zero - btw. how did you find the emmc clk pin with an earphone? can you describe that a bit more?

     

    actually i have tried about 4 other false pin on the board, before i got the real emmc clk pin, but i have to make sure that all my test probe pin is safe to be short to GND,,,

    ahhh,,, never mind for this tips, actually its does not make a certain clue,,, forgive me,,, (what a joke using an ear phone, its clocked about 200Mhz right? )

    just i don't event have an oscilloscope, or frequency meter etc,,, should use that equimpmnt,,,

    once again forgive me, this morning just really a live in a day for me,,, 

     

    and your post about fake rk3318, yes i did, i see that when i was searching about it, i just want to make it sure,,,

    and ofcourse, for sharing my feelings about this fake world... :(

    0

    Armbian for TV box rk3328

    in Rockchip CPU Boxes

    Posted

    11 hours ago, srx said:

    Looks like 5.3 has the same crashing problem, it just took longer to get there (unless of course it is hardware issue that causes it).

    My A5X max just crashed again. Storage gone, nothing works. Shell is accessible but nothing works, everything gives "not found" or I/O error. Even reboot, init 6 or crtl+alt+del does not work. Only way is to pull the plug.

    And as storage is gone, no logs to diagnose the problem.

    This time I got 4 days uptime before it crashed.

     

    I guess I will try unified image next. It has 5.5.0 rc2 kernel.

    have u set the reserved tee memory on your dtb?

    it cost about 32MB or 36MB i'm not sure...

    like whats @hexdump already describe, yesterday this is was fixing my crash issue... 

            reserved-memory {
                #address-cells = <2>;
                #size-cells = <2>;
                ranges;

                tee@0x8400000 {
                        reg = <0x0 0x8400000 0x0 0x2400000>;
                        no-map;
                };
        };

     

    0

    Armbian for TV box rk3328

    in Rockchip CPU Boxes

    Posted

    ---CONFUSED---

    started at last night i just broke my x88 pro tvb, by flashing false uboot on the emmc, then every boot its crash caused by wrong DRAM frequency,,

    i guess my only way to fix it by entering maskroom mode, i open the boxes and pull out the heatsink, seeking some clue on there,,,

    just a bit surprissed, its was "Rockchip rk3318" (not 3328) cleary writen there...

     

    that was my confusion...

    Whats is rk3318? is it has the same family whit rk3328?

    searching on the web just found some few documentation about it,,,

    searching some configuration on some u-boot or kernel repository almost cant find anything usefull...

    hmmm...

     

    luckily this i found the EMMC CLK pin, searching it manually by using an earphone and listen to it.. (bcz i didnt see my board on the web)

    i reflash it then, its comeback to alive...

    i put it back on Armbian 19.11.9 using legacy kernel 4.4.210 which i compiled last night and using the Rock64 debian buster rootfs, since it was fine,,, (eth,IR OK, no wifi BT)

    may be will just stop trial on the 5.x kernel for now, until have enough clue on the 3318 things...

     

    here i attach some picture and logs... just a story...

    IMG_20200124_100150.jpg

    IMG_20200124_100331.jpg

    IMG_20200124_100117.jpg

    scr.png

    1

    Armbian for TV box rk3328

    in Rockchip CPU Boxes

    Posted

    3 hours ago, slaven said:

    srx, how did you manage to run the 5.3 kernel image on A5X max?

    I tried it myself but non of the dtb worked for me. I even tried to adapt a dtb step by step to the old dtb in Kerner 4.4 images...

    Can you please share and detail more how you succeeded booting Kernel 5.3 image?

    Did you even tried the universal images for all platforms?

     

     

     

    5 hours ago, srx said:

    New 5.3 kernel seems to be better than old 4.4.

    I tried image with 4.4 kernel version and it kept crashing with IO errors at least once a day. I could not get any logs because it was just like storage suddenly disconnected or something like that. Nothing worked. Not even reboot.

    I tried different SD cards but no change.

     

    Now I have image with 5.3 kernel and so far I have 3 days uptime and no problems/crashes yet.

     

    I am running it on A5X Max with 4GB ram from SD card.

    same to @slaven here i have x88-pro which can run linux 4.4.x but still keep crashing on 5.3.x or 5.4.x,,,

    wonder how @srx can manage to run it on 5.x

    but since i'm not expert on this compile things, may there is just a bit something that miss configured, usualy...

     

    so, here i attach the last log for i've been working on last few days...

    it stopped at say :

    [    3.473639] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
    [    3.474420] cfg80211: failed to load regulatory.db

    complete detail on the log file a attached, hope some help,,, again:rolleyes:

    rk3328-linux-5.3.0.log

    0

    Armbian for TV box rk3328

    in Rockchip CPU Boxes

    Posted

    4 hours ago, balbes150 said:

    Try running in combined mode (burn an image to two SD+USB media at once, configure it, and connect them simultaneously). Most likely, your DTB doesn't have support for the SD card.

     

    24 minutes ago, wdtz said:

    That's the  error for a misconfigured dtb, the voltage supply to mmc, @500000 and 5100000

    A non-standard regulator setup, like t9 or h96max+

    ...ahh,, that was it, @wdtz mmc supply voltage is the problem...

    now fixed :) thxs 

    [    3.047452] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/dwmmc@ff5f0000[0]'
[    3.048324] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/dwmmc@ff5f0000[0]'
[    3.049176] dwmmc_rockchip ff5f0000.dwmmc: using lookup tables for GPIO lookup
[    3.049857] dwmmc_rockchip ff5f0000.dwmmc: No GPIO consumer wp found
[    3.050502] dwmmc_rockchip ff5f0000.dwmmc: allocated mmc-pwrseq
[    3.051051] mmc_host mmc2: card is non-removable.
[    3.060702] vcc_arm: ramp_delay not set
[    3.064330] mmc_host mmc2: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[    3.067231] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[    3.068218] mmc0: new high speed SDHC card at address aaaa
[    3.070820] mmcblk0: mmc0:aaaa SL08G 7.40 GiB
[    3.073398]  mmcblk0: p1

    now mmc is working fine although still having another errors,

    @balbes150 USB+SD just a good ideas, at some case may this is tricks what i needed,, but for now i'll just continue on using SD,,,

    thxs

    0

    Single Armbian image for RK + AML + AW (aarch64 ARMv8)

    in General Chat

    Posted

    20 minutes ago, balbes150 said:

    By default, the image contains u-boot for rk3399. Did you replace u-boot with your version after writing the image to the SD card ?

     

    Images that already include u-boot for H6 (Tanix TX6) can be found here

    https://yadi.sk/d/GJbDt3-FjQ-dQA

    that time (while not booting to sdcard) not yet replace the u-boot,,,

    and now i did, replace the allwinner u-boot...

    first i got this (compiled config from orangepi 3 with ddr3 patch), stuck on the "Starting kernel ..." 

    U-Boot SPL 2019.10-armbian (Jan 18 2020 - 04:35:32 +0700)
DRAM: 2048 MiB
Trying to boot from MMC1


U-Boot 2019.10-armbian (Jan 18 2020 - 04:35:32 +0700) Allwinner Technology

CPU:   Allwinner H6 (SUN50I)
Model: OrangePi 3
DRAM:  2 GiB
MMC:   mmc@4020000: 0, mmc@4022000: 1
Loading Environment from EXT4...
** Unable to use mmc 0:auto for loading the env **
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 U-Boot script /boot.scr
673 bytes read in 2 ms (328.1 KiB/s)
## Executing script at 4fc00000
start mainline u-boot
1113 bytes read in 2 ms (543 KiB/s)
## Error: "mac" not defined
## Error: "eth_mac" not defined
23357952 bytes read in 2340 ms (9.5 MiB/s)
17531 bytes read in 6 ms (2.8 MiB/s)
## Flattened Device Tree blob at 4fa00000
   Booting using the fdt blob at 0x4fa00000
   Loading Device Tree to 0000000049ff8000, end 0000000049fff47a ... OK

Starting kernel ...

     

    second try (compiled config from orangepi oneplus with ddr3 patch) 

    U-Boot SPL 2019.10 (Jan 16 2020 - 22:13:46 +0700)
DRAM: 2048 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.2(debug):a04808c-dirty
NOTICE:  BL31: Built : 07:15:09, Jan 16 2020
NOTICE:  BL31: Detected Allwinner H6 SoC (1728)
NOTICE:  BL31: Found U-Boot DTB at 0xc07fff8, model: OrangePi One Plus
INFO:    ARM GICv2 driver initialized
NOTICE:  PMIC: Probing AXP805
IN

     

    both u-boot compiled using u-boot tools v2019.10 from Armbian build tools...

     

    0

    Single Armbian image for RK + AML + AW (aarch64 ARMv8)

    in General Chat

    Posted

    18 hours ago, balbes150 said:

    For some reason that I don't understand yet, on the Allwinner H6 (Tanix TX6) model, I have the SD card and eMMC numbers on the opposite side than on the other RK and AML models. If you have problems running on H6, try replacing these files with these options.

     

    https://yadi.sk/d/3crtWoQvvosh1w

    just tried to run "Armbian_19.11.5_Arm-64_bionic_dev_5.5.0-rc2_2020017.img" on on my H6 tvb (slightly different from tanix tx6 but it could run a tanix tx6 img from sdcard)

    and the result is as u expected,,, it's not boot the armbian, it's boot the android on the emmc directly, no attempt to boot the sdcard from logs...

    i did apply the "ALLWINNER_FIX_SCRIPT", and still the problem persist,,,

    may be there is another different issue especially on my h6 board (since its not exact tanix tx6)? or there was an issue on the u-boot?

    the last 19.11.4 did boot the armbian,,,

    what step i can try next?

    0

    Since Tanix TX6 can boot from the SD card

    in Allwinner CPU Boxes

    Posted

    34 minutes ago, balbes150 said:

    By the way, I published new images 20200117 19.11.5, there are several different DTB there. You can take this image, add your u-boot to it, and play with the different DTB that are there (you can try other ready-made DTB for kernel 5 from other sources). Setting up the DTB used there is very simple - change the name in the file " uEnv.txt".  

     

     

    For all. These images added a test version of the system installation in eMMC for H6.  :)

    great,,, and where i can download and try this "20200117 19.11.5" things?:D

    0

    Since Tanix TX6 can boot from the SD card

    in Allwinner CPU Boxes

    Posted

    2 hours ago, balbes150 said:

    Judging by the Armbian startup log, you are missing a working DTB for the kernel itself.

     

    ok thanks, i'll give it a try...

    so far i only working on the u-boot part...

     

    still have not touch or doing any patch on the kernel, i just copy it from a working kernel from my orangepi 3 board...

    soon i'll report again... thank you..

    0

    Since Tanix TX6 can boot from the SD card

    in Allwinner CPU Boxes

    Posted

    i have qidianz H6-6K series tvb, it seems almost the same with the tanix tx6 (H6 with DDR3)

    this device is able to run tanix image "Tanix_H6_4Gddr_8822bs_20190228.img" from the sdcard. everything seems to be well except the wifi

     

    nah,,, the problem is it still couldn't run any linux until now, for about a week have been working on it...

    so far this is what i got, the success boot log from the Android and the stuck log from compiled linux Armbian 19.11.8 - Orangepi 3 (with few patch, LPDDR3 to DDR3)

     

    hope anyone can tell what next step i should do on it... thanks...

    android.log linux-failed.log

    0

    Armbian for TV box rk3328

    in Rockchip CPU Boxes

    Posted

    have not try yet to run the 5.x kernel on my tvb... may will be do it soon...

     

    and about reserved tee memory, does that really needed? since it cost about 32M of memory...?

    last time i was still be able to run the system before i apply the patch from @caruso

     

     

    one more question about the armbian-firmware (usualy on "/lib/firmware")

    i didn't install any of it on the rootfs, does that have some further effect?

    for now cpu, ethernet, usb, ir, etc (except wifi-bt) are able to works without it's installed...

    0

    Armbian for TV box rk3328

    in Rockchip CPU Boxes

    Posted

    All the hard part are done by everyone's here,,, since the last u-boot and the dtb files from hexdump are telling almost everything to the board...:)

    I had the kernel run great on Armbian 19.11.7 image with Debian Buster 4.4.208 on its rootfs,,,

    So many thanks to hexdump and everyone...

    and i did some patch also on the cpu part on the dtb, for the scaling capabilities

    Quote


        cpu0-opp-table {
            nvmem-cell-names = "cpu_leakage";
            opp-shared;
            compatible = "operating-points-v2";
            nvmem-cells = <0x05>;
            phandle = <0x03>;
            rockchip,leakage-voltage-sel = <0x01 0x0a 0x00 0x0b 0xfe 0x01>;
            rockchip,video-4k-freq = <0xf6180>;

            opp-408000000 {
                opp-suspend;
                opp-hz = <0x00 0x18519600>;
                opp-microvolt = <0xe7ef0 0xe7ef0 0x149970>;
                opp-microvolt-L0 = <0xe7ef0 0xe7ef0 0x149970>;
                opp-microvolt-L1 = <0xe7ef0 0xe7ef0 0x149970>;
                clock-latency-ns = <0x9c40>;
            };
            
            opp-600000000 {
                opp-hz = <0x00 0x23c34600>;
                opp-microvolt = <0xe7ef0 0xe7ef0 0x149970>;
                opp-microvolt-L0 = <0xe7ef0 0xe7ef0 0x149970>;
                opp-microvolt-L1 = <0xe7ef0 0xe7ef0 0x149970>;
                clock-latency-ns = <0x9c40>;
            };

            opp-816000000 {
                opp-hz = <0x00 0x30a32c00>;
                opp-microvolt = <0x100590 0x100590 0x149970>;
                opp-microvolt-L0 = <0x100590 0x100590 0x149970>;
                opp-microvolt-L1 = <0xf4240 0xf4240 0x149970>;
                clock-latency-ns = <0x9c40>;
            };

            opp-1008000000 {
                opp-hz = <0x00 0x3c14dc00>;
                opp-microvolt = <0x118c30 0x118c30 0x149970>;
                opp-microvolt-L0 = <0x118c30 0x118c30 0x149970>;
                opp-microvolt-L1 = <0x10c8e0 0x10c8e0 0x149970>;
                clock-latency-ns = <0x9c40>;
            };
            
            opp-1104000000 {
                opp-hz = <0x00 0x41cdb400>;
                opp-microvolt = <0x137478 0x137478 0x149970>;
                opp-microvolt-L0 = <0x137478 0x137478 0x149970>;
                opp-microvolt-L1 = <0x12b128 0x12b128 0x149970>;
                clock-latency-ns = <0x9c40>;
            };
        };

     patch that i got by dumping the dtb on the original Android firmware running on my tvb...

    so far so good, at least for last 3 hours, since i apply the last patch from hexdump...

    Anyway my tvb is x88-pro, no much different from the h96...

     

    and.... waiting for any newer pacth...:P

    0
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept