• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 80 subscribers
  • Views 1058 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP 430 display interfacing

Adam Hoover
Intellectual 370 points
Other Parts Discussed in Thread: MSP430F4152, MSP430F6638

Hello,

I am looking to brainstorm with the community over the latest options in MSP430 display interfacing.  We are redesigning our product and considering upgrading.  Our current product uses an MSP430F4152 to drive a 4 character 7 segment display.  We are considering using a new MSP430 that would drive either a 10 character 16 segment display (custom made by Varitronix) or a pixel-based LCD graphics module (such as those made by Truly, Sharp, etc.).

My understanding of the MSP430 LCDA module is that it can drive up to 8x40=320 segments.  Is that correct?  We currently only use 21 and no MUXing.  I'm having a hard time envisioning the wiring if I increase to 160 segments.  Would the design use each single output pin from the MSP430 to connect in series to 4 inputs on my LCD glass, using the bit memory in the LCDA module to control which of the 4 inputs actually gets activated?  Or is another MUX circuit needed in-between, or do I have my glass manufacturer build the MUX into the LCD?

Do any MSP430 models come with graphics LCD module drivers, or are they always included in the display, and typically use SPI to communicate with the MSP430?

All feedback appreciated.

-Adam

  • 0
    Intellectual 510 points
    Hi,
    I am using LCD_B from a msp430f6638.
    And all the multiplexing is done inside the module. actually each segment pin from MSP can be connected tto 4 segments on the LCD. but each LCD segment has to be connected with a different common.
    so when connecting the LCD display you have to look careful in to specification.
    After that you will be able to write on to LCD memory turning on or off any segment you want without warring about multiplexing.
  • 0
    Expert 2665 points

    Hi,

    We use LM6020 graphical LCD with 128x64 pixels which is cheap as dirt. It has Sitronics ST7565R controller on-board (analog of Epson SED1565). It is controlled from MSP430 via 8-bit parallel port + WR/RD/CS/RST strobes.

  • 0 in reply to Serge A
    Intellectual 510 points

    Hi,

    if you are going to stay with the LCD with built in driver. tha LCD driver inside the MSP430 will have no use. the microcontroller driver has the function of the built in LCD driver you are using.

    Edriano Carlos de Araújo

  • 0 in reply to Edriano De Araujo
    Expert 2665 points

    edriano araujo said:

    Hi,

    if you are going to stay with the LCD with built in driver. tha LCD driver inside the MSP430 will have no use. the microcontroller driver has the function of the built in LCD driver you are using.

    Edriano Carlos de Araújo

    Exactly. You can use cheaper MSP430 part without internal LCD controller.

  • 0 in reply to Serge A
    Intellectual 370 points

    Thanks for all the great feedback.

    I'm finding that graphical LCDs typically pull 100 uA to 10 mA, whereas segmented displays pull <10 uA.  One exception I found is a new Sharp LCD "e-paper" that pulls 3 uA (http://www.mouser.com/new/Sharpsma/sharpmemorylcd/), but it is relatively expensive ($9/unit).


    My product is in the form of a wristwatch, so I am constrained by needing very low power (and low cost).  Any further suggestions?

**Attention** This is a public forum