BeagleBone Black, successful compilation but unable to boot (Lacking MLO, u-boot.img, uImage, uEnv.txt, rootfs.tar.bz2) about android-keyboard-gadget HOT 9 CLOSED

I also did checkout rowboat-am335x-kernel-3.2, I tried manually editing the files (based on kernel-3.1.patch found here), but some of the lines are missing.

And I'm not sure if the build would be successful, please advise. Thanks!

from android-keyboard-gadget.

Hi.

Did you try to generate a build without this patch, using clean Beaglebone
repository? Did it boot?

Please attach here your build logs (you can use smth like
http://gist.github.com or http://pastebin.com
On Mar 26, 2015 1:32 PM, "Sumofwhich" [email protected] wrote:

I also did checkout rowboat-am335x-kernel-3.2, I tried manually editing
the files (based on kernel-3.1.patch found here), but some of the lines are
missing.

And I'm not sure if the build would be successful, please advise. Thanks!

—
Reply to this email directly or view it on GitHub
#25 (comment)
.

from android-keyboard-gadget.

Warmest greetings Pelya,

Thanks for your prompt reply :)
I will try to build it based on this tutorial (https://github.com/csimmonds/bbb-android-device-files/tree/kk4.4-sdcard) BUT using a clean repo and -b android-4.4.2_r1

Will let you know when I'm done and will attach the build logs. Thanks!

from android-keyboard-gadget.

Completed, everything is successful but couldn't boot up with the sdcard method, skipped SGX and Android VNC server

Logs:
https://gist.github.com/d879be890aa3220f0f41.git

from android-keyboard-gadget.

I didn't see anything suspicious in the log, so I cannot tell where is the
problem.

On Mon, Mar 30, 2015 at 9:36 AM, Sumofwhich [email protected]
wrote:

Completed, everything is successful but couldn't boot up with the sdcard
method, skipped SGX and Android VNC server

Logs:
https://gist.github.com/d879be890aa3220f0f41.git

—
Reply to this email directly or view it on GitHub
#25 (comment)
.

from android-keyboard-gadget.

When I turned on the power, all 4 leds are not lit up. I could only see red lines on the display (I'm using HDMI to DVI converter).

When I tried using aosp version 4.4.4_r1 with sgx drivers and android vnc server installed, all 4 leds are not lit up too. I could see red lines on display at first, but the android logo shows up and I manage to boot into the home screen.

Retried with clean 4.4.2_r1, and 4.4.2_r1 with sgx drivers and android vnc server, couldn't boot.

from android-keyboard-gadget.

Do you have a.y way to capture kernel logs? Serial console maybe?
On Apr 2, 2015 9:25 AM, "Sumofwhich" [email protected] wrote:

When I turned on the power, all 4 leds are not lit up. I could only see
red lines on the display (I'm using HDMI to DVI converter).

When I tried using aosp version 4.4.4_r1 with sgx drivers and android vnc
server installed, all 4 leds are not lit up too. I could see red lines on
display at first, but the android logo shows up and I manage to boot into
the home screen.

—
Reply to this email directly or view it on GitHub
#25 (comment)
.

from android-keyboard-gadget.

Ahh it's okay Pelya, I've managed to manually apply the changes in kernel 3.1.patch for the android aosp 4.4.4_r1 build, and then rebuild it.

Now I can send keypresses by following your Scripting section! Thanks a lot!

from android-keyboard-gadget.

Problem seems to have been fixed, therefore closing.

from android-keyboard-gadget.