<hgs>
hi all, i am attempting to learn how to compile the entire 64 bit build system for rockchip
<hgs>
I checked out the latest repository contents, updated evb-rk3399_defconfig, rk3399-sapphire-excavator-linux.dts from the build system which was already working.
<hgs>
Generated the following files kernel.img,parameter.txt, trust.img, MiniLoaderAll.bin, resource.img, uboot.img (used rootfs of the old build for now) and then flashed using AndroidTool_Reelase_v2.52.
<hgs>
Issued gpt write mmc 0 $partitions and it was not booting successfully
<hanetzer>
hgs: what's your bootloader and main boot device?
<hgs>
following is the error in the console "Unknown command 'boot_android' - try 'help' Unknown command 'bootrkp' - try 'help' switch to partitions #0, OK mmc0(part 0) is current device Failed to mount ext2 filesystem... ** Unrecognized filesystem type ** MMC Device 1 not found no mmc device at slot 1"
<hgs>
is it trying to boot from mmc
<hgs>
?
<hgs>
looks like Unknown command 'boot_android' - try 'help' Unknown command 'bootrkp' - try 'help' switch to partitions
<hgs>
is the problem
<hanetzer>
hgs: I would suggest using upstream u-boot. do you actually want to use android?
<hgs>
no i want linux distribution
<hgs>
debian or ubuntu
<hanetzer>
yeah. upstream u-boot, not the vendor stuff. which device?
<hgs>
hanetzer: pico rk3399
<hanetzer>
may need some porting
<hanetzer>
usually new rockchip devices just need a bit of glue code
<hanetzer>
pico or rico ?
<hgs>
hanetzer: updated evb-rk3399_defconfig, rk3399-sapphire-excavator-linux.dts from the working build system, would that not be sufficient also how to narrow down to the glue code?
<hgs>
hanetzer: pico from boardcon
<hanetzer>
arch/arm/mach-rockchip/rk3399* needs adjustments. link to the specs?
<hgs>
hanetzer: so just the uboot from upstream and the glue code patching should make it work?
<hanetzer>
probably. its what I did for my asus c201/rk3288-veyron-speedy
<hgs>
hanetzer: thanks, but seems not so easy
<hanetzer>
it is. assuming you know a bit of stuff on how this works.
<hgs>
hanetzer: between i am new to these kind of stuff, what i know is about some baremetal programming, user space linux programing, not sure if those would be sufficient?
<hanetzer>
u-boot is essentially baremetal.
<hgs>
hanetzer: yaa, never worked on uboot though, have some reading to make, do you have reference to get started
<hanetzer>
hgs: doc/README.rockchip and the source code itself
<hgs>
hanetzer: ok thanks, between even if you are building for arm64 bit you still look in to arch/arm/mach-rockchip/rk3399
<kever>
Rockchip U-Boot do support linux distro format
<kever>
hgs: the log shows that there is no available boot found.
<hanetzer>
yeah.
<kever>
if you are using kernel.img/resource.img from vendor, you need enable BOOT_ROCKCHIP to boot this format image.
<hgs>
kever: not sure what you referring to by saying vendor, i using code from https://github.com/rockchip-linux/repo and patched the evb-rk3399_defconfig, rk3399-sapphire-excavator-linux.dts which was taken from vendor build source
<hanetzer>
hgs: vendor == rockchip
<hanetzer>
it has a sort of slang meaning 'kinda shitty code that works, but is not suitable to be merged into upstream' where upstream is u-boot or linux itself
<kever>
Rockchip is using android format or rkimg format for product, so if you want to use Linux distro format, you need ot pack the boot.img by yourself.
ramcq has quit [Ping timeout: 265 seconds]
<hgs>
hanetzer: vendor i meant it is from pico who is oem of rockchip
<hgs>
kever: ok any information on how to pack the boot.img?
adj_ has joined #linux-rockchip
adj__ has quit [Read error: Connection reset by peer]
<hgs>
kever: thanks i will try to connect the dots before i put my questions
<hgs>
apart from uboot kernel rootfs, i dont have clue on other binaries like idbloader miniloader etc also not sure about whether the address that come default are valid
tl_lim has quit [Ping timeout: 246 seconds]
adj__ has joined #linux-rockchip
tl_lim has joined #linux-rockchip
<kever>
I think the image type from PICO is origin from rockchip, no difference.
adj_ has quit [Ping timeout: 250 seconds]
lurchi_ has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 264 seconds]
<hanetzer>
in any case. should avoid 'think' and make it 'know'. if you use standard, known working formats, you don't have to play guessing games :)
vstehle has joined #linux-rockchip
ramcq has joined #linux-rockchip
tl_lim has quit [Ping timeout: 246 seconds]
tl_lim has joined #linux-rockchip
anarsoul has quit [Ping timeout: 246 seconds]
<kever>
Well, hgs says his image including kernel.img/parameter.txt/trust.img, this is definitly rockchip rkimg format, no matter it's from rockchip or from pico, that's why I say no difference.
<hgs>
kever: following the way in which pico build system generated package (boot.img, idbloader.img, rk3399_loader_v1.10.112.bin, trust.img, uboot.img, Image, rk3399-sapphire-excavator-linux.dtb), i made some progress, but still it crashed logs in the follwoing link https://pastebin.com/KhMzzxJ7
aalm has joined #linux-rockchip
aalm has quit [Ping timeout: 268 seconds]
aalm has joined #linux-rockchip
cnxsoft has quit [Read error: Connection reset by peer]
tl_lim has quit [Read error: Connection reset by peer]
fireglow has quit [Quit: Gnothi seauton; Veritas vos liberabit]
fireglow has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
nighty- has quit [Quit: Disappears in a puff of smoke]
<maz>
hgs: well, exactly what it says on the tin: IRQ120 is screaming, and no driver is willing to shut it down. after a while, the kernel shuts it off.
<mrfixit2001>
rompelstompel: I've used rkmpp before but nothing with gstreamer. I've built packages for it in libreelec and buildroot. Use the source from ayufan's github repo.