00:00 <edolnx> which is surprising to me. I need to solder my connectors to the board to get a good stable link, let me do that and post a log.

00:11 <edolnx> Here is the serial port output during poweron http://edolnx-public.objects.dreamhost.com/CX-R8/minicom-log0001.txt

00:13 <edolnx> hehe "Press any key to abort autoboot" seems to be a lie...

00:18 <karlp> any key might be a specific key but wasn't changed :)

00:26 <edolnx> indeed :D

00:26 <edolnx> Now the question is, which one?

00:27 <edolnx> Since the line is "Hit any key to stop autoboot: 0" that could mean it's disabled too

00:56 <edolnx> Oh, hello there. When you boot into Android recovery, and the "reboot into bootloader" the bootloader says "reboot to rockusb." which _may_ mean it's trying to boot to a USB device. Now I just need to build an image to test that

01:08 <naobsd> edolnx: no need to investigate/assume about bootloader so much

01:10 <naobsd> the reason count down start at 0 is because it's defined and compiled so. you can change it by recompiling

01:10 <naobsd> and you'll get not so much useful u-boot prompt

01:11 <naobsd> you can use rockusb protocol with rkflashtool

01:12 <naobsd> you can enter rockusb mode by "reboot bootloader" command from (serial console|adb) shell on (Android|recovery)

01:13 <naobsd> or if your box has a button which is used for firmware update, then you can press&hold it while power on. it's rockusb mode.

01:15 <naobsd> basically rockusb mode is for flashing images, not for booting

01:16 <naobsd> if you have any experience about (more useful) bootloader with non-Rockchip SoCs, I recommend to forgot about it.

01:19 <edolnx> naobsd, all good information to know :D

01:20 <edolnx> naobsd, So, the only issue is I'm not sure where/if there is an OTG port. I'm thinking the one wired directly to the SoC may be, but the only USB A-A cable I have didn't seem to work...

01:23 <naobsd> I tought USB A-A works... is there any factory/update firmware image and tool which requires OTG for your box?

01:26 <naobsd> well, one point, the key you pressed and got recovery mode is for rockusb mode. when entering rockusb mode, if there is no OTG connection, bootloader try to boot recovery (see "Usb Timeout, Return for boot recovery!" in your console output)

01:27 <naobsd> are you sure OTG is connected to PC while pressing that key and powering on?

01:36 <naobsd> edolnx: OTG is nearest SD slot, right?

01:40 <naobsd> mm, it might be wrong, but anyway,

01:40 <naobsd> usb hub is connected to ehci, and no usb hub for otg

01:42 <naobsd> OTG port should be run as HOST while running Android. you have to change setting to connect PC with Android

01:51 <naobsd> oh, is eMMC TOSHIBA? I'm curious about performance ;)

01:52 <edolnx> Yes, the one I'm guessing is OTG is the one next to the SD slot

01:52 <edolnx> Let me plug in my cable and try again

01:54 <edolnx> oh hey, that is working!

01:54 <naobsd> nice :)

01:55 <naobsd> it might be nice if I2C/SPI holes can be configured as another UART

01:55 <edolnx> OK, now I just need an image and the tool to send it

01:55 <naobsd> is wifi chip AP6330?

01:55 <edolnx> How would you like me to test the flash performance?

01:56 <edolnx> Yes, WiFi and BT is from the AP6330

01:56 <edolnx> The antenna is only 2.4GHz is looks like, which is disappointing but I'm using wired ethernet so no problem

01:56 <naobsd> then your box should be Sunchip CX-R8

01:56 <naobsd> s/box/board/

01:57 <edolnx> probably, I'm sure they are all the same board just different logos on the cases :D

01:58 <naobsd> there is some possibility that some parts e.g. wifi/emmc/etc can be different

01:58 <naobsd> for customized products

01:58 <edolnx> The Android dmesg shows at least 3 serial ports, I'm not sure where they all go

01:59 <naobsd> 3 holes near wifi/bt antenna are probably 2 gpio and 1 gnd...it looks like for dual color LED

01:59 <edolnx> alright, so I need rkflashtool and some form of image. Let me checkout and build those

02:00 <naobsd> you can get Android firmware from here http://chinagadgetsreviews.com/download-latest-android-lollipop-5-1-1-stock-firmware-for-sunchip-cx-r8-tv-box.html

03:21 <edolnx> Ran Androbench and Geekbench on the Android install while waiting for the firmware to download. Results are posted here: http://edolnx-public.objects.dreamhost.com/CX-R8/index.html

03:21 <edolnx> (couldn't figure out how to get the raw results files, sorry)

04:05 <rk___> ls

12:54 <mmind00> pulser: btw. the missing battery data for me, was just caused by it being module and me being dumb and not rebuilding them

12:55 <mmind00> pulser: when simply switching them to =y, I again get battery-infos on my jerry (upower -d)

12:57 <pulser> OK interesting mmind00 - I will quickly try again. I don't think it was modular when I checked

12:58 <pulser> (I use a shell script to clear the old modules, make a new folder, install them to it, then I punt them to the SD)

13:18 <pulser> mmind00: OK, so I tested it again on veyron-minnie - built from your tree, but made the sbs config line "y" rather than "m" to get it inside the kernel. When I do "upower -d", the only device I get is gpio-charger ahd DisplayDevice - daemon says it is not on battery

13:19 <mmind00> pulser: ah ... you're on a Minnie, sorry I forgot that detail

13:20 <pulser> oh no worries - do I need to tweak something in my config then? I guess different battery driver

13:20 <mmind00> pulser: minnie has a bq27500 battery-thingy connected to the i2c provided by cros_ec

13:20 <pulser> right - that makes sense then why it caused an issue

13:20 <pulser> let me force enable that :)

13:21 <mmind00> it should be ... at least I made sure in kconfig that it was enabled

13:21 <pulser> OK - it was set to "m" in your latest kernel config

13:21 <pulser> I will rebuild with it as "y", as I do not see a module made for it in my modules directory

13:22 <mmind00> pulser: yeah, I fixed that 10 minutes ago :-)

13:22 <pulser> (I assume the name would include "bq" (grep -i bq failed)

13:22 <mmind00> just need to push

13:22 <pulser> ah cool, thanks - will force enable and try that

13:22 <pulser> I'm sure I did that already, but oh well

13:34 <pulser> mmind00: battery confirmed working on 178053b (HEAD)

13:34 <pulser> thanks :)

13:35 <pulser> I shall continue to look into the mali stuff, although I am not likely to find anything (I suspect), as it's a slight blind-hunt for me :)

13:40 <mmind00> nice :-) ... I'll look too hopefully later today

13:47 <pulser> yeah - I posted the source of the errors on the dmesg, but it's going backward to the root cause that's harder

13:47 <pulser> I might find it if it's something directly linked to the error; if it's more subtle I'll not find it

19:26 <edolnx> OK, I think I have all the parts, but I'm having a heck of a time figuring out how to build an image for rkflashtool. Any pointers?

19:39 <cristian_c> edolnx: what?

19:40 <edolnx> I'm trying to build a firmware image for an RK3368 board to run debian. I have the loader, and the kernel, and the initrd. Just not understanding how to put all that together.

19:42 <cristian_c> edolnx: I suppose micro-sd card

19:42 <cristian_c> edolnx: maybe you have got too 'parameter' file

19:43 <cristian_c> *parameter file too

19:43 <edolnx> I have those

19:43 <cristian_c> you should transfer them into micro-sd, I suppose

19:44 <cristian_c> (in linux environment, by dd, for example)

19:44 <cristian_c> edolnx: you also could search in radxa rock documentation

19:48 <Danukeru> edolnx: try this > https://github.com/neo-technologies/rockchip-mkbootimg

19:51 <Danukeru> edolnx: also try > https://github.com/neo-technologies/rockchip-pack-tools

20:04 <cristian_c> ah, sorry, true, I forgot that repack with crc is needed in some cases

20:04 <cristian_c> rkcrc, f0r example

20:04 <cristian_c> -k

20:04 <cristian_c> either mkbootimg

20:36 <Xeta> Hi! Anyone where have experience installing linux on a MK 902 II box? Is it possible to write an OS image to the boxes internal harddrive from my PC?

21:53 <edolnx> Right, I'm just not understanding how the images are put together. It looks like the firmware image as another image in it with the kernel and ramdisk. Ideally I'd like to put a second stage bootloader in there so I can change out kernels more easily (read from USB,etc) but right now just putting in a kernel and initrd would be a great start

21:59 <edolnx> It looks like rockchip-mkbootimage/img_maker makes the "firmware.img" and then rockchip-mkbootimage/mkbootimage makes the boot payload that would be inside the "update.img" inside the "firmware.img"?

22:00 <edolnx> There also appear to be specific name requirements, but I'm not sure