Create Account
Search
You are here: TDG Forum  >>  Texas Instruments SOMs and Development Kits  >>  OMAP35x, DM3730, AM3703 Torpedo SOM Development Kit  >>  interfacing with NEC NL8084HL11 LCD

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 28 Jan 2014 05:00 PM by  steven.eckhoff
interfacing with NEC NL8084HL11 LCD
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages
mvly
Basic Member
Basic Member
Posts:104


--
16 Jan 2014 05:21 PM

    I am trying to interface with this screen.

    I notice the driver is already in the android source build. I was hoping all it takes is to enable the module. But sadly it does not work this way. Any help/guidance would be appreciated.

    I am pretty sure what I did so far is necessary to get the module up and running. I just don't know what else to do afterword or where to look for more information.

    Here is what I have done so far:

    1) The driver is located in: ~/dm3730logic-icecreamsandwich/kernel/drivers/video/omap2/displays/ folder

    It is named: panel-nec-nl8048hl11-01b.c

    2) In the driver, there is a SPI module require. Hence I went ahead and modified the Kconfig file to reflect this. I don't know why it did not have this in the beginning.

    config PANEL_NEC_NL8048HL11_01B
            tristate "NEC NL8048HL11-01B Panel"
            depends on OMAP2_DSS_DPI && SPI
            select BACKLIGHT_CLASS_DEVICE
            help
                    This NEC NL8048HL11-01B panel is TFT LCD
                    used in the Zoom2/3/3630 sdp boards.

    3) Then I went ahead and modify the make menuconfig of the kernel to enable the module

     It is located in:

    -> Device Drivers -> Graphics support -> OMAP2+ Display Subsystem support (EXPERIMENTAL) -> OMAP2/3 Display Device Drivers -> NEC NL8084HL11-01B

     

     This is where I got lost. I don't know what else to do. I know I have to modify the board-omap3logic-display.c in:

    ~/dm3730logic-icecreamsandwich/kernel/arch/arm/mach-omap2/ folder.

     However, I don't know what to modify there.

    In terms of how I connected the LCD, I wired everything the same as the LCD before according to the LCD schematic on this website.

    Hence the RGB signals should NOT change. As for the SPI signals, I don't know how to add this. Any help would be appreciated.

     

    Also I have tested this LCD and it does display somewhat properly (1/2 successfuly) during the uboot. I have modified logic-display.c and bit-bang the SPI to initialize it properly. This is located in:

    ~/dm3730logic-icecreamsandwich/u-boot/board/ti/logic/ folder

     
    mvly
    Basic Member
    Basic Member
    Posts:104


    --
    28 Jan 2014 04:34 PM

    So I got the display to work.

     

    I did what I said in the initial post, but I additionally made the following changes:

    change .driver_name in /kernel/board/arch/arm/mach-omap2/board-omap3logic-display.c to "NEC_8048_panel"

    change .modalias in /kernel/board/arch/arm/mach-omap2/board-omap3logic.c to "nec_8048_spi"
    change .max_speed_hz from 48000000 to 5000000
    remove .bits_per_word because it will be set by the NEC driver

    Of course I also made sure the SPI is correctly wired up.

     

    That's about it. I also had to change the DPI to 160 manually in the /system/build.prop from 128 to 160 to prevent the stock launcher from crashing.

    I made the usual hack to the board to make sure android does not search for the wifi and bluetooth kernel module. i.e. by removing them from /system/lib/modules/ folder.

     

    Everything seems to be in working order. I might have to raise the DPI or change the screen a bit because the unlock screen is a bit messed up.
    steven.eckhoff
    Basic Member
    Basic Member
    Posts:192


    --
    28 Jan 2014 05:00 PM
    mvly,

    Thank you for adding your solution to the forums.
    You are not authorized to post a reply.

    Forums Texas Instruments SOMs and Development Kits OMAP35x, DM3730, AM3703 Torpedo SOM Development Kit