Currently, my pin assignments are: 11-SID (MOSI), 13-SCK, 9-A0/RS, 6-RST, 10-CS

I uncommented line 54 (U8GLIB_LM6059) in the HelloWorld example program for the u8glib library.  When I upload the HelloWorld program with this modification, nothing is displayed.  If I then upload the dogm128 example program GraphicTest, it works as expected.

Did you also added the reset pin? Instead of

Code:

//U8GLIB_LM6059 u8g(13, 11, 10, 9);                    // SPI Com: SCK = 13, MOSI = 11, CS = 10, A0 = 9

use

Code:

U8GLIB_LM6059 u8g(13, 11, 10, 9, 6);                    // SPI Com: SCK = 13, MOSI = 11, CS = 10, A0 = 9

If the LM6059 device does not work, it might be also interesting to see if the LM6063 will show something on the display:

Code:

U8GLIB_LM6063 u8g(13, 11, 10, 9, 6);

I am glad that the dogm128 lib works.

Documentation: Will sent PM.

Oliver

It seems that the Adafruit display is a TOPWAY LM6059 display.
I have added an experimental device to the u8glib: http://code.google.com/p/u8glib/downloads/list
So you could try the U8GLIB_LM6059() constructor with the Adafruit display. Please let me know if this works.

Thanks for testing!

Oliver

Many displays from a mobile phone have an integrated controller.

Have a look here:
http://www.module.ro/nokia_3510.html
There are also pages on other (none nokia) cell phones too.

Once you know the controller, you can search for a library.

Oliver

Hi

There had been one person who contributed the Adafruit code for the dogm128 lib. I know that it once worked, but I do not own this device, so I am not able to maintain it. I only know, that it was different to the other displays with same controller.

The U8glib does not include the specific code for the Adafruit device. Maybe I can port the code from dogm128 to u8glib. But then I would need someone else to test it.

A0 pin:
It is always there, but often named different. Identical are:
RS: Register Select
DI: Data / Instruction

So A0, RS, DI are all the same.

Oliver

Finally, U8glib writes to my ST7920 display. The latest version v0.09 supports ST7920 displays:
http://code.google.com/p/u8glib/downloads/list

I did not do any FPS measures 

Oliver

Maybe you can give a more precise information which display you have.

Oliver

Hi

What I see at the moment: There are several vendors for displays which fit into the Arduino World. All come with some software for the Arduino IDE. However the documentation for this "vendor software" often is, hmm, not so good. Sometimes I think that the hardware is sold with some software just to prove that the hardware is working.

