Oops, Sorry. Forgot to do that. I did plug them in before I powered up. They still went dead.
On Sunday, 29 September 2013 20:27:40 UTC+5:30, Gerald wrote: > > It is not a HW limitation. All devices must be plugged in BEFORE you power > on the board to make the software happy. > > Also. I suggest you register so I don't have to approve your spots. That > means they go through immediately. > > Gerald > > > > On Sun, Sep 29, 2013 at 1:49 AM, <[email protected] <javascript:>>wrote: > >> The mouse works fine if I plug it in seperately. >> >> I bought a basic USB hub and plugged that into my beaglebone. It powered >> up normally. >> I plugged in the mouse as well. They both power up for a second and then >> go blank. >> Is this a hardware limitation? Can I ONLY use powered USB hubs? >> >> Thanks >> >> On Thursday, 26 September 2013 23:11:16 UTC+5:30, William Hermans wrote: >> >>> Hi Sushant Khanna, >>> >>> I have read about similar issues with all sorts of devices, and as far >>> as I can tell the type of hub used can be a big factor in this situation. >>> First, if you have not tried checking if each device works by its self on >>> the USB host port ( individually ) I would do so now. >>> >>> So, I think in this case I would check to see if the keyboard works by >>> its self with nothing else plugged into it. If it does, then yes this would >>> be a bit of a quandary, as putting this specific keyboard on another hub >>> may make the situation worse. All may not be lost though, there could be a >>> kernel driver module for this specific keyboard, although I would not hold >>> my breathe. >>> >>> You may want to try using a different keyboard / mouse, with a known >>> good working USB hub( if you have such laying around ). Spending money on >>> something and not having that work either . . . yes, I know would not be >>> ideal. Said hub should also be self powered. >>> >>> As to whether you're needing an external power supply I am not sure, and >>> Gerald would know better than I. However we all could use more information >>> to help us know what exactly is happening. Such as the serial debug output >>> at the time the board is powered up with the keyboard and mouse plugged >>> into the USB port. Sometimes, it can not be overstated how handy a serial >>> debug interface can be . . . >>> >>> >>> On Thu, Sep 26, 2013 at 6:35 AM, Gerald Coley <[email protected]>wrote: >>> >>>> Not sure it will fix your issue, but the image you are using is very >>>> old. I suggest that you try a more up to date image on your board. >>>> >>>> http://circuitco.com/support/**BeagleBoneBlack<http://circuitco.com/support/BeagleBoneBlack> >>>> >>>> >>>> Gerald >>>> >>>> >>>> >>>> On Thu, Sep 26, 2013 at 12:56 AM, <[email protected]> wrote: >>>> >>>>> Hi Guys >>>>> >>>>> Someone asked a similar question before, but no one had an answer then. >>>>> I was going to give up and buy another keyboard but when I googled a >>>>> bit more, I saw that a lot of people are able to use it with their >>>>> beaglebone black. >>>>> >>>>> I will explain the conditions and problem in details. >>>>> >>>>> I have a beaglebone black powered up via a USB charger (NOT via the 5V >>>>> DC adapter) >>>>> I have it connected to a display via a microHDMI cable. >>>>> I am running Angstrom. Updated to 4.09.2013 image. (emmc boot) >>>>> >>>>> When I plugged in a normal wired optical mouse, it powered up and I >>>>> was able to use it. >>>>> I then used an Apple keyboard as described in the title and plugged >>>>> the mouse to its internal hub on the sides. Nothing worked, both did not >>>>> show any signs of being powered up. >>>>> I of course rebooted and checked *lsusb *output. I could see the >>>>> Apple device listed there. >>>>> >>>>> Is this a driver issue or a power supply problem? >>>>> Kinda new, so help me out please. >>>>> >>>>> Thanks >>>>> >>>>> -- >>>>> 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...@**googlegroups.com. >>>>> >>>>> For more options, visit >>>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>>> . >>>>> >>>> >>>> -- >>>> 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...@**googlegroups.com. >>>> >>>> For more options, visit >>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> >>>> . >>>> >>> >>> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- 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/groups/opt_out.
