muvlon has quit [Remote host closed the connection]
vstehle has joined #linux-rockchip
wzyy2 has joined #linux-rockchip
lurchi_ is now known as lurchi__
kloczek has quit [Quit: kloczek]
kloczek has joined #linux-rockchip
agusan has quit [Ping timeout: 252 seconds]
kloczek_ has joined #linux-rockchip
kloczek has quit [Ping timeout: 255 seconds]
kloczek_ is now known as kloczek
kloczek has quit [Client Quit]
kloczek has joined #linux-rockchip
kaspter has joined #linux-rockchip
lurchi__ is now known as lurchi_
anarsoul|2 has quit [Ping timeout: 248 seconds]
tl_lim has quit [Ping timeout: 252 seconds]
tl_lim has joined #linux-rockchip
cnxsoft has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 240 seconds]
cnxsoft has joined #linux-rockchip
lurchi_ is now known as lurchi__
lurchi__ is now known as lurchi_
wzyy2 has quit [Remote host closed the connection]
wzyy2 has joined #linux-rockchip
cnxsoft1 has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 248 seconds]
cnxsoft1 is now known as cnxsoft
dni_ has quit [Ping timeout: 260 seconds]
adj__ has joined #linux-rockchip
wzyy2 has quit [Quit: Konversation terminated!]
kloczek has quit [Remote host closed the connection]
kloczek has joined #linux-rockchip
wzyy2 has joined #linux-rockchip
lurchi__ has joined #linux-rockchip
vagrantc has joined #linux-rockchip
vagrantc has quit [Changing host]
vagrantc has joined #linux-rockchip
lurchi_ has quit [Ping timeout: 252 seconds]
vagrantc has quit [Quit: leaving]
tl_lim has quit [Ping timeout: 258 seconds]
tl_lim has joined #linux-rockchip
kaspter has quit [Quit: kaspter]
fixmer has joined #linux-rockchip
aalm has quit [Quit: xyz 1.9.1]
indy has quit [Ping timeout: 240 seconds]
indy has joined #linux-rockchip
kaspter has joined #linux-rockchip
kaspter has quit [Read error: Connection reset by peer]
kaspter1 has joined #linux-rockchip
kaspter1 is now known as kaspter
akaizen has quit [Read error: Connection reset by peer]
akaizen has joined #linux-rockchip
wouterstreamit has joined #linux-rockchip
aalm has joined #linux-rockchip
ganbold has quit [Remote host closed the connection]
ganbold has joined #linux-rockchip
wzyy2 has quit [Remote host closed the connection]
wzyy2 has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
dni has joined #linux-rockchip
<wouterstreamit>
I have been reading sources and if I understand correctly, pressing the recover button to enter miniloader mode is not enabled for rk3288 in yocto as it does not write the miniloader image to emmc, why?
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
<phh>
Afaik on rk3288, loader mode is handled by uvoot
<phh>
Uvoot*
<phh>
Grah u-boot
<wouterstreamit>
Thank you, I have found that as well but that does not work with the "recover" button on my board - only "reboot loader" command works. But suppose I brick my linux and I cant do that anymore, then I have a problem
<wouterstreamit>
So I want to be able to access rockusb loader mode by pressing the recover button - I suppose I could modify u-boot to support this but I think miniloader already does this?
<stdint>
which board?
<stdint>
in most of board, I think the recovery button is designed for the android, so it is used for entering the downloading mode of the bootloader
<stdint>
or the recovery of the android
<stdint>
if you want to enter the mode to download the miniloader, what you need is the massrom mode
<wouterstreamit>
Its a custom board but its exactly the same on the firefly rk3288. In images not made with yocto that still use the miniloader, both on my board and the firefly the recover button enables LOADER mode which allows rkdeveloptool to flash new images. I want to emulate exactly this behaviour in images made with Yocto. I suppose the easiest way to do this is to enable the miniloader path in rockchip-gpt-img.bbclass and update
<wzyy2>
Have you try rockusb mode in u-boot?
<wouterstreamit>
Yes, but entering that can only be done by rebooting from a linux command line?
<wouterstreamit>
I am not saying rockusb mode does not work, I simply want to enable a physical button to get into that mode in case I accidentally flash a bricked linux
<wzyy2>
The button behavior is supposed to be defined by yourself
<wzyy2>
you could modify u-boot to do that
<wouterstreamit>
So why is this behaviour enabled in miniloader without any work from my side?
<phh>
wouterstreamit: anyway if you're afraid of bricking, you should make a switch to block eMMC and boot into maskrom
<wzyy2>
miniloader? We don't use miniloader in rk3288
<wzyy2>
after maskrom, it enter u-boot spl, and then u-boot
<wouterstreamit>
I normally do my development from SD cards with empty emmc (maskrom), but I want to use the emmc now
<wouterstreamit>
wzyy2: I know miniloader is not used from yocto, but when using the RK3288UbootLoader_V2.19.06.bin I am pretty sure that contains miniloader?
tl_lim has quit [Read error: Connection reset by peer]
<wouterstreamit>
and rkbin also contains a miniloader for rk3288 which I am pretty sure is usable as well
<wouterstreamit>
So maybe I am making wrong assumptinos here, but what I see is that when I use the RK3288UBootLoader_V2.19.07.bin (which comes from Rockchip - nobody there who knows anything about my recover button) I get the behaviour I want, and when I dont and instead build my own u-boot and use u-boot-spl I dont
<phh>
wouterstreamit: I don't know if rk3288ubootloader has a miniloader, but again, in this case, it's uboot who does rockusb, and the difference between your u-boot and the one in rk3288uboot, is that the later listens to "recover" button
<wouterstreamit>
Thank you, that code does exactly what I want
<phh>
wzyy2: erm, according to board/rockchip/common/rkloader/key.c, on rk3288, rockusb key is on ADC ladder, so not exactly so easy
adj__2 has joined #linux-rockchip
nashpa_ has joined #linux-rockchip
fixmeer has joined #linux-rockchip
<wouterstreamit>
Why wasnt that code ported to the opensource version?
nighty-__ has joined #linux-rockchip
afaerber has quit [Quit: Leaving]
<phh>
because there is a huge lot of code missing, and far from being clean
ckeepax1 has joined #linux-rockchip
<phh>
I mean, rockusb made it into mainline (or hasn't yet?)
narmstrong has quit [Read error: Connection reset by peer]
nashpa has quit [Ping timeout: 248 seconds]
jelly has quit [Ping timeout: 248 seconds]
indy has quit [Ping timeout: 248 seconds]
adj__ has quit [Ping timeout: 248 seconds]
fixmer has quit [Ping timeout: 248 seconds]
nighty-_ has quit [Ping timeout: 248 seconds]
ckeepax has quit [Ping timeout: 248 seconds]
narmstrong_ is now known as narmstrong
indy has joined #linux-rockchip
<wzyy2>
: ) I think it's because they don't want to limit it, people should add their own code to handle buttons ....
<wzyy2>
You could send a email to opensource@rock-chips.com, let them provide a guide at least
<wzyy2>
rockusb is merged i think.
<wzyy2>
is recover button adc key?
<wzyy2>
- -ok, then it will be not so easy.
<phh>
that's what board/rockchip/common/rkloader/key.c says at least
<wouterstreamit>
Alternatively, instead of spending hours porting key.c to the release branch, I suppose I could also just use the rkproduct branch in my Yocto image I suppose? Or is this a bad idea
<phh>
yes, just reading the ADC shouldn't be too hard
<wzyy2>
if you are satisfied with rk-uboot, it's ok to use it.
<wzyy2>
e.g: usb-keyboard, usb-disk,ethernet.
jelly-home has joined #linux-rockchip
kever has joined #linux-rockchip
<topi`>
does anyone know if there are any useful kernels for a Geekbox out there? (rk3368)
<topi`>
afaik armbian.com doesn't offer images for Geekbox
<topi`>
there is a 3.10.0 kernel for geekbox on the image from forums, but it doesn't include e.g. support for AES instructions
<phh>
yeah rk3368 seems quite poorly supported in mainline/linux-rockchip :/
<topi`>
I guess code using the aes instructions could actually work even on a 3.10 kernel even though there is no aes flag anywhere near /proc/cpuinfo
<topi`>
I'll try to debootstrap a aarch64 debian...
afaerber has joined #linux-rockchip
nashpa_ has quit [Quit: Going away]
nashpa has joined #linux-rockchip
<topi`>
it seems I cannot find where the kernel boot params are defined. There are 5 partitions on the emmc and none of them contain even a "root=" string
<topi`>
the 32MB partition probably hosts the kernel image. It starts with "ANDROID!"
<stdint>
I don't think so, except the GPU part, the rk3368 works as well as rk3228
<stdint>
I don't care but the rootfs build script, I never use them
<stdint>
as long as the kernel works, the userspace is not a big problem
<phh>
well, in u-boot, there is a config only for sheep-rk3368, no evb
<stdint>
in my memory, the partition table of the u-boot for rk3368 doesn't support the standard partition table
ramcq has joined #linux-rockchip
wzyy2 has quit [Ping timeout: 258 seconds]
PoueT has quit [Quit: Ping timeout (120 seconds)]
PoueT has joined #linux-rockchip
leah2 has quit [Ping timeout: 255 seconds]
nighty- has joined #linux-rockchip
leah2 has joined #linux-rockchip
wzyy2 has joined #linux-rockchip
<wouterstreamit>
phh: wzyy2: I have managed to get my recovery button and the rockusb driver in u-boot release branch working :) but the behaviour of rockusb seems slightly different from the behaviour in rkproduct branch - most notably, the rkdeveloptool db command does not work. Any idea why?
matthias_bgg has quit [Ping timeout: 258 seconds]
<beeble>
isn't db not only relevant if in maskrom?
<phh>
well, I think so, but when using upgrade_tool uf update.img, the first step is to boot into the bootloader in the update.img
<beeble>
because you are already running u-boot in rockusb mod
<phh>
oh, that's interesting, there is a "reboot to maskrom" rockusb command
<phh>
which is not implemented in release's rockusb
wzyy2 has quit [Ping timeout: 252 seconds]
wzyy2 has joined #linux-rockchip
<phh>
yup, rkdeveloptool rd 3 reboots to maskrom \o/
<phh>
so, it's likely that upgrade_tool uf update.img reboots into maskrom, then boots update.img's bootloader