Luckily there is this forum, where people not only try to give good answers, but also try to create a good documentation for their software (thinking of Bill's GLCD documentation for the KS0108 devices).

I try to do the same for the ST7565 devices. The first version of this ST7565 lib is here:
http://code.google.com/p/dogm128/
There is also a reference manual and examples here:
http://code.google.com/p/dogm128/wiki/cpp

I am currently working on a new, more general lib for ST7565 (and similar) devices:
http://code.google.com/p/u8glib/
While still beta, the ST7565 support should be fine. Additionally to the reference manual (http://code.google.com/p/u8glib/wiki/userreference) I started to write tutorials to discuss special parts of the library (http://code.google.com/p/u8glib/wiki/thelloworld).

Oliver

@Bill

Yes sure, I fully agree: FPS is difficult to measure and dangerous to compare. I just wanted to say, that I am very confident that U8glib will be faster than 1 FPS.

@dc42
I agree, shiftOut is very slow. There had been some discussion about improvements here. I also wrote my high speed version. I guess for the atmega328 HW SPI is always faster than SW SPI. Things change with the PIC32 of a ChipKit board. SW SPI has equal speed. Indeed, I had to slow down SW SPI, otherwise speed is above specification and i indeed go dropouts on the display.

There is only one issue with the Atmel HW SPI subsystem. Of course we need clock and data out lines. But additionally the HW SPI subsystem occupies the "data in" line. So we loose one line here (at least to what i know, and i never was able to use this pin for something else)
 
Oliver

Just to clarify my initial post on u8glib: It does not use a full frame buffer, it does not need read access to the display memory, it works fine with SPI, it usually has 20 and more frame per second. But unfortunately there is no low level driver for the ST7920 at the moment...

Oliver

Hi

U8glib does not yet support this controller. I have a display with this controller here. I always wanted to build something with it, but did not do so until no. So, there is no driver for the ST7920 yet.

SPI: Usually HW SPI is faster, especially for a slow CPU. I did not measure parallel bus yet.

Oliver

Hi Chris

Thats all good news.
I modified the code in the u8glib repository so that it matches your code.

However, I also did this:

You may also replace 0x0a3 in line 80 by 0x0a2, which was suggested in the lm6063 datasheet.

This could improve the contrast a little bit.

Font:
Use the setFont member procedure to assign a font:
http://code.google.com/p/u8glib/wiki/userreference#setFont

Fonts are described here:
http://code.google.com/p/u8glib/wiki/fontgroup

All fonts start with "u8g_font_". For example "u8g_font_osr18" will select the "OldStandard" font with a capital A of 18 pixel height. Note, that not all pixel heights are available, but this is all documented in the wiki pages. There should be a screenshot for every font.

Console Example:
Thanks for the hint and, well, all is still beta. I have created an issue tracker for that and will check it.
Also thanks for the Arduino 1.0 correction.

Pin/Wiring:
No issue, you can select whatever pins are suitable for you.

Oliver

Hi
With my (similar) displays, I usually see more than 15 frames per seconds with Arduino Uno. I once reached 73 fps with a ChipKit Uno and a serial dogs102 display.

I could assist you to write a low level driver for http://code.google.com/p/u8glib/
There should also be a st7920 in my lab, but i did not have time until now to wire it and write that low level driver.

Oliver

Hi

As far as i see things, there are two options:

1. M2TKLIB
http://code.google.com/p/m2tklib/
use the STRLIST element

2. Liudr's Library
http://liudr.wordpress.com/libraries/phi_prompt/

Oliver

Hi

Es gibt drei Ansätze:
1. Zero Ram Libraries
Achtung: Nur möglich, wenn das Display es erlaubt Daten zurückzulesen. Vereinfacht: Displays mit 8 Bit Bus erlauben das, Displays mit SPI Erlauben kein Auslesen des Displayrams.
Beispiel: http://code.google.com/p/glcd-arduino/
Funktionsweise: Pixel werden direkt in den Displayram geschrieben

2. Full Frame Lib
Es wird im RAM des Controllers eine Kopie des Display Frame Buffers angelegt.
Pixel/Text wird erst in das Arduino RAM geschrieben und dann zum Display kopiert.
Dieser Ansatz verbaucht tatsächlich viel RAM.
Beispiel: https://github.com/adafruit/ST7565-LCD/tree/master/ST7565

3. Hybridansätze mit reduziertem RAM-Verbrauch.
Funktionsweise: http://code.google.com/p/u8glib/wiki/tpictureloop
Der RAM verbrauch hängt vom Treiber und Display ab. Für die u8glib habe ich das hier angegeben: http://code.google.com/p/u8glib/wiki/device
Beispiele: http://code.google.com/p/u8glib/, http://code.google.com/p/dogm128/

Oliver



3.

Hi

However, everything is mirrored!

Sure, i just copied the adafruit init sequence.
Please do the following:
1. Locate file u8g_dev_st7565_lm6063.c (.../libraries/U8glib/utility/...)
2. Try: Replace 0x0a0 with 0x0a1 (line  81), then compile and check if you see improvements
3. Try: Replace 0x0c0 with 0x0c8 (line 82), then compile and check if you see improvements

Please let me know, if 2. or 3. or both will lead to the correct result.

You may also replace 0x0a3 in line 80 by 0x0a2, which was suggested in the lm6063 datasheet.

BTW: your display is fine. The missing 4 lines are because of the fact, that the controller has a 132x64 memory, but the LCD itself is 128x64. While mirrored, we write to the 4 invisible rows.

Oliver