R2fan Posted January 30, 2019 Posted January 30, 2019 This is so painful! out of about 50 attempts, I got it to boot once with the different DDR Version 1.14 20180803 displayed on serial comms, but then it hang, I presume because I removed the short pin too quickly. I also tried shorting the both sides of R90303 out in turn (which is closer to the eMMC IC in terms of electrical) , and I think this did help for the 1 time I got it to work. Now, the way that works best is to use a very short length of wire (its actually a header pin folded over 180 degrees) , to short out TP50265 and GND pins - this works 3 out of 5 times now., and I am able to get the Armbian login. Great!! I also managed to press space bar within 2 seconds of booting, to access uboot, and did: setenv devnum 1 run mmc_boot but this did not persist on rebooting the unit. I also tried changing the apparent order of boot devices: setenv boot_targets 'mmc1 mmc0 usb0 pxe dhcp' saveenv but get this: Saving Environment to EXT4... ** Unable to use mmc 0:auto for saveenv ** Failed (1) did you do anything else to your uboot? Thanks. Spoiler U-Boot 2018.11-armbian (Jan 26 2019 - 19:18:58 +0100) Model: OrangePi boards based on Rockchip RK3399 DRAM: 2 GiB MMC: dwmmc@fe310000: 2, dwmmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from EXT4... Card did not respond to voltage select! In: serial@ff1a0000 Out: serial@ff1a0000 Err: serial@ff1a0000 Model: OrangePi boards based on Rockchip RK3399 rockchip_dnl_key_pressed: adc_channel_single_shot fail! Net: Error: ethernet@fe300000 address not set. eth-1: ethernet@fe300000 Hit any key to stop autoboot: 0 => printenv arch=arm baudrate=1500000 board=evb_rk3399 board_name=evb_rk3399 boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr} boot_efi_binary=if fdt addr ${fdt_addr_r}; then bootefi bootmgr ${fdt_addr_r};else bootefi bootmgr ${fdtcontroladdr};fi;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_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 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=0 cpu=armv8 distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done efi_dtb_prefixes=/ /dtb/ /dtb/current/ fdt_addr_r=0x01f00000 fdtcontroladdr=7df212a8 kernel_addr_r=0x02080000 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=loader2,start=8MB,size=4MB,uuid=${uuid_gpt_loader2};name=trust,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 soc=rockchip stderr=serial@ff1a0000 stdin=serial@ff1a0000 stdout=serial@ff1a0000 usb_boot=usb start; if usb dev ${devnum}; then setenv devtype usb; run scan_dev_for_boot_part; fi vendor=rockchip Environment size: 3884/32764 bytes => saveenv Saving Environment to EXT4... ** Unable to use mmc 0:auto for saveenv ** Failed (1) => setenv devnum 1 => saveenv Saving Environment to EXT4... ** Unable to use mmc 0:auto for saveenv ** Failed (1) => for reference - schematics. Spoiler This is the underside layout with R90303 circled - note this is for an older v1.4 board, thats why I crossed out TP50265, because on v1.5 its on the top side.
R2fan Posted January 31, 2019 Posted January 31, 2019 Just for my understanding @martinayotte - when we make changes by "setenv ..." after entering uboot by pressing space bar, that is trying to write to the uboot on eMMC, right? Do you think there is any write protect on this by default? when trying to saveenv I still get Saving Environment to EXT4... ** Unable to use mmc 0:auto for saveenv ** Failed (1) Thanks
Igor Posted January 31, 2019 Posted January 31, 2019 1 hour ago, R2fan said: when we make changes by "setenv ..." after entering uboot by pressing space bar, that is trying to write to the uboot on eMMC Have you installed Armbian to eMMC? Only after that, you can use those commands to boot from SD card again. If you need to - if you broke the OS on eMMC. If you totally broke everything, you need to enter Maskrom mode again by shorting pins ...
R2fan Posted January 31, 2019 Posted January 31, 2019 No - its running the factory Android on eMMC. Only have Armbian on SD card. Is "nand-sata-install" the right thing whilst booted from SD card armbian?
martinayotte Posted January 31, 2019 Posted January 31, 2019 5 minutes ago, R2fan said: Is "nand-sata-install" the right thing whilst booted from SD card armbian? If you wish to get rid of Android and having Armbian installed on eMMC, yes, "nand-sata-install" is the tool for that ...
Igor Posted January 31, 2019 Posted January 31, 2019 2 minutes ago, martinayotte said: and having Armbian installed on eMMC, yes, But you can't change devnum at Android's u-boot, right?
Igor Posted January 31, 2019 Posted January 31, 2019 11 minutes ago, R2fan said: Is "nand-sata-install" the right thing whilst booted from SD card armbian? Yes.
martinayotte Posted January 31, 2019 Posted January 31, 2019 1 minute ago, Igor said: But you can't change devnum at Android's u-boot, right? Right ! If I remember correctly ... In such case, tweezers or jumper is the way to go !
R2fan Posted January 31, 2019 Posted January 31, 2019 OK, well good and bad news - I started getting very slow / inconsistent SSH and serial comms, but did manage to go through nand-sata-install via serial, and install to eMMC. Now I dont have Android on eMMC, and appears to be Armbian - great. but now, it just gets stuck in reboot cycle: Spoiler DDR Version 1.14 20180803 In soft reset SRX Channel 0: DDR3, 800MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB Channel 1: DDR3, 800MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB 256B stride ch 0 ddrconfig = 0x101, ddrsize = 0x20 ch 1 ddrconfig = 0x101, ddrsize = 0x20 pmugrf_os_reg[2] = 0x32817281, stride = 0x9 OUT Boot1: 2018-08-06, version: 1.15 CPUId = 0x0 ChipType = 0x10, 272 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 SdmmcInit=0 1 StorageInit ok = 67464 SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit read PBA: 0x1404 SecureInit read PBA: 0x1804 SecureInit read PBA: 0x1c04 SecureInit ret = 0, SecureMode = 0 GPT 0x3190d20 signature is wrong LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0x99bc0 RunBL31 0x10000 NOTICE: BL31: v1.3(debug):f947c7e NOTICE: BL31: Built : 12:34:33, Nov 26 2018 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: plat_rockchip_pmu_init(1089): pd status 3e INFO: BL31: Initializing runtime services INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2018.11-armbian (Jan 26 2019 - 19:18:58 +0100) Model: OrangePi boards based on Rockchip RK3399 DRAM: 2 GiB MMC: dwmmc@fe310000: 2, dwmmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from EXT4... OK In: serial@ff1a0000 Out: serial@ff1a0000 Err: serial@ff1a0000 Model: OrangePi boards based on Rockchip RK3399 rockchip_dnl_key_pressed: adc_channel_single_shot fail! Net: Error: ethernet@fe300000 address not set. eth-1: ethernet@fe300000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2958 bytes read in 7 ms (412.1 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 0 188 bytes read in 2 ms (91.8 KiB/s) 8679416 bytes read in 1153 ms (7.2 MiB/s) 14031360 bytes read in 1851 ms (7.2 MiB/s) 74945 bytes read in 28 ms (2.6 MiB/s) 232 bytes read in 11 ms (20.5 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 39000000 ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 8679352 Bytes = 8.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to 7d6d7000, end 7df1dfb8 ... OK reserving fdt memory region: addr=1f00000 size=78000 Loading Device Tree to 000000007d65c000, end 000000007d6d6fff ... OK Starting kernel ... [ 20.725428] reboot: Restarting system DDR Version 1.14 20180803 In soft reset SRX Channel 0: DDR3, 800MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB Channel 1: DDR3, 800MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB 256B stride ch 0 ddrconfig = 0x101, ddrsize = 0x20 ch 1 ddrconfig = 0x101, ddrsize = 0x20 pmugrf_os_reg[2] = 0x32817281, stride = 0x9 OUT Boot1: 2018-08-06, version: 1.15 CPUId = 0x0 ChipType = 0x10, 272 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 mmc0:cmd8,20 mmc0:cmd5,20 mmc0:cmd55,20 mmc0:cmd1,20 SdmmcInit=0 1 StorageInit ok = 67460 SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit read PBA: 0x1404 SecureInit read PBA: 0x1804 SecureInit read PBA: 0x1c04 SecureInit ret = 0, SecureMode = 0 GPT 0x3190d20 signature is wrong LoadTrust Addr:0x4000 No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0x99bc0 RunBL31 0x10000 NOTICE: BL31: v1.3(debug):f947c7e NOTICE: BL31: Built : 12:34:33, Nov 26 2018 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: plat_rockchip_pmu_init(1089): pd status 3e INFO: BL31: Initializing runtime services INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2018.11-armbian (Jan 26 2019 - 19:18:58 +0100) Model: OrangePi boards based on Rockchip RK3399 DRAM: 2 GiB MMC: dwmmc@fe310000: 2, dwmmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from EXT4... OK In: serial@ff1a0000 Out: serial@ff1a0000 Err: serial@ff1a0000 Model: OrangePi boards based on Rockchip RK3399 rockchip_dnl_key_pressed: adc_channel_single_shot fail! Net: Error: ethernet@fe300000 address not set. eth-1: ethernet@fe300000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2958 bytes read in 7 ms (412.1 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 0 188 bytes read in 2 ms (91.8 KiB/s) 8679416 bytes read in 1134 ms (7.3 MiB/s) 14031360 bytes read in 1820 ms (7.4 MiB/s) 74945 bytes read in 29 ms (2.5 MiB/s) 232 bytes read in 12 ms (18.6 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 39000000 ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 8679352 Bytes = 8.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to 7d6d7000, end 7df1dfb8 ... OK reserving fdt memory region: addr=1f00000 size=78000 Loading Device Tree to 000000007d65c000, end 000000007d6d6fff ... OK Starting kernel ... when I try to boot from SD card (I tried 3 different, recently opened from packet, and tried bionic images and Stretch), using space-bar to uboot, setenv devnum 1, run mmc_boot, I get this: Spoiler U-Boot 2018.11-armbian (Jan 26 2019 - 19:18:58 +0100) Model: OrangePi boards based on Rockchip RK3399 DRAM: 2 GiB MMC: dwmmc@fe310000: 2, dwmmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from EXT4... OK In: serial@ff1a0000 Out: serial@ff1a0000 Err: serial@ff1a0000 Model: OrangePi boards based on Rockchip RK3399 rockchip_dnl_key_pressed: adc_channel_single_shot fail! Net: Error: ethernet@fe300000 address not set. eth-1: ethernet@fe300000 Hit any key to stop autoboot: 0 => setenv devnum 1 => run mmc_boot switch to partitions #0, OK mmc0(part 0) is current device ** Bad device specification mmc -bootable ** Scanning mmc :1... Found U-Boot script /boot/boot.scr 2958 bytes read in 7 ms (412.1 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc Applying user provided fixup script (fixup.scr) ## Executing script at 39000000 Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing... => EDIT: one of the SD cards just worked, so am in via serial, but it is all a little strange at the moment, ill try installing to eMMC again with nand-sata-install. EDIT2: Ill try to verify the genuine-ness of these SD cards with H2testw. (they are Sandisk Ultra 16GB A1). Any ideas? Thanks
Igor Posted February 1, 2019 Posted February 1, 2019 12 hours ago, R2fan said: Applying user provided fixup script (fixup.scr) ## Executing script at 39000000 Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing... This suggest some corruption. Make sure you use good SD card (sometimes SD card brand or too fancy SD card could be an issue) and proven writing method ... and a good PSU to rule out most stupid errors.
Myy Posted February 1, 2019 Posted February 1, 2019 Post pour `printenv` just for confirmation. I think that mmc_boot just throw a setenv devnum X before running another script, which basically cancel your modification.
R2fan Posted February 1, 2019 Posted February 1, 2019 printenv: Spoiler => printenv arch=arm baudrate=1500000 board=evb_rk3399 board_name=evb_rk3399 boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr} boot_efi_binary=if fdt addr ${fdt_addr_r}; then bootefi bootmgr ${fdt_addr_r};else bootefi bootmgr ${fdtcontroladdr};fi;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_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=root=/dev/mmcblk0p1 rootwait rootfstype=ext4 console=ttyS2,1500000 console=tty1 panic=10 consoleblank=0 loglevel=1 ubootpart=593409a6-01 usb-storage.quirks= cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 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=0 bootfstype=ext4 console=both consoleargs=console=ttyS2,1500000 console=tty1 cpu=armv8 devnum=1 devplist=1 devtype=mmc distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done docker_optimizations=on efi_dtb_prefixes=/ /dtb/ /dtb/current/ fdt_addr_r=0x01f00000 fdtcontroladdr=7df212a8 fileaddr=500000 filesize=b8e kernel_addr_r=0x02080000 load_addr=0x39000000 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 overlay_error=false partitions=uuid_disk=${uuid_gpt_disk};name=loader1,start=32K,size=4000K,uuid=${uuid_gpt_loader1};name=loader2,start=8MB,size=4MB,uuid=${uuid_gpt_loader2};name=trust,size=4M,uuid=${uuid_gpt_atf};name=boot,size=112M,bootable,uuid=${uuid_gpt_boot};name=rootfs,size=-,uuid=B921B045-1DF0-41C3-AF44-4C6F280D3FAE; partuuid=593409a6-01 pxefile_addr_r=0x00600000 ramdisk_addr_r=0x04000000 rootdev=/dev/mmcblk0p1 rootfstype=ext4 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 soc=rockchip stderr=serial@ff1a0000 stdin=serial@ff1a0000 stdout=serial@ff1a0000 usb_boot=usb start; if usb dev ${devnum}; then setenv devtype usb; run scan_dev_for_boot_part; fi vendor=rockchip verbosity=1 Environment size: 4401/32764 bytes => when I try to boot from SD card now by pressing space bar to get into uboot, and do setenv devnum 1, run mmc_boot. I just re-burnt this SD card with Etcher (validated OK), and changed PSU to a ATX PC style PSU. (made no difference to the situation). Spoiler U-Boot 2018.11-armbian (Jan 26 2019 - 19:18:58 +0100) Model: OrangePi boards based on Rockchip RK3399 DRAM: 2 GiB MMC: dwmmc@fe310000: 2, dwmmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial@ff1a0000 Out: serial@ff1a0000 Err: serial@ff1a0000 Model: OrangePi boards based on Rockchip RK3399 rockchip_dnl_key_pressed: adc_channel_single_shot fail! Net: Error: ethernet@fe300000 address not set. eth-1: ethernet@fe300000 Hit any key to stop autoboot: 0 => => => setenv devnum 1 => run mmc_boot switch to partitions #0, OK mmc0(part 0) is current device ** Bad device specification mmc -bootable ** Scanning mmc :1... Found U-Boot script /boot/boot.scr 2958 bytes read in 6 ms (481.4 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Applying user provided fixup script (fixup.scr) ## Executing script at 39000000 Wrong image format for "source" command Bad Linux ARM64 Image magic! SCRIPT FAILED: continuing... Thanks
R2fan Posted February 1, 2019 Posted February 1, 2019 plugging in an HDMI and keyboard, I can login OK. I did nand-sata-install, and this time selected option 5 (Install/Update the bootloader on SD/eMMC), and then re-selected option 2 (boot from eMMC - system on eMMC). so it boots now, but for some reason either the ethernet does not get a DHCP sometime, or when it does, putty hangs (as does SSH from a raspberry pi) when I type in the password. This is for root and normal users. I need to take a break from this board for a while, but in passing, has anyone managed to get mini PCIe wifi boards working with this board? or with any RK3399 board (NEO4, etc)? I see no output from lspci. Thanks
Igor Posted February 1, 2019 Posted February 1, 2019 11 minutes ago, R2fan said: so it boots now, but for some reason either the ethernet does not get a DHCP sometime, or when it does, putty hangs (as does SSH from a raspberry pi) when I type in the password. This is for root and normal users. I need to take a break from this board for a while, but in passing, has anyone managed to get mini PCIe wifi boards working with this board? or with any RK3399 board (NEO4, etc)? I see no output from lspci. RK3399 board support and especially this board is months/a year away from being stable/matured. Those images were made for development/testing purposes only. PCI stack on a modern kernel is completely broken at this moment. On all boards.
R2fan Posted February 1, 2019 Posted February 1, 2019 OK understood, thanks, and thanks all on this thread for the help so far.
Дядя Серёжа Posted February 23, 2019 Posted February 23, 2019 Hi everyone! Does armbian support msata ssd? I have tried to use few images (including android) with OrangePI rk3399 and still don't see my ssd drive in /dev 1
gounthar Posted May 14, 2019 Posted May 14, 2019 How can we power an SSD when using Sata on this board? Is there some kind of power splitter somewhere? I'm using the barrel connector to power the board. Thanks.
NicoD Posted May 14, 2019 Posted May 14, 2019 5 hours ago, gounthar said: How can we power an SSD when using Sata on this board? Is there some kind of power splitter somewhere? Hi. There are multiple threads about that. Look here. Quote from @Da Alchemist Quote There must be two connections to the SSD of course, power and sata (there are cables for both connections). If everthing is allright, there must be a green and a red LED turned on. Is your SSD formatted? If not use Gparted to get it formatted. I hope that helps.
gounthar Posted May 15, 2019 Posted May 15, 2019 The OrangePi RK3399 doesn't have that kind of Molex connector, but I will keep searching. Thanks for your help.
pfry Posted May 15, 2019 Posted May 15, 2019 12 hours ago, gounthar said: The OrangePi RK3399 doesn't have that kind of Molex connector, but I will keep searching. Thanks for your help. The Orange Pi RK3399 has 5V and 3.3V available on the 40-pin header (and nowhere else that I can see offhand). Pinout is in the manual; it's a standard .1"/2.54mm header - lots of connector options. The mSATA interface is a bit inconvenient (uncommon); it also has 3.3V power available - perfect for an mSATA device; not much use if you're adapting it to a 2.5" device. I didn't check to see how much power is available, but I'd expect it to be fine for typical devices. 1
gounthar Posted May 15, 2019 Posted May 15, 2019 Thanks. I'll try to find something that could be connected to the GPIO.
gounthar Posted July 1, 2019 Posted July 1, 2019 On 12/3/2018 at 1:04 AM, Myy said: Alright, turns out that the /path/to/your/rkdeveloptool rd # Reboot step in my procedures wasn't rebooting the board anyway. So, basically, when in Maskrom mode (the mode you are in when the serial console is quiet, or when you keep the "Recovery" button pushed with the Right U-Boot), all writes are "as-is". If you reboot (unplug and plug the power cable back again) with a Loader, a Firmware and the Trust image, you'll get into a special "rockusb" mode that offset everything by 0x2000 sectors (0x2000 * 512 bytes). Since I'm not interested in that special rockusb mode, here's the "right" process for installing a U-Boot and Trust.img when you are in "quiet" mode : /path/to/your/rkdeveloptool db /path/to/RK3399MiniLoaderAll_V1.05_DDR600MHz.bin # Write the Bootloader /path/to/your/rkdeveloptool ul /path/to/RK3399MiniLoaderAll_V1.05_DDR600MHz.bin # Which is also their firmware /path/to/your/rkdeveloptool wl 0x4000 /path/to/uboot.img # Write the U-Boot image /path/to/your/rkdeveloptool wl 0x6000 /path/to/trust.img # Write the Trust bits # "Turn it off and on again" by unpluging and plugging the power cable back (Either the USB-C cable or the power plug) # Rebooting through the little button generate "Tinkerboard"-esque issues with the eMMC, which won't be properly power up anymore. Now, if you already have an eMMC image, you can do this instead : /path/to/your/rkdeveloptool db /path/to/RK3399MiniLoaderAll_V1.05_DDR600MHz.bin # Write the Bootloader /path/to/your/rkdeveloptool ul /path/to/RK3399MiniLoaderAll_V1.05_DDR600MHz.bin # Which is also their firmware /path/to/your/rkdeveloptool wl 0 /path/to/eMMC.img # This will be STUPIDLY slow. You'll have to wait betweens 10 and 30 minutes. # Unplug and plug the power cable back again, after the command finishes. I tested successfully these last steps and, therefore, have been able to directly flash my semi-working Armbian installation based on the Firefly RK3399 image. So, the current step now is "Getting a Rockchip kernel working correctly with this board". Thanks for these commands. They helped me getting my board out of a strange mode where it only displayed hw 0 0 0 0 0 0 0 0 0 0 and powerOn "someNumbers". Before that, I could not get into MASKROM mode anymore, nor in LOADER mode... It appeared kind of bricked to me. By the way, I read there that one could get into MASKROM mode from software by zeroing part of the boot partition. That's what got me into that "almost bricked" mode. If anyone has the correct sequence of commands that could do it, I will use it from now on. 1
gounthar Posted November 18, 2019 Posted November 18, 2019 I made some progress with this board, but am still stuck with its Debian version because of the HDMI-IN thingie (upgraded to Sid). I now have a working hardware accelerated ffmpeg for decoding (thanks to rkmpp), but no hardware accelerated encoding. The RockChip gstreamer fork has h.264 hwaccel, but it freezes the board way too often. OrangePi has finally made available a camera for this board, as the one from FriendlyArm froze the board too. I haven't been able to recompile a kernel on the board itself yet, but I'm working on it.
gounthar Posted December 12, 2019 Posted December 12, 2019 I rebuilt the image for my RK3399 two days ago, and it is stuck at boot with this message: Spoiler DDR Version 1.08 20170320 In Channel 0: DDR3, 800MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB Channel 1: DDR3, 800MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB 256B stride ch 0 ddrconfig = 0x101, ddrsize = 0x20 ch 1 ddrconfig = 0x101, ddrsize = 0x20 pmugrf_os_reg[2] = 0x32817281, stride = 0x9 OUT Boot1: 2017-04-07, version: 1.06 CPUId = 0x0 ChipType = 0x10, 1836 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 SdmmcInit=0 0 BootCapSize=0 UserCapSize=14922MB FwPartOffset=2000 , 0 StorageInit ok = 111125 LoadTrustBL No find bl30.bin No find bl32.bin RunBL31 0x40000 NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: plat_rockchip_pmu_init(1190): pd status 3e INFO: BL31: Initializing runtime services INFO: BL31: Initializing BL32 I rebuilt it today, and have the same output: Spoiler DDR Version 1.08 20170320 In Channel 0: DDR3, 800MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB Channel 1: DDR3, 800MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB 256B stride ch 0 ddrconfig = 0x101, ddrsize = 0x20 ch 1 ddrconfig = 0x101, ddrsize = 0x20 pmugrf_os_reg[2] = 0x32817281, stride = 0x9 OUT Boot1: 2017-04-07, version: 1.06 CPUId = 0x0 ChipType = 0x10, 1833 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 SdmmcInit=0 0 BootCapSize=0 UserCapSize=14922MB FwPartOffset=2000 , 0 StorageInit ok = 172930 LoadTrustBL No find bl30.bin No find bl32.bin RunBL31 0x40000 NOTICE: BL31: v1.3(debug):42583b6 NOTICE: BL31: Built : 07:55:13, Oct 15 2019 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: plat_rockchip_pmu_init(1190): pd status 3e INFO: BL31: Initializing runtime services INFO: BL31: Initializing BL32
gounthar Posted December 12, 2019 Posted December 12, 2019 I also downloaded Armbian Buster desktop legacy kernel 4.4.y and I got Spoiler DDR Version 1.08 20170320 In Channel 0: DDR3, 800MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB Channel 1: DDR3, 800MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB 256B stride ch 0 ddrconfig = 0x101, ddrsize = 0x20 ch 1 ddrconfig = 0x101, ddrsize = 0x20 pmugrf_os_reg[2] = 0x32817281, stride = 0x9 OUT Boot1: 2017-04-07, version: 1.06 CPUId = 0x0 ChipType = 0x10, 1827 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 SdmmcInit=0 0 BootCapSize=0 UserCapSize=14922MB FwPartOffset=2000 , 0 StorageInit ok = 310967 LoadTrustBL No find bl30.bin No find bl32.bin RunBL31 0x10000 Unhandled Exception in EL3. x30 = 0x0000000000034b84 x0 = 0x0000000000000238 x1 = 0x0000000000039f40 x2 = 0x000000000001fe18 x3 = 0x00000000ff00fff0 x4 = 0x0000000000034260 x5 = 0x0000000000034288 x6 = 0x0000000000000000 x7 = 0x0000000000000000 x8 = 0x0000000003011e8e x9 = 0x00000000032c0768 x10 = 0x0000000000010024 x11 = 0x0000000000000000 x12 = 0x000000000000000a x13 = 0x0000000000000001 x14 = 0x0000000000000002 x15 = 0x0000000000000004 x16 = 0x0000000000000000 x17 = 0x0000000000000000 x18 = 0x0000000000800000 x19 = 0x000000000001000c x20 = 0x00000000ff8cf800 x21 = 0x0000000000000000 x22 = 0x0000000000000010 x23 = 0x0000000000000000 x24 = 0x0000000000080000 x25 = 0x0000000000000001 x26 = 0x00000000ff8c2000 x27 = 0x0000000000000484 x28 = 0x0000000000000484 x29 = 0x00000000032c1040 scr_el3 = 0x0000000000000238 sctlr_el3 = 0x0000000000c5383a cptr_el3 = 0x0000000000000000 tcr_el3 = 0x0000000000000000 daif = 0x00000000000003c0 mair_el3 = 0x44e048e000098aa4 spsr_el3 = 0x00000000200002cd elr_el3 = 0x000000000001003c ttbr0_el3 = 0x001010e01200d312 esr_el3 = 0x00000000bf000000 far_el3 = 0x0000100a4204913e spsr_el1 = 0x0000000080028100 elr_el1 = 0xc1286301c01b1841 spsr_abt = 0x000000004a010743 spsr_und = 0x00000000c00147a4 spsr_irq = 0x0000000006046448 spsr_fiq = 0x000000002a042040 sctlr_el1 = 0x0000000000c52838 actlr_el1 = 0x0000000000000000 cpacr_el1 = 0x0000000000000000 csselr_el1 = 0x0000000000000000 sp_el1 = 0x0c92280013b001a4 esr_el1 = 0x0000000020d41000 ttbr0_el1 = 0x8971000a12c15a02 ttbr1_el1 = 0x202280a0b6028091 mair_el1 = 0x44e048e000098aa4 amair_el1 = 0x0000000000000000 tcr_el1 = 0x0000000000000000 tpidr_el1 = 0x5300022005293004 tpidr_el0 = 0x803208440d028422 tpidrro_el0 = 0x6904246005000888 dacr32_el2 = 0x000000002a208214 ifsr32_el2 = 0x0000000000000000 par_el1 = 0x2800000045e34a43 mpidr_el1 = 0x0000000080000000 afsr0_el1 = 0x0000000000000000 afsr1_el1 = 0x0000000000000000 contextidr_el1 = 0x0000000000000000 vbar_el1 = 0x0000000000000000 cntp_ctl_el0 = 0x0000000000000000 cntp_cval_el0 = 0x93c8300008001002 cntv_ctl_el0 = 0x0000000000000000 cntv_cval_el0 = 0x0181006046a02120 cntkctl_el1 = 0x0000000000000000 fpexc32_el2 = 0x0000000000000700 sp_el0 = 0xd944a09a80152021 isr_el1 = 0x0000000000000000 cpuectlr_el1 = 0x0000000000000040 cpumerrsr_el1 = 0x0000000000000000 l2merrsr_el1 = 0x0000000000000000 gicc_hppir = 0x0000000000000000 gicc_ahppir = 0x0000000000000000 gicc_ctlr = 0x0000000014000082 gicd_ispendr regs (Offsets 0x200 - 0x278) 0000000000000200: 0x0000001800000000 0000000000000208: 0x0000000000000000 0000000000000210: 0x0000000000000010 0000000000000218: 0x0000000000000000 0000000000000220: 0x0000000000000000 0000000000000228: 0x0000000000000000 0000000000000230: 0x0000000000000000 0000000000000238: 0x0000000000000000 0000000000000240: 0x0000000000000000 0000000000000248: 0x0000000000000000 0000000000000250: 0x0000000000000000 0000000000000258: 0x0000000000000000 0000000000000260: 0x0000000000000000 0000000000000268: 0x0000000000000000 0000000000000270: 0x0000000000000000 0000000000000278: 0x0000000000000000 cci_snoop_ctrl_cluster0 = 0x00000000c0000000 cci_snoop_ctrl_cluster1 = 0x00000000c0000000 With Buster minimal 5.4 I got Spoiler DDR Version 1.08 20170320 In Channel 0: DDR3, 800MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB Channel 1: DDR3, 800MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB 256B stride ch 0 ddrconfig = 0x101, ddrsize = 0x20 ch 1 ddrconfig = 0x101, ddrsize = 0x20 pmugrf_os_reg[2] = 0x32817281, stride = 0x9 OUT Boot1: 2017-04-07, version: 1.06 CPUId = 0x0 ChipType = 0x10, 1826 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 SdmmcInit=0 0 BootCapSize=0 UserCapSize=14922MB FwPartOffset=2000 , 0 StorageInit ok = 268186 LoadTrustBL No find bl30.bin No find bl32.bin RunBL31 0x40000 Unhandled Exception in EL3. x30 = 0xUnhandled Exception in EL3. x30 = 0xUnhandled Exception in EL3. x30 = 0xUnhandled Exception in EL3. x30 = 0xUnhandled Exception in EL3. x30 = 0xUnhandled Exception in EL3. x30 = 0xUnhandled Exception in EL3. x30 = 0xUnhandled Exception in EL3. x30 = 0xUnhandled Exception in EL3. x30 = 0xUnhandled Exception in EL3. x30 = 0xUnhandled Exception in EL3. x30 = 0xUnhandled Exception in EL3. x30 = 0xUnhandled Exception in EL3.
gounthar Posted December 12, 2019 Posted December 12, 2019 With Buster server I got: Spoiler DDR Version 1.08 20170320 In Channel 0: DDR3, 800MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB Channel 1: DDR3, 800MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=1024MB 256B stride ch 0 ddrconfig = 0x101, ddrsize = 0x20 ch 1 ddrconfig = 0x101, ddrsize = 0x20 pmugrf_os_reg[2] = 0x32817281, stride = 0x9 OUT Boot1: 2017-04-07, version: 1.06 CPUId = 0x0 ChipType = 0x10, 1827 SdmmcInit=2 0 BootCapSize=100000 UserCapSize=14910MB FwPartOffset=2000 , 100000 SdmmcInit=0 0 BootCapSize=0 UserCapSize=14922MB FwPartOffset=2000 , 0 StorageInit ok = 292962 LoadTrustBL No find bl30.bin No find bl32.bin RunBL31 0x10000 Unhandled Exception in EL3. x30 = 0x0000000000034b84 x0 = 0x0000000000000238 x1 = 0x0000000000039f40 x2 = 0x000000000001fe18 x3 = 0x00000000ff00fff0 x4 = 0x0000000000034260 x5 = 0x0000000000034288 x6 = 0x0000000000000000 x7 = 0x0000000000000000 x8 = 0x0000000003011e8e x9 = 0x00000000032c0768 x10 = 0x0000000000010024 x11 = 0x0000000000000000 x12 = 0x000000000000000a x13 = 0x0000000000000001 x14 = 0x0000000000000002 x15 = 0x0000000000000004 x16 = 0x0000000000000000 x17 = 0x0000000000000000 x18 = 0x0000000000800000 x19 = 0x000000000001000c x20 = 0x00000000ff8cf800 x21 = 0x0000000000000000 x22 = 0x0000000000000010 x23 = 0x0000000000000000 x24 = 0x0000000000080000 x25 = 0x0000000000000001 x26 = 0x00000000ff8c2000 x27 = 0x0000000000000484 x28 = 0x0000000000000484 x29 = 0x00000000032c1040 scr_el3 = 0x0000000000000238 sctlr_el3 = 0x0000000000c5383a cptr_el3 = 0x0000000000000000 tcr_el3 = 0x0000000000000000 daif = 0x00000000000003c0 mair_el3 = 0x44e048e000098aa4 spsr_el3 = 0x00000000200002cd elr_el3 = 0x000000000001003c ttbr0_el3 = 0x001011e01200db1b esr_el3 = 0x00000000bf000000 far_el3 = 0x0000100a420491ac spsr_el1 = 0x0000000080028100 elr_el1 = 0xc1284309c11b1841 spsr_abt = 0x000000004a010743 spsr_und = 0x00000000c00146a6 spsr_irq = 0x0000000086046448 spsr_fiq = 0x000000002a042040 sctlr_el1 = 0x0000000000c52838 actlr_el1 = 0x0000000000000000 cpacr_el1 = 0x0000000000000000 csselr_el1 = 0x0000000000000000 sp_el1 = 0x0c1228001bb000a0 esr_el1 = 0x0000000020941000 ttbr0_el1 = 0x8921000a02c15a02 ttbr1_el1 = 0x202080a016228091 mair_el1 = 0x44e048e000098aa4 amair_el1 = 0x0000000000000000 tcr_el1 = 0x0000000000000000 tpidr_el1 = 0x4300022005283004 tpidr_el0 = 0x803208400d068422 tpidrro_el0 = 0x6904246005000888 dacr32_el2 = 0x000000002a208204 ifsr32_el2 = 0x0000000000000000 par_el1 = 0x2800000045e34a43 mpidr_el1 = 0x0000000080000000 afsr0_el1 = 0x0000000000000000 afsr1_el1 = 0x0000000000000000 contextidr_el1 = 0x0000000000000000 vbar_el1 = 0x0000000000000000 cntp_ctl_el0 = 0x0000000000000000 cntp_cval_el0 = 0x93c8300008001002 cntv_ctl_el0 = 0x0000000000000000 cntv_cval_el0 = 0x0181106046a02130 cntkctl_el1 = 0x0000000000000000 fpexc32_el2 = 0x0000000000000700 sp_el0 = 0xd944b09a80142021 isr_el1 = 0x0000000000000000 cpuectlr_el1 = 0x0000000000000040 cpumerrsr_el1 = 0x0000000000000000 l2merrsr_el1 = 0x0000000000000000 gicc_hppir = 0x0000000000000000 gicc_ahppir = 0x0000000000000000 gicc_ctlr = 0x0000000014000082 gicd_ispendr regs (Offsets 0x200 - 0x278) 0000000000000200: 0x0000001800000000 0000000000000208: 0x0000000000000000 0000000000000210: 0x0000000000000010 0000000000000218: 0x0000000000000000 0000000000000220: 0x0000000000000000 0000000000000228: 0x0000000000000000 0000000000000230: 0x0000000000000000 0000000000000238: 0x0000000000000000 0000000000000240: 0x0000000000000000 0000000000000248: 0x0000000000000000 0000000000000250: 0x0000000000000000 0000000000000258: 0x0000000000000000 0000000000000260: 0x0000000000000000 0000000000000268: 0x0000000000000000 0000000000000270: 0x0000000000000000 0000000000000278: 0x0000000000000000 cci_snoop_ctrl_cluster0 = 0x00000000c0000000 cci_snoop_ctrl_cluster1 = 0x00000000c0000000
chwe Posted December 13, 2019 Posted December 13, 2019 19 hours ago, gounthar said: for my RK3399 we might not now what your RK3399 is so maybe you want to be a bit more specific?
gounthar Posted December 13, 2019 Posted December 13, 2019 I'm sorry, I meant OrangePi RK3399 of course.
gounthar Posted December 17, 2019 Posted December 17, 2019 Today's build went farther on the OrangePi RK3399: Spoiler Hit any key to stop autoboot: 0 => setenv devnum 1 => run mmc_boot switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 2940 bytes read in 21 ms (136.7 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 139 bytes read in 18 ms (6.8 KiB/s) 6975843 bytes read in 477 ms (13.9 MiB/s) 20587008 bytes read in 1346 ms (14.6 MiB/s) 73823 bytes read in 58 ms (1.2 MiB/s) 2698 bytes read in 32 ms (82 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 39000000 ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 6975779 Bytes = 6.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to 7d859000, end 7df00123 ... OK reserving fdt memory region: addr=1f00000 size=78000 Loading Device Tree to 000000007d7de000, end 000000007d858fff ... OK Starting kernel ... It is now stuck, but it never got that far previously for me.
Igor Posted December 17, 2019 Posted December 17, 2019 1 hour ago, gounthar said: It is now stuck Looong boot delay is (currently) normal on those board. If this is the problem? 1
Recommended Posts