Was this ever resolved? I am experiencing a similar issue. On Tuesday, March 31, 2015 at 2:06:14 PM UTC-4, [email protected] wrote: > > Hi Andrew, > > Please you help me with the USB ADB. > I downloaded bbbandroid_111514.img.xz image, and I wrote this image to my > Beaglebone Black. > I use Ubuntu 14.04, I have made /etc/udev/rules.d file with content: > #adb protocol on BeagleBone Black (BBB 1) > SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666" > #adb protocol on BeagleBone Black (BBB 2) > SUBSYSTEM=="usb", ATTR{idVendor}=="0451", MODE="0666" > and I grant permission: > chmod a+r /etc/udev/rules.d/51-android.rules > and: adb kill-server, adb start-server > But when I give command "adb devices", I only see "List of devices > attached", my BBB can't attach. > So I decide to replace three files that you have attached to my BBB. > But now my BBB can't start into Android OS, I only see 'ANDROID' on screen > forever. > What's happen here? > Please you help me for USB ADB. > > Best regards > Jimmy Trinh > > > On Tuesday, October 7, 2014 at 8:10:50 AM UTC+7, Andrew Henderson wrote: >> >> I have not made a new premade image with USB ADB, but I have it working. >> In your current BBBAndroid image, replace your uEnv.txt (/boot partition) >> with the one I have attached. Replace your two init.genericam33xx*.rc >> files (/rootfs partition) with the two I have attached. In addition to >> getting USB ADB up and running, the main .rc file also changes some >> permissions to make them more relaxed. Now, i2c-tools work without >> superuser privileges and it "wakes up" all four GPIO banks in case you need >> to mmap() the GPIO registers. >> >> If you watch the FTDI output from the BBB (when the USB is plugged in at >> boot), you'll see something like the following: >> >> [ 5.784087] CAUTION: musb: Babble Interrupt Occurred >> [ 5.854604] CAUTION: musb: Babble Interrupt Occurred >> [ 6.048723] CAUTION: musb: Babble Interrupt Occurred >> [ 6.119724] CAUTION: musb: Babble Interrupt Occurred >> [ 6.341756] gadget: high-speed config #1: FunctionFS >> >> On your dev system side, use ADB to list the devices: >> >> $ adb devices >> List of devices attached >> BBBANDROID device >> >> $ adb logcat >> ... >> D/AlarmScheduler( 917): No events found starting within 1 week. >> I/ActivityManager( 592): Waited long enough for: ServiceRecord{a5fb0900 >> u0 com.android.calendar/.alerts.InitAlarmsService} >> D/InitAlarmsService( 917): Clearing and rescheduling alarms. >> D/ConnectivityService( 592): Sampling interval elapsed, updating >> statistics .. >> D/ConnectivityService( 592): Done. >> D/ConnectivityService( 592): Setting timer for 720seconds >> >> >> On Sunday, October 5, 2014 5:24:27 PM UTC, Andrew Henderson wrote: >>> >>> USB ADB is currently being worked on. The image I provided builds in >>> FunctionFS support, but I have not yet made the modifications to the .rc >>> files to point ADB to FunctionFS. I'm currently working on a few >>> modifications to the .rc files to make the image a bit more "BBB friendly" >>> for those interested in using it for Android hardware interfacing practice. >>> >>> On Sunday, October 5, 2014 12:31:33 PM UTC-4, Lei Wang wrote: >>>> >>>> May I ask if ADB over USB is supported in this release? Thanks very >>>> much! -lei >>> >>>
-- 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.
