4 4
pbies

Ramblings and progress with the RK3399

Recommended Posts

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

image.png.609bcd81d7c1f4442fcf85ce2253d933.png

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. 

image.thumb.png.e3f16850c5bec3195408641f7ba951c2.png


 

Share this post


Link to post
Share on other sites

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

 

Share this post


Link to post
Share on other sites
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 ...

Share this post


Link to post
Share on other sites

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? 

Share this post


Link to post
Share on other sites
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 ...

 

Share this post


Link to post
Share on other sites

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

 

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

 

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

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.

 

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
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.

 

Share this post


Link to post
Share on other sites
4 4