Yeah. I think I can disable the onboard HDMI framer and enable my own LCD display through the cape manager at runtime or set it in the Env.txt to do it at boot process( as I have read from here http://learn.adafruit.com/introduction-to-the-beaglebone-black-device-tree/exporting-and-unexporting-an-overlay ).
Here's what I have done so far. based here http://www.cemetech.net/forum/viewtopic.php?t=7814&postdays=0&postorder=asc&start=0 1. cloned the angstrom setup script 2. checkout the 2013.06 source 3. setup using the oebb.sh for beaglebone 4. compile the menuconfig and looked through it. 5. bitbake virtual/kernel compile now I can see the kernel source somewhere in the build folder Here's what I am planning to do. 1. use and edit an existing device tree source in the firmware/capes (I'm gonna go with BB-BONE-LCD4-01-00A0.dts. 2. add the touch screen driver (I'm still figuring out where and how including how to enable the kernel to know that the driver for the touch interface in the device tree is this one.) 3. build the image. I still can't say if I am on the right track because I have just read about device tree since yesterday. kit On Tuesday, October 1, 2013 1:28:27 AM UTC+8, Gerald wrote: > > Ever here of Device tree? You have to disable the onboard HDMI framer to > use the pins for your LCD. > > http://circuitco.com/support/index.php?title=BeagleBone_Black_FAQ > > > Gerald > > > > On Mon, Sep 30, 2013 at 11:35 AM, <[email protected] <javascript:>>wrote: > >> Beaglebone black. Right now, I am building the circuit to power and >> connect my LCD, backlight and touch interface. My LCD has 24 pins for the >> data. I think I'll just connect 16 for now and try to modify a dts of an >> existing lcd cape. About the touch interface, how do I let the kernel load >> my driver? >> >> >> On Monday, September 30, 2013 11:30:08 PM UTC+8, Gerald wrote: >> >>> Which BeagleBone do you have? >>> >>> Gerald >>> >>> >>> >>> On Mon, Sep 30, 2013 at 9:56 AM, <[email protected]> wrote: >>> >>>> Thank you Gerald. I'm reading about device tree because I'm using the >>>> 3.8 version of the linux kernel. I'm going to make my LCD as my main >>>> display. It has capacitive touch panel. The touch has an I2C interface and >>>> uses FT5x02 driver( I have the C source for this). I think I can >>>> understand >>>> how to make a dts base on the existing dts in the kernel source. However, >>>> I >>>> am still on the process of learning it. >>>> >>>> >>>> On Saturday, September 14, 2013 12:00:37 AM UTC+8, Gerald wrote: >>>> >>>>> The 24 bit is standard on all 24 bit displays. There are also 8 bit >>>>> displays as well. And 16 bit displays. The BBB is setup for 16 bit >>>>> displays, but you can still use the 24b display. >>>>> >>>>> As to whether it will work, a lot of displays can work. You nee dto >>>>> get help form some one that knows the AM3359 processor. >>>>> >>>>> There are several references for LCD that can be found by looking at >>>>> the schematics for the LCDs that are already on the market, built, and >>>>> ready to go. >>>>> >>>>> http://circuitco.com/support/**i**ndex.php?title=BeagleBone_**Cape**s<http://circuitco.com/support/index.php?title=BeagleBone_Capes>has >>>>> a few isted and there others out there as well. >>>>> >>>>> Gerald >>>>> >>>>> >>>>> >>>>> On Fri, Sep 13, 2013 at 10:55 AM, <[email protected]> wrote: >>>>> >>>>>> Hi everyone! >>>>>> >>>>>> I want to connect an LCD for primary display to my beaglebone black. >>>>>> I have not yet purchased an LCD because I am still on the process of >>>>>> choosing which LCD works. I don't have a background on writing drivers >>>>>> and >>>>>> patching, but I can program and have experienced compiling a linux >>>>>> kernel >>>>>> for an amd geode singleboard computer in the past. >>>>>> >>>>>> After searching the net about LCDs and beaglebone, I learned about >>>>>> the builtin LCD support of the AM335x processor. So now I looked for >>>>>> LCDs >>>>>> with similar interface and I came across this: >>>>>> https://www.google.com/**u**rl?sa=t&rct=j&q=&esrc=s&**source** >>>>>> =web&cd=1&ved=0CCwQFjAA&**url=**http%3A%2F%2Fwww.fannal.**com%** >>>>>> 2Fsupport%2Fdocument-**download%**2Fitem%2Fdownload%**2F13_**f59fd95* >>>>>> *29e0ce870e8347832c9f482**2a.**html&ei=**7DAzUvb0FYe4iAfF7IGQBw** >>>>>> &usg=**AFQjCNHINBIAaYblpZ1cBXIqX**U0qyK**T6ZQ&sig2=** >>>>>> s5nJqjlkH14jVrCn-**oalqw&bvm=bv.**52164340,d.aGc&**cad=rja<https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0CCwQFjAA&url=http%3A%2F%2Fwww.fannal.com%2Fsupport%2Fdocument-download%2Fitem%2Fdownload%2F13_f59fd9529e0ce870e8347832c9f4822a.html&ei=7DAzUvb0FYe4iAfF7IGQBw&usg=AFQjCNHINBIAaYblpZ1cBXIqXU0qyKT6ZQ&sig2=s5nJqjlkH14jVrCn-oalqw&bvm=bv.52164340,d.aGc&cad=rja> >>>>>> >>>>>> It has 24-bit TTL interface. So my questions are: >>>>>> 1. Is the 24-bit TTL RGB interface stadard? That is, I can just >>>>>> connect this to the beaglebone with at most editing the pinmux >>>>>> 2. How do I know if an LCD is compatible with the AM335x processor? >>>>>> 3. According to the supplier the touch controller is SSD2532. What >>>>>> are the things do I need to do, to make the touch interface work? Do I >>>>>> have >>>>>> to make my own driver to interpret touch data from the I2C communication? >>>>>> >>>>>> I am looking forward for your responses. >>>>>> >>>>>> Thank you very much. >>>>>> >>>>>> Sincerely, >>>>>> kit >>>>>> >>>>>> >>>>>> On Tuesday, May 1, 2012 8:34:50 AM UTC+8, KermM wrote: >>>>>> >>>>>>> I've been playing around with my BeagleBone for a few weeks now, and >>>>>>> I figured it was time to try to connect an LCD to it. After a fair bit >>>>>>> of >>>>>>> digging, kernel-compile, and testing, I've decided that I might as well >>>>>>> run >>>>>>> my questions by the experts to see if you guys can shed some light. >>>>>>> First >>>>>>> of all, what I know and what I've tried: >>>>>>> >>>>>>> - I have a 320x240 RGB LCD (with SPI touchscreen) that has either an >>>>>>> HX8347-A or SSD1289 compatible display driver. >>>>>>> - The AM335x has an LCDC that supports Raster and LIDD modes. Based >>>>>>> on the pinout of the display (D0-D15, CS, RS [aka CD], WR, RD, RESET), >>>>>>> I >>>>>>> believe it requires LIDD mode >>>>>>> - From the 5000-page AM335x manual, I found the proper pin mappings >>>>>>> and got my display all hooked up. >>>>>>> - I looked for and found a /drivers/video/ssd1289 module for another >>>>>>> platform that I could theoretically port >>>>>>> - I found via http://processors.wiki.ti.com/****** >>>>>>> index.php/AM335x_LCD_**Controlle****r_Driver%27s_Guide<http://processors.wiki.ti.com/index.php/AM335x_LCD_Controller_Driver%27s_Guide>that >>>>>>> I should look at the da8xx module for the am335x as a start >>>>>>> - I downloaded and built the Angstrom source kernel and root image >>>>>>> via Angstrom's git repository. I also tried the Angstrom Narcissus >>>>>>> tool, >>>>>>> but had less success >>>>>>> - I managed to build Angstrom successfully, and I managed to perform >>>>>>> a menuconfig that confirmed that the da8xx driver was configured. I >>>>>>> tried >>>>>>> as built-in and as a module >>>>>>> - In neither case, performing a console-image build, could I manage >>>>>>> to actually get anything related to the da8xx to appear in the kernel >>>>>>> or as >>>>>>> a module. Perhaps I need a GUIfied image? >>>>>>> - Unfortunately, trying to build a full GUI image with gnome and >>>>>>> friends failed due to bad XML in one of the gdm components >>>>>>> - I searched through the many files in the Angstrom bitbake >>>>>>> directories, and found such interesting items as patches for the >>>>>>> Beagleboard Toys' ULCD7 (which appears to use the Raster mode, not the >>>>>>> LIDD >>>>>>> mode) >>>>>>> - I tried copying over the kernel source directory from my >>>>>>> cross-compiling Linux machine to my Beaglebone itself, but ran into >>>>>>> myriad >>>>>>> problems trying to build the da8xx module manually on the 'bone. >>>>>>> >>>>>>> At this point, I believe that my plan of attack should be something >>>>>>> like this: >>>>>>> - Get the da8xx driver to somehow build, anywhere >>>>>>> - Insmod it and see if I can use it to get anything to appear on my >>>>>>> LCD >>>>>>> - If not, merge the SSD1289 module I found for another platform as a >>>>>>> patch / extension to the da8xx driver >>>>>>> - If and when I get it working as a driver, figure out how to >>>>>>> compile it directly into the kernel. >>>>>>> >>>>>>> Thanks in advance for any feedback, experience, or comments you >>>>>>> might have; please don't hesitate to ask any additional questions you >>>>>>> might >>>>>>> have about what steps and approaches I have or have not yet tried. >>>>>>> >>>>>> -- >>>>>> 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/**grou**ps/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.
