FreezingCold has quit [Remote host closed the connection]
FreezingCold has joined #linux-rockchip
Tony_ has joined #linux-rockchip
field^Mop has quit [Ping timeout: 255 seconds]
Tony_ has quit [Remote host closed the connection]
Tony_ has joined #linux-rockchip
hipboi has joined #linux-rockchip
hipboi_ has quit [Ping timeout: 252 seconds]
nighty-_ has quit [Quit: Disappears in a puff of smoke]
amstan_ has joined #linux-rockchip
amstan has quit [Ping timeout: 255 seconds]
naobsd has joined #linux-rockchip
<Tony_>
naobsd, hi.
<Tony_>
naobsd, good morning.
<Tony_>
naobsd, I think the problem is about Mutil Thread in start_kernel.
cnxsoft has joined #linux-rockchip
markm_ has quit [Ping timeout: 240 seconds]
<Tony_>
naobsd, hi.
FreezingCold has quit [Ping timeout: 256 seconds]
<naobsd>
hi
<naobsd>
hm, I can see some updates for RK in barebox bootloader
<Tony_>
naobsd, hi, I got something after debug.
<Tony_>
naobsd, the only differece is here. populate_rootfs function.
<Tony_>
naobsd, If boot fail, it will say "rootfs image is not initramfs (no cpio magic); looks like an initrd"
<Tony_>
naobsd, after "Trying to unpack rootfs image as initramfs...".
FreezingCold has joined #linux-rockchip
FreezingAlt has joined #linux-rockchip
<naobsd>
yes, that's what I explained
FreezingCold has quit [Ping timeout: 246 seconds]
<naobsd>
but I have no time to investigate detail now
FreezingAlt is now known as FreezingCold
<Tony_>
naobsd, ah, you mean that the problem is in bootloader, right ?
<naobsd>
sorry, no idea for now
Astralix` has joined #linux-rockchip
Astralix has quit [Ping timeout: 264 seconds]
GriefNorth has joined #linux-rockchip
<Tony_>
naobsd, what's your test result for rk3188 ? ;P
<Tony_>
naobsd, would you tell me ?
RayFlower_ has joined #linux-rockchip
<Tony_>
naobsd, ...
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
Astralix` is now known as Astralix|away
premoboss has quit [Remote host closed the connection]
<rperier>
hi all
<hipboi>
rperier, hi
cnxsoft1 has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 256 seconds]
<naobsd>
Tony_: again, I'm extremely busy
<naobsd>
Tony_: please understand I have my own job
cnxsoft has joined #linux-rockchip
<rperier>
Tony_: again, if you have questions, ask here to everyone. Not to naobsd. Also please not that most of us do that in our free time, so that's not possible to answer all the time
cnxsoft1 has quit [Ping timeout: 252 seconds]
Astralix|away is now known as Astralix
<Tony_>
rperier, what can I do for you ? ;)
RayFlower_ has quit [Read error: Connection reset by peer]
<rperier>
? :/
RayFlower_ has joined #linux-rockchip
QQ has joined #linux-rockchip
markm has joined #linux-rockchip
ganbold_ has quit [Remote host closed the connection]
<Tony_>
rperier, Vous êtes très beau.
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
akaizen has joined #linux-rockchip
panicking has joined #linux-rockchip
QQ has quit [Quit: Page closed]
field^Mop has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
selfbg has joined #linux-rockchip
naobsd has quit [Quit: naobsd]
apritzel has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
premoboss has joined #linux-rockchip
nighty-_ has joined #linux-rockchip
GriefNorth has quit [Quit: WeeChat 0.4.2]
naobsd has joined #linux-rockchip
Tony_ has quit [Remote host closed the connection]
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
naobsd has quit [Quit: naobsd]
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
<naobsd>
I'm still not sure your uboot.img is broken or NAND is broken or something elase
Tony__ has quit [Remote host closed the connection]
<naobsd>
if my binary doesn't work too, please tell me "sha1sum upgrade_tool" and please try "rkflashtool w 0x2000 0x2000 < uboot.img" instead of "upgrade_tool wl 0x2000 uboot.img"
<Astralix>
I checked the size of the uboot images and it fits
<naobsd>
this is Linux_Upgrade_Tool_v1.21
<Astralix>
There must be a problem with my compile results as your image works
<naobsd>
I see
<Astralix>
So your explanations tell to use 4.7.2 compiler and I know that hf is not a good idea
<naobsd>
no
<Astralix>
so I used 4.9.2 eabi (non-hf)
<naobsd>
"arm-eabi-4.6 is the official toolchain."
<Astralix>
ah, I see, it is rk3288 with the 4.7
<Astralix>
Ok, I need to upgrade uboot to be compliant with 4.7+ toolchains
<naobsd>
it's also mentioned on radxa's wiki.
<Astralix>
this toolchain dependencies of rk SOCs are pure horror
<naobsd>
please explain if you didn't follow wiki :(
<naobsd>
it's small problem
<Astralix>
I just overlooked the rk3288 hint for the toolchain
<naobsd>
no explanation is big problem for me
<naobsd>
I'm extremely busy :(
<Astralix>
Me too, hat lot of work in the last few weeks, big last minute projects for expositions and such
<Astralix>
So just enjoying some times after finishing everything
<Astralix>
So just thank you for the leading hand, I'll try to find the problem that avoids uboot proper booting with new toolchains
<naobsd>
I'm not enjoying at all. if you ask something next time, please explain what you did more exactly :(
<naobsd>
this is not first time "please try official toolchain at first"
<Astralix>
Oh sorry, 8if you perefer to not beeing held up from anything, then just reply that you have no time
<naobsd>
if it was better to say that, then, I was wrong, sorry :(
selfbg has joined #linux-rockchip
<Astralix>
No, I was wrong, that is no problem
VargaD_ has joined #linux-rockchip
<Astralix>
I already told about that I missed the line that say 4.7 is for 3288, not 3188
<Astralix>
mmind00: we already discussed about startup issues related to compilers... is one of the reasons probably the same for u-boot that avoids proper start of the kernel
<Astralix>
however, independent from toolchain, does the u-boot support dtb and resource.img handling?
VargaD has quit [Ping timeout: 264 seconds]
VargaD_ is now known as VargaD
<naobsd>
what you followed was radxa's wiki (if your message was true), not my page. I'm not talking about what you missed when you saw my page.
<Astralix>
Yes, but if I had carefully read your page, I would have seen that I used the wrong toolchain
<Astralix>
But I missed to do that, I only saw 4.7 and thought: fine!
<Astralix>
your binary image works fine for now and I am flashing all the images
<naobsd>
if you carefully read radxa's wiki, you used 4.6
<Astralix>
yes probably
<Astralix>
I was doing lots of iMX u-boot and used 4.9.3 without a problem
<Astralix>
So I just run the commands I used for the last three weeks
<naobsd>
I think your uboot.img was compiled before you (mis)read my page. again, I'm not talking about what you missed when you saw my page.
<naobsd>
rk3188 is not iMX
<Astralix>
however, do you know about resource and dtb handling?
<Astralix>
I think I'll run a test with 4.9.3 bare metal toolchain on the latest u-boot on rk3288 later this day. I really like to know how it works
<naobsd>
for now only u-boot for rk3288 support it
<naobsd>
but I'm not talking it's impossible at all
<Astralix>
Ok we know in 40s
<Astralix>
SecureBootCheckOK:0
<Astralix>
booti: do_bootm_linux...
<Astralix>
Starting kernel ...
<Astralix>
That's all
<Astralix>
Doesn't look like it can handle dtb in resource.img
<naobsd>
I don't understand what you did
<naobsd>
again, please explain
<Astralix>
I build an Android 5.0.2 that works fine on RK3288 and try to adopt RK3188
<naobsd>
I'm talking about resource/dtb support in u-boot for rk
<Astralix>
Android for RK3288 uses kernel 3.10+ and uses dtb. Boot images and dtb are probably put in resource.img
RayFlower_ has joined #linux-rockchip
<naobsd>
and what I said is "for now only u-boot for rk3288 support it"
<Astralix>
for now I just did nothing but flashing all images and your precompiled u-boot
ssvb has joined #linux-rockchip
<Astralix>
But you said it may not be impossible
<naobsd>
yes
<Astralix>
So I just verified and unfortunately you where right with your first statement so it looks like a bit of workk
<Astralix>
So I can try two ways now:
<naobsd>
you can add necessary code into u-boot for rk3188 to support resource/dtb
<Astralix>
1) build a combined kernel image that carries dtb after kernel
<naobsd>
I think it's not impossible, or am I wrong?
<Astralix>
I am at moving RK3188 back into Rockchips RK3288/RK312X kernel sources
<Astralix>
So as I have some support at this, and I am right busy in u-boot for some other projects, I can move in RK3188 into the 3288 u-boot, I hope
<Astralix>
But it could result in that you're limited to the SD-Card
<Astralix>
as the sd/mmc interface is well supported in 3288 codes but not the NAND... however... we'll see
<naobsd>
there is rknand.ko for 3.10
<Astralix>
for 3188 or for all rk3xxx?
<naobsd>
not sure. when I tried it on rk3188 + 3.10 kernel, insmod ok. if my memory is correct, I could access NAND a little (probably only read? I cannot remember). I didn't have so much time at that time, it was very experimental and unstable.
<naobsd>
"there is rknand.ko for 3.10" in rk3288 rbox sdk. this is "it" I tried.
selfbg has quit [Quit: Leaving]
GriefNorth has joined #linux-rockchip
<Astralix>
I think I can ask the guy who made it... So we can get confirmation and can concentrate on things we do not get from RK
<naobsd>
NAND priority is very low for me
<Astralix>
most 3188 devices I have, have NAND. You can boot from SD and even treat SD like eMMC.
<Astralix>
hmm.. I wonder why the u-boot shows version 2014.01 but it doesn't support dtb?
<Astralix>
however, thank you for you patience, I have to leave now. I do some tests with kernel/dtb combined images tonight and then we see
<naobsd>
I never said that dtb support is completely missing from u-boot for rk3188
<Astralix>
??
Astralix is now known as Astralix|away
<naobsd>
I'm mankind in real world. I don't think/say things must be only "1" or "0"... there are many things between "it's available and works perfectly without any work" and "completely missing"
panicking has joined #linux-rockchip
<naobsd>
"for now only u-boot for rk3288 support it" this doesn't deny existing code in tree and possible future.
<naobsd>
probably I should keep silent :(
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]
RayFlower_ has joined #linux-rockchip
FreezingCold has quit [Ping timeout: 252 seconds]
panicking has quit [Ping timeout: 256 seconds]
akaizen_ has joined #linux-rockchip
mat1 has quit [Ping timeout: 265 seconds]
akaizen has quit [Ping timeout: 265 seconds]
mat1 has joined #linux-rockchip
JohnDoe_71Rus has joined #linux-rockchip
FreezingCold has joined #linux-rockchip
RayFlower_ has quit [Read error: Connection reset by peer]