chicken

Always a sucker for displays of any form and shape I ordered one of the 1.35 inch SHARP LS013B4DN02 memory LCD when it made the rounds last year. At $20 apiece it's quite expensive for its size, but it's sooo pretty
 

 
I finally finished up the code and published everything on Github.
https://github.com/a...-memory-display
 
According to the datasheet, this display runs on less than 15uW. I was not able to measure current with my lowly multimeter, so I'm pretty positive that the MSP430 plus display use way below 1mA.
 
If the display looks familiar, that's because it was featured in the Wolverine teaser a few months back
http://www.43oh.com/...cd-boosterpack/
 
My code probably also works with the breakout board that fellow 43oh member reagle designed:
http://forum.43oh.co...akout-for-sale/
 
More information about the display at SHARP:
http://www.sharpmemo...memory-lcd.html
 
According to Mouser LS013B4DN02 is end-of-life. However LS013B4DN04 has very similar specs and should also work with this breakout and code. Both displays are in stock at Mouser:
LS013B4DN02
LS013B4DN04
 
I have two extra PCBs including matching FPC connector (10pos .5mm) sitting in my drawer. PM me if anyone wants one, I'll give or trade them away as long as it's within the US.
 
Regards
Adrian

Always a sucker for displays of any form and shape I ordered one of the 1.35 inch SHARP LS013B4DN02 memory LCD when it made the rounds last year. At $20 apiece it's quite expensive for its size, but it's sooo pretty
 

 
I finally finished up the code and published everything on Github.
https://github.com/a...-memory-display
 
According to the datasheet, this display runs on less than 15uW. I was not able to measure current with my lowly multimeter, so I'm pretty positive that the MSP430 plus display use way below 1mA.
 
If the display looks familiar, that's because it was featured in the Wolverine teaser a few months back
http://www.43oh.com/...cd-boosterpack/
 
My code probably also works with the breakout board that fellow 43oh member reagle designed:
http://forum.43oh.co...akout-for-sale/
 
More information about the display at SHARP:
http://www.sharpmemo...memory-lcd.html
 
According to Mouser LS013B4DN02 is end-of-life. However LS013B4DN04 has very similar specs and should also work with this breakout and code. Both displays are in stock at Mouser:
LS013B4DN02
LS013B4DN04
 
I have two extra PCBs including matching FPC connector (10pos .5mm) sitting in my drawer. PM me if anyone wants one, I'll give or trade them away as long as it's within the US.
 
Regards
Adrian

Always a sucker for displays of any form and shape I ordered one of the 1.35 inch SHARP LS013B4DN02 memory LCD when it made the rounds last year. At $20 apiece it's quite expensive for its size, but it's sooo pretty
 

 
I finally finished up the code and published everything on Github.
https://github.com/a...-memory-display
 
According to the datasheet, this display runs on less than 15uW. I was not able to measure current with my lowly multimeter, so I'm pretty positive that the MSP430 plus display use way below 1mA.
 
If the display looks familiar, that's because it was featured in the Wolverine teaser a few months back
http://www.43oh.com/...cd-boosterpack/
 
My code probably also works with the breakout board that fellow 43oh member reagle designed:
http://forum.43oh.co...akout-for-sale/
 
More information about the display at SHARP:
http://www.sharpmemo...memory-lcd.html
 
According to Mouser LS013B4DN02 is end-of-life. However LS013B4DN04 has very similar specs and should also work with this breakout and code. Both displays are in stock at Mouser:
LS013B4DN02
LS013B4DN04
 
I have two extra PCBs including matching FPC connector (10pos .5mm) sitting in my drawer. PM me if anyone wants one, I'll give or trade them away as long as it's within the US.
 
Regards
Adrian

I just committed an updated version to Github that fixes a glaring bug and adds touch calibration
 
- Bug: Forgot to toggle CS in most places, dooh! (a miracle it ever worked :-)
- Addition: Functions to calibrate touch display. After calibration the StellarisWare touch implementation works just fine with this display

I implemented a Stellaris grlib display driver for Adafruit's 320x240x18 TFT Touch display.
http://adafruit.com/products/335
 
The code can be found on github
https://github.com/a...uit-TFT-ILI9325
 
I tested it only with Lab 10 in the Stellaris Launchpad workshop (w/o touch). Please let me know if you run into issues and I'm glad to fix it.
 
Wiring is a mess as the pins of individual ports are all over the place.
 

 
Regards
Adrian

I implemented a Stellaris grlib display driver for Adafruit's 320x240x18 TFT Touch display.
http://adafruit.com/products/335
 
The code can be found on github
https://github.com/a...uit-TFT-ILI9325
 
I tested it only with Lab 10 in the Stellaris Launchpad workshop (w/o touch). Please let me know if you run into issues and I'm glad to fix it.
 
Wiring is a mess as the pins of individual ports are all over the place.
 

 
Regards
Adrian

This is software IIC master code in C, and C++ using a class and a template. There is also code/class/template for IIC EEPROM and the INA219 voltage/current monitor.
 
There are 4 core functions...

init(); // Init GPIO start(); // Start bit stop(); // Stop bit unsigned ex(unsigned); // Data byte & ack exchange
 
and 3 helper functions that call ex();...

unsigned write(unsigned); // Write a byte & ack, verify unsigned read(); // Read a byte & ack unsigned read_nak(); // Read a byte & nak
 
Creating an instance of the IIC object is different for each code type:

C: T_IIC iic = { BIT1, BIT0, &P2IN, &P2OUT, &P2DIR }; C++ class: CSWIIC iic(BIT1, BIT0, P2IN, P2OUT, P2DIR); C++ template: CSWIIC iic;
 
The C functions require that the IIC structure be passed as the first argument. The C++ class and template use the usual class.function notation.

C: iic_start(&iic); a = iic_write(&iic, ; iic_stop(&iic); C++ class or template: iic.start(); a = iic.write(; iic.stop();
 
This is a disassembly of the start() function for all three versions. The C function and C++ class member function are identical code! The template allows the compiler to do compile time optimization that can not be done with C or C++ class. It is smaller, faster and uses less RAM.
 

iic.zip