On Thu, 9 Jan 2020 22:16:38 +0100 (CET)
Mark Kettenis <mark.kette...@xs4all.nl> wrote:

> > Date: Tue, 31 Dec 2019 00:28:23 +0100
> > From: Olivier <oliv...@burelli.fr>
> > 
> > Hello all,
> > 
> > In first, i would like to wish you happy new years celebrations, enjoy !
> > 
> > I would like to know if, for ROCK PRO64 i have issue or not.
> > 
> > _ From : https://github.com/jasperla/openbsd-rockpro64 and the image 
> > provided, the dmesg is containing a detection of rkpcie
> >     --> rkpcie0 at mainbus0
> > _ From the Mark's firmware that i am using, my dmesg does not contain any 
> > rkpcie device. (see below)
> > 
> > 
> > Questions :
> > 
> > _ Does my board is broken ?
> > _ Do we have to put some instructions to scan the pci-e slot ? (in the 
> > second part of u-boot)
> > _ Does the Mark's firmware includes rkpie device ?
> > 
> > Thanks‌ in advance.
> 
> You should probably use the firmware from the u-boot-aarch64-2020.01
> package that is now available for -current.

Hi Mark, thanks for your answers.

I already use it since the 4th January :)

In fact i done also a mistake on my side. I did not put the dtb file in the i 
partition. Now i am using your firmware, great ^^.

I whould like precise my mistakes for another people that run too fast like me 
:)


2 way to work on Rock64 / RockPro64 : using the Jasperla / Ayufan work or 
MArk's and OpenBSD's works :)

case 1) - Deprecated since the last u-boot-aarch64 package
Using dtb file 
--> put the dtb file : dtb/rockchip/rk3399-rockpro64.dtb on the sdxi partition. 
From the last ayufan image : 
https://github.com/ayufan-rock64/linux-kernel/releases/download/4.4.202-1237-rockchip-ayufan/linux-image-4.4.202-1237-rockchip-ayufan-gfd4492386213-dbg_4.4.202-1237-rockchip-ayufan_arm64.deb

case 2) - The way to follow.
Using snapshots/aarch64/u-boot-aarch64 package on the emmc / sdc.
_ Install the package u-boot-aarch64
# dd if=/usr/local/share/idbloader.img of=/dev/sdxc seek=64
# dd if=/usr/local/share/u-boot/u-boot.itb of=/dev/sdxc seek=16384


Thank you a lot for all the works :)

-- 
burelli.fr <oliv...@burelli.fr>

Reply via email to