Hello Polash. I received your mail to me this morning on this topic. Keep in mind that I have about four to five people mailing me data sheets EVERY MORNING asking me how to get this or that working with the BBB, so I'm going to give you the quick overview and post it here so perhaps others can find it.
1. Get your LCD working under Linux, rather than Android. The kernel in Android is the Linux kernel with a few extra Android features in it. You'll have more tools under Linux for querying the system, loading/unloading device tree overlays, etc. than you will under Android, and it makes it a lot easier. If you get your display working under Linux, then start working with Android. 2. Use a Linux image with the 3.8 kernel to do your development. This will allow you to boot and then dynamically load your overlay later, which will make your life easier during development. 3. Use the TILCDC driver in the kernel. This is a generic-ish LCD driver that has a lot of flexibility. The driver is controlled by a device tree fragment that describes behavior specific to the controller chip for your LCD. For an example that is similar to your LCD, please examine the firmware/capes/BB-BONE-LCD4-01-00A1.dts file in the 3.8 kernel source tree to see a working example of the LCD interfacing for a similar LCD. This file works for both the CircuitCo LCD4 and the 4D Systems 4DCAPE-43T cape boards. You use the device tree to map control lines for your LCD controller to specific BBB pins, define your PWM duty cycles for backlight brightness, and any clocks rates, inverted signals, etc. 4. Once you get your display working, if you are permanently attaching this display to the BBB, statically build your overlay fragment into the kernel's device tree. 5. Disable the HDMI and HDMIN built-in capes so that they don't claim the LCD pins during development. You'll be doing your interaction with the system over the network or, even better, via the FTDI serial interface. 6. Your display is not a cape without an eeprom to identify the cape to the I2C capebus. This is not actually required if you are hard-coding the device tree nodes into the device tree. Making your display into a full cape enables the capemgr to dynamically discover the cape and load the appropriate device tree overlay at boot. But, if you are manually loading the overlay on the command line, you're fine. This is a VERY brief look at the process. Please keep in mind that I spend a few hours answering mail on the BBB each day and I just can't hold your hand to walk you through the process of developing your product. Good luck! Andrew On Wednesday, June 4, 2014 1:35:11 AM UTC-4, [email protected] wrote: > > I followed the steps recommended in the link > http://icculus.org/~hendersa/android/ .The BBB is booting through HDMI > properly. My requirement is to boot on a new LCD SH480272T-006-I13Q with > the datasheet link as > http://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0CCMQFjAA&url=http%3A%2F%2Fwww.cec-mc.ru%2Fpdf%2FSPF-PH480272T-006-I13Q_002[2].pdf&ei=z66OU9q1I8aokAXDi4DYDQ&usg=AFQjCNFxB5up6lYg3ohs5YGn2vuaGpWPCg&bvm=bv.68235269,d.dGI > How do I manipulate the EEPROM pins to work for my LCD in the firmware.(if > that is required...I dont know!). > Suggestions Requested Please!!! > > > Regards > Polash > > -- 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.
