<beeble>
and depending on your devicetree a console=/dev/ttyyouareusing
sb35 has quit [Ping timeout: 256 seconds]
Omegamoon has joined #linux-rockchip
xerpi has joined #linux-rockchip
xerpi has quit [Remote host closed the connection]
xerpi has joined #linux-rockchip
<hgs>
beeble: sorry i meant built using buildroot that is available in rockchip repo?
<hgs>
bootargs for rootfs that is built using buildroot from rockchip repo
<hgs>
beeble: ok thanks will experiment
<beeble>
it generates a tar with the rootfs right?
<beeble>
looks like it as there is no genimage config
<beeble>
so whatever rootdevice you are putting it is your rootfs
<hgs>
rootfs.ext2 is generated and then i use mkfirmware.sh and update using rkflash.sh
<beeble>
here as an example, adapt the device setenv bootargs root=/dev/mmcblk0p1 rw rootwait
<hgs>
beeble: i am newbie are there any reference documents on how these partitions are assigned, named and mounted
<hgs>
i see some images called oem.img, userdata.img, recovery.img misc.img getting created , but understand what are those and how to change these partitions map? any references
<hgs>
beeble: so the sector or the address of the images are fixed?
<hgs>
beeble: i think i hav to go thru the reference u had mentioned, thanks
<beeble>
looks like the partitionmap is somewhat fixed and rkflashtool is getting partitionnumbers as an argument
<hgs>
beeble: looks like they using new upgrade tool which means wiki is old??
jailbox has joined #linux-rockchip
<hgs>
i see some information in parameter.txt file regarding partion mapping
<beeble>
i'm sorry. i don't follow their image development closely. but the wiki is probably the second best source for information for their tools
<beeble>
the best is the sourcecode itself :)
tl_lim has quit [Ping timeout: 245 seconds]
tl_lim has joined #linux-rockchip
<hgs>
beeble: yep, just need help on where to look (reference)
<beeble>
so my best guess would be to look at your rkflash.sh, see at what partition your ext image gets written
<beeble>
and set your bootargs to that
<beeble>
but i would have also guessed that if you are using the rockchip tooling everything would work out of the box
<beeble>
where does it actually fail?
xerpi has quit [Remote host closed the connection]
xerpi has joined #linux-rockchip
<hgs>
beeble: i saw some error message during uboot process "ANDROID: reboot reason: "recovery""
yann|work has quit [Ping timeout: 240 seconds]
cnxsoft has joined #linux-rockchip
<hgs>
beeble: so i thought the default bootargs were not working for mounting rootfs from buildroot, you suggestions are helpful and i will try to dig in to it thanks
<hgs>
yocto for rk3399 is available? any suggestion on which one to go for buildroot or yocto?
<beeble>
there are rockchip overlays available. but not a fan of OE/yocto so maybe not the best one suggest it :)
<beeble>
hmm the error message is from android_bootloader.c
<beeble>
that is all rockchip own stuff not available in mainline
<hgs>
beeble: ok, buildroot it is
<beeble>
on what board are you anyway?
<hgs>
beeble: pico right now
<beeble>
ok, then i can't just suggest to go with mainline
tl_lim has quit [Ping timeout: 240 seconds]
tl_lim has joined #linux-rockchip
BenG83 has quit [Ping timeout: 256 seconds]
yann|work has joined #linux-rockchip
tigit has joined #linux-rockchip
afaerber has quit [Quit: Leaving]
BenG83 has joined #linux-rockchip
afaerber has joined #linux-rockchip
afaerber has quit [Client Quit]
fysa has quit [Remote host closed the connection]
fysa has joined #linux-rockchip
tl_lim has quit [Read error: Connection reset by peer]