OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

> Porting M5rc14 To Real Hardware
Mrflying
post Feb 18 2008, 07:38 PM
Post #1





Group: Members
Posts: 4
Joined: 24-January 08
Member No.: 21,256



Hi everyone:
Does anyone can help me? Thanks in advance.
I'm now working on porting m5rc14 to our platform.
I meet 2 problems:

1) when system starts, console seem almost hangs. and process
system_server
occupies 99% of CPU time.

This is my logcat:
W/AudioFlinger( 557): Using stubbed audio hardware. No sound will be
produced.
I/AudioFlinger( 557): AudioFlinger's main thread ready to run.
I/ServiceManager( 539): ServiceManager: addService(AudioFlinger,
0x133f8)
I/sysproc ( 557): System server: starting Android runtime.
I/sysproc ( 557): System server: starting Android services.
I/SystemServer( 557): Entered the Android system server!
I/sysproc ( 557): System server: entering thread pool.
D/TouchDex( 557): TouchDex parent waiting for pid=580 (timeout=36.4s)
I/ServiceManager( 539): ServiceManager: unable to find service
activity
I/runtime ( 539): Still waiting for activity manager...
I/ServiceManager( 539): ServiceManager: waiting for service activity
D/AudioFlinger( 557): Audio hardware entering standby
I/ServiceManager( 539): ServiceManager: unable to find service
activity
I/runtime ( 539): Still waiting for activity manager...
I/ServiceManager( 539): ServiceManager: waiting for service activity
I/ServiceManager( 539): ServiceManager: unable to find service
activity
I/runtime ( 539): Still waiting for activity manager...
I/ServiceManager( 539): ServiceManager: waiting for service activity
I/ServiceManager( 539): ServiceManager: unable to find service
activity
I/runtime ( 539): Still waiting for activity manager...
I/ServiceManager( 539): ServiceManager: waiting for service activity
I/ServiceManager( 539): ServiceManager: unable to find service
activity
I/runtime ( 539): Still waiting for activity manager...
I/ServiceManager( 539): ServiceManager: waiting for service activity
I/ServiceManager( 539): ServiceManager: unable to find service
activity
I/runtime ( 539): Still waiting for activity manager...
I/ServiceManager( 539): ServiceManager: waiting for service activity
I/ServiceManager( 539): ServiceManager: unable to find service
activity
I/runtime ( 539): Still waiting for activity manager...
I/ServiceManager( 539): ServiceManager: waiting for service activity
E/TouchDex( 557): timed out waiting for 580; kill(0) returns 0

It seems services don't respond to SeviceManager, it doesn't happen on
previous version

2). There's nothing appear on the screen. (screen is turned to black,
it doesn't happen on previous version, too)

m3rc37 system runs well on our platform with new released kernel.
Go to the top of the page
 
+Quote Post
 
Start new topic
Replies
speculatrix
post Feb 25 2008, 02:51 PM
Post #2





Group: Admin
Posts: 3,281
Joined: 29-July 04
From: Cambridge, England
Member No.: 4,149



very much please to have even a partial version working!!!
Go to the top of the page
 
+Quote Post
cortez
post Feb 25 2008, 11:51 PM
Post #3





Group: Members
Posts: 376
Joined: 18-March 04
From: The Netherlands
Member No.: 2,380



QUOTE(speculatrix @ Feb 25 2008, 11:51 PM) *
very much please to have even a partial version working!!!

You mean you don't even care that the screen is black all the time? tongue.gif
I've created an installable image from the new SDK. From what I see in the traces Android starts normally. It's just that there's nothing displayed...
Go to the top of the page
 
+Quote Post
speculatrix
post Feb 26 2008, 04:37 AM
Post #4





Group: Admin
Posts: 3,281
Joined: 29-July 04
From: Cambridge, England
Member No.: 4,149



QUOTE(cortez @ Feb 26 2008, 07:51 AM) *
QUOTE(speculatrix @ Feb 25 2008, 11:51 PM) *
very much please to have even a partial version working!!!

You mean you don't even care that the screen is black all the time? tongue.gif
I've created an installable image from the new SDK. From what I see in the traces Android starts normally. It's just that there's nothing displayed...


if you tap around on the screen, can you tell if something's happening by looking at debug output and any processes/threads running?
Go to the top of the page
 
+Quote Post
zaurick
post Feb 26 2008, 08:48 AM
Post #5





Group: Members
Posts: 19
Joined: 2-October 06
Member No.: 11,617



QUOTE(cortez @ Feb 26 2008, 07:51 AM) *
QUOTE(speculatrix @ Feb 25 2008, 11:51 PM) *
very much please to have even a partial version working!!!

You mean you don't even care that the screen is black all the time? tongue.gif
I've created an installable image from the new SDK. From what I see in the traces Android starts normally. It's just that there's nothing displayed...


Hi,

