ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | Wiki at http://linux-rockchip.info | Logs at http://irclog.whitequark.org/linux-rockchip | ML at http://groups.google.com/group/linux-rockchip
zhecka_ has joined #linux-rockchip
Bad_UID has quit [Ping timeout: 245 seconds]
cnxsoft has joined #linux-rockchip
libv_ has joined #linux-rockchip
libv has quit [Ping timeout: 240 seconds]
libv has joined #linux-rockchip
libv_ has quit [Ping timeout: 240 seconds]
k_ has quit [Ping timeout: 260 seconds]
cnxsoft has quit [Quit: cnxsoft]
cnxsoft has joined #linux-rockchip
<LongChair> @phh : i'm stuck with that image. tried a lot of things and i can't get it to boot. i folowed the full procedure that's on the rk repos ... but it won't boot. just get a black screen
<LongChair> maybe i'm doing something wrong, but here is what i did : http://pastebin.com/T4cmVcX6
<LongChair> if you can spot anything wrong, feel free to tell me :)
ganbold has quit [Remote host closed the connection]
wzyy2 has joined #linux-rockchip
<wzyy2> LongChair, any log from serial if you copy the out/kernel files to the fat partition of my existing card?
<LongChair> i haven't setup any serial link yet .. not sure where that is on tinker btw
<LongChair> but i tried to copy the linux image and the dtb to the fat partition and it doesn't boot either
<LongChair> if i copy back the original kernel & dtb it works again
ganbold has joined #linux-rockchip
<LongChair> do you know where i could plug any serial cable ?
<wzyy2> You can add 'console=tty1' to extlinux.conf
<wzyy2> It will output kernel log to screen
<LongChair> i think that was already there
<LongChair> and i see nothing, but lemme doublecheck
Omegamoon has joined #linux-rockchip
<LongChair> yeah this is the content of extlinux.conf:
<LongChair> label kernel-4.4
<LongChair> fdt /rk3288-miniarm.dtb
<LongChair> append earlyprintk console=tty1 console=ttyS1,115200n8 root=/dev/mmcblk0p2 rw init=/sbin/init
<LongChair> kernel /zImage
<LongChair> so it's already there, but won't boot and won't display anything
<wzyy2> You can find uart1 in schematic and plug a serial cable to it.
<Omegamoon> without a serial console, you're pretty much blind when searching for these issues...
<LongChair> found it I need to find a longer wire though
<LongChair> so what about the comm config 115200, 8,N,1 ?
<Omegamoon> @LongChair: those are proper settings
wzyy2 has quit [Ping timeout: 255 seconds]
mrjay has joined #linux-rockchip
<LongChair> OmegaMoon : figured out how to temporailly get some serail output. will need to make a proper cable afterwards
<LongChair> i'll try to flash the rockchip image and see what i get
<Omegamoon> @LongChair: I just soldered a serial console on my Ugoos UT3S... phew... glad that worked :)
wzyy2 has joined #linux-rockchip
<phh> (or you could use the uart over usb dp/dm feature)
JohnDoe_71Rus has joined #linux-rockchip
<LongChair> ok i have made a proper cable to the tinker
<LongChair> so if i use the tinker image with replacing the zImage and the .dtb file, i get some kernel startup
<LongChair> and it will stop saying
<LongChair> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
<LongChair> [ 16.289191] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
<LongChair> [ 16.480400] IPVS: Creating netns size=1104 id=1
<LongChair> root@linaro-alip:~# [ 16.280380] rk_gmac-dwmac ff290000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
<LongChair> permitted by applicable law.
<LongChair> [ 17.204120] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
<LongChair> now if i flash the rockhip rootfs image .. i get just nothing
<phh> add earlyprintk to your cmdline?
wzyy2 has quit [Ping timeout: 240 seconds]
<LongChair> @phh : there seem to be a singificant diff in the image though
<LongChair> the image created from rootfs doesn't really show any partition when flashed
<LongChair> the asus tinker OS shows a FAT partition and then an ext4 partition
<LongChair> so there must be something in the creation process that doesn't work right
cnxsoft has quit [Remote host closed the connection]
<LongChair> @phh : ok trying to boot the ASUS one with updated kernel
<LongChair> i get the boot process ok with lot of logs
<LongChair> but still have black screen, when looking at console i get two errorish messages
<LongChair> [ 28.209415] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
<LongChair> and also that one everytime something change on hdmi output (cable replugged and such)
<LongChair> [ 153.090526] dwhdmi-rockchip ff980000.hdmi: Pixel clock 594000000 - unsupported by HDMI
<LongChair> i'm wondering if the latter is my issue
<LongChair> this is the full log of the boot : http://pastebin.com/6rZjr6vb
wzyy2 has joined #linux-rockchip
<wzyy2> So it looks like your system is up, just hdmi have been broken.
<phh> LongChair: your plugging it to a tv or a pc monitor?
<phh> you're
<wzyy2> The image created from build script also have a FAT partition and then an ext4 partition, but the boot partition is marked as EFI, so it won't be shown
<LongChair> @phh : it's a tv
<LongChair> @wzyy2 : any idea of what could break hdmi ?
<LongChair> @wzyy2 : if i flash the system.image that comes out of build script ... it doesn't even start to boot
<LongChair> i used those steps : http://pastebin.com/T4cmVcX6 , maybe there is something missing there ?
<wzyy2> U-boot in the system.image use ttys2.
<LongChair> so i need to connect to uart2 ?
<wzyy2> Rockchip platform usually use ttys2 as debug serial, but asus insist to use ttys1 because they want to keep same with rpi....
<wzyy2> yep, and change console=ttyS1,115200n8 to console=ttyS2,115200n8
<LongChair> ok will try
<LongChair> on diff i can see between ASUS image and the rootfs image is that it doesnt seem to use the same modules from hdmi
<LongChair> last lines i get with original asus iamge are :
<LongChair> 16:28:37 - LongChair : […] 30.198496] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
<LongChair> 16:28:37 - LongChair : [ 39.672619] rockchip-vop ff930000.vop: Timeout waiting for IRQ
<LongChair> 16:28:37 - LongChair : [ 39.574520] rk3288-dmc ff610000.dmc: failed to change dmc freq
<LongChair> 16:28:37 - LongChair : [ 39.562639] rockchip-vop ff930000.vop: Timeout waiting for IRQ
<LongChair> 16:28:37 - LongChair : [ 39.568478] rk3288-dmc ff610000.dmc: Failed to determine timeout
<LongChair> 16:28:37 - LongChair : [ 39.678452] rk3288-dmc ff610000.dmc: Failed to determine timeout
<LongChair> with the kernel replaced it get :
<LongChair> [ 153.090526] dwhdmi-rockchip ff980000.hdmi: Pixel clock 594000000 - unsupported by HDMI
<LongChair> @wzyy2 : log on rootfs image with uart2 : http://pastebin.com/NyVKc1ig
<LongChair> so from this log it looks like it doesnt use the right dtb
<wzyy2> You should replace extlinux.conf tamplate
<wzyy2> template
<LongChair> right
<LongChair> i only need to rebuild the image after that right ?
<wzyy2> You can edit it driectly in FAT partitions
<wzyy2> mount /dev/sdb6 <dir>
<wzyy2> LongChair, are you using 4k screen?
<LongChair> the tv is 4k, but it's going thru a 1080p AVR
<wzyy2> revert this commit
mrjay has quit [Quit: Page closed]
<LongChair> hehe yeah that looks like what it's complaining about :)
<LongChair> i'll try that on the ASUS image
<wzyy2> It seems your screen require a 4k-60hz display mode which is not yet supported in linux.
<LongChair> i see
<LongChair> @wzyy2 : works ! awesome thanks ! :)
wens has quit [Ping timeout: 240 seconds]
Myy has joined #linux-rockchip
mrueg has quit [Remote host closed the connection]
mrueg has joined #linux-rockchip
mrjay has joined #linux-rockchip
<mrjay> hi does mmc works in your uboot tree?
<mrjay> i can't get it up on rk3066
<mrjay> sorry wrong window
<mrjay> mmind00: ^
<mmind00> mrjay: never tried so far ... I've only used tftp so far ... but keep in mind, the mmc handling is also different in the kernel between rk3066/rk3188 and the newer socs
<mrjay> ahh ... i didn't know that
<mrjay> mmind00: i need to investigate more ... but usb works out of the box
<mrjay> mmind00: when you'll have time ... please test mmc and post here if it works
<mrjay> mmind00: thanks
mrjay has quit [Quit: Page closed]
JohnDoe_71Rus has quit [Quit: KVIrc 4.9.2 Aria http://www.kvirc.net/]
wzyy2 has quit [Ping timeout: 245 seconds]
paulk-collins has quit [Quit: Leaving]
k_ has joined #linux-rockchip
Omegamoon has left #linux-rockchip [#linux-rockchip]
<k_> can't get any output from https://github.com/rockchip-linux/kernel
<k_> earlyprintk is enabled. is there way to debug boot process?
<Myy> AFAIK, the other way is to connect an UART<->USB cable and use minicom, in order to see any string that will output by the kernel (given the current kernel's loglevel).
<Myy> There might be other ways involving TCP/IP debuggers, but I have no idea how to use them.
<Myy> Anyway, I'll have to go. If nothing work, but you have the DTB of your board, you can give https://github.com/Miouyouyou/MyyQi a try. You might have kernel panics about the root partition mmc0blkX becoming mmc1blkX though.
<Myy> However, a few extlinux.conf changes should solve the problem, if that's the case.
<Myy> See you everyone !
Myy has quit [Quit: Leaving]
<k_> I already use serial console, but last message is "Starting kernel ..." from u-boot
<mmind00> k_: I guess at first making sure that it's the correct debug_ll settings in the config?
<k_> earlyprintk should use u-boot's console
<mmind00> k_: while somewhat true, you still need to tell the kernel where to put stuff and thus need to enable a correct DEBUG_LL setting
<mmind00> k_: DEBUG_LL for 32bit of course, 64bit requires an earlycon as base
nighty has quit [Remote host closed the connection]