Hi Maxim,
Seems I have the rk3399 OP1 SoC variant which has slightly different DT in the kernel https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/rockchip/r...
Unfortunately the website I bought the board from (which was the only place which had stock) was in German.
Peter.
On Tue, 11 Jan 2022 at 09:17, Peter Griffin peter.griffin@linaro.org wrote:
Hi Maxim,
On Tue, 11 Jan 2022 at 08:57, Maxim Uvarov maxim.uvarov@linaro.org wrote:
On Tue, 11 Jan 2022 at 11:32, Peter Griffin peter.griffin@linaro.org wrote:
Hi Maxim,
(adding smart-dev ml to CC as per Anmars request)
@Mike / Tom see below about md5sums now matching but image still
failing to boot. Sorry I accidentally dropped you off cc.
@Maxim I actually got sent two RockPi 4 boards by mistake, so I just tried the
image on the second board I have, unfortunately I still get the same issue. So it seems unlikely to be an issue with my board. Also I had debian image booting into a graphical environment when I first got the board ok.
With the u-boot EFI boot stuff, what env variable do I need to update
to get earlyprintk or similar enabled?
EFI partition has /extlinux/exlinux.conf you can specify additional kernel parameters there, right after initrd=. You can try dtb from debian, maybe it will boot your board.
Thanks. I've added earlycon=uart8250,mmio32,0xff1a0000 earlyprintk
Unfortunately that gets me 0 extra prints :(
Which version of the board do you have? Mine is Rock OI 4B v1.4
Mine is Rock Pi 4 Model B OP1 v1.72 - so a later revision 4Gb of RAM
There is one small switch on the back side on my board and it's in the left position. Closer to ethernet.
Thanks, I checked and the switch is in the same position.
Peter.
Maxim.
Thanks,
Peter.
On Mon, 10 Jan 2022 at 16:37, Peter Griffin peter.griffin@linaro.org
wrote:
Hi Maxim,
Unfortunately all the md5sum now match, but it still fails in the same
place :(
The last few prints are as before
Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 1: Poky (Yocto Project Reference Distro) Retrieving file: /ledge-initramfs.rootfs.cpio.gz Retrieving file: /efi/boot/bootaa64.efi append: root=UUID=6091b3a4-ce08-3020-93a6-f755a22ef03b rootwait
panic=60 console=ttyS2,1500000
Retrieving file: /dtbs/rockchip/rk3399-rock-pi-4b.dtb Moving Image from 0x2080000 to 0x2200000, end=4310000 ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000
Then nothing more printed. I'm using serial console on 10,8 and 6
(which is what the bootloader prints are going to).
Does anyone else have a board who can try it?
Pete.
On Mon, 10 Jan 2022 at 16:04, Maxim Uvarov maxim.uvarov@linaro.org
wrote:
Uploaded with the same name.
gzipped image md5 has to be:
md5sum ledge-rockpi4b_sd.img.gz fddaa676e014a42d37f3d3e1111d70b5 ledge-rockpi4b_sd.img.gz
On Mon, 10 Jan 2022 at 18:23, Peter Griffin peter.griffin@linaro.org
wrote:
Hi Maxim,
I guess the good news is the md5sum is different
md5sum ledge-rockpi4b_sd.img c6c50a326f99355f8a323d720def4dd9 ledge-rockpi4b_sd.img
Where can I get the working image from?
Thanks,
Peter.
On Mon, 10 Jan 2022 at 14:31, Maxim Uvarov maxim.uvarov@linaro.org
wrote:
> > Peter, > > Image boots for me: > > 1. cat ledge-rockpi4b_sd.img > /dev/sdb > 2. then boot. > I attached a boot log. > md5sum ledge-rockpi4b_sd.img > bdbed269fd8dda5c1013265f2bc2e28a ledge-rockpi4b_sd.img > > Do you use serial cable on pins 10,8 and 6? (Maybe you are looking > for a different console...). > > > > > > On Mon, 10 Jan 2022 at 15:36, Peter Griffin <
peter.griffin@linaro.org> wrote:
> > > > Hi Maxim, > > > > On Mon, 10 Jan 2022 at 12:18, Maxim Uvarov <
maxim.uvarov@linaro.org> wrote:
> >> > >> On Mon, 10 Jan 2022 at 14:41, Peter Griffin <
peter.griffin@linaro.org> wrote:
> >> > > >> > Hi Maxim, > >> > > >> > On Mon, 10 Jan 2022 at 10:44, Maxim Uvarov <
maxim.uvarov@linaro.org> wrote:
> >> >> > >> >> Hello Peter, > >> >> > >> >> Are there any additional applications which I need to add to
LEDGE RP
> >> >> for the smart camera project? > >> >> > >> >> I updated wiki with an SD card image for Rock PI. Were you
able to run it?
> >> > > >> > > >> > U-Boot & TF-A all boot OK, but I don't get any uart output
from the kernel.
> >> > See log below > >> > > >> > U-Boot TPL 2022.01-rc4 (Dec 20 2021 - 16:15:15) > >> > Channel 0: LPDDR4, 50MHz > >> > BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16
Size=2048MB
> >> > Channel 1: LPDDR4, 50MHz > >> > BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16
Size=2048MB
> >> > 256B stride > >> > lpddr4_set_rate: change freq to 400000000 mhz 0, 1 > >> > lpddr4_set_rate: change freq to 800000000 mhz 1, 0 > >> > Trying to boot from BOOTROM > >> > Returning to boot ROM... > >> > > >> > U-Boot SPL 2022.01-rc4 (Dec 20 2021 - 16:15:15 +0000) > >> > Trying to boot from MMC2 > >> > > >> > > >> > U-Boot 2022.01-rc4 (Dec 20 2021 - 16:15:15 +0000) > >> > > >> > SoC: Rockchip rk3399 > >> > Reset cause: POR > >> > Model: Radxa ROCK Pi 4B > >> > DRAM: 3.9 GiB > >> > PMIC: RK808 > >> > MMC: mmc@fe310000: 2, mmc@fe320000: 1, mmc@fe330000: 0 > >> > Loading Environment from SPIFlash... Invalid bus 1 (err=-19) > >> > *** Warning - spi_flash_probe_bus_cs() failed, using default
environment
> >> > > >> > In: serial > >> > Out: serial > >> > Err: serial > >> > Model: Radxa ROCK Pi 4B > >> > Net: eth0: ethernet@fe300000 > >> > starting USB... > >> > Bus usb@fe380000: USB EHCI 1.00 > >> > Bus usb@fe3a0000: USB OHCI 1.0 > >> > Bus usb@fe3c0000: USB EHCI 1.00 > >> > Bus usb@fe3e0000: USB OHCI 1.0 > >> > Bus usb@fe800000: Register 2000140 NbrPorts 2 > >> > Starting the controller > >> > USB XHCI 1.10 > >> > Bus usb@fe900000: Register 2000140 NbrPorts 2 > >> > Starting the controller > >> > USB XHCI 1.10 > >> > scanning bus usb@fe380000 for devices... 1 USB Device(s)
found
> >> > scanning bus usb@fe3a0000 for devices... 1 USB Device(s)
found
> >> > scanning bus usb@fe3c0000 for devices... 1 USB Device(s)
found
> >> > scanning bus usb@fe3e0000 for devices... 1 USB Device(s)
found
> >> > scanning bus usb@fe800000 for devices... 1 USB Device(s)
found
> >> > scanning bus usb@fe900000 for devices... 1 USB Device(s)
found
> >> > scanning usb for storage devices... 0 Storage
Device(s) found
> >> > Hit any key to stop autoboot: 0 > >> > switch to partitions #0, OK > >> > mmc1 is current device > >> > Scanning mmc 1:2... > >> > Found /extlinux/extlinux.conf > >> > Retrieving file: /extlinux/extlinux.conf > >> > 1: Poky (Yocto Project Reference Distro) > >> > Retrieving file: /ledge-initramfs.rootfs.cpio.gz > >> > Retrieving file: /efi/boot/bootaa64.efi > >> > append: root=UUID=6091b3a4-ce08-3020-93a6-f755a22ef03b
rootwait panic=60 console=ttyS2,1500000
> >> > Retrieving file: /dtbs/rockchip/rk3399-rock-pi-4b.dtb > >> > Moving Image from 0x2080000 to 0x2200000, end=4310000 > >> > ## Flattened Device Tree blob at 01f00000 > >> > Booting using the fdt blob at 0x1f00000 > >> > > >> > No further prints after that > >> > > >> > >> Hm, that is interesting. I see kernel boot messages and can
login to
> >> the board. I will think about where there might be
differences...
> > > > > > Ok thanks :) BTW this is the output from the image hosted here > >
https://people.linaro.org/~maxim.uvarov/ledge-rockpi4b_sd.img.gz
> > > > Let me know if there is some other image you want me to try. > > > > Thanks, > > > > Peter > >> > >> > >> > Peter. > >> > > >> >>