* Support for the Android emulator using the msm8960 device build
@ 2012-02-04 0:28 Merrill, William M.
2012-02-04 7:56 ` David Brown
0 siblings, 1 reply; 8+ messages in thread
From: Merrill, William M. @ 2012-02-04 0:28 UTC (permalink / raw
To: linux-arm-msm
Hello,
I am attempting to test out AOSP package, trimmed for an embedded device
using intended to run on the MSM8960. Prior to having hardware I would
like to test the Android code base using the Android emulator and
running with the prebuilt kernel included in the code aurora source
package. Now prior to making any changes to the default AOSP target
(using the 8960 manifest) I wanted to test running the emulator without
a display. However, once I build the msm8960 target, and run this with
the prebuilt qemu kernel, adb logcat displays an endless loop as the
JNI_CreateJavaVM fails. I believe this is the correct mailing list to
post this question, but please let me know if I am mistaken.
My question is if there is support for running the Android emulator
using the stock code aurora distribution built for the 8960? Any
suggestions are appreciated, I have searched Google, the AOSP source,
and mailing list without success yet for identifying a solution to my
problem.
The steps I have run are:
1) Using the M8960AAAAANLYA1021.xml manifest build the full AOSP target
. build/envsetup.sh
choosecombo 1 2 msm8960 3
m
2) Run the emulator using the prebuilt qemu armv7 kernel instead of the
kernel built with the code aurora:
emulator -verbose -no-window -kernel
prebuilt/android-arm/kernel/kernel-qemu-armv7
3) Connect to the running emulator instance, first confirm shell access
adb shell
#
4) Monitor status using logcat:
adb logcat
5) The result is a continuous loop of:
I/DEBUG ( 30): *** *** *** *** *** *** *** *** *** *** *** *** ***
*** *** ***
I/DEBUG ( 30): Build fingerprint:
'qcom/msm8960core/msm8960:2.3.5/GRJ90/eng.merrillw.20120203.163348:eng/d
ebug,test-keys'
I/DEBUG ( 30): pid: 5441, tid: 5441 >>> /system/bin/dexopt <<<
I/DEBUG ( 30): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr
deadd00d
I/DEBUG ( 30): r0 fffffe84 r1 deadd00d r2 00000026 r3 00000000
I/DEBUG ( 30): r4 aca9759c r5 aca8132a r6 00000000 r7 aca8132a
I/DEBUG ( 30): r8 00000000 r9 00000000 10 415ad028 fp 00005160
I/DEBUG ( 30): ip aca976a8 sp be9e3a40 lr afd192b9 pc aca3dad4
cpsr 20000030
I/DEBUG ( 30): d0 6472656767756265 d1 6f727245646e756e
I/DEBUG ( 30): d2 756f466665447367 d3 3b726f727245640a
I/DEBUG ( 30): d4 6172662f6d657473 d5 732f6b726f77656d
I/DEBUG ( 30): d6 2e73656369767265 d7 7379732f3a72616a
I/DEBUG ( 30): d8 0000000000000000 d9 0000000000000000
I/DEBUG ( 30): d10 0000000000000000 d11 0000000000000000
I/DEBUG ( 30): d12 0000000000000000 d13 0000000000000000
I/DEBUG ( 30): d14 0000000000000000 d15 0000000000000000
I/DEBUG ( 30): d16 0000000000000000 d17 0000000000000000
I/DEBUG ( 30): d18 0000000000000000 d19 0000000000000000
I/DEBUG ( 30): d20 0000000000000000 d21 0000000000000000
I/DEBUG ( 30): d22 0000000000000000 d23 0000000000000000
I/DEBUG ( 30): d24 0000000000000000 d25 0000000000000000
I/DEBUG ( 30): d26 0000000000000000 d27 0000000000000000
I/DEBUG ( 30): d28 0000000000000000 d29 0000000000000000
I/DEBUG ( 30): d30 0000000000000000 d31 0000000000000000
I/DEBUG ( 30): scr 00000000
I/DEBUG ( 30):
I/DEBUG ( 30): #00 pc 0003dad4 /system/lib/libdvm.so
I/DEBUG ( 30): #01 pc 0003d262 /system/lib/libdvm.so
I/DEBUG ( 30): #02 pc 0003d2c4 /system/lib/libdvm.so
I/DEBUG ( 30): #03 pc 00061296 /system/lib/libdvm.so
I/DEBUG ( 30): #04 pc 000614e2 /system/lib/libdvm.so
I/DEBUG ( 30): #05 pc 000614fa /system/lib/libdvm.so
I/DEBUG ( 30): #06 pc 0003d268 /system/lib/libdvm.so
I/DEBUG ( 30): #07 pc 0003d2c4 /system/lib/libdvm.so
I/DEBUG ( 30): #08 pc 00061296 /system/lib/libdvm.so
I/DEBUG ( 30): #09 pc 000614e2 /system/lib/libdvm.so
I/DEBUG ( 30): #10 pc 000614fa /system/lib/libdvm.so
I/DEBUG ( 30): #11 pc 000527c0 /system/lib/libdvm.so
I/DEBUG ( 30): #12 pc 00052a16 /system/lib/libdvm.so
I/DEBUG ( 30): #13 pc 00052c14 /system/lib/libdvm.so
I/DEBUG ( 30): #14 pc 0000902a /system/bin/dexopt
I/DEBUG ( 30): #15 pc 000091e4 /system/bin/dexopt
I/DEBUG ( 30): #16 pc 00014c36 /system/lib/libc.so
I/DEBUG ( 30):
I/DEBUG ( 30): code around pc:
I/DEBUG ( 30): aca3dab4 447a4479 f7d34c0b 2000ed50 ee54f7d3
I/DEBUG ( 30): aca3dac4 447c4809 6bdb5823 4798b103 22264902
I/DEBUG ( 30): aca3dad4 f7d3700a bf00eebc deadd00d 00040f38
I/DEBUG ( 30): aca3dae4 0004273d 00059ad2 fffffe84 4b09b40e
I/DEBUG ( 30): aca3daf4 4c09b517 aa05447b f852591b 6b5b1b04
I/DEBUG ( 30):
I/DEBUG ( 30): code around lr:
I/DEBUG ( 30): afd19298 4a0e4b0d e92d447b 589c41f0 26004680
I/DEBUG ( 30): afd192a8 686768a5 f9b5e006 b113300c 47c04628
I/DEBUG ( 30): afd192b8 35544306 37fff117 6824d5f5 d1ef2c00
I/DEBUG ( 30): afd192c8 e8bd4630 bf0081f0 00028288 ffffff84
I/DEBUG ( 30): afd192d8 b086b570 f602fb01 9004460c a804a901
I/DEBUG ( 30):
I/DEBUG ( 30): stack:
I/DEBUG ( 30): be9e3a00 00000000
I/DEBUG ( 30): be9e3a04 aca78285 /system/lib/libdvm.so
I/DEBUG ( 30): be9e3a08 fffffffc
I/DEBUG ( 30): be9e3a0c 0000ffff
I/DEBUG ( 30): be9e3a10 afd4272c
I/DEBUG ( 30): be9e3a14 afd426d8
I/DEBUG ( 30): be9e3a18 00000000
I/DEBUG ( 30): be9e3a1c afd192b9 /system/lib/libc.so
I/DEBUG ( 30): be9e3a20 00059ad2
I/DEBUG ( 30): be9e3a24 aca8132a /system/lib/libdvm.so
I/DEBUG ( 30): be9e3a28 00000000
I/DEBUG ( 30): be9e3a2c aca8132a /system/lib/libdvm.so
I/DEBUG ( 30): be9e3a30 00000000
I/DEBUG ( 30): be9e3a34 afd183b1 /system/lib/libc.so
I/DEBUG ( 30): be9e3a38 df002777
I/DEBUG ( 30): be9e3a3c e3a070ad
I/DEBUG ( 30): #00 be9e3a40 00018570
I/DEBUG ( 30): be9e3a44 aca3d267 /system/lib/libdvm.so
I/DEBUG ( 30): #01 be9e3a48 00018570
I/DEBUG ( 30): be9e3a4c 00018570
I/DEBUG ( 30): be9e3a50 00018570
I/DEBUG ( 30): be9e3a54 aca8132a /system/lib/libdvm.so
I/DEBUG ( 30): be9e3a58 00000000
I/DEBUG ( 30): be9e3a5c aca3d2c9 /system/lib/libdvm.so
W/dalvikvm( 5434): DexOpt: --- END 'core-junit.jar' --- status=0x000b,
process failed
E/dalvikvm( 5434): Unable to extract+optimize DEX from
'/system/framework/core-junit.jar'
E/dalvikvm( 5434): No valid entries found in bootclasspath
'/system/framework/core.jar:/system/framework/bouncycastle.jar:/system/f
ramework/ext.jar:/system/framework/framework.jar:/system/framework/andro
id.policy.jar:/system/framework/services.jar:/system/framework/core-juni
t.jar'
W/dalvikvm( 5434): JNI_CreateJavaVM failed
E/AndroidRuntime( 5434): JNI_CreateJavaVM failed
E/dalvikvm( 5447): ERROR: bad checksum (89bf37fd, expected ca93277d)
E/dalvikvm( 5447): ERROR: Byte swap + verify failed
E/dalvikvm( 5447): Optimization failed
W/dalvikvm( 5446): DexOpt: --- END 'core.jar' --- status=0xff00, process
failed
E/dalvikvm( 5446): Unable to extract+optimize DEX from
'/system/framework/core.jar'
E/dalvikvm( 5448): ERROR: bad checksum (35868349, expected 75cb8252)
E/dalvikvm( 5448): ERROR: Byte swap + verify failed
E/dalvikvm( 5448): Optimization failed
W/dalvikvm( 5446): DexOpt: --- END 'bouncycastle.jar' --- status=0xff00,
process failed
E/dalvikvm( 5446): Unable to extract+optimize DEX from
'/system/framework/bouncycastle.jar'
E/dalvikvm( 5449): ERROR: bad checksum (82a90104, expected e2871ae9)
E/dalvikvm( 5449): ERROR: Byte swap + verify failed
E/dalvikvm( 5449): Optimization failed
W/dalvikvm( 5446): DexOpt: --- END 'ext.jar' --- status=0xff00, process
failed
E/dalvikvm( 5446): Unable to extract+optimize DEX from
'/system/framework/ext.jar'
E/dalvikvm( 5450): ERROR: bad checksum (f3c8afc6, expected cfc3a253)
E/dalvikvm( 5450): ERROR: Byte swap + verify failed
E/dalvikvm( 5450): Optimization failed
W/dalvikvm( 5446): DexOpt: --- END 'framework.jar' --- status=0xff00,
process failed
E/dalvikvm( 5446): Unable to extract+optimize DEX from
'/system/framework/framework.jar'
E/dalvikvm( 5452): ERROR: bad checksum (2c9eacb1, expected 2c43861b)
E/dalvikvm( 5452): ERROR: Byte swap + verify failed
E/dalvikvm( 5452): Optimization failed
W/dalvikvm( 5446): DexOpt: --- END 'android.policy.jar' ---
status=0xff00, process failed
E/dalvikvm( 5446): Unable to extract+optimize DEX from
'/system/framework/android.policy.jar'
E/dalvikvm( 5453): ERROR: bad checksum (8cda2a70, expected e4068d1e)
E/dalvikvm( 5453): ERROR: Byte swap + verify failed
E/dalvikvm( 5453): Optimization failed
W/dalvikvm( 5446): DexOpt: --- END 'services.jar' --- status=0xff00,
process failed
E/dalvikvm( 5446): Unable to extract+optimize DEX from
'/system/framework/services.jar'
E/dalvikvm( 5454): Too many exceptions during init (failed on
'Ljava/lang/NoClassDefFoundError;' 'java.lang.NoClassDefFoundError')
E/dalvikvm( 5454): VM aborting
Sincerely,
Billy
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Support for the Android emulator using the msm8960 device build
2012-02-04 0:28 Support for the Android emulator using the msm8960 device build Merrill, William M.
@ 2012-02-04 7:56 ` David Brown
2012-02-04 8:42 ` cee kvish
2012-02-04 16:43 ` Merrill, William M.
0 siblings, 2 replies; 8+ messages in thread
From: David Brown @ 2012-02-04 7:56 UTC (permalink / raw
To: Merrill, William M.; +Cc: linux-arm-msm
On Fri, Feb 03, 2012 at 07:28:45PM -0500, Merrill, William M. wrote:
> My question is if there is support for running the Android emulator
> using the stock code aurora distribution built for the 8960? Any
I'm not aware of any support for any real MSM devices. The emulator
is for a special ARM target called "goldfish" specifically made for
the emulator.
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Support for the Android emulator using the msm8960 device build
2012-02-04 7:56 ` David Brown
@ 2012-02-04 8:42 ` cee kvish
2012-02-04 16:53 ` Merrill, William M.
2012-02-04 16:43 ` Merrill, William M.
1 sibling, 1 reply; 8+ messages in thread
From: cee kvish @ 2012-02-04 8:42 UTC (permalink / raw
To: linux-arm-msm
Hi,
Why do you want to run emulator with real devices?
Cee
Thanks
2012/2/4 David Brown <davidb@codeaurora.org>
>
> On Fri, Feb 03, 2012 at 07:28:45PM -0500, Merrill, William M. wrote:
>
> > My question is if there is support for running the Android emulator
> > using the stock code aurora distribution built for the 8960? Any
>
> I'm not aware of any support for any real MSM devices. The emulator
> is for a special ARM target called "goldfish" specifically made for
> the emulator.
>
> David
>
> --
> Sent by an employee of the Qualcomm Innovation Center, Inc.
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 8+ messages in thread
* RE: Support for the Android emulator using the msm8960 device build
2012-02-04 7:56 ` David Brown
2012-02-04 8:42 ` cee kvish
@ 2012-02-04 16:43 ` Merrill, William M.
2012-02-05 0:51 ` David Brown
2012-02-05 3:47 ` David Brown
1 sibling, 2 replies; 8+ messages in thread
From: Merrill, William M. @ 2012-02-04 16:43 UTC (permalink / raw
To: David Brown; +Cc: linux-arm-msm
Thanks David,
I understand the goldfish target is a distinct target in the build
environment that allows you to build the complete AOSP including the
kernel for the emulator. However I thought the qemu basis of the
emulator allows any device AOSP build to be run against a goldfish
kernel.
As I understand it you can build for real devices, then run components
(except for the kernel) using the prebuilt kernel. While there is a
goldfish target to build the emulator, you can run the emulator. What I
would like to do is run the device specified build on the emulator. I
have done this using different code bases (the cyanogenmod) but have not
yet been able to do this with code aurora's.
Thanks for your response.
Sincerely,
Billy
-----Original Message-----
From: linux-arm-msm-owner@vger.kernel.org
[mailto:linux-arm-msm-owner@vger.kernel.org] On Behalf Of David Brown
Sent: Friday, February 03, 2012 11:56 PM
To: Merrill, William M.
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: Support for the Android emulator using the msm8960 device
build
On Fri, Feb 03, 2012 at 07:28:45PM -0500, Merrill, William M. wrote:
> My question is if there is support for running the Android emulator
> using the stock code aurora distribution built for the 8960? Any
I'm not aware of any support for any real MSM devices. The emulator is
for a special ARM target called "goldfish" specifically made for the
emulator.
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum.
--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm"
in the body of a message to majordomo@vger.kernel.org More majordomo
info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 8+ messages in thread
* RE: Support for the Android emulator using the msm8960 device build
2012-02-04 8:42 ` cee kvish
@ 2012-02-04 16:53 ` Merrill, William M.
0 siblings, 0 replies; 8+ messages in thread
From: Merrill, William M. @ 2012-02-04 16:53 UTC (permalink / raw
To: cee kvish, linux-arm-msm
Hi Cee,
I want to modify a device specific build, to run on the emulator prior to having a device to test with. Since I am looking at an embedded target I am in the process of taking out components of the AOSP including system components running in Dalvek as well as adding in underlying Linux services. However I do not have a hardware target yet (due to availability of the msm8960).
As I understand it to run a device specific build in the emulator you need to direct the emulator to the kernel to using the prebuilt qemu kernel (or a kernel built with the goldfish target). This allows you to run the specific ~/out/ files built using the build system with the specific target.
Thanks for you your response. I am still learning what the emulator supports, so would appreciate any suggestions or feedback.
Sincerely,
Billy
-----Original Message-----
From: linux-arm-msm-owner@vger.kernel.org [mailto:linux-arm-msm-owner@vger.kernel.org] On Behalf Of cee kvish
Sent: Saturday, February 04, 2012 12:42 AM
To: linux-arm-msm@vger.kernel.org
Subject: Re: Support for the Android emulator using the msm8960 device build
Hi,
Why do you want to run emulator with real devices?
Cee
Thanks
2012/2/4 David Brown <davidb@codeaurora.org>
>
> On Fri, Feb 03, 2012 at 07:28:45PM -0500, Merrill, William M. wrote:
>
> > My question is if there is support for running the Android emulator
> > using the stock code aurora distribution built for the 8960? Any
>
> I'm not aware of any support for any real MSM devices. The emulator
> is for a special ARM target called "goldfish" specifically made for
> the emulator.
>
> David
>
> --
> Sent by an employee of the Qualcomm Innovation Center, Inc.
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-arm-msm" in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Support for the Android emulator using the msm8960 device build
2012-02-04 16:43 ` Merrill, William M.
@ 2012-02-05 0:51 ` David Brown
2012-02-05 3:47 ` David Brown
1 sibling, 0 replies; 8+ messages in thread
From: David Brown @ 2012-02-05 0:51 UTC (permalink / raw
To: Merrill, William M.; +Cc: linux-arm-msm
On Sat, Feb 04, 2012 at 11:43:41AM -0500, Merrill, William M. wrote:
> I understand the goldfish target is a distinct target in the build
> environment that allows you to build the complete AOSP including the
> kernel for the emulator. However I thought the qemu basis of the
> emulator allows any device AOSP build to be run against a goldfish
> kernel.
>
> As I understand it you can build for real devices, then run components
> (except for the kernel) using the prebuilt kernel. While there is a
> goldfish target to build the emulator, you can run the emulator. What I
> would like to do is run the device specified build on the emulator. I
> have done this using different code bases (the cyanogenmod) but have not
> yet been able to do this with code aurora's.
The issue is that qemu would have to have code written for it to
emulate the hardware of the specific SoC you wish to use. There is
support for a couple of real devices in qemu, but I don't believe any
MSM devices are in there.
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Support for the Android emulator using the msm8960 device build
2012-02-04 16:43 ` Merrill, William M.
2012-02-05 0:51 ` David Brown
@ 2012-02-05 3:47 ` David Brown
2012-02-05 18:18 ` Merrill, William M.
1 sibling, 1 reply; 8+ messages in thread
From: David Brown @ 2012-02-05 3:47 UTC (permalink / raw
To: Merrill, William M.; +Cc: linux-arm-msm
On Sat, Feb 04, 2012 at 11:43:41AM -0500, Merrill, William M. wrote:
> Thanks David,
>
> I understand the goldfish target is a distinct target in the build
> environment that allows you to build the complete AOSP including the
> kernel for the emulator. However I thought the qemu basis of the
> emulator allows any device AOSP build to be run against a goldfish
> kernel.
>
> As I understand it you can build for real devices, then run components
> (except for the kernel) using the prebuilt kernel. While there is a
> goldfish target to build the emulator, you can run the emulator. What I
> would like to do is run the device specified build on the emulator. I
> have done this using different code bases (the cyanogenmod) but have not
> yet been able to do this with code aurora's.
Ah, I understand, I think.
The CodeAurora tree appears to not have the goldfish support in it
(it's a separate branch in Google's tree). It shouldn't be too hard
to make the tree just use a specific kernel image rather than building
on. There are some commits by David 'Digit' Turner in the ICS
mentioning 'atree'. It mentions a -kernel
prebuilt/android-arm/kernel-qemu-armv7 option. I'm not sure how to
use it, since I don't really do much outside of the kernel.
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
^ permalink raw reply [flat|nested] 8+ messages in thread
* RE: Support for the Android emulator using the msm8960 device build
2012-02-05 3:47 ` David Brown
@ 2012-02-05 18:18 ` Merrill, William M.
0 siblings, 0 replies; 8+ messages in thread
From: Merrill, William M. @ 2012-02-05 18:18 UTC (permalink / raw
To: David Brown; +Cc: linux-arm-msm
Hi David,
I will take a look at the commits you mention, thanks for the feedback.
Sincerely,
Bily
-----Original Message-----
From: David Brown [mailto:davidb@codeaurora.org]
Sent: Saturday, February 04, 2012 7:48 PM
To: Merrill, William M.
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: Support for the Android emulator using the msm8960 device
build
On Sat, Feb 04, 2012 at 11:43:41AM -0500, Merrill, William M. wrote:
> Thanks David,
>
> I understand the goldfish target is a distinct target in the build
> environment that allows you to build the complete AOSP including the
> kernel for the emulator. However I thought the qemu basis of the
> emulator allows any device AOSP build to be run against a goldfish
> kernel.
>
> As I understand it you can build for real devices, then run components
> (except for the kernel) using the prebuilt kernel. While there is a
> goldfish target to build the emulator, you can run the emulator. What
> I would like to do is run the device specified build on the emulator.
> I have done this using different code bases (the cyanogenmod) but have
> not yet been able to do this with code aurora's.
Ah, I understand, I think.
The CodeAurora tree appears to not have the goldfish support in it (it's
a separate branch in Google's tree). It shouldn't be too hard to make
the tree just use a specific kernel image rather than building on.
There are some commits by David 'Digit' Turner in the ICS mentioning
'atree'. It mentions a -kernel
prebuilt/android-arm/kernel-qemu-armv7 option. I'm not sure how to use
it, since I don't really do much outside of the kernel.
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum.
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2012-02-05 18:19 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-02-04 0:28 Support for the Android emulator using the msm8960 device build Merrill, William M.
2012-02-04 7:56 ` David Brown
2012-02-04 8:42 ` cee kvish
2012-02-04 16:53 ` Merrill, William M.
2012-02-04 16:43 ` Merrill, William M.
2012-02-05 0:51 ` David Brown
2012-02-05 3:47 ` David Brown
2012-02-05 18:18 ` Merrill, William M.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.