balbes150 Posted August 30, 2018 Share Posted August 30, 2018 A test version of the image Armbian for TV boxes on the basis of RK3328. Tested on MVR9 http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/653167-bqeel-mvr9-rk3328-quad-core-64bit-cortex-a53-android-7-2-16gb-2-4ghz-wifi-bt4 All basic functions work. For running. Download. Unpack. To record on the SD card. Connect the SD card to TV box, connect a keyboard and mouse. To turn the power on the TV box. The system should start within 2-3 minutes. You must perform the initial configuration of Armbian.https://yadi.sk/d/DSO6euzB3ahemo https://mega.nz/#F!zoZywCTQ!9sNfXIAB3m_DyLl5I8P94w The system of choosing the correct dtb has changed. Please note, now it should be done on a different principle (files do not need to be copied). To select the desired dtb, you need to change the line in the text file "/extlinux/extlinux.conf". In the line "FDT" you need to change the name of the file that the system will use at startup. The list of available files (names to specify in the configuration) can be found in the "dtb"directory. If you do not know exactly what file you need , you can enter all available names in turn and check the operation of the system. In accordance with this, the system installation script in eMMC has been changed. The steps to install the system on the eMMC remain the same. 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. 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. 6 Link to comment Share on other sites More sharing options...
rob0809 Posted August 30, 2018 Share Posted August 30, 2018 Thanks balbes150. I'm going to try this on the RK3328 boxes I own as soon as I get a chance. I'll report back. Do you have a collection of dtb's for RK3328 boxes anywhere? Thanks, Rob Link to comment Share on other sites More sharing options...
clarkss12 Posted August 30, 2018 Share Posted August 30, 2018 Installed this onto my "SCISHION AI ONE Android 8.1 TV Box - SILVER US PLUG" crap RK3328 box using the "px30-evb-ddr3-lvds-v10" dtb file. It loads, but when I enter admin and 1234, says "login incorrect". Link to comment Share on other sites More sharing options...
jeanrhum Posted August 30, 2018 Share Posted August 30, 2018 I suppose you mean root and not admin as username for the first log, isn't it? Link to comment Share on other sites More sharing options...
clarkss12 Posted August 30, 2018 Share Posted August 30, 2018 You mean it should be root as login, and not admin?????????? Link to comment Share on other sites More sharing options...
jeanrhum Posted August 30, 2018 Share Posted August 30, 2018 Yes, as for every linux distribution. Link to comment Share on other sites More sharing options...
clarkss12 Posted August 30, 2018 Share Posted August 30, 2018 I must be doing something wrong. By using "root" instead of "admin", I now have installed Armbian on my RK3328 box. The Ethernet does NOT work. Now the question I have is, by changing the device tree and restarting the box, does it use the just installed device tree?? This is my procedure. I shut down, Linux, remove the microSD card, and connect it to my Windows 10 computer. I then open the microSD card, and copy a device tree (ex.px30-evb-ddr3-lvds-v10.dtb) to the root of the microSD card, and rename it to dtb.img. I remove it from my computer (safely) and re-insert it back into my Android box, that is running Android. I then open the terminal emulator, and type "reboot update", it reboots back into Armbian desktop. I enter my password and then check the network, and it shows no valid connection found. I have done the same procedure for almost all of the device trees from the included folder. So, it appears, that it is NOT using the device trees that I keep changing. Link to comment Share on other sites More sharing options...
balbes150 Posted August 31, 2018 Author Share Posted August 31, 2018 9 hours ago, clarkss12 said: I must be doing something wrong. By using "root" instead of "admin", I now have installed Armbian on my RK3328 box. The Ethernet does NOT work. Now the question I have is, by changing the device tree and restarting the box, does it use the just installed device tree?? This is my procedure. I shut down, Linux, remove the microSD card, and connect it to my Windows 10 computer. I then open the microSD card, and copy a device tree (ex.px30-evb-ddr3-lvds-v10.dtb) to the root of the microSD card, and rename it to dtb.img. I remove it from my computer (safely) and re-insert it back into my Android box, that is running Android. I then open the terminal emulator, and type "reboot update", it reboots back into Armbian desktop. I enter my password and then check the network, and it shows no valid connection found. I have done the same procedure for almost all of the device trees from the included folder. So, it appears, that it is NOT using the device trees that I keep changing. In this version, only automatic use of dtb by ID is used. The option to manually assign an arbitrary dtb will be in the next versions of the images. Link to comment Share on other sites More sharing options...
balbes150 Posted August 31, 2018 Author Share Posted August 31, 2018 The new version of images 20180831 with support for the standard use of dtb (with manual copying of the desired option to the root of the FAT partition with the name " dtb.img"). If you are using automatic dtb mode, your system is not fully functional (some hardware is not working) or the system does not start at all. You can try to manually add your own version of the dtb file (copy from the directory "/dtb" or use files from other systems Libreelec, Armbian, etc.). To do this, copy the desired option to the root of the FAT partition and rename it to "dtb.img" (in the same way as is done in the images Armbian\Libreelec for Amlogic). Link to comment Share on other sites More sharing options...
balbes150 Posted August 31, 2018 Author Share Posted August 31, 2018 Are there owners of Z28 or V88 models here ? Link to comment Share on other sites More sharing options...
jeanrhum Posted August 31, 2018 Share Posted August 31, 2018 Yes, I have v88 mini III. I'll try to test your image this week-end. Is there a specific image you want some feedback ? Link to comment Share on other sites More sharing options...
martos Posted August 31, 2018 Share Posted August 31, 2018 v88 mini too, i will test. Link to comment Share on other sites More sharing options...
martos Posted August 31, 2018 Share Posted August 31, 2018 Don't boot in automatic, i try dtb Link to comment Share on other sites More sharing options...
balbes150 Posted August 31, 2018 Author Share Posted August 31, 2018 53 minutes ago, jeanrhum said: Yes, I have v88 mini III. I'll try to test your image this week-end. Is there a specific image you want some feedback ? I'm interested in a few things. 1. What will happen if after recording the image, do not change anything in the image manually, connect the SD card with Armbian to the TV box and turn on the power. Whether the system will be able to start automatically. 2. If the system does not start, try to manually add the correct dtb ("dtb.img") and check the launch. 3. If the system can start, check what hardware is running. 11 minutes ago, martos said: Don't boot in automatic, i try dtb If you have a dtb that works in any other images (with kernel 4.4), try using it. Link to comment Share on other sites More sharing options...
martos Posted August 31, 2018 Share Posted August 31, 2018 i try all dtb rk3328 one by one for the moment : i boot on sd on : xenial-minimal-rock64-0.5.15-136-arm64.img.xz in read the changelog i see after : "0.6.0: Use SPL/TPL instead of Rockchip's loaders (supports flashing and booting from SPI)," delete partition 6 and 7 , reboot with usb stick(bionic-minimal-rock64-0.7.9-1067-arm64.img.xz), activate eth1 ( all explain in the post off segv ) If you want I can try to open the box to find rs232 connection to see bootlog. Link to comment Share on other sites More sharing options...
balbes150 Posted August 31, 2018 Author Share Posted August 31, 2018 7 minutes ago, martos said: i try all dtb rk3328 one by one for the moment : i boot on sd on : xenial-minimal-rock64-0.5.15-136-arm64.img.xz in read the changelog i see after : "0.6.0: Use SPL/TPL instead of Rockchip's loaders (supports flashing and booting from SPI)," delete partition 6 and 7 , reboot with usb stick(bionic-minimal-rock64-0.7.9-1067-arm64.img.xz), activate eth1 ( all explain in the post off segv ) If you want I can try to open the box to find rs232 connection to see bootlog. What firmware is installed in the TV box now ? If possible, it is better to check on the regular firmware that comes out of the factory. The presence of a log from the UART console will be useful for diagnostics. Link to comment Share on other sites More sharing options...
martos Posted August 31, 2018 Share Posted August 31, 2018 on emm is stock android,if i don't have sd it boot . I find a file dtb in the boot sd on xenial-minimal-rock64-0.5.15-136-arm64.img.xz, i rename it in dtb.img and put in the sd of "Armbian_5.59_Rk3328-tv_Ubuntu_bionic_default_4.4.152_desktop_20180831.img.xz" without success I open the box and come back Link to comment Share on other sites More sharing options...
jeanrhum Posted August 31, 2018 Share Posted August 31, 2018 Mine is flashed with superceleron rom and I don't have official rom to flash it back to the device. Link to comment Share on other sites More sharing options...
martos Posted August 31, 2018 Share Posted August 31, 2018 I open the box v88 mini box : i see connection in J3500. Search my usb, my soldering gun ... Link to comment Share on other sites More sharing options...
martos Posted August 31, 2018 Share Posted August 31, 2018 I try 115200 sor srial spped , i have some ascii but not readable ... Link to comment Share on other sites More sharing options...
martinayotte Posted August 31, 2018 Share Posted August 31, 2018 22 minutes ago, martos said: I try 115200 sor srial spped , i have some ascii but not readable ... Rockchip default UART are at 1500000 baud. 1 Link to comment Share on other sites More sharing options...
martos Posted August 31, 2018 Share Posted August 31, 2018 perfect !!! 1500000 Link to comment Share on other sites More sharing options...
martos Posted August 31, 2018 Share Posted August 31, 2018 ok so the log is : U-Boot 2017.09-armbian (Aug 31 2018 - 11:03:12 +0300) Model: Firefly ROC-RK3328-CC DRAM: Link to comment Share on other sites More sharing options...
martos Posted August 31, 2018 Share Posted August 31, 2018 android boot : 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, 170 SdmmcInit=2 0 BootCapSize=2000 UserCapSize=7456MB FwPartOffset=2000 , 2000 SdmmcInit=0 2 StorageInit ok = 79048 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 20 SdmmcInit = 2 0 storage init OK! Using default environment GetParam remotectl v0.1 pwm freq=0x23c346 pwm_freq_nstime=0x1aa Load FDT from boot image. no key node can't find dts node for fixed rk816_set_regulator_init vdd_arm init uV:1225000 pmic:rk805 can't find dts node for pwm0 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: 2018-01-10#2.44 empty serial no. normal boot. checkKey vbus = 1 board_fbt_key_pressed: ir_keycode = 0x0, frt = 0 no fuel gauge found no fuel gauge found can't find power_ctr node for lcdc0 can't find dts node for deviceinfo rk_hdmi_register:fail to read deviceinfo hdmi baseparamer 0x0@0-0 left = 0, right = 0, top = 0, bottom = 0, overscan = 0 panel->left = 100 , panel->right = 100 ,panel->top = 100, panel->bottom = 100, p anel->overscan = 100 tve baseparamer 0x0@0-0 [EDID-EXTEND] It is a CEA 861 Series Extension. no baseparametr,find best edid mode,vic=16 hdmi_dev->video.vic is 16 hdmi_dev_config_video vic 16 color_output 3 color_output_depth 8 pixel clk is 148500000 tmds clk is 148500000 hsync_pol 1 vsync_pol 1 [HDMI] sucess output HDMI. hdmi_dev_config_audio HDMI_AUDIO_FS_48000 rate = 4, tmdsclk = 148500000, N = 6144, CTS = 148500 read logo on state from dts [1] no fuel gauge found checkKey vbus = 1 board_fbt_key_pressed: ir_keycode = 0x0, frt = 0 Hit any key to stop autoboot: 0 vendor read error! Set oem_unlocked=0Secure Boot state: 0 kernel @ 0x00280000 (0x00de4fa8) ramdisk @ 0x04bf0000 (0x0019d150) bootrk: do_bootm_linux... Loading Device Tree to 0000000004600000, end 000000000461d5c5 ... OK Add bank:0000000000200000, 0000000008200000 Add bank:000000000a200000, 0000000075e00000 WARNING: could not set reg FDT_ERR_BADOFFSET. Starting kernel ... <hit enter to activate fiq debugger> [ 0.000000] [0: swapper: 0] Initializing cgroup subsys cpuset [ 0.000000] [0: swapper: 0] Initializing cgroup subsys cpu [ 0.000000] [0: swapper: 0] Initializing cgroup subsys cpuacct [ 0.000000] [0: swapper: 0] Linux version 3.10.104 (qiaohy@server1 ) (gcc version 4.9 20150123 (prerelease) (GCC) ) #12 SMP PREEMPT Wed Jan 24 14:2 Link to comment Share on other sites More sharing options...
martos Posted August 31, 2018 Share Posted August 31, 2018 i think your devide have ddr4 and my device ddr3 Link to comment Share on other sites More sharing options...
martos Posted August 31, 2018 Share Posted August 31, 2018 boot sd : xenial-minimal-rock64-0.5.15-136-arm64.img ! 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 = 212180 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 No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0x92d74 RunBL31 0x10000 NOTICE: BL31: v1.3(debug):f947c7e NOTICE: BL31: Built : 09:28:45, May 31 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 WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2017.09-g5aef9f7 (Oct 12 2017 - 09:11:39 +0000), Build: jenkins-linux-build-rock-64-136 Model: Pine64 Rock64 DRAM: 2 GiB MMC: rksdmmc@ff500000: 1, rksdmmc@ff520000: 0 *** Warning - bad CRC, using default environment In: serial@ff130000 Out: serial@ff130000 Err: serial@ff130000 Model: Pine64 Rock64 Net: eth0: ethernet@ff540000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... invalid extent block invalid extent block invalid extent block invalid extent block invalid extent block invalid extent block invalid extent block invalid extent block invalid extent block invalid extent block switch to partitions #0, OK mmc1 is current device Scanning mmc 1:6... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf reading /extlinux/extlinux.conf 259 bytes read in 3 ms (84 KiB/s) 1: kernel-4.4 Retrieving file: /initrd.img reading /initrd.img 3504483 bytes read in 157 ms (21.3 MiB/s) Retrieving file: /Image reading /Image 18606088 bytes read in 814 ms (21.8 MiB/s) append: earlycon=uart8250,mmio32,0xff130000 rw root=LABEL=linux-root rootwait rootfstype=ext4 init=/sbin/init coherent_pool=1M ethaddr=da:d1:f5:a1:86:84 eth1addr=da:d1:f5:a1:86:a4 serial=2f1213b77b38289 Retrieving file: /dtb reading /dtb 42707 bytes read in 5 ms (8.1 MiB/s) ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to 7dbc2000, end 7df19963 ... OK Loading Device Tree to 000000007dbb4000, end 000000007dbc16d2 ... OK Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0 Link to comment Share on other sites More sharing options...
martos Posted August 31, 2018 Share Posted August 31, 2018 escuse me more the start of Armbian_5.59_Rk3328-tv_Ubuntu_bionic_default_4.4.152_desktop_20180831.img.xz 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, 170 SdmmcInit=2 0 BootCapSize=2000 UserCapSize=7456MB FwPartOffset=2000 , 2000 SdmmcInit=0 0 BootCapSize=0 UserCapSize=15193MB FwPartOffset=2000 , 0 StorageInit ok = 231192 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 No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0xa3bbc RunBL31 0x10000 NOTICE: BL31: v1.3(debug):f947c7e NOTICE: BL31: Built : 12:09:31, Aug 30 2018 NOTICE: BL31:Rockchip release version: v1.3 INFO: ARM GICv2 driver initialized INFO: Using rkfiq sec cpu_context! INFO: boot cpu mask: 1 INFO: plat_rockchip_pmu_init: pd status 0xe INFO: BL31: Initializing runtime services INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2017.09-armbian (Aug 31 2018 - 11:03:12 +0300) Model: Firefly ROC-RK3328-CC DRAM: --- it stop here --- Link to comment Share on other sites More sharing options...
balbes150 Posted August 31, 2018 Author Share Posted August 31, 2018 Can you stop running Android in u-boot and execute two commands "printenv" and "help" ? Show the result here. By the way, you can try to replace the u-boot in the image 5.59, the option from the media that you run. To do this, use dd. Just do not forget when writing u-boot to the media with 5.59 use two commands (with saving MBR). Link to comment Share on other sites More sharing options...
martos Posted August 31, 2018 Share Posted August 31, 2018 boot xenial-minimal-rock64-0.5.15-136-arm64.img => printenv arch=arm baudrate=1500000 board=rock64_rk3328 board_name=rock64_rk3328 boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr} boot_efi_binary=load ${devtype} ${devnum}:${distro_bootpart} ${kernel_addr_r} efi/boot/bootaa64.efi; if fdt addr ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r};else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}extlinux/extlinux.conf boot_mode=unknown boot_net_usb_start=usb start boot_prefixes=/ /boot/ boot_script_dhcp=boot.scr.uimg boot_scripts=boot.scr.uimg boot.scr boot_targets=mmc0 mmc1 usb0 pxe dhcp bootargs=earlycon=uart8250,mmio32,0xff130000 rw root=LABEL=linux-root rootwait rootfstype=ext4 init=/sbin/init coherent_pool=1M ethaddr=da:d1:f5:a1:86:84 eth1addr=da:d1:f5:a1:86:a4 serial=2f1213b77b38289 bootcmd=run distro_bootcmd bootcmd_dhcp=run boot_net_usb_start; if dhcp ${scriptaddr} ${boot_script_dhcp}; then source ${scriptaddr}; fi;setenv efi_fdtfile ${fdtfile}; setenv efi_old_vci ${bootp_vci};setenv efi_old_arch ${bootp_arch};setenv bootp_vci PXEClient:Arch:00011:UNDI:003000;setenv bootp_arch 0xb;if dhcp ${kernel_addr_r}; then tftpboot ${fdt_addr_r} dtb/${efi_fdtfile};if fdt addr ${fdt_addr_r}; then bootefi ${kernel_addr_r} ${fdt_addr_r}; else bootefi ${kernel_addr_r} ${fdtcontroladdr};fi;fi;setenv bootp_vci ${efi_old_vci};setenv bootp_arch ${efi_old_arch};setenv efi_fdtfile;setenv efi_old_arch;setenv efi_old_vci; bootcmd_mmc0=setenv devnum 0; run mmc_boot bootcmd_mmc1=setenv devnum 1; run mmc_boot bootcmd_pxe=run boot_net_usb_start; dhcp; if pxe get; then pxe boot; fi bootcmd_usb0=setenv devnum 0; run usb_boot bootdelay=2 bootfile=/extlinux/extlinux.conf bootfstype=fat cpu=armv8 cpuid#=55524b5030393030350000000015051e devnum=0 devplist=6 devtype=mmc distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done efi_dtb_prefixes=/ /dtb/ /dtb/current/ eth1addr=da:d1:f5:a1:86:a4 ethact=ethernet@ff540000 ethaddr=da:d1:f5:a1:86:84 fdt_addr_r=0x01f00000 fdtcontroladdr=7df1db70 fdtfile=rockchip/rk3328-rock64.dtb fileaddr=1f00000 filesize=0 kernel_addr_r=0x02000000 load_efi_dtb=load ${devtype} ${devnum}:${distro_bootpart} ${fdt_addr_r} ${prefix}${efi_fdtfile} mmc_boot=if mmc dev ${devnum}; then setenv devtype mmc; run scan_dev_for_boot_part; fi partitions=uuid_disk=${uuid_gpt_disk};name=loader1,start=32K,size=4000K,uuid=${uuid_gpt_loader1};name=reserved1,size=64K,uuid=${uuid_gpt_reserved1};name=reserved2,size=4M,uuid=${uuid_gpt_reserved2};name=loader2,size=4MB,uuid=${uuid_gpt_loader2};name=atf,size=4M,uuid=${uuid_gpt_atf};name=boot,size=112M,bootable,uuid=${uuid_gpt_boot};name=rootfs,size=-,uuid=B921B045-1DF0-41C3-AF44-4C6F280D3FAE; pxefile_addr_r=0x00600000 ramdisk_addr_r=0x04000000 scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; done;run scan_dev_for_efi; scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro_bootpart} bootfstype; then run scan_dev_for_boot; fi; done scan_dev_for_efi=setenv efi_fdtfile ${fdtfile}; for prefix in ${efi_dtb_prefixes}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${efi_fdtfile}; then run load_efi_dtb; fi;done;if test -e ${devtype} ${devnum}:${distro_bootpart} efi/boot/bootaa64.efi; then echo Found EFI removable media binary efi/boot/bootaa64.efi; run boot_efi_binary; echo EFI LOAD FAILED: continuing...; fi; setenv efi_fdtfile scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}extlinux/extlinux.conf; then echo Found ${prefix}extlinux/extlinux.conf; run boot_extlinux; echo SCRIPT FAILED: continuing...; fi scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; done scriptaddr=0x00500000 serial#=2f1213b77b38289 soc=rockchip stderr=serial@ff130000 stdin=serial@ff130000 stdout=serial@ff130000 usb_boot=usb start; if usb dev ${devnum}; then setenv devtype usb; run scan_dev_for_boot_part; fi vendor=rockchip Environment size: 4497/8188 bytes => bdinfo arch_number = 0x00000000 boot_params = 0x00000000 DRAM bank = 0x00000000 -> start = 0x00200000 -> size = 0x7FE00000 baudrate = 1500000 bps TLB addr = 0x7FFF0000 relocaddr = 0x7FF27000 reloc off = 0x7FD27000 irq_sp = 0x7DF1DB60 sp start = 0x7DF1DB60 Early malloc usage: 470 / 800 fdt_blob = 000000007df1db70 Link to comment Share on other sites More sharing options...
martos Posted August 31, 2018 Share Posted August 31, 2018 i can't stop android boot. ( hit a key at 0 ) i boot on android in the shell command try : reboot command (usage: reboot [-p] [rebootcommand] ) hit a key quickly without sucess , android boot ... Link to comment Share on other sites More sharing options...
Recommended Posts