11:19 <cb182d> Hello, any one playing with Firefly RK3399 here?

11:19 <Ke> many people

11:19 <Ke> just ask your question

11:20 <cb182d> Is there any guide or docs to get u-boot spl and extlinux working? I'm tired of flashing kernel.img every time I need to update the kernel.

11:24 <Ke> why not EFI boot and grub, though I don't have that working at all

11:25 <cb182d> EFI & grub are also great, what I'm looking for is some method to allow the Linux distro (such as Debian flash-kernel) managing the kernel updating.

11:26 <cb182d> but there's even less docs about EFI booting on RK3399 platform

11:26 <Ke> u-boot can also do EFI boot, but I have not seen that working anywhere

11:28 <cb182d> u-boot UEFI seems to be preferred by Fedora and openSUSE

11:30 <cb182d> https://github.com/xypron/debian-image-firefly-rk3399 This one is quite close to what I want.

11:31 <cb182d> But last time I tried this, it hangs when booting the kernel. No output on serial console after u-boot started the kernel.

11:34 <adj__> cb182d, I just connected, so maybe I lost a lot of context, but have you tried this http://opensource.rock-chips.com/wiki_Debian ?

11:37 <cb182d> rootfs is not a problem for me, I'm already running a Debian buster rootfs.

11:38 <cb182d> My question is about the boot process and kernel, can I use a more standardized boot method, like extlinux or grub, instead of having to use rkdeveloptool to flash kernel.img/resource.img every time I want to update the kernel?

11:41 <Ke> definitely just u-boot supports loading from a filesystem

11:47 <maz> I think cb182d has a valid question here: is there a documented way for installing mainline u-boot together with ATF on a firefly. so far, all I've seen are partial scripts and not much in the way of synthetic documentation.

11:51 <cb182d> https://en.opensuse.org/HCL:Firefly-RK3399 like this one, openSUSE HCL page.

11:52 <cb182d> I tried this recently, and the only result is a bricked device.

11:52 <cb182d> Then having to short the eMMC and flash the official Xubuntu img to restore the device.

12:02 <mmind00> cb182d: https://github.com/mmind/u-boot-rockchip/commit/cd0088bfb0270b2c605e6023d4d1f8be9b11f7aa is what I was using

12:04 <mmind00> again also only a partial script though :-)

12:06 <rtp> mmind00: the uboot fit image is not necessary at 0x200. It depend on CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR value in uboot, which is 0x4000 nowadays.

12:07 <mmind00> rtp: see the slightly older uboot base on there ... I try to limit time spent on uboot, as the maskrom wiggling is so tedious ;-)

12:08 <mmind00> so it was more meant as "that was working for me in the past"

12:12 <rtp> fwiw, rockchip's solution is a little bit more complicated. they generate the its at build time: https://github.com/rockchip-linux/u-boot/blob/release/board/rockchip/evb_rk3399/mk_fit_atf.sh

12:13 <beeble> you can configure the payload offset also via the dts with u-boot,mmc-env-offset

12:19 <rtp> btw, is there any difference between rk3399 evb and sapphire board ? I see in mainline kernel a rk3399-evb.dts and a rk3399-sapphire.dtsi. If they're the same board, which the rk3399-evb.dts doesnt only include the rk3399-sapphire.dtsi ?

12:19 <rtp> s/which/why/

12:31 <mmind00> rtp: you'll need to ask that someone from Rockchip

12:34 <rtp> mmind00: hm. which will be hard as I've no contact with them. I only bought a board at vamrs store.

12:43 <mmind00> rtp: but I'd think it is very much possible for more than one generation of eval-boards to exist ... I remember having an evb way before the chip being on the market, so it's very much possible that sapphire/excavator are newer designs

12:49 <cb182d> mmind00: So after build & flash the u-boot-rockchip branch (tmp/rk3399-firefly), it will load boot.scr from the bootable ext2 partition?

12:49 <mmind00> cb182d: on the board that is using this, I'm using extlinux, so the standard extlinux/extlinux.conf thingy

12:58 <cb182d> mmind00: One more question, is firefly flash mode (entered by holding recovery key and press reset key) available after flashing this bootloader? or only MaskRom mode is available to flash OS images on a PC?

12:59 <mmind00> cb182d: most likely not ... I remember seeing patches for the rockusb stuff on the uboot mailinglists ... but that I'm currently using is older

13:35 <beeble> rockusb is not yet merged

14:07 <beeble> and i c&p the wrong option above. it's u-boot,spl-payload-offset not u-boot,mmc-env-offset

14:44 <cb182d> mmind00: Just now I followed the steps of your commit description, built & flashed the idbspl.img and bl3.itb, as well as an ext2 boot partition which contains extlinux/extlinux.conf, kernel, and a rootfs partition. But when I boot up the system, the serial console prints "U-Boot SPL board initphy_dll_bypass_set: phy regs at 0xffa82000" and hangs. Are there anything wrong with my steps?

14:44 <cb182d> Here is the gpt parameter: http://paste.ubuntu.com/26177097/