LCD-Button-BP v1

This page contains technical information about version 1 of the LCD-Button-Boosterpack, marked 1/4/2012.

First a short important note. If you don’t get the buttons to work, remove the jumper on your launchpad that controls the P1.0 LED. This can’t work at the same time as the board, because the P1.0 is the first button on the LCD board. 

The board supports:

  • 4 standard tactile buttons, that can be soldered on below the display area (not included).
  • There is also room for a 20-pin MSP430 MCU. The standard software library supports the MSP430G2553 as the MCU, but the display can be used with other versions using bitbanging. The board can either be used by attaching it to an MSP430 Launchpad, with the MSP430 on the Launchpad, or by placing the MCU on the LCD-board.
  • The back of the board has room for a SOT-89 LDO voltage regulator such as this (Upper right corner on the bottom, marked IC1). If you choose to attach a voltage regulator, you should also add a decoupling capacitor at C4 and C5. The power connection for the regulator is on the top left (seen from the front), above the BAT-text. Ground is on the outer pins, and the positive voltage is in the middle.
  • Example code for IAR is available on https://github.com/mobilars/LarsLCD . If you have requests for new features or input, please use the 43oh Forum topic for the display to give input.
  • The boards are based on the Powertip PE9665WRF display with the ST7579 controller. The screen is small (28x19mm viewable area) and requires little power (0.2mA). It is SPI-based, has backlight and has 96×65 dots. It’s a perfect display if you need a cheap, small and low-power display for your next project.
  • The display can be used in parallel with other SPI devices such as the Anaren RF Booster Pack, as long as each devices has it’s own Chip-Select signal and you do not send signals to two devices simultaneously.
  • The datasheet for the display can be found here.
  • The datasheet for the controller can be found here.
  • The solder used to attach the components to the board is led-based and is not RoHS compliant.
  • These boards are meant as development kits as part of your electronics projects and for testing purposes. They are not complete products in themselves.
  • This is a relatively cheap display, which also limits the quality, but I have found it works very well for a number of projects.
  • The backlight connection is rated at 3V, and if you use it with a standard Launchpad voltage, you should add a resistor (for example 150ohms) between two points on the board. The connection is marked with a red line on the picture below. This is the only point that needs to be connected.
(text continues below picture).

The picture above shows which connection to make to turn on the LCD. This should preferably be done using a 150-200 ohm resistor, especially if you are using the default 3.5V Launchpad voltage. If you connect them with a cable and no resistor, the backlight may start flashing after a while and may also burn out eventually.

The pin connections are:
  • VCC – Positive supply
  • P1.0 - Button 1
  • P1.1 - Button 2
  • P1.2 - Servo 1 end pin (top)
  • P1.3 - Servo 2 end pin (top)
  • P1.4 – Chip select on LCD
  • P1.5 – Clock
  • P2.0 – Not connected
  • P2.1 - Button 3
  • P2.2 - Button 4
  • GND – Ground
  • P2.6 – Not connected
  • P2.7 - Not connected
  • TEST - Not connected
  • RST – Connected to reset circuit to reset LCD on powerup and reset of MCU
  • P1.7 – Data input on LCD
  • P1.6 – Con1 (pin to the right). Con1 has middle connected to VCC and left to GND.
  • P2.5 - Not connected
  • P2.4 - Not connected
  • P2.3  - Not connected

The picture below shows the schematics of the board:

The picture below shows the board layout:

6 thoughts on “LCD-Button-BP v1”

  1. Hi!

    I purchased your BP and I managed to upload the example code into a G2553 controller. However I noticed, that I can’t debug or upload the code whenever LCD Boosterpack is connected on top of the Launchpad (MSP430 connected to LP-socket). I did try to take out the reset resistor and i tried without the capacitor which is hooked up on the reset line too, but these didn’t have any effect. Code composer studio tells that device is unreckocknizable, but when I remove the BP, everything works fine. Do you have any idea why this would be the case? I think there’s something to do with the SBW-lines. My launchpad is rev1.5 and LCD boosterpack is v2 PCB with switches. Hopefully you understand what i mean 🙂

    1. Sorry it’s not working as it should. With the same board version and CCS I can run debug, but entering a breakpoint will clear the display. I’m not quite sure, but it might be that the reset line is being used while debugging and that this resets the display. Doing another SPISetup() in the code after the breakpoint makes the display work again.

      The above could be seen as an annoyance, but your problem seems worse. You should definitely be able to upload code (and debug, though the display doesn’t work then) when the board is connected. It might be a hardware problem on your board version. I’ve tested all of them before shipping them, but there may have been a problem during shipping.

      I’ll send you an email to discuss some debugging, and if it doesn’t work out I’ll try shipping you another board.

    2. Mika’s fix for this is posted here: http://lars.roland.bz/lcd/reset-hack/ It seems that for some computers, the 56K resistor may be too large, so changing it to 10K worked better for him. He also describes how to connect the display reset pin to a separate MCU output to have better control of the display reset (and allow for debugging without affecting the display). It is an easy fix. The standard boards don’t do this because I wanted to save the extra pin. It would have saved me some work if I just had connected the display reset to an MCU pin, but my thought was that I wanted to save a pin. This works in general, but there may be special cases when you want to implement the change he describes.

Leave a Reply

Your email address will not be published. Required fields are marked *