Open RaviBeagle opened 3 years ago
I see the traces you left around the net while you were looking for information on how to emulate android on the jetson nano. I think that you have a bad habit. You are not open to collaborate. Maybe you want all the credit if u will have success. I'm not like you. In order to obtain the result, I am willing to join forces. You can think about how much energy and knowledge are needed to someone who wants to work alone and that don't have the proper knowledge. I really hate this kind of behavior.
Well, not always actually. I do look a lot to community and experts for help. But not before trying out on my own to work out solution if its within my knowledge. In any case, I am taking small steps to work around chromiumos build. Let me see how it goes.. I am willing to share whatever i know.. :)
aren't u satisfied by android antmicro ? is it working well ? are u able to grab the connection while it is running ?
No yet able to run. There are some issues with display. Will be checked later when I do a clean install to sdcard
I’ve installed this version of qemu :
root@zi-desktop:/home/zi/Desktop/Work/I9/Android/Antmicro# qemu-system-aarch64 --version QEMU emulator version 6.0.50 (v6.0.0-1145-g7258034ab4)
and the antmicro android does not boot anymore on the jetson nano. It works only with qemu-system-aarch64 vers. 5.0 dirty.
have downloaded ARM (arm-generic) pre-built imgaes from:
https://chromium.arnoldthebat.co.uk/?dir=daily
But when try to boot on my arach64 system (jetson-nano) , I am not able to do so.
qemu-system-aarch64 -M virt -m 2048 -smp 2 -cpu host -enable-kvm \ -device usb-ehci -device usb-kbd -device usb-mouse -usb -serial stdio \ -device virtio-gpu-pci,virgl=on,xres=1600,yres=900 -display sdl,gl=on \ -device virtio-blk-device,drive=hd \ -drive if=none,file=chromiumos_image.bin,format=raw,id=hd \ -netdev user,id=mynet \ -device virtio-net-device,netdev=mynet \ -bios edk2-aarch64-code.fd -no-reboot
The problem seems to me that the image is not a proper EFI. It depends some legacy booting system. The ESP (EFI system partition) is empty ?!
I suppose on a x86 system its not a problem, but on the aarch64 its not working.