Terry23

Member Since: December 26, 2013

Country: United States

  • Product DEV-12085 | about 3 months ago

    Got to use another cape in between. LCD capes are designed to be the final cape in the ‘stack’. So simply put something like a prototyping cape in between the BBB and the LCD to access the unused pins. A few on the market. Check out www.beaglebonecapes.com, and something like http://elinux.org/Tigal:BeagleBone_ProtoCape

  • Product LCD-11315 | about 3 months ago

    If it has a UART serial port, then sure, don’t see why not

  • Product LCD-12087 | about 3 months ago

    http://www.4dsystems.com.au/productpages/4D-Arduino-Adaptor-Shield-II/downloads/4D-Arduino-Adaptor-REV2.xx_datasheet_R_1_2.pdf

  • Product LCD-11740 | about 3 months ago

    Yes

  • Product LCD-11740 | about 3 months ago

    Yes, easy peasy

  • Product DEV-12085 | about 3 months ago

    Touch issues solved with latest 3.8.13-bone37 kernel. Debian image with all fixes in place available from here. Works really well. http://rcn-ee.net/deb/testing/2014-01-29/

  • Product DEV-12086 | about 3 months ago

    Touch issues solved with latest 3.8.13-bone37 kernel. Debian image with all fixes in place available from here. Works really well. http://rcn-ee.net/deb/testing/2014-01-29/

  • Product DEV-12086 | about 4 months ago

    http://downloads.ti.com/sitara_android/esd/TI_Android_DevKit/TI_Android_JB_4_2_2_DevKit_4_1_1/exports/TI_Android_JB_4.2.2_DevKit_4.1.1_beagleboneblack.tar.gz

    Instructions are inside. Its open source man, always expect to have to do some things yourself. The BBB is not a commercial product with commercial quality software, expect things to be a work in progress.

  • Product DEV-12086 | about 4 months ago

    You are running Andrews version of Android it seems (http://icculus.org/~hendersa/android/) ?, which does not have the keys mapped for Android via a Key Layout file. This isn’t a problem with the display. The keys just haven’t been mapped on that version by Andrew. See something like this, however I personally haven’t mapped the keys (http://source.android.com/devices/tech/input/key-layout-files.html).

    If you use the TI version which is in the Datasheet from 4D, that one works great. Does depend if you are wanting Kernel 3.8 or 3.2 though, as the TI version is 3.2 and Andrews is 3.8. But hardware acceleration for graphics is only working on 3.2 so far I believe, so is actually quite a bit faster than the 3.8.

  • Product DEV-12086 | about 4 months ago

    What’s not working? You checked the datasheet out, and the EEPROM jumper settings if you are trying to run Android? Go to the www.4dsystems.com.au website and go to the product page for the Cape, the datasheet above is out of date.

No public wish lists :(