Hi all,
Is the android sources for Zynq out? Where can i download it from?
Cheers
Shakith
Hi all,
Is the android sources for Zynq out? Where can i download it from?
Cheers
Shakith
The Android source is not available yet. We are working on it, though.
Bryan
One answer from the Xilinx forums. Is is the same distribution?
http://forums.xilinx.com/t5/EDK-and-Platform-Studio/Android-on-Zynq/m-p/244998/highlight/false#M23608
Yes, we will take the existing port for ZC702 and modify for ZedBoard.
Bryan
With the Digilent Linux kernel (https://github.com/Digilent/linux-3.3-digilent.git) and with the iveia Android sources (http://wiki.xilinx.com/android-on-zynq-building-bsp) I've actually succeeded booting into an Android system. Keyboard and mouse input does not work yet.
I've created a basic documentation about building Android for ZedBoard. Is there a wiki or a site where I can upload it?
Hi Wachag,
It would be really helpful if you could share the document with me.
email: akini@synapticon.com
Or, you could share a public link through DropBox or Google Drive.
Thanks,
Anup.
I have Android 2.3.7 running with VGA output and keyboard working. Currently trying to get 4.2.2 up.
I've classes tomorrow, but I can try and publish the source (already going home for today :).
Meanwhile, if you wanna give it a try, basically what I did was the following:
1) Checked out the 3.3 kernel from Digilent.
2) Checked out the 3.3 kernel from Google.
3) Merged Google into Digilent.
4) Created a new bitstream with the Xillybus VGA IP used in the Xillinux distribution, and generated a new boot.bin. Also manually modified the dts and generated a new blob.
5) Merged the Xillybus VGA IP driver.
6) Reconfigured the kernel, adding the android options (except the tracer) and the Xillybus driver. Note that the ipv6 support as module is broken, add it as built-in or remove it.
That's it for the Linux kernel.
For Android:
1) I checked out the sources from Iveia. It did not compile at first so I had to do some quickfixes, nothing extraordinary though. Used generic-eng as lunch.
2) At this point Android boots but the keyboard doesn't work. Kinda. It actually does, but the screen state (logically) seems to always stay locked, so the keyboard events end up never being sent to the application and it looks like it doesn't. There's an option in one of the .xml files so it never locks, or you can quickfix by short circuiting the test in Android's code. You may also want to change the keyboard layout, look for .kl files.
I couldn't find support for the mouse and ethernet in the Iveia source, but I've found some patches from the androidX86 project to add them. Haven't tested it though. Anyway, adding them should be straightforward.
Ethernet works ok in Linux and you can use adb without problems.
Hope it helps :-)
My solution was similar, it is downloadable from http://home.mit.bme.hu/~wacha/android_zed.pdf
As for the keyboard:
diff --git a/policy/src/com/android/internal/policy/impl/PhoneWindowManager.java b/policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
index f934e6b..9fb842a 100755
--- a/policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
+++ b/policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
@@ -1767,7 +1767,7 @@ public class PhoneWindowManager implements WindowManagerPolicy {
// the device some other way (which is why we have an exemption here for injected
// events).
int result;
- if (isScreenOn || isInjected) {
+ if (isScreenOn || isInjected || true) {
// When the screen is on or if the key is injected pass the key to the application.
result = ACTION_PASS_TO_USER;
} else {
Nice. Do you mind if I put this into the guide?
(Also, I am thinking about wikifying it so everyone could edit it)