Vishveshwar, I saw your post. I am using a BB VA6A With the LCD7 Cape Rev A3. But The LCD7 cape displays nothing. I know the cape works I am able to load, display, and interact with Angstrom.
root@android:/ # [ 6.571105] Disabling lock debugging due to kernel taint [ 6.645782] warning: `rild' uses 32-bit capabilities (legacy support in use) [ 6.680664] android_work: did not send uevent (0 0 (null)) [ 6.766143] android_work: sent uevent USB_STATE=CONNECTED [ 6.772979] gadget: high-speed config #1: android [ 6.778656] android_work: sent uevent USB_STATE=CONFIGURED [ 72.969177] request_suspend_state: wakeup (3->0) at 72936041438 (2000-01-01 00:01:11.328032443 UTC) [ 74.772583] net eth0: CPSW phy found : id is : 0x7c0f1 [ 74.778808] PHY 0:01 not found [ 74.789642] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 75.644439] acc_open [ 75.647125] acc_release [ 77.763763] PHY: 0:00 - Link is Up - 100/Full [ 77.768554] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 184.802795] init: sys_prop: permission denied uid:1003 name:service.bootanim.exit Cheers Nathan On Tuesday, January 28, 2014 at 11:49:15 PM UTC-7, Vishveshwar wrote: > > On Monday, January 27, 2014 10:26:41 PM UTC+5:30, Mihir Jariwala wrote: >> >> I recently started working on baglebone. I followed the steps on >> >> >> http://processors.wiki.ti.com/index.php/TI-Android-JB-4.2.2-DevKit-4.1.1_UserGuide >> & >> >> http://processors.wiki.ti.com/index.php/BeagleBone-Android-DevKit_Guide#Hardware_setup >> >> After establishing serial communication the window starts "cccc" as >> recommended. As instructed I insert the bootable sdmmc card into the >> beaglebone. Android starts booting and in the end the log stops... snippet >> of the log is as below. Now i dont know what i have to do. Please provide >> some support regarding it. I am using ubantu 11.10 using VMware on windows7 >> 64bit >> >> log.. >> >> root@android:/ # [ 3.365753] android_work: sent uevent >> USB_STATE=CONNECTED >> [ 3.371520] android_work: sent uevent USB_STATE=DISCONNECTED >> >> [ 3.379119] Disabling lock debugging due to kernel taint >> >> [ 3.435455] android_work: sent uevent USB_STATE=CONNECTED >> >> [ 3.784362] warning: `rild' uses 32-bit capabilities (legacy support >> in use) >> [ 3.845520] android_work: sent uevent USB_STATE=DISCONNECTED >> >> [ 3.890869] android_work: did not send uevent (0 0 (null)) >> >> [ 3.955291] android_work: sent uevent USB_STATE=CONNECTED >> >> [ 4.109863] android_work: sent uevent USB_STATE=DISCONNECTED >> >> [ 4.141540] android_work: sent uevent USB_STATE=CONNECTED >> >> [ 4.147369] android_work: sent uevent USB_STATE=DISCONNECTED >> >> [ 4.211578] android_work: sent uevent USB_STATE=CONNECTED >> >> [ 4.377655] gadget: high-speed config #1: android >> >> [ 4.397521] android_work: sent uevent USB_STATE=CONFIGURED >> >> [ 20.203216] request_suspend_state: wakeup (3->0) at 20170814787 >> (2000-01-01 00:23:56.3389) >> [ 21.057922] net eth0: CPSW phy found : id is : 0x7c0f1 >> >> [ 21.064208] PHY 0:01 not found >> >> [ 21.076110] ADDRCONF(NETDEV_UP): eth0: link is not ready >> >> [ 21.768341] acc_open >> >> [ 21.773101] acc_release >> >> [ 25.053070] PHY: 0:00 - Link is Up - 100/Full >> >> [ 25.069183] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready >> >> [ 33.759277] init: sys_prop: permission denied uid:1003 >> name:service.bootanim.exit >> > > Congratulations! Android booted up. If you did not attach a LCD cape, > that's all you get.. a working console with shell prompt. > The shell prompt got lost in the kernel boot messages, but it is there. > Press Enter key again and you should see it. > > -Vishveshwar > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
