zero

Members
  • Content Count

    19
  • Joined

  • Last visited

  1. 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,,,
  2. 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?
  3. thanks,,, will try the latest one...
  4. 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
  5. @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" 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...
  6. 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; }; };
  7. ---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...
  8. 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 rk3328-linux-5.3.0.log
  9. ...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
  10. last week i was working on H6 tvb, but unfortunatly i broke the hardware... so now back to rk-3328 tvb,,, i was try to build linux 5.4.13 on it, last time it was working fine on 4.4.208... using the same kernel config, here errors what i got... (somehow it seems cant mount/find the rootfs) hope someone can help me figure it out... thanks... tvb-rk3328-model-x88-pro-armbian-linux-5.4.13.log linux-5.4.13-rk3328.config
  11. is that? congratulation to me,,, "my very first working self compiled u-boot" ok sir, next, move on to the dtbs,,, will try to find which is working... will continue using "Armbian_19.11.5_Arm-64_bionic_dev_5.5.0-rc2_2020017.img" which already write on my sdcard... thank for the advice,,,
  12. 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...
  13. 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?
  14. just great,,, will try the new "Armbian_19.11.5_Arm-64_bionic_dev_5.5.0-rc2_2020017.img"
  15. great,,, and where i can download and try this "20200117 19.11.5" things?