Have you got some IOCTL errors about /dev/fb or /dev/graphics in the debug output.
The last time i've got a black screen problem when porting an appli, it was because of the use of a double framebuffer.
The framebuffer was mmaped in ram with the size of two screens and it started with the second screen !!!
and then tried to switch the base address of the visible window with "FBIOPAN" IOCTL (don't work with our driver).
Maybe It's not our actual problem, but i have no other idea.

All of you make a great work about porting android !!!

Go to the top of the page
 
+Quote Post
cortez
post Feb 26 2008, 09:36 AM
Post #6





Group: Members
Posts: 376
Joined: 18-March 04
From: The Netherlands
Member No.: 2,380



QUOTE(zaurick @ Feb 26 2008, 05:48 PM) *
QUOTE(cortez @ Feb 26 2008, 07:51 AM) *
QUOTE(speculatrix @ Feb 25 2008, 11:51 PM) *
very much please to have even a partial version working!!!

You mean you don't even care that the screen is black all the time? tongue.gif
I've created an installable image from the new SDK. From what I see in the traces Android starts normally. It's just that there's nothing displayed...


Hi,

Have you got some IOCTL errors about /dev/fb or /dev/graphics in the debug output.
The last time i've got a black screen problem when porting an appli, it was because of the use of a double framebuffer.
The framebuffer was mmaped in ram with the size of two screens and it started with the second screen !!!
and then tried to switch the base address of the visible window with "FBIOPAN" IOCTL (don't work with our driver).
Maybe It's not our actual problem, but i have no other idea.

All of you make a great work about porting android !!!


I see no IOCTL errors of significance. All devices are created nicely when running the /init executable, including /dev/graphics/fb0. This is no double framebuffer as far as I can tell. All services start successfully (I don't see the errors as described in the first post).

The main difference between Qemu emulator and Zaurus seems to be the supported OpenGL options. From what I remember, the Zaurus doesn't support page flipping.
Go to the top of the page
 
+Quote Post

Posts in this topic
Mrflying   Porting M5rc14 To Real Hardware   Feb 18 2008, 07:38 PM
cortez   Did you create a new kernel with latest Google pat...   Feb 19 2008, 12:32 AM
jpmatrix   QUOTE(cortez @ Feb 19 2008, 09:32 AM) Did...   Feb 19 2008, 07:50 AM
Mrflying   QUOTE(cortez @ Feb 19 2008, 12:32 AM) Did...   Feb 21 2008, 07:12 PM
jpmatrix   QUOTE(Mrflying @ Feb 22 2008, 04:12 AM) Q...   Feb 22 2008, 11:35 AM
Android Zaurus   QUOTE(Mrflying @ Feb 19 2008, 12:38 PM) 2...   Feb 19 2008, 06:47 PM
Mrflying   QUOTE(Android Zaurus @ Feb 19 2008, 06:47...   Feb 21 2008, 01:15 AM
speculatrix   QUOTE(Mrflying @ Feb 21 2008, 09:15 AM) I...   Feb 21 2008, 02:57 PM
Mrflying   QUOTE(speculatrix @ Feb 21 2008, 02:57 PM...   Feb 21 2008, 07:04 PM
speculatrix   very much please to have even a partial version wo...   Feb 25 2008, 02:51 PM
cortez   QUOTE(speculatrix @ Feb 25 2008, 11:51 PM...   Feb 25 2008, 11:51 PM
speculatrix   QUOTE(cortez @ Feb 26 2008, 07:51 AM) QUO...   Feb 26 2008, 04:37 AM
zaurick   QUOTE(cortez @ Feb 26 2008, 07:51 AM) QUO...   Feb 26 2008, 08:48 AM
cortez   QUOTE(zaurick @ Feb 26 2008, 05:48 PM) QU...   Feb 26 2008, 09:36 AM
Android Zaurus   My guess for now. Let the Android use drivers/vide...   Feb 26 2008, 05:32 PM
cortez   QUOTE(Android Zaurus @ Feb 27 2008, 02:32...   Feb 27 2008, 01:40 AM
Android Zaurus   Cortez, Thanks for trying to make a module. QUOT...   Feb 27 2008, 02:39 AM
cortez   Would it be possible to make the second page (the ...   Feb 27 2008, 04:10 AM
zaurick   QUOTE(cortez @ Feb 27 2008, 01:10 PM) Wou...   Feb 27 2008, 05:29 AM
speculatrix   ask the angstrom kernel guy, (richard purdie?), he...   Feb 27 2008, 06:00 AM
cortez   I guess I need to adjust the default pxafb framebu...   Feb 27 2008, 07:43 AM
Android Zaurus   Is there anyone who is familliar with OpenEZX? htt...   Feb 27 2008, 05:01 PM
cortez   I did it, it works! The problem was the unsupp...   Feb 28 2008, 01:09 PM
matthis   >>More info later, it needs some more tweaki...   Feb 29 2008, 06:12 AM
Android Zaurus   Today I implemented my version of double buffer an...   Mar 1 2008, 11:56 PM
zaurick   QUOTE(Android Zaurus @ Mar 2 2008, 08:56 ...   Mar 2 2008, 02:36 AM
Android Zaurus   QUOTE(zaurick @ Mar 2 2008, 07:36 PM) Nor...   Mar 2 2008, 04:24 AM
matthis   is touchscreen any better in this version?   Mar 2 2008, 05:58 AM
cortez   QUOTE(matthis @ Mar 2 2008, 02:58 PM) is ...   Mar 2 2008, 12:51 PM
zaurick   QUOTE(Android Zaurus @ Mar 2 2008, 01:24 ...   Mar 2 2008, 12:46 PM
Android Zaurus   zaurick Thanks for your tips. I guess I need to c...   Mar 3 2008, 03:08 AM
zaurick   Happy to hear that the project go ahead. Could so...   Mar 3 2008, 06:02 AM
cortez   QUOTE(Android Zaurus @ Mar 2 2008, 08:56 ...   Mar 2 2008, 06:34 AM
speculatrix   I'm looking forward to being able to download ...   Mar 2 2008, 01:11 PM


Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 31st August 2014 - 02:30 AM