ARM64 emulator - device offline

1,408 views
Skip to first unread message

Serban Constantinescu

unread,
Mar 5, 2015, 1:00:38 PM3/5/15
to android-em...@googlegroups.com
Hi all,

I am trying to use ADB with the upstream ARM64 emulator (aosp/master) and I get the following message:

$adb devices 

List of devices attached 

emulator-5554 offline


$adb shell

error: device offline


The other emulators (arm, x86) do not report the error message mentioned above.

Could there be anything missing in my environment that the ARM64 emulator needs?


Cheers,

Serban Constantinescu 

Miodrag Dinic

unread,
Mar 9, 2015, 6:13:44 AM3/9/15
to android-em...@googlegroups.com
Hi Serban,

you probably figured it by yourself by now, but you were probably trying to run the emulator built from scratch using the prebuilt kernel image (or the other way around), but you need to have both of those in sync because of the change to the
Android Pipe device/driver :

https://android-review.googlesource.com/#/c/128280/

So just rebuild both qemu & kernel and you should be fine.

Regards,
Miodrag

timor....@gmail.com

unread,
Dec 8, 2015, 12:16:56 PM12/8/15
to Android emulator development
Hi Miodrag, Serbian
Sorry for old thread.

I seem to be facing the same issue with recent aosp master branch.
> So just rebuild both qemu & kernel and you should be fine.


Any pointers on how to "rebuild qemu & kernel"?
Do you mean the emulator with qemu support or host system qemu/kvm hypervisor?

I was not able to find documentation on getting the emulator to re-compile during the android image build..

Miodrag Dinic

unread,
Dec 9, 2015, 5:06:12 AM12/9/15
to Android emulator development, timor....@gmail.com
Hi Timor,

yeah this an old thread :). Here is the current valid procedure which I use :

# Building the AOSP
mkdir aosp && cd aosp
repo sync

# This is building procedure for mips32
source build/envsetup.sh
lunch aosp_mips-eng && nice make -j<N>


# Building the kernel

NOTE:

Kernel code is managed on several branches for different architectures:

Goldfish emulators : android-goldfish-3.4 : ARM, MIPS32, x86
Ranchu emulators : android-goldfish-3.10 : ARM64, MIPS64, x86_64

# mips32 example :
git checkout remotes/origin/android-goldfish-3.4 -b android-goldfish-3.4

#Use the script from android for building
<AOSP_DIR>/prebuilts/qemu-kernel/build-kernel.sh --arch=mips

---------------------------------------------------

# Get the emulator sources
mkdir emu-master-dev && cd emu-master-dev
repo init -u https://android.googlesource.com/platform/manifest -b emu-master-dev
repo sync

# Build the emulators
cd external/qemu
./android-rebuild.sh

# Lunch appropriate combo to export necessary variables for the emulator to pick up
cd <AOSP_DIR>
source build/envsetup.sh
lunch aosp_mips-eng

cd <EMU_MASTER_DEV>/external/qemu

# Run the freshly built emulators
# Prerequisite is that you have already built the lunched combo (mips32)
./objs/emulator -show-kernel -gpu on -kernel 
/tmp/kernel-qemu/mips-3.4/kernel-qemu

Hope this helps.
Reply all
Reply to author
Forward
0 new messages