00:53 <afaerber> naobsd: serial console for the fearless is working now on rk3368 ;)

00:53 <naobsd> well?

00:54 <naobsd> u-boot?

00:56 <afaerber> yes

00:57 <afaerber> (kernel serial console on the GeekBox I have already since January)

01:28 <afaerber> ayaka: please remember to use --subject-prefix="PATCH v3" and so on and maintain a changelog in your cover letter and in your patches beneath ---

01:28 <afaerber> mmind00: ^

01:28 <afaerber> also nested series are usually discouraged as it gets difficult to read after a while

08:53 <dowu> Hi guys!

08:53 <dowu> I have a problem on upgrading image file into flash memory on rk3188

08:55 <dowu> using upgrade_tool, the update.img file is looked like downloaded but during checking image file there is a message "fail".

08:57 <dowu> I have compiled the 4.7.4 kernel. I have made a image file with radax root file system.

09:00 <dowu> any wrong?

10:30 <naobsd> dowu: how did you make update.img? size of each images doesn't exceed size of partition?

10:30 <naobsd> and

10:30 <naobsd> I don't think root file system in update.img(flashed into NAND) is usable with 4.7.4 kernel

10:43 <Bad_UID> as i know images must be signed ? or no ?

10:44 <Bad_UID> also you found nand driver for rk3188 ?

11:13 <dowu> Sorry, kernel version is 4.6.4

11:14 <dowu> Also what is "images must be signed"?

11:15 <dowu> My work was like this.

11:15 <dowu> I compiled kernel 4.6.4 with cross compiler

11:16 <dowu> then made with initrd together.

11:17 <dowu> then I imported just radax file system as they do on 14.10 version.

11:17 <dowu> I was upgrading with upgrade_tool.

11:18 <dowu> uploading was fine.

11:18 <dowu> But just after this, upgrade_tool tried to check image file.

11:20 <dowu> I have got a "fail" message such as "Check Image Total(1067267K),Current(16387K)" then "Download Firmware Fail"

11:22 <dowu> The file size of update.img is 1093292504

11:34 <Bad_UID> for what you use update.img ? on which platform ?

11:46 <dowu> customized board

11:47 <dowu> But radax package is very ok. I can flash radax update.img.

11:47 <dowu> without any problems

11:49 <dowu> I was just curious on this with the latest kernel.

11:51 <dowu> I used the cross compiler, gcc-linaro-5.3-2016.02-x86_64_armeb-linux-gnueabihf.tar.xz.

11:54 <dowu> I compiled the radax update.img with arm-2013.05-24-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.

11:54 <dowu> How about the cross compiler?

21:46 <coolblade> I’m trying to diagnose a kernel crash causing boot loop. I’m listening via serial-to-usb @ 115.2k baud on UART2. I’ve tried both “console=ttyS2 earlyprintk” and “console=ttyS2,115200 earlyprintk” CMDLINE setting in the parameters file and also CONFIG_EARLY_PRINTK=y, CONFIG_RK_DEBUG_UART=2, CONFIG_SERIAL_ROCKCHIP=y in my kernel .config. From my serial tty console I can see u-boot print messages but nothing from

21:46 <coolblade> kernel prior to crashing. Any ideas on how I can get printk to work over uart2? Or is there a method to gain access to the nand flash to recover last_kmsg?

22:33 <naobsd> dowu: did you read my message?

22:34 <naobsd> coolblade: which kernel?

22:42 <coolblade> naobsd: flounder, also tlk

23:22 <afaerber> dowu, naobsd: an armeb cross compiler sounds very adventurous... expect trouble ;)