5 5
tkaiser

ROC-RK3399-PC (Renegade Elite)

Recommended Posts

Success, Used the dts from here rk3399-roc-pc.dts and merged some of the kernel config from here firefly_linux_defconfig and presto! I have a booting Armbian image for the Renegade Elite :D

 

Spoiler

U-Boot 2018.11-armbian (Mar 03 2019 - 05:52:50 +0100)

Model: Firefly-RK3399 Board
DRAM:  3.9 GiB
MMC:   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: Firefly-RK3399 Board
Net:   
Error: ethernet@fe300000 address not set.
eth-1: ethernet@fe300000
Hit any key to stop autoboot:  0 
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
2958 bytes read in 2 ms (1.4 MiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
137 bytes read in 1 ms (133.8 KiB/s)
4240622 bytes read in 276 ms (14.7 MiB/s)
18591752 bytes read in 1200 ms (14.8 MiB/s)
100282 bytes read in 11 ms (8.7 MiB/s)
** File not found /boot/dtb/rockchip/overlay/rockchip-fixup.scr **
## Loading init Ramdisk from Legacy Image at 04000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    4240558 Bytes = 4 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 f5b12000, end f5f1d4ae ... OK
   reserving fdt memory region: addr=1f00000 size=7e000
   Loading Device Tree to 00000000f5a91000, end 00000000f5b11fff ... OK

Starting kernel ...
 

Spoiler

 _____ _           __ _         ____  _  ____________ ___   ___    ____  
|  ___(_)_ __ ___ / _| |_   _  |  _ \| |/ /___ /___ // _ \ / _ \  |  _ \ 
| |_  | | '__/ _ \ |_| | | | | | |_) | ' /  |_ \ |_ \ (_) | (_) | | |_) |
|  _| | | | |  __/  _| | |_| | |  _ <| . \ ___) |__) \__, |\__, | |  __/ 
|_|   |_|_|  \___|_| |_|\__, | |_| \_\_|\_\____/____/  /_/   /_/  |_|    
                        |___/                                            
  ____                                                                   
 / ___|                                                                  
| |                                                                      
| |___                                                                   
 \____|                                                                  
                                                                         

Welcome to ARMBIAN 5.76 user-built Debian GNU/Linux 9 (stretch) 4.4.176-rk3399-pc   
System load:   0.93 0.65 0.29      Up time:       4 min        
Memory usage:  2 % of 3812MB     IP:            192.168.0.153
CPU temp:      30°C               
Usage of /:    4% of 30G        


pi@rk3399:~$ 

 

 

Share this post


Link to post
Share on other sites

Oooo... Does this mean we'll see an Armbian build soon? :D I'm afraid I'll be spending so much time waiting after Libre to release functional mainline content that I might just scrap this board. If I can boot Armbian off the SSD, I've just made this thing a whole lot more interesting. 

Share this post


Link to post
Share on other sites
17 hours ago, Fred St-Pierre said:

Oooo... Does this mean we'll see an Armbian build soon? 

Potentially a WIP/csc until Armbian in general properly supports rk3399.  This isn't so much a libre computer issue as it is a u-boot/kernel issue, all Rockchip boards with high-spec ram have been a challenge to support because the Rockchip binary blobs aren't so great sometimes.  I have this board, I can test any PR's in the meantime while I clean up some other stuff

Share this post


Link to post
Share on other sites
53 minutes ago, TonyMac32 said:

Potentially a WIP/csc until Armbian in general properly supports rk3399.  This isn't so much a libre computer issue as it is a u-boot/kernel issue, all Rockchip boards with high-spec ram have been a challenge to support because the Rockchip binary blobs aren't so great sometimes.  I have this board, I can test any PR's in the meantime while I clean up some other stuff

 

Ok great. I have the board in hand, full kit with PoE mezzanine and 256gb SSD onboard if ever you want to use me as a guinea pig. 

Share this post


Link to post
Share on other sites
On 2/20/2019 at 5:22 AM, TonyMac32 said:

 

the USB-C at the rear with the Ethernet port is the power-in, not hard to do backwards.

 

 

Call me stupid... It started when I switched the USB-C port. :wacko:

On 3/5/2019 at 4:58 PM, Fred St-Pierre said:

 

Ok great. I have the board in hand, full kit with PoE mezzanine and 256gb SSD onboard if ever you want to use me as a guinea pig. 

Wow, I was very tempted by the mezzanine, but I had to choose between that and the emmc...

Share this post


Link to post
Share on other sites

I should be able to create a PR for a WIP. I just wondering how to handle the BL31 issue. It is either to pull the binaries from here: https://github.com/rockchip-linux/rkbin/tree/master/bin/rk33 or try to build from https://github.com/ARM-software/arm-trusted-firmware. Also need input for the common board name, I guess "rk3399-roc-pc" is the one?

 

@TonyMac32   I will also try to build ayufans mainline and see if it boots ok.

 

Share this post


Link to post
Share on other sites

Tried building BL31 from mainline here: https://github.com/ARM-software/arm-trusted-firmware

Seems to build OK, but it links it to load @ 0x0 which probably is bad. I'm guessing the BL31 should have it's base addr @ 0x10000.

Maybe it's possible to load it @ 0x0, anyone has experience? I'm in the deep-end here :wacko:

 

UART Boot log:

...

LoadTrust Addr:0x4000
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0x9abc0
RunBL31 0x0

<Hangs here>

 

 

trust_merger --verbose

Spoiler

Built build/rk3399/debug/bl31.bin successfully

D: [main] do_merge
D: [parseOpts] start parse
D: [parseVersion] major:1, minor:0
D: [parseBL3x] bl30 sec: 0
D: [parseBL3x] bl31 sec: 1
D: [parseBL3x] bl31 path:./build/rk3399/debug/bl31/bl31.elf
D: [parseBL3x] bl31 addr:0x10000
D: [parseBL3x] bl32 sec: 0
D: [parseBL3x] bl33 sec: 0
out:trust.bin
---------------
USING CONFIG:
[BL30_OPTION]
SEC=0
[BL31_OPTION]
SEC=1
PATH=./build/rk3399/debug/bl31/bl31.elf
ADDR=0x00010000
[BL32_OPTION]
SEC=0
[BL33_OPTION]
SEC=0
[OUTPUT]
PATH=trust.bin
---------------
D: [filter_elf] index=1,file=./build/rk3399/debug/bl31/bl31.elf
D: [getFileSize] path:./build/rk3399/debug/bl31/bl31.elf, size:1079048
D: [filter_elf] bl31: filesize = 147552, imagesize = 149504, segment=0
D: [filter_elf] bl31: filesize = 8024, imagesize = 8192, segment=1
D: [filter_elf] bl31: filesize = 8192, imagesize = 8192, segment=2
D: [mergetrust] bl3x bin sec = 3
D: [getBCD] ret:1
D: [getBCD] ret:0
D: [mergetrust] trust bin sign offset = 944
D: [mergetrust] bl31: LoadAddr = 0x00000000, StorageAddr = 4, ImageSize = 292
D: [mergetrust] bl31: LoadAddr = 0xff3b0000, StorageAddr = 296, ImageSize = 16
D: [mergetrust] bl31: LoadAddr = 0xff8c0000, StorageAddr = 312, ImageSize = 16
merge success(trust.bin)
 

 

Share this post


Link to post
Share on other sites

I'm holding off until the DDR4 support is working in mainline, this board would be in the same unfortunate state as the RockPi 4/etc. once the u-boot is working properly we can get rk3399 all put into one happy family and get the support fixed.

Share this post


Link to post
Share on other sites

Funny. I was just about to give it another go since I just received the 128GB eMMC for this board. I really don't remember where I left off, but I had issues with the ARM trust not working. So I'll just pull it from the rockchip repo and this what gives...

Share this post


Link to post
Share on other sites
49 minutes ago, Redferne said:

So I'll just pull it from the rockchip repo and this what gives...

 

The rockchip repo will *mostly* work, but I've had issues with it being consistent as well.

Share this post


Link to post
Share on other sites
5 5