Jump to content

Current State of Rock Pi 4 Support

Race666
 Share

Recommended Posts

Race666

Race666

Posted
Posted

I've recently bought a Rock Pi 4a Board and can't get running armbian (The Image provided by Radxa works) but I want to get running the latest version.

 

I've tried both nightly builds

Armbian Bionic nightly development branch 4.20.y  (22.05.2019)and

Armbian Stretch nightly development branch 4.20.y

 

Both Image boots U-Boot but cannot start the kernel:

  


U-Boot 2017.09-armbian (May 22 2019 - 04:11:32 +0200)

Model: RockPi-4B
DRAM:  3.9 GiB
DCDC_REG1@vdd_center: ; enabling
DCDC_REG2@vdd_cpu_l: ; enabling
DCDC_REG3@vcc_ddr: ; enabling (ret: -38)
DCDC_REG4@vcc_1v8: set 1800000 uV; enabling
LDO_REG1@vcc1v8_dvp: set 1800000 uV; enabling
LDO_REG2@vcc3v0_touch: set 3000000 uV; enabling
LDO_REG3@vcc1v8_pmu: set 1800000 uV; enabling
LDO_REG4@vcc_sd: set 3300000 uV; enabling
LDO_REG5@vcca3v0_codec: set 3000000 uV; enabling
LDO_REG6@vcc_1v5: set 1500000 uV; enabling
LDO_REG7@vcca1v8_codec: set 1800000 uV; enabling
LDO_REG8@vcc_3v0: set 3000000 uV; enabling
SWITCH_REG1@vcc3v3_s3: ; enabling (ret: -38)
SWITCH_REG2@vcc3v3_s0: ; enabling (ret: -38)
vcc1v8-s0@vcc1v8_s0: set 1800000 uV; enabling (ret: -38)
dc-12v@dc_12v: set 12000000 uV; enabling (ret: -38)
vcc-sys@vcc_sys: set 5000000 uV; enabling (ret: -38)
vcc3v3-sys@vcc3v3_sys: set 3300000 uV; enabling (ret: -38)
vcc-phy-regulator@vcc_phy: ; enabling (ret: -38)
vdd-log@vdd_log: ; enabling (ret: -38)
MMC:   sdhci@fe330000: 0, dwmmc@fe320000: 1
SF: unrecognized JEDEC id bytes: ff, ff, ff
*** Warning - spi_flash_probe_bus_cs() failed, using default environment

