martos Posted August 31, 2018 Share Posted August 31, 2018 (edited) the boot with bionic-minimal-rock64-0.7.9-1067-arm64.img.xz ( it stop at the end ) Spoiler DDR version 1.10 20171106 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: 2017-06-12, version: 2.44 ChipType = 0x11, 171 SdmmcInit=2 0 BootCapSize=2000 UserCapSize=7456MB FwPartOffset=2000 , 2000 SdmmcInit=0 0 BootCapSize=0 UserCapSize=15193MB FwPartOffset=2000 , 0 StorageInit ok = 226015 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 LoadTrustBL LoadTrustBL error:-1 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 LoadTrustBL No find bl30.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0x59ba4 RunBL31 0x10000 NOTICE: BL31: v1.3(debug):0ac3e1a NOTICE: BL31: Built : 09:14:58, Nov 15 2017 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-126-g2a74125 #46 Thu Dec 14 08:21:08 UTC 2017 aarch64) 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 2017.02-RK3328-06-02632-g6d55d18 (Jan 24 2018 - 14:26:32) CPU: rk3328 cpu version = 1 CPU's clock information: arm pll = 600000000HZ general pll = 491519999HZ ddr pll = 664000000HZ codec pll = 1200000000HZ new pll = 594000000HZ Board: Rockchip platform Board Uboot as second level loader DRAM: Found dram banks: 1 Adding bank:0000000000200000(000000007fe00000) Reserve memory for trust os. dram reserve bank: base = 0x08400000, size = 0x01e00000 128 MiB GIC CPU mask = 0x00000001 SdmmcInit = 0 0 SDCard Update. storage init OK! Using default environment GetParam W: Invalid Parameter's tag (0x00000000)! Invalid parameter remotectl v0.1 pwm freq=0x23c346 pwm_freq_nstime=0x1aa No pmic detect. CPU's clock information: arm pll = 1200000000HZ general pll = 491519999HZ ddr pll = 664000000HZ codec pll = 1200000000HZ new pll = 594000000HZ SecureBootEn = 0, SecureBootLock = 0 #Boot ver: 0000-00-00#0.00 empty serial no. Writing env to storage... done normal boot. no fuel gauge found no fuel gauge found read logo on state from dts [0] no fuel gauge found 'recovery' does not seem to be a partition nor an address Unable to boot:recovery try to start backup 'backup' does not seem to be a partition nor an address Unable to boot:backup try to start rockusb Edited August 31, 2018 by Tido added Spoiler with Code box Link to comment Share on other sites More sharing options...
Tido Posted August 31, 2018 Share Posted August 31, 2018 @martos will you please make use of the function: Spoiler and Code. Your posts are kilometers long, for this the forum software offers tools named before. Thank you Link to comment Share on other sites More sharing options...
martos Posted August 31, 2018 Share Posted August 31, 2018 ok escuse me Link to comment Share on other sites More sharing options...
clarkss12 Posted August 31, 2018 Share Posted August 31, 2018 Thank you Mr. Balbes, for the update to manually change the Device tree. Now, my crappy Rockshit box (SCISHION AI ONE Android 8.1 TV Box - SILVER US PLUG) has an OS To look forward to. I tested ALL of the device trees included in your firmware, and finally found ONE that worked reasonably well (rk3328-evb.dtb). Some of the device trees would NOT boot at all, most would scroll, but not completely install. Now the work begins, I am using it on a 65" 4k TV, so the fonts are soooooo tiny, I can't read them unless I am 3 feet from the screen. I will be digging to see if I can find a solution, unless some one on here can tell me how, in layman's terms... This is the firmware that I used >>> Armbian_5.59_Rk3328-tv_Ubuntu_xenial_default_4.4.152_desktop_20180831.img.xz <<< Thanks. Edit: After trying to set everything up, I noticed that this Rockshit device is pathetically slow, compared to one of my older Amlogic S905 boxes. Not sure why it is so slow, more testing then, I will give up this box. One last thing, since you had a correct device tree for this box, I will see if it will work on LIbreELEC or CoreELEC. Link to comment Share on other sites More sharing options...
balbes150 Posted September 1, 2018 Author Share Posted September 1, 2018 13 hours ago, martos said: boot xenial-minimal-rock64-0.5.15-136-arm64.img I see a lot of interesting things here .... Try to erase the bootloader from the SD card with version 5.59, with the command "dd if=/dev/zero of=you_device bs=1 count=400" and try to start the system using a regular u-boot. This may not work because u-boot android may have different settings. Link to comment Share on other sites More sharing options...
balbes150 Posted September 1, 2018 Author Share Posted September 1, 2018 7 hours ago, clarkss12 said: Now the work begins, I am using it on a 65" 4k TV, so the fonts are soooooo tiny, I can't read them unless I am 3 feet from the screen. I will be digging to see if I can find a solution, unless some one on here can tell me how, in layman's terms... By default, the maximum available screen resolution is turned on (you probably have 3080 x 2160 for 4K), try to enable lower resolution in the screen settings , for example 1920x1080. At the same time minimal screen settings it speeds up the system. By the way, I think the launch Libreelec possible, it is necessary, by analogy with Armbian, if collect the generic version. Link to comment Share on other sites More sharing options...
balbes150 Posted September 1, 2018 Author Share Posted September 1, 2018 The list of models on which the system started automatically (without additional manual operations) expanded to 5 models. By the way, some models use DDR3 (as described) and the system starts. http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/739863-linux-for-tv-box-rk3328?p=742873#post742873 Link to comment Share on other sites More sharing options...
balbes150 Posted September 3, 2018 Author Share Posted September 3, 2018 I built a new version of the 20180903 image without including u-boot. This option should try to use a regular u-boot (for those who have a problem with determining the type of memory). Link to comment Share on other sites More sharing options...
martos Posted September 3, 2018 Share Posted September 3, 2018 i try it tomorrow ... Link to comment Share on other sites More sharing options...
balbes150 Posted September 4, 2018 Author Share Posted September 4, 2018 Does anyone have any information what sources are used to build u-boot in Android firmware ? Or it is possible to obtain the output of the command "printenv" and "help" from the console UART in u-boot Android. Link to comment Share on other sites More sharing options...
martos Posted September 4, 2018 Share Posted September 4, 2018 For my version the boot delay it's put at 0, so i can't stop it. I try CTRL+C to stop the u-boot but nothing, if you can find an option to stop it i can try. Link to comment Share on other sites More sharing options...
balbes150 Posted September 4, 2018 Author Share Posted September 4, 2018 8 minutes ago, martos said: I try CTRL+C to stop the u-boot but nothing, if you can find an option to stop it i can try. If you try to use the "space" or "Enter" keys ? Can you show the entire Android startup log ? Link to comment Share on other sites More sharing options...
martos Posted September 4, 2018 Share Posted September 4, 2018 Yes ( i try all the keys) but the boot delay is at 0 so don't stop and i read with google : "It is possible to configure u-Boot at build time so that it will ignore any character from the console and always do autoboot. a u-Boot configured in this way is used, for instance, for secure boot." Link to comment Share on other sites More sharing options...
balbes150 Posted September 4, 2018 Author Share Posted September 4, 2018 Show command output on PC "fdisk -l" to SD card with the image xenial-minimal-rock64-0.5.15-136-arm64.img Have you tried to move the boot loader from SD card xenial-minimal-rock64-0.5.15-136-arm64 to SD card with Armbian 5.59 ? Link to comment Share on other sites More sharing options...
balbes150 Posted September 4, 2018 Author Share Posted September 4, 2018 The update image 20180904. Added a utility to full backup and restore the entire eMMC "ddbr". Checked mode the backup MVR9. Now if you try to check the recovery mode. Link to comment Share on other sites More sharing options...
balbes150 Posted September 6, 2018 Author Share Posted September 6, 2018 I tried to run Armbian on MVR9 with different dtb files. The test system runs with almost all options rk3328*. When using the (rk3328-evb.dtb) option, the system is very slow. The dtb at a different part of the iron does not work (this is understandable). Therefore, those who try to start the system on their TV boxes, I recommend manually check all options dtb (copy in turn to the root FAT and rename to "dtb.img " all options rk3328*). Perhaps you will find one that will work better than others. During the test I found out (for myself) that on MVR9 the boot block from eMMC is started first and then it tries to start the secondary boot loader either from SD card or, if it does not find it there, from eMMC (on other TV boxes it is possible it is differently). On V88, I see the same algorithm. So there is a chance to use a universal image and only change the secondary loader to run on different models of TV boxes. Link to comment Share on other sites More sharing options...
balbes150 Posted September 8, 2018 Author Share Posted September 8, 2018 New version of the image 20180809. Changes. Added the function to install the system in eMMC. Pay attention, this option is available ONLY for TV models Boxing MVR9 and compatible models. If you try to install the system in eMMC for non-supported systems, you will get a brick. The order of installation in eMMC. 1. Download, unzip and burn the image to SD card. 2. Start Armbian on the TV box and perform the initial setup of the system. 3. If the system works correctly and you are satisfied, run the utility "ddbr" and create a full backup of eMMC (this is a prerequisite). 4. Rename the file "/boot/mvr9-uboot.img" in "/boot/uboot.img". 5. Run as user "root" script "/boot/create-mbr-linux.sh" 6. To run the script "/root/install.sh" Pay attention to the correct operation of the installation procedure need to comply strictly with the order of the steps. Link to comment Share on other sites More sharing options...
balbes150 Posted September 9, 2018 Author Share Posted September 9, 2018 Added another version of the image 20180909. On the model MVR9 image Xenial-desktop earned WiFi (maybe will work BT, I haven't checked). To use this version, you must manually add the correct DTB. For MVR9 model you need to copy the file " /dtb/rockchip/rk3328-box-trn9.dtb" in the root of the FAT partition and rename to "dtb.img" Link to comment Share on other sites More sharing options...
balbes150 Posted September 11, 2018 Author Share Posted September 11, 2018 On 9/4/2018 at 11:04 AM, martos said: Yes ( i try all the keys) but the boot delay is at 0 so don't stop and i read with google : "It is possible to configure u-Boot at build time so that it will ignore any character from the console and always do autoboot. a u-Boot configured in this way is used, for instance, for secure boot." Have you checked reaction to u-boot replacement ? I've put together some new u-boot options for different Board models. It will be interesting to check their behavior, whether the system will be able to start with them. Link to comment Share on other sites More sharing options...
balbes150 Posted September 13, 2018 Author Share Posted September 13, 2018 Perhaps it will be interesting for potential clients on MVR9 .... I collected scripts for installation Libreelec in eMMC. Checked them out on my MVR9. Everything is installed and Libreelec works fine from eMMC. Details can be found in this topic. http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/712961-mvr9-rk3328-libreelec-release?p=744476#post744476 Link to comment Share on other sites More sharing options...
rob0809 Posted September 14, 2018 Share Posted September 14, 2018 I have my V88 Piano box booting using the 09092018 image but I'm trying to get wifi working. How can I tell if the onboard wifi is being recognized? Is there something I can look for in dmesg? I'm not seeing anything in network setting that would tell me there is a wifi device configured. Link to comment Share on other sites More sharing options...
balbes150 Posted September 14, 2018 Author Share Posted September 14, 2018 4 hours ago, rob0809 said: I have my V88 Piano box booting using the 09092018 image but I'm trying to get wifi working. How can I tell if the onboard wifi is being recognized? Is there something I can look for in dmesg? I'm not seeing anything in network setting that would tell me there is a wifi device configured. You can see the output of "ip a" Link to comment Share on other sites More sharing options...
rob0809 Posted September 14, 2018 Share Posted September 14, 2018 6 hours ago, balbes150 said: You can see the output of "ip a" Ok, thanks. It's not showing up with any of the DTBs I tried. Link to comment Share on other sites More sharing options...
balbes150 Posted September 14, 2018 Author Share Posted September 14, 2018 There may be a lack of proper "firmware" or settings. Link to comment Share on other sites More sharing options...
mmss Posted September 17, 2018 Share Posted September 17, 2018 Thanks for your work @balbes150 I would like to buy a new box, is rk3328 faster than the s912? Link to comment Share on other sites More sharing options...
balbes150 Posted September 17, 2018 Author Share Posted September 17, 2018 45 minutes ago, mmss said: I would like to buy a new box, is rk3328 faster than the s912? Sorry, I didn't understand your question. Link to comment Share on other sites More sharing options...
martos Posted September 17, 2018 Share Posted September 17, 2018 In cpu only s912 la more powerfull only rk3399 have more cpu power. But rockchip give more information than amlogic to opensource ... Link to comment Share on other sites More sharing options...
balbes150 Posted September 18, 2018 Author Share Posted September 18, 2018 IMHO I would compare rk3328 to s905x2\d2. Link to comment Share on other sites More sharing options...
Xiaofan Posted September 18, 2018 Share Posted September 18, 2018 2 hours ago, balbes150 said: IMHO I would compare rk3328 to s905x2\d2. Ref: https://www.cnx-software.com/2017/11/27/amlogic-s905x-vs-rockchip-rk3328-vs-allwinner-h6/ CPU wise roughly: RK3399 > Amlogic S912 > Allwinner H6 > Amlogic S905X = RK3328 On the other hand, there are very few H6 based TV Box and majority of them are based on S912/S905W and RK3328. Some of the RK3328 based boxes have the advantages of higher memory and storage) (4GB/64G) compared to S912 based (usually 3GB/32GB) and S905W based (usually 2GB/16GB). I like my recently bought X96 Mini but I also ordered Rock64 and RK3328 based box (H96 Max 4GB/64GB) and S912 based box (H96 Pro Plus 3GB/32GB) to play with Android and follow the Armbian development here. The RK3328 based TV box is actually more expensive than S912 based because of the higher memory/storage. Link to comment Share on other sites More sharing options...
mmss Posted September 18, 2018 Share Posted September 18, 2018 @balbes150 and @Xiaofan ok, thanks I will buy a rk3328 box ? Link to comment Share on other sites More sharing options...
Recommended Posts