{"id":926,"date":"2013-01-15T21:51:48","date_gmt":"2013-01-16T04:51:48","guid":{"rendered":"http:\/\/www.graphics-muse.org\/wp\/?p=926"},"modified":"2013-01-17T20:33:10","modified_gmt":"2013-01-18T03:33:10","slug":"pibox-beaglebox-update-lost-keyboard-access","status":"publish","type":"post","link":"https:\/\/www.graphics-muse.org\/wp\/?p=926","title":{"rendered":"PiBox \/ BeagleBox update: lost keyboard access?"},"content":{"rendered":"

I’ve finally got a build for PiBox<\/a> that supports a proper XBMC build.  The latter took some finagling to force a cross compile that didn’t pick up any bits and pieces from the build system.  So it’s all checked in and the builds placed on the SD card and it’s ready to test.  Except for some reason none of my keyboards work with the Raspberry Pi<\/a> anymore.<\/p>\n

The original keyboard I was using was wired through a powered USB hub so I could also have a wireless mouse and a USB wifi dongle and so I could easily switch the powered hub between the Pi, my BeagleBox<\/a> and an APC board.  The mouse still works (I haven’t checked the dongle) but the keyboard stopped working.  I plugged the keyboard into my desktop and it worked, but not quite completely.  I also tried it on my BeagleBox, where it didn’t work either.  I plugged the keyboard directly into the Pi and BeagleBox, skipping the powered hub, but no joy.<\/p>\n

So I assumed the keyboard is broken.  I ordered a Logitech wireless keyboard.  When it arrived, I tried it on the Pi and BeagleBox.  No joy.  I plugged it into the desktop.  No joy.  Then I noticed it is one of the special Unified<\/strong> wireless devices from Logitech.  These require special software to enable the keyboard<\/a>.  There is some open source software that can make this work, but I blew it off for now in favor of running to Target to get another wireless keyboard – one without special mongo features.<\/p>\n

So the newer keyboard is a GE keyboard.  I plug it in to the Pi, BeagleBox and the desktop.  The first two – no joy.  The desktop worked fine with it.  So now I’m getting really freaked.  Did I munge the kernel config on both board builds?  I fiddled with the PiBox build but then decided to blow that off and go get another GE wired keyboard from Target.  Wired is what worked before.<\/p>\n

And no joy with either board, though the wired keyboard does work with the desktop.  So now I’m thinking I somehow I fried the USB ports on both boards.  Weird, cuz the wireless mouse still seems to work.  I checked the USB ports using u-boot on the BeagleBoard and they didn’t seem to show the devices connected to the hub (not the OTG port).  You can’t do that kind of check on the PiBox because it doesn’t use a bootloader that’s of any use to integration testing.  At least not as far as I’ve seen yet.<\/p>\n

So perhaps I shocked the ports.  I had a blanket in my office that was causing me to get a lot of static shock when I sat at my desktop.  I shocked my wired mouse on my desktop a few times, but I don’t remember shocking the Pi or BeagleBoard.  But maybe I did.<\/p>\n

I’ve orderded two more Pi’s.  If these work with the keyboards, then I’ll order another BeagleBoard C4.  At the moment, I’m not convinced the ports are fried.  But I’m at a loss as to what else could be wrong with them.  And until I can fix the keyboard, I won’t be able to test the lastest PiBox with XBMC builds.  Bummer.<\/p>\n","protected":false},"excerpt":{"rendered":"

I’ve finally got a build for PiBox that supports a proper XBMC build.  The latter took some finagling to force a cross compile that didn’t pick up any bits and pieces from the build system.  So it’s all checked in and the builds placed on the SD card and it’s ready to test.  Except for […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"jetpack_post_was_ever_published":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[566,390,562,515],"tags":[],"class_list":{"0":"post-926","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-beagleboard-2","7":"category-beaglebox-hardware","8":"category-pibox","9":"category-xbmc","10":"czr-hentry"},"jetpack_publicize_connections":[],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pe9t8-eW","jetpack_sharing_enabled":true,"jetpack-related-posts":[],"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=\/wp\/v2\/posts\/926","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=926"}],"version-history":[{"count":2,"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=\/wp\/v2\/posts\/926\/revisions"}],"predecessor-version":[{"id":928,"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=\/wp\/v2\/posts\/926\/revisions\/928"}],"wp:attachment":[{"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=926"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=926"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=926"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}