I realize I am kind of "lurking" on this thread,but could you posting large
console output please post these console outputs to a pastebin ?


I am interrested in debug information, but pastebin is surely better for
this sort of output.

On Mon, Dec 22, 2014 at 7:19 AM, Andrew Henderson <hende...@icculus.org>
wrote:

> Using the HDMI cable to connect the BBB to your DVI/HDMI display should
> work without an issue.  You do not need HDMI audio to use the Android
> image.  I have used it without an issue with the various LCD capes without
> audio, for example.  Using the ethernet LAN connection and USB mouse are
> also supported.
>
> I will need more information before I am able to help you.
>
> Can you supply a complete FTDI output from bootloader boot through to
> about 60 seconds?  The reason that I ask for this is because I need to see
> where the video resolution is being set in the TILCDC framebuffer driver.
> While there are a number of failed services in the logcat output that you
> provided in your other post, I need to see the results of the kernel
> booting output first before I can move on to helping you troubleshoot any
> user space issues.  The logcat output shows that you are well into the boot
> process of user space.  If anything is failing in kernel space, I need to
> know that first.
>
> Are you not seeing anything on your display?  One of the most common
> problems is the EDID block not being sent from your monitor to the BBB.
> When this happens, the TILCDC kernel driver will default to a resolution of
> 1024x768 (which may not be supported by your monitor).  This results in a
> blank screen.  My first guess is that this is your problem (especially if
> you see it for both the old and new Android images).
>
> Are you stuck at the screen with the "Android" animation on it?  You
> should not be, from what I can see of your logcat output.
>
>
> On Friday, December 19, 2014 3:33:01 AM UTC-5, kiran...@gmail.com wrote:
>>
>> Hi andrew! i tried you images (old and new) for beagle bone black. But i
>> am not getting booted into it.
>>
>> Is it required to connect Display, LAN, and USB mouse.
>> If I use HDMI CABLE (sony erricsion) to connect my PC monitor, will it
>> drive.
>>
>> the FTDI output:
>> [    6.038794] g_ffs: read descriptors
>> [    6.042738] g_ffs: read strings
>> [    6.060551]  gadget: g_ffs ready
>> [    6.064563] musb-hdrc musb-hdrc.0.auto: MUSB HDRC host driver
>> [    6.072874] musb-hdrc musb-hdrc.0.auto: new USB bus registered,
>> assigned bus number 2
>> [    6.081893] usb usb2: New USB device found, idVendor=1d6b,
>> idProduct=0002
>> [    6.089055] usb usb2: New USB device strings: Mfr=3, Product=2,
>> SerialNumber=1
>> [    6.096608] usb usb2: Product: MUSB HDRC host driver
>> [    6.101795] usb usb2: Manufacturer: Linux 3.8.13+ musb-hcd
>> [    6.107524] usb usb2: SerialNumber: musb-hdrc.0.auto
>> [    6.114174] hub 2-0:1.0: USB hub found
>> [    6.118361] hub 2-0:1.0: 1 port detected
>> shell@beagleboneblack:/ $ [    6.293332] CAUTION: musb: Babble Interrupt
>> Occurred
>> [    6.391168] CAUTION: musb: Babble Interrupt Occurred
>> [   27.787048] warning: `zygote' uses 32-bit capabilities (legacy support
>> in use)
>> [   43.804027] healthd: battery l=0 v=0 t=0.0 h=1 st=1 chg=
>> [   46.763599] net eth0: initializing cpsw version 1.12 (0)
>> [   46.772805] net eth0: phy found : id is : 0x7c0f1
>> [   46.789857] libphy: PHY 4a101000.mdio:01 not found
>> [   46.794916] net eth0: phy 4a101000.mdio:01 not found on slave 1
>> [   46.817629] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>> [   68.388050] init: sys_prop: permission denied uid:1003
>>  name:service.bootanim.exit
>>
>  --
> 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 beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to