logo

Could not compile stylesheet for simplistic. Using last compiled stylesheet.

Android gingerbread on igepv2

posted in Uncategorized
Friday, November 04 2011, 02:07 PM
marcog
marcog
Offline
0
I\\\'m trying to run gingerbread on igepv2 using the rowboat source code. I followed the instructions on the igep forum for froyo but used gingerbread source code adding the igepv2 vendor/ti/igepv2 files... using the igep0020_android_defconfig for the kernel. After a successful building I get this error trying to run android on the igep: [...] kjournald starting. Commit interval 5 seconds EXT3-fs (mmcblk0p2): using internal journal EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode VFS: Mounted root (ext3 filesystem) on device 179:2. Freeing init memory: 176K Warning: unable to open an initial console. init: Timed out waiting for /dev/.coldboot_done init: service \\\'console\\\' requires console init: cannot find \\\'/system/etc/install-recovery.sh\\\', disabling \\\'flash_recovery\\\' init: untracked pid 532 exited init: untracked pid 533 exited init: untracked pid 541 exited init: untracked pid 540 exited init: untracked pid 585 exited request_suspend_state: wakeup (3->0) at 26835296634 (1970-01-01 00:00:26.835266117 UTC) init: untracked pid 584 exited init: untracked pid 594 exited init: untracked pid 603 exited pvrsrvkm: disagrees about version of symbol module_layout init: untracked pid 606 exited request_suspend_state: wakeup (0->0) at 33470001225 (1970-01-01 00:00:33.470001225 UTC) init: untracked pid 610 exited init: critical process \\\'servicemanager\\\' exited 4 times in 4 minutes; rebooting into recovery mode omaplfb: disagrees about version of symbol module_layout Restarting system with command \\\'recovery\\\'. and the system reboots... anyone got any info on this? Thanks in advance.
Responses (13)
  • Accepted Answer

    hedwin
    hedwin
    Offline
    Friday, November 04 2011, 03:48 PM - #permalink
    0
    What type of board are you using? Can you also add the logcat output. Hedwin
    The reply is currently minimized Show
  • Accepted Answer

    marcog
    marcog
    Offline
    Monday, November 07 2011, 05:31 PM - #permalink
    0
    I am using igepv2 board DM3730@1GHz with the expansion board attached to the igepv2 expansion board and a PH480272T-005-I11Q TFT Module - 4.3\\\" 480x272 Backlight LED. Regarding the logcat I\\\'m running adb over tcp with the init.rc modified for that purpose (I tested that before in froyo and works correctly) and logcat does not show anything. Just this: - waiting for device - For the record, prebuilt froyo version from the wiki page works properly. Please any help would be appreciated, I\\\'m kind of stuck here.
    The reply is currently minimized Show
  • Accepted Answer

    hedwin
    hedwin
    Offline
    Wednesday, November 09 2011, 09:22 AM - #permalink
    0
    Can you try a serial interface to get the logcat data. Btw I have gingerbread running on the same board. All needed updates have been posted by me and are (should be) in the rowboat repository. What I also did was use the latest x-loader (skipping u-boot).
    The reply is currently minimized Show
  • Accepted Answer

    marcog
    marcog
    Offline
    Wednesday, November 09 2011, 11:41 AM - #permalink
    0
    do you have like a clone of the main rowboat? How can I get those changes? I\\\'ve tried to get the rowboat ginger bread changes for igepv2 but I think I could have done something wrong... I\\\'m new using git...
    The reply is currently minimized Show
  • Accepted Answer

    handtems
    handtems
    Offline
    Tuesday, January 03 2012, 11:51 PM - #permalink
    0
    Hi Hedwin, We are using the same board and today, I tried to compile Android Gingerbread for it. I have tried both, uboot and direct x-loader loading as you suggested, but once the kernel is picked up and uncompressed, it hangs while displaying a distorted image of the boot logo (i.e. a couple of green robots). What I did was simply to checkout the gingerbread manifest (without dsp support) and then after running the environment setup, I ran lunch and make. Afterwards I created the rootfs and copied the uImage or zImage respectively. For the x-loader tests, I used the latest binary distribution (I think it is 2.2.0) that I got from the igep website. I played around with different settings for boot.scr and igep.ini respectively, but I guess I either have a broken kernel or I am not able to find the right settings. Since you have it running, could you please post your igep.ini settings? Thanks in advance, Marcus
    The reply is currently minimized Show
  • Accepted Answer

    hedwin
    hedwin
    Offline
    Wednesday, January 04 2012, 12:31 AM - #permalink
    0
    Did you add OMAPES=5.x when doing make?
    The reply is currently minimized Show
  • Accepted Answer

    handtems
    handtems
    Offline
    Wednesday, January 04 2012, 07:24 AM - #permalink
    0
    I am pretty sure that I did. However, I have started to rebuild Gingerbread from scratch to make sure that I did not miss it. I will post the result as soon as I am in the office. Marcus
    The reply is currently minimized Show
  • Accepted Answer

    handtems
    handtems
    Offline
    Thursday, January 05 2012, 12:12 PM - #permalink
    0
    Ok, so here is the result of yesterday: After putting the kernel in debug mode with CONFIG_DEBUG_LL and early printk I figured out that the kernel was actually booting just fine. However, I did not see any output since the rowboat gingerbread kernel detects the serial port on the igepv2 board as ttyO2 instead of ttyS2 as on froyo. The reason why I did not see more than the distorted green robots on the hdmi output was that init was continously trying to restart zygote and media which crashed immediately. As I suspected when I was asking for the igep.ini file, this was due to the kernel parameters that I was passing. In addition to configuring the output mode as described in the Froyo howto, it is also necessary to configure the video ram. Otherwise the framebuffer will not be accessible to videoflinger and zygote will crash. Just in case somebody stumbles upon this post, the following settings have worked for me: omapfb.mode=dvi:640x480MR-24 vram=64M omapfb.vram=0:32M After that, zygote will be able to access the framebuffer and stops to crash. The next problem that I ran into is the lack of libertas firmware in the gingerbread rootfs (you can see the libertas module failing by looking at the output of dmesg). I tried to copy the firmware from my froyo rootfs that I built according to the igepv2 howto (i.e. /system/etc/firmware/sd86*.bin) to the same folder on the gingerbread rootfs. Thereafter, the wifi driver stops complaining and loads it properly. However, when starting wpa_supplicant, it complains about not having a dhcpcd servic. I fixed that by renaming dhcpcd_wlan0 to dhcpcd in the init.rc script. However, the driver hooks in the firmware seem to be incompatible with gingerbread (as can be seen by looking at the nice crash-restart loop of wpa_supplicant in logcat - once you enable wifi) it is also not possible to load the froyo modules into the gingerbread kernel. Is there a way to either compile compatible modules from source or to get an updated firmware that works with gingerbread? Another thing that I noticed is that audioflinger complains about not having an alsa module. Does the builtin audio card work on your gingerbread build? Finally, it seems as if the gingerbread settings panel does not have an eth0 configuration. Is that normal or am I missing something? I assume that I can modify the framework package to take care of networking but if this has been already solved, I would prefer copying as opposed to coding. Thanks for any info on this ... Marcus PS: The good thing so far is that with gingerbread i am able to use adb over usb and bluetooth seems to work just fine.
    The reply is currently minimized Show
  • Accepted Answer

    hedwin
    hedwin
    Offline
    Thursday, January 05 2012, 02:04 PM - #permalink
    0
    Ok, so here is the result of yesterday: After putting the kernel in debug mode with CONFIG_DEBUG_LL and early printk I figured out that the kernel was actually booting just fine. However, I did not see any output since the rowboat gingerbread kernel detects the serial port on the igepv2 board as ttyO2 instead of ttyS2 as on froyo.
    Kernel version 2.6.32 uses ttyS while version 2.6.37 uses ttyO
    The reason why I did not see more than the distorted green robots on the hdmi output was that init was continously trying to restart zygote and media which crashed immediately. As I suspected when I was asking for the igep.ini file, this was due to the kernel parameters that I was passing. In addition to configuring the output mode as described in the Froyo howto, it is also necessary to configure the video ram. Otherwise the framebuffer will not be accessible to videoflinger and zygote will crash. Just in case somebody stumbles upon this post, the following settings have worked for me: omapfb.mode=dvi:640x480MR-24 vram=64M omapfb.vram=0:32M
    I\\\'m running on 1280x720 but the other values are correct. The TI propriatery graphics drivers need more memory than was the case for froyo or gingerbread (using 2.6.32 kernel)
    After that, zygote will be able to access the framebuffer and stops to crash. The next problem that I ran into is the lack of libertas firmware in the gingerbread rootfs (you can see the libertas module failing by looking at the output of dmesg). I tried to copy the firmware from my froyo rootfs that I built according to the igepv2 howto (i.e. /system/etc/firmware/sd86*.bin) to the same folder on the gingerbread rootfs. Thereafter, the wifi driver stops complaining and loads it properly. However, when starting wpa_supplicant, it complains about not having a dhcpcd servic. I fixed that by renaming dhcpcd_wlan0 to dhcpcd in the init.rc script. However, the driver hooks in the firmware seem to be incompatible with gingerbread (as can be seen by looking at the nice crash-restart loop of wpa_supplicant in logcat - once you enable wifi) it is also not possible to load the froyo modules into the gingerbread kernel. Is there a way to either compile compatible modules from source or to get an updated firmware that works with gingerbread?
    The patches/solutions to get wifi/bluetooth running are available on the rowboat mailing list. Most is also available in the rowboat repository.
    Another thing that I noticed is that audioflinger complains about not having an alsa module. Does the builtin audio card work on your gingerbread build? Finally, it seems as if the gingerbread settings panel does not have an eth0 configuration. Is that normal or am I missing something? I assume that I can modify the framework package to take care of networking but if this has been already solved, I would prefer copying as opposed to coding.
    This is correct. Past honeycomb android releases do not have a solution for ethernet. Some changes where made in the android-x86 project but these tent to conflict with wifi. All changes/patches I made for gingerbread on igep are published in the rowboat mailing list. See [url=http://code.google.com/p/rowboat/]http://code.google.com/p/rowboat/[/url] to get access to the mailing list. Glad you got it working in the end. Cheers Hedwin
    The reply is currently minimized Show
  • Accepted Answer

    handtems
    handtems
    Offline
    Thursday, January 05 2012, 02:43 PM - #permalink
    0
    I am acutally quite sure that I have the most recent version of your patches. Before starting to work on gingerbread, I checked that my tree included everything from your publicly visible branches on gitorious. Could you point me to the post in the mailing list that you are referring to? I went through all the posts that have \\\"hedwin\\\" and \\\"firmware\\\" or \\\"wifi\\\" in them but they are either already included in my build or they are for froyo. I also ran a diff on the firmware files that you had posted in the rowboat forum but they do not seem to be different. Thanks in advance. Marcus
    The reply is currently minimized Show
  • Accepted Answer

    hedwin
    hedwin
    Offline
    Thursday, January 05 2012, 03:58 PM - #permalink
    0
    Some might still be in the mailing list though.
    The reply is currently minimized Show
  • Accepted Answer

    handtems
    handtems
    Offline
    Thursday, January 05 2012, 08:05 PM - #permalink
    0
    When you say \\\"might\\\" does that mean you know or you don\\\'t?
    The reply is currently minimized Show
  • Accepted Answer

    hedwin
    hedwin
    Offline
    Thursday, January 05 2012, 10:58 PM - #permalink
    0
    What I tried to say is the patches are in the mailing list but these might not all be added to the rowboat repository. Sorry about the confusion
    The reply is currently minimized Show
Your Reply

SUPPORT


This email address is being protected from spambots. You need JavaScript enabled to view it.
This email address is being protected from spambots. You need JavaScript enabled to view it.
IGEP Community Wiki
IGEP Community Forum
IGEP Community Online Chat