Comments on: Interfacing LCD via SPI.

By: oleg

oleg — Fri, 11 May 2012 19:59:51 +0000

The delays are pretty short here. If you need to eliminate them altogether, you can read D7 to detect the end of operation.

By: Michael

Michael — Fri, 11 May 2012 07:43:42 +0000

Great Post. I have build this interface and is working!! Thanks. I would like to know if you can help me incorporate this algorhytm into real time(No RTOS)(No Waits/Delays) Thanks Again

By: sdb

sdb — Thu, 02 Feb 2012 06:24:35 +0000

And you can use one of the currently unused outputs of the ’565 to control the backlight of the LCD. (Might also need a transistor current amplifier and/or a current limiting resistor.) Too bad the board doesn’t have routing for that. (My LCD has a 16 pin DIL header, some have 16 pin SIL.)

By: Bryan Mayland

Bryan Mayland — Tue, 27 Dec 2011 18:38:39 +0000

The reason I brought it up is because I have implemented the same circuit using an ATmega and for some reason it only works reliably if the software is written the way you have. If I do 3 SPI transfers (value, value | E, value) I eventually end up with the LCD being shifted off in that the last nibble of the previous byte write is being interpreted with the first nibble of the current byte write. I thought maybe you had seen the same behavior and perhaps adapted your code to fit. I think I’ll just follow your experience and ignore the datasheet for what actually works. Thanks!

By: oleg

oleg — Tue, 27 Dec 2011 17:14:18 +0000

You are right – per datasheet, the data and RS must be valid some time before E strobe. However, setting E, RS and data at the same time works fine for all HD44780-compatible displays I’ve seen so far.

You can change LCD_sendbyte() to do “set E”, “clear E” to “clear E”, “set E”, if you want the signals to appear per datasheet.

By: Bryan Mayland

Bryan Mayland — Tue, 27 Dec 2011 15:50:56 +0000

In your “Software. Low-level functions.” section, step 4 says to send the variable over SPI (with the enable bit not set). Looking at your LCD_sendbyte() method, you skip step 4 and the first transfer over SPI has the enable bit set. Same thing for step 10. The algorithm says there should be 3 SPI transfers per nibble but LCD_sendbyte() only has 2 SPI transfers per nibble.

Is this intentional? The LCD controller latches RS on the rising edge of E so theoretically it could “miss” RS if the RS and E bits are set simultaneously in the first transfer.

By: oleg

oleg — Thu, 08 Dec 2011 15:47:09 +0000

It’s right there in the article.

By: A. Rafay

A. Rafay — Thu, 08 Dec 2011 10:46:53 +0000

Hi everyone,
can anybody please share the CIRCUIT DIAGRAM of SPI (pic 18f452).
actually I just want to check the code given above. i need it for my FYP(Final Year Project).

By: SEB

SEB — Sun, 30 Oct 2011 02:58:51 +0000

bsr oleg ,je travaille avec STM32F100RB ,je souhaite contrôler un module d’affichage à base de MAX7219
http://www.mikroe.com/eng/products/view/163/serial-7-seg-display-2-board/ via l’interface SPI;
et Implémenter un compteur piloté par les appuis du bouton USER.
en utilisant les périphériques: SPI et GPIO.est ce que vous pouvez m aider à ce propos v que je suis nouveau avec les STM32

By: oleg

oleg — Fri, 14 Oct 2011 15:34:24 +0000

Yes, you need to follow proper bit order. Usually, you set bit order once during init.