In:    serial@ff1a0000
Out:   serial@ff1a0000
Err:   serial@ff1a0000
Model: RockPi-4B
boot mode 5242c300.
normal boot
Net:   eth0: ethernet@fe300000
Hit any key to stop autoboot:  0
Card did not respond to voltage select!
mmc_init: -95, time 19
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
2949 bytes read in 38 ms (75.2 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
102 bytes read in 31 ms (2.9 KiB/s)
8335365 bytes read in 937 ms (8.5 MiB/s)
14107136 bytes read in 1548 ms (8.7 MiB/s)
74997 bytes read in 103 ms (710.9 KiB/s)
1847 bytes read in 55 ms (32.2 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:    8335301 Bytes = 7.9 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 f570f000, end f5f01fc5 ... OK
   reserving fdt memory region: addr=1f00000 size=78000
   Loading Device Tree to 00000000f5694000, end 00000000f570efff ... OK

Starting kernel ...

Then i tried to compile Armbian from scratch with vendor kernel 

BOARD=rockpi-4b BRANCH=default RELEASE=stretch BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no CLEAN_LEVEL=make ./compile.sh

I flashed the image to the SD Card by 

dd if=Armbian.... of=/dev/mmcblk0 bs=4M

With this image, U-boot starts and ends up in an reboot loop 

U-Boot 2017.09-armbian (Dec 10 2018 - 09:24:29 +0800)

Model: Rockchip RK3399 Evaluation Board
DRAM:  3.9 GiB
Relocation Offset is: f5c0b000
PMIC:  RK808
pwm-regulator(vdd-center): init 950000 uV
vdd_center 950000 uV
regulator(vdd-center) init 950000 uV
MMC:   dwmmc@fe320000: 1, sdhci@fe330000: 0
Using default environment

Warn: can't find connect driver
Failed to found available display route
Warn: can't find connect driver
Failed to found available display route
In:    serial
Out:   serial
Err:   serial
Model: Rockchip RK3399 Evaluation Board
RKPARM: Invalid parameter part table
switch to partitions #0, OK
mmc1 is current device
do_rkimg_test found IDB in SDcard
Boot from SDcard
get part misc fail -1
Net:   eth0: ethernet@fe300000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
2949 bytes read in 37 ms (77.1 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
102 bytes read in 31 ms (2.9 KiB/s)
4460205 bytes read in 247 ms (17.2 MiB/s)
18978824 bytes read in 877 ms (20.6 MiB/s)
** File not found /boot/dtb/rockchip/rockpi-4b-linux.dtb **
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.

It did not find /boot/dtb/rockchip/rockpi-4b-linux.dtb.

 

I've copied /boot/dtb/rockchip/rk3399-rockpi4b.dtb to /boot/dtb/rockchip/rockpi-4b-linux.dtb but this ends in an kernel panic.

 

Any hints?

Igor

Igor

Posted
Posted
10 hours ago, Race666 said:

I've tried both nightly builds


Trying is the main purpose. Good!
 

10 hours ago, Race666 said:

Any hints?


Usually none without R&D. Things in development are changing daily.

 

10 hours ago, Race666 said:

Then i tried to compile Armbian from scratch with vendor kernel


If board is not declared stable, you are wasting your time, unless you are going to fix things.

martinayotte

martinayotte

Posted
Posted
19 hours ago, Race666 said:

** File not found /boot/dtb/rockchip/rockpi-4b-linux.dtb **

Armbian never used that filename ... I think your SDCard has a mix of Non-Armbian U-Boot somehow ...

 

dolphs

dolphs

Posted
Posted
On 5/22/2019 at 9:00 PM, Race666 said:

I've recently bought a Rock Pi 4a Board and can't get running armbian

 

 

Current status appears to be mature, at least from "compile.sh" ?

That is good news,  therefore also would like to test a ROCK Pi 4 Model A board ( 2gb and sdcard ) using 5.1 kernel (dev).

Learnt flags to use are: 

./compile.sh BOARD=rockpi-4b BRANCH=dev RELEASE=stretch BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no

Just like to confirm, but suppose " rockpi-4b " flag also works for the 4a edition - except for the WiFi, BT, PoE additions that do not exist on 4a.

cheers

gufmar

gufmar

Posted
Posted
On 6/13/2019 at 3:03 AM, dolphs said:

 

 

Current status appears to be mature, at least from "compile.sh" ?

That is good news,  therefore also would like to test a ROCK Pi 4 Model A board ( 2gb and sdcard ) using 5.1 kernel (dev).

 

I have a and b versions in my lab (all 4GB equipped)

Do you still need some confirmation/verification?

chwe

chwe

Posted
Posted

@Igor when did we change RockPi to supported? Especially cause we provide 4.4 kernel in the first two dl. options as mature support.. IMO it doesn't represent the current status.. Only difference compared to before is that @ayufan took our patch and added it to his kernel (which is good cause it saves us a patch to maintain). But the 4.4 dts was never cleaned and iirc it had a bunch of 'not as healthy stuff in combination with this kernelfork.

 

On 6/13/2019 at 3:03 AM, dolphs said:

 

Current status appears to be mature, at least from "compile.sh" ?

IMHO the status should still be wip, as more or less for the whole rk3399 family. But happily it's not my decision. Tagging @TonyMac32 and @martinayotte :lol:

Igor

Igor

Posted
Posted
11 hours ago, chwe said:

IMO it doesn't represent the current status.. Only difference compared to before is that


Software maturity with RK3399 legacy is IMO decent enough to pull it out from "testing only" -> "good software support", I agree that matured is not right description but we don't have anything in-between. If most of https://github.com/orgs/armbian/teams/boards-rockchip/members?add=true thinks that it is too soon, edit and change back. I did sent you invite there, since you are well updated with the rk3399 support status. And your voice counts.

 

Users anyway doesn't care about this status considering how much end-users questions are piling up everywere.

dacen

dacen

Posted
Posted

hi guy, i want to know how do you get the log use serial? I seem cannot get info from serial port, i only get messy code in putty

martinayotte

martinayotte

Posted
Posted
2 hours ago, dacen said:

hi guy, i want to know how do you get the log use serial? I seem cannot get info from serial port, i only get messy code in putty

The default baudrate on Rockchip is 1500000 baud ...

piter75

piter75

Posted
Posted
On 7/23/2019 at 10:54 PM, gufmar said:

I have a and b versions in my lab (all 4GB equipped)

Do you still need some confirmation/verification?

 

@gufmar do you possibly also have an eMMC module?

If so did you have luck using it reliably with model A?

 

As strange as it may sound eMMC in model B is working reliably but in A it is only detected once in N boots with 5.2 kernel.

On the other hand with kernel 4.4 it is initialised correctly all of the times also in model A.

gufmar

gufmar

Posted
Posted
17 hours ago, piter75 said:

do you possibly also have an eMMC module?

If so did you have luck using it reliably with model A?

Yes most of all my boards run on eMMC (just started experimenting with the NVME extension)
I never noticed a difference between A and B regarding eMMC behaviour.


I'm not sure if it is related (or my mistake) but 3 from my 8 eMMC cards are not recognised anymore at full size. As they appear with onle 1/8 of size, I guess it is some mistake between 4096 and 512 sector size, happened either on disc resizing after boot, or re-flashing with etcher (on a notebook with weird SDCard driver)
I wasn't able to bring them back to original capacity with whatever operating system, device and partitioning tools I tried.  I also tried with a usb-2-emmm adapter but no luck.
But this didn't happen during normal operation, but while playing around, flashing, re-installing. So in my eyes not a Board or eMMC failure.


All other eMMC modules run fine for many months now, with quite a lot of software compilations and benchmarking tests (phoronix). 

 

 

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept