RK3188 Source Code Compilation for MK908 - Question.

[hoabycsr]

It seems that people are getting the source to build and run on their sticks, t428´s and others that are similar to that. I´ve noticed that alot of roms are cross-compatible between alot of these 3188 sticks, but the mk908 seems to be the odd one out. I´m not talking about wireless/bluetooth functionality or anything like that, just getting the android kernel to boot my mk908. I´ve tried switching video output to the 0 port in the menuconfig rather than port 1 which is the default.. I know the mk808b differs in that way compared to many other rk3066 sticks (sort of in reverse though.)

I´ve played with a plethora of options in the make config, trying different box types for instance. Some will compile and not boot and some will not even compile. I´m using arm-linux-gnueabihf- for my CROSS_COMPILE variable. If anyone can point me in the right direction for this stick, I´d be very grateful. Also I´m curious how big my kernel can be if I don´t want to change any paramater options in a finless rom... Wondering if it might just be too big at the moment.

Thanks in advance.

Hoaby

[hoabycsr]

Ok I managed to make a kernel that boots on the mk908. The problem that seems to persist is that it will boot once after flashing, reboot as many times as I like through the reboot app, but when I power it off physically and plug it back in, it just sits there with the light off and I get no video. The PC, however, seems to detect the device because I´m powering it through the otg port so I believe some part of it is booting...

Any suggestions?

[leolas]

Re: RK3188 Source Code Compilation for MK908 - Question.

Ok I managed to make a kernel that boots on the mk908. The problem that seems to persist is that it will boot once after flashing, reboot as many times as I like through the reboot app, but when I power it off physically and plug it back in, it just sits there with the light off and I get no video. The PC, however, seems to detect the device because I´m powering it through the otg port so I believe some part of it is booting...

Any suggestions?

I will start to play with the new sources today, but all i can say is patiece, try to keep note of all importants chips in your stick, the original dmesg has some useful info too, and try and try.

leolas

[hoabycsr]

Here´s how far I´ve gotten. Wifi works, bluetooth works, rom is snappy and has not much video lag but it´s still there. Still running into the problem where I power off the stick and it doesn´t boot again till I flash at least the kernel and boot images to the stick again... After the recovery thing does it´s formatting it will boot the rom but power it off and it´s toast. I feel that I need to resolve this before I really delve into video skip issues.

Notice in this screenshot that both wifi and bluetooth are functional and connected.

http://www.hoaby.com/android/Screenshot.png

[leolas]

Re: RK3188 Source Code Compilation for MK908 - Question.

Here´s how far I´ve gotten. Wifi works, bluetooth works, rom is snappy and has not much video lag but it´s still there. Still running into the problem where I power off the stick and it doesn´t boot again till I flash at least the kernel and boot images to the stick again... After the recovery thing does it´s formatting it will boot the rom but power it off and it´s toast. I feel that I need to resolve this before I really delve into video skip issues.

Notice in this screenshot that both wifi and bluetooth are functional and connected.

http://www.hoaby.com/android/Screenshot.png

Good, i have wifi working but no bt in qx1.
Which is your base rom? Maybe the problem is not in the kernel you compiled. Maybe the problem is in the rom, dmesg can help to see what is happend.

leolas

[hoabycsr]

Good, i have wifi working but no bt in qx1.
Which is your base rom? Maybe the problem is not in the kernel you compiled. Maybe the problem is in the rom, dmesg can help to see what is happend.

leolas

I thought about that.. I´ve tried it with bobś t428 alpha 1.6 rom (because I like the UI and itś 4.1.1) and just for giggles I also tried it with bobś mk908 4.2.2 official 1.5.

I sadly do not know how to utilize dmesg. I think I could get at it through adb but have no idea what I´d be looking for.

[JugsteR]

Re: RK3188 Source Code Compilation for MK908 - Question.

I know we're not quite there yet, but has anyone tried booting anything compiled with the linaro tool chain? I've managed to compile it successfully but I have not yet got any hardware to test it on.

It is does make some other android devices a bit snappier.

I put a link to the tool chain on the Rico magic forums, if you can't convince Google to give you the link.

Signature? Signature!

[leolas]

I thought about that.. I´ve tried it with bobś t428 alpha 1.6 rom (because I like the UI and itś 4.1.1) and just for giggles I also tried it with bobś mk908 4.2.2 official 1.5.

I sadly do not know how to utilize dmesg. I think I could get at it through adb but have no idea what I´d be looking for.

Use terminal emulator or adb to acces to the console then write:

su
dmesg>/sdcard/dmesg.txt

Then in the root of your sdcard you will have a file called dmesg.txt, in this file you can see the boot&init procces, and if you compare it with the stock one you can see what is wrong in some situations. If you want to upload both dmesg i will try to look at them and see if we can find where is the fail part.

leolas

[hoabycsr]

OK Thank you very much and here you go.

http://www.hoaby.com/android/dmesg1.txt - stock rom/kernel

http://www.hoaby.com/android/dmesg2.txt - stock rom/custom kernel while video is working

http://www.hoaby.com/android/dmesg3.txt - stock rom/custom kernel from cold boot


Iḿ noticing those i2c errors... but guessing that´s not my boot issue. It really just won´t kick the screen on but it works...

[leolas]

OK Thank you very much and here you go.

http://www.hoaby.com/android/dmesg1.txt - stock rom/kernel

http://www.hoaby.com/android/dmesg2.txt - stock rom/custom kernel while video is working

http://www.hoaby.com/android/dmesg3.txt - stock rom/custom kernel from cold boot


Iḿ noticing those i2c errors... but guessing that´s not my boot issue. It really just won´t kick the screen on but it works...

I am going to study that dmesg files, i will answer you soon.

PS: Ok your stock kernel, I dont know how it works
There are multiple fails to get the gpios and ic2 bus, your custom kernel is cleaner than the stock :P. It don't have the proper PMU configured (Power management unit)
Please, if you can, open the case of your stick and look for all microchips that are in it, do it carefully with the antenna, cause you can broke it. and look for a small chip in it, those sticks must have some chips:
NAND: Big chip, is the internal storage, dont needed to make a kernel.
RAM: Some bigs chips too, It can be usefull to know how your ram can be overclocked, but for a basic kernel work, it is not needed.
CPU: the biggest one, is down of the heat disipator, dont worry about it, we know it must be rk3188.
WIFI: In your stick it is ap6210 I think it has wifi and BT in the same chip.
BT:some devices have the BT out of the wifi chipset like in my qx1, yours must be inside your wifi chip so dont worry about it.
HDMI&SOUND: Some sticks have additional chips to control sound over hdmi, or sound, rk1000 or rk610 are usually used in this sticks.
PMU: (Power Management Unit)A small chip. Very important to make your kernel work properly, It controls the GPIO SDIO and I2C bus, some devices (like my mk808b) don't have it and have fixed regulators, if it is your situation bad (like in my mk808b, I cant make a full custom kernel for it). Please look in your stick board if you find this chip, some usual used chips for it are: act8846(QX1,mk802IV, and some more);65910, etc..

Are you using the stock rom that was in your device from factory? Or an update?

[sam321]

hoabycsr sent me his config and I modified it so it hopefully works, I think some of the hdmi settings were wrong and that is why it only worked through recovery as there is a kernel in there and I think it was configuring the display, but once rebooted the configuration was gone

[leolas]

hoabycsr sent me his config and I modified it so it hopefully works, I think some of the hdmi settings were wrong and that is why it only worked through recovery as there is a kernel in there and I think it was configuring the display, but once rebooted the configuration was gone

Yes i noticed that he use lcdc0 instead of lcdc1 like we use, but his dmesg and his stock dmesg are full of bad msg about i2c, the regulator, it his device has it is miss-configured.

[hoabycsr]

For my device it is lcd0. And yes, if i did an adb reboot after powering it up in recovery mode i would get video.

[sam321]

hoabycsr I can guarantee that config I sent you works on my stick excluding the wifi and bluetooth. I have changed more than just the lcdc1. However if you get no display output change it back to lcd0

[hoabycsr]

hoabycsr I can guarantee that config I sent you works on my stick excluding the wifi and bluetooth. I have changed more than just the lcdc1. However if you get no display output change it back to lcd0

I am using MK908 stick. I tried making that change only, and got through compilation but compile errors came up about some of the display support. Once flashed it wouldn´t give me screen. It booted, though - gave me usb storage eventually. I manually made some changes to source files to correct for lcd0 support and got less errors. Still having power up issues but Iḿ beginning to think that´s in the power management...


I have an idea I´m going to try quick.