leowt changed the topic of #linux-rockchip to: Rockchip development discussion | http://linux-rockchip.info | http://irclog.whitequark.org/linux-rockchip
markm has quit [Ping timeout: 255 seconds]
markm has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 240 seconds]
akaizen has joined #linux-rockchip
GriefNorth has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 240 seconds]
akaizen has joined #linux-rockchip
GriefNorth has quit [Ping timeout: 260 seconds]
viric has quit [Ping timeout: 250 seconds]
viric has joined #linux-rockchip
srao has quit [Ping timeout: 240 seconds]
Bludot has quit [Quit: Connection closed for inactivity]
<rperier> dlezcano: hi, how did you get a rk3288 board ? throught your company I guess...
viric has quit [Ping timeout: 272 seconds]
viric has joined #linux-rockchip
rz2k has quit [Ping timeout: 250 seconds]
FreezingCold has quit [Ping timeout: 250 seconds]
irsol has quit [Ping timeout: 264 seconds]
FreezingCold has joined #linux-rockchip
irsol has joined #linux-rockchip
wildea01 has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 245 seconds]
<dlezcano> rperier: rockchip sent me one
AstralixNB has joined #linux-rockchip
<rperier> dlezcano: that's for personnal or professional needs ? sorry for all these questions, but I sent an email to service@rock-chips.com about rk3288 evaluation boards and still have no answers
nighty^ has joined #linux-rockchip
FreezingCold has quit [Ping timeout: 260 seconds]
cyrozap has quit [Ping timeout: 264 seconds]
cyrozap has joined #linux-rockchip
Bludot has joined #linux-rockchip
markm has quit [Ping timeout: 255 seconds]
akaizen has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
akaizen_ has joined #linux-rockchip
akaizen_ has quit [Ping timeout: 240 seconds]
akaizen has joined #linux-rockchip
AstralixNB has quit [Ping timeout: 250 seconds]
akaizen has quit [Remote host closed the connection]
markm has joined #linux-rockchip
akaizen has joined #linux-rockchip
lauri has joined #linux-rockchip
akaizen has quit [Remote host closed the connection]
akaizen has joined #linux-rockchip
akaizen has quit [Ping timeout: 240 seconds]
akaizen has joined #linux-rockchip
nighty^ has quit [Quit: Disappears in a puff of smoke]
hramrach has quit [Ping timeout: 264 seconds]
hramrach has joined #linux-rockchip
wildea01 has quit [Quit: leaving]
<karlp> bleh, the screws on this x5 mini are fucking stripping
<karlp> woo, brown pcb
<karlp> hehe, it has a metal weight in it!
<karlp> ok, well we have the tx pin for the console,
<karlp> guess it's time for the soldering iron then
GriefNorth has joined #linux-rockchip
hramrach has quit [Ping timeout: 264 seconds]
hramrach has joined #linux-rockchip
GriefNorth has quit [Ping timeout: 250 seconds]
nighty^ has joined #linux-rockchip
nighty^ has quit [Read error: Connection reset by peer]
<karlp> fuck, I hate soldering shit this small
nighty^ has joined #linux-rockchip
<dlezcano> Can someone give me a hand to flash correctly a custom kernel on a rk3288 ?
<mmind00> then hold recovery while powering on/resetting
<dlezcano> mmind00: ok, I got this part
<dlezcano> mmind00: what I am wondering is how to flash the kernel (uImage ?)
<mmind00> and then upgrade_tool DI -k ../kernel.img
<dlezcano> mmind00: what about the dtb ?
<mmind00> nope zImage (+dtb) + rockchip-specific checksum
<dlezcano> ah,ok
<mmind00> I'm currently searching if rockchip they hide their crc-tool also somewhere in their
<mmind00> in their source repository
<dlezcano> shall i compute the checksum of zimage + dtb and then append it
<dlezcano> ?
<mmind00> so in full: zImage + dtb -> mkkrnlimg image image.img -> then upgrade_tool
<karlp> does that tool do anything differently than any of the other rkflash tool things?
<mmind00> karlp: I think it should do the same than say "rkcrc -k"
<karlp> too many damn variants
<mmind00> yep :-)
<karlp> man, I should have used hot glue, but I thought superglue would be faster and less messy
<dlezcano> mmind00: ok, mkkrnlimg appends the crc, right ?
<karlp> this superglue isn't setting.
<mmind00> dlezcano: correct
<dlezcano> mac-:
<dlezcano> oops ^^^
<dlezcano> mmind00: ok, I give a try
<dlezcano> mmind00: oh, which dtb shall I use
<dlezcano> for rk3288
<dlezcano> there is rk3288-evb-rk808.dtb and rk3288-evb-act8846.dts
<dlezcano> and I am not able to determine what my board is
<mmind00> dlezcano: look at the smaller subboard on it
<dlezcano> ok
<mmind00> there should be a print on it either mentioning rk808 or act8846
<dlezcano> mmind00: nope
<dlezcano> I just have rk32xx_SDK
<mmind00> there are two sub-boards
<mmind00> one bigger and one smaller, right?
<mmind00> the bigger say RK3288_SDK_DDR3_....
<dlezcano> mmind00: right
<mmind00> the smaller one should say something like RK32xx_SDK_POWER(RK808)_...
<dlezcano> mmind00: right
<dlezcano> mmind00: ok, I find it
<mmind00> dlezcano: :-)
<dlezcano> it is act8846
<dlezcano> mmind00: thx :)
<mmind00> oh cool ... first test for it :-)
<dlezcano> :)
<dlezcano> btw, I noticed when calling 'make dtbs', the dtb for rockchip are not generated and they miss in the Makefile
<mmind00> yeah ... I'll need to add those
<karlp> what is the rk808 meant to be, if the act8846 is just a regulator chip?
<mmind00> karlp: the rk808 is pmic + rtc, while the act8846 uses a separate hym8563 as rtc
<dlezcano> mmind00: ok, I appended the dtb with the kernel and ran the crc tool but it fails to boot
<dlezcano> mmind00: based on linux-next and the patches you mentioned yesterday
npcomp is now known as npcomp|away
<karlp> who makes that? is that a rockchip part?
rz2k has joined #linux-rockchip
<mmind00> I would guess so, as you mentioned the rk808 vs. act8846 dts files
<karlp> are there other major branches close to upstream that I should watch? or just yours?
<mmind00> is the correct lowlevel uart selected? ... CONFIG_DEBUG_RK32_UART2=y CONFIG_DEBUG_UART_PHYS=0xff690000 etc
* dlezcano checking
<dlezcano> mmind00: no, none of them
<mmind00> karlp: everything is spread quite wide ... aka most stuff goes through specific maintainer trees, so you should check linux-next
<mmind00> dlezcano: that might be a clue to what's missing ;-)
<mmind00> the branch I mentioned is the stuff that is supposed to to arm-soc shortly, now that the clocks have landed
* dlezcano checking
<mmind00> where did you get the dts files then ... I'm confused
<dlezcano> mmind00: I pulled mike's branch
<karlp> mmind00: who's the maintainer for rockchip?
<mmind00> karlp: that would be me ;-)
<karlp> right, so yours is probably bleeding edge enough then :)
<karlp> can I pull enough of the right figures out of the bootlog from a device to make the right dts file?
<karlp> or is that, "it depends" I guess
<mmind00> karlp: it depends :-D ... in general the basic design seems always to be the same ... tps659102 on rk3066 and act8846 on rk3188 boards ...
<karlp> yeah, this one has tps659102, lan is smsc 8720a, and wifi rtl8188es, which all seems pretty common
dlezcano has quit [Quit: Leaving]
<karlp> major downside, I've lifted the track on the tx line, and will need to reglue it
dlezcano has joined #linux-rockchip
<dlezcano> mmind00: ok, so as I was not succeeding to make the linux-next to boot, I tried your branch above, and I have the same result
<dlezcano> mmind00: any suggestions ?
<dlezcano> mmind00: (fixed the UART things)
Bludot has quit [Quit: Connection closed for inactivity]
<mmind00> dlezcano: hmm, I just build my next/rk3288 branch using http://pastebin.com/t7B7TGZ2 and it did boot
<mmind00> (at least partially)
<dlezcano> mmind00: what LOADADDR are you using ?
<mmind00> dlezcano: what do you mean with LOADADDR? ... rk is not using uImages
<dlezcano> mmind00: ah right
<dlezcano> (so used to)
<dlezcano> mmind00: I am trying to compile with your config file but I have the error:
<dlezcano> "./scripts/gen_initramfs_list.sh: Cannot open 'initramfs.cpio'"
* dlezcano googling
<mmind00> dlezcano: sorry, that is my initramfs ... just set CONFIG_INITRAMFS_SOURCE="" in the config
<dlezcano> ok
<dlezcano> mmind00: unfortunately it does not boot with your config file also
FreezingCold has joined #linux-rockchip
<mmind00> hmm, that is veeery strange
<mmind00> just to check ... you see no kernel output at all, right?
<dlezcano> mmind00: right
<dlezcano> mmind00: just starting kernel ...
<mmind00> can you try the rk808 dts? ... At the moment the rk808 variant has no pmic listed at all, so nothing bad will happen
<dlezcano> ok
<mmind00> I just want to make sure I didn't mess up anything in the act8846 variant ... which is essentially untested, as I only have a rk808 board
<dlezcano> mmind00: I have the same result
<dlezcano> mmind00: let me double check I did not make a mistake when generating the kernel image
<dlezcano> mmind00: nope, everything seems right
<mmind00> dlezcano: hmm, this is very unfortunate, but I'm also currently out of ideas ... can you list the commands you executed?
<dlezcano> mmind00: sure
<dlezcano> make -j 3 ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- zImage && \
<dlezcano> make -j 3 ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- rk3288-evb-rk808.dtb && \
<dlezcano> ~/Work/src/rockchip/u-boot-rockchip/mkkrnlimg rk3288-kernel rk3288-kernel.img && \
<dlezcano> sudo ~/Work/src/rockchip/u-boot-rockchip/upgrade_tool di -k ./rk3288-kernel.img
<dlezcano> cat arch/arm/boot/zImage arch/arm/boot/dts/rk3288-evb-rk808.dtb > rk3288-kernel && \
<mmind00> hmm ... really everything as it should be
<dlezcano> mmind00: is it possible you have an uncommitted file ?
<dlezcano> mmind00: or a local file which escape the commit ?
<mmind00> nope everything accounted for ... also as you see no output at all ... either something with the kernel itself or with the low-level uart must be wrong
<dlezcano> mmind00: ok, I will investigate more tomorrow
<dlezcano> mmind00: time for me to go to bed
<dlezcano> mmind00: thanks a lot for your help, it has been very valuable
<dlezcano> mmind00: I wouldn't have been able to "boot" a custom kernel myself
<mmind00> dlezcano: yep, I'm also way past my bedtime :-)
<dlezcano> :)
<dlezcano> bye
<mmind00> see you tomorrow or so
cyrozap has quit [Ping timeout: 245 seconds]
cyrozap has joined #linux-rockchip
Astralix has quit [Ping timeout: 250 seconds]
nighty^ has quit [Remote host closed the connection]
Astralix has joined #linux-rockchip
ganbold_ has quit [Ping timeout: 255 seconds]