NOKIA-3310/5110 LCD library

sielcon · Joined: 16 Mar 2006 Posts: 74 Location: Argentina

I'm going to try it, thanks

sielcon · Joined: 16 Mar 2006 Posts: 74 Location: Argentina

Change the screen and it works perfect.
Smile

rizzo · Joined: 30 Oct 2014 Posts: 7

Hello is it posible with this lib... use pset command.

I also need box write how make this?

Thanks.

sielcon · Joined: 16 Mar 2006 Posts: 74 Location: Argentina

Hello, the truth is that I did not try it, but according to what I saw in the examples, only SETFON, SHOWPIC and LCDAT work, and they were the instructions I used.
Best regards.

ampervadasz78 · Joined: 14 Jul 2016 Posts: 3

Hy!
My little speak engish.
Nokia 5110 wiring problem.

Connetcted Nokia 5110 display <-> 8-channel Bi-directional Logic Level Converter - TXB0108 <-> Atmega 128

Pinout:
Display VCC connect +3,3V
Display GND connect 0V
Display SCE connect logic level converter (A1), (B1) connect Atmega 128 Port D.1
Display RST connect logic level converter (A2), (B2) connect Atmega 128 Port D.0
Display D/C connect logic level converter (A3), (B3) connect Atmega 128 Port D.2
Display DN<MOSI> connect logic level converter (A4), (B4) connect Atmega 128 PortD.3
Display SCLK connect logic level converter (A5), (B5) connect Atmega 128 PortD.4
Display LED -> 100ohm -> +3,3V

Load program Atmega128, not pixel, character, picture display

Display tipe:
https://learn.sparkfun.com/tutorials/graphic-lcd-hookup-guide?_ga=2.209351890.1371307869.1606689616-764629793.1606689616

What I ruined?

Program:

O-Family · Joined: 23 May 2010 Posts: 320 Location: Japan

The same port is used for LCD and KEY.

sielcon · Joined: 16 Mar 2006 Posts: 74 Location: Argentina

Hello everyone, I have a problem with the library that I do not understand, I attach the code and photo of the result. On each line it prints the first character and then continues with the ASCII characters that follow in the list instead of the string sent. If this has happened to anyone, I would appreciate your help. The compiler version is :2.0.8.6
Thank you very much.

O-Family · Joined: 23 May 2010 Posts: 320 Location: Japan

This problem occurs when the AVR chip is ATmega2560.
I think the compiler is probably causing an error when the flash exceeds 64K.
Please contact MCS support with your issue.

albertsm · Joined: 09 Apr 2004 Posts: 5922 Location: Holland

please notice that this is a third party lib. this means that it is not supported by MCS.
The reason is simple : for all supported hardware we have this hardware with documentation, connections, etc.
But for third party libs we do not have the hardware to check possible problems.
In this case i also wonder : which version is it?

when we discover a bug or handle things different we check and modify all libs but only the MCS supported ones.

I noticed you use a PORTL. this is an extended port.
it means cbi/sbi will need a temp register which is r23.
MCS rewrote some libs to use r11 instead of r23 but another option is to protect r23.
in the nokia lib i found this is done in _gwrite_datamisc with push r23 and when the code ends a pop r23

but that is not the proper entry point since now _gwride_cmd and _gwrite_data are not guarded.
so remark/remove the push r23 in _gwrite_datamisc and put it in both _gwrite_cmd and _gwrite_data
both labels end in _gwrite_datamisc so that is not a problem and the pop that exists there you need to keep.

i imagine this solves the problem.

O-Family · Joined: 23 May 2010 Posts: 320 Location: Japan

Mark, thank you for your quick advice.
The issue has been fixed.
I have faced R23 problems several times in the past, but since the problems occur in various patterns, I was late to notice them.
Since this issue is derived from the original library, we will need to continue to fix libraries with the same symptoms.
Please give me some advice at that time.

albertsm · Joined: 09 Apr 2004 Posts: 5922 Location: Holland

original libs are fixed by using R11 for R23.
in this lib you can also do this. R11 is not used with immediate code like LDI so you can simply replace them.
this eliminated the push/pop for r23

then some other remarks.
when the lib is included using $lib and the lib is not compiled/used as LBX you can change : *# into #
I mean for #IF #ENDIF

then LD/ST that use Y or Z with offset like : st y+1 should be written as STD y+1
and LDD for LD
not really important since the compiler and assembler will use proper code. but it is more clear. example you can find in all MCS libs.

thanks for your work and support on the various LCD libs.

sielcon · Joined: 16 Mar 2006 Posts: 74 Location: Argentina

Thank you all very much, it works perfectly.
Kind regards

jure_m · Joined: 14 Jan 2005 Posts: 68 Location: Ljubljana

Hi,

I am driving 84x48 LCD as described on ZL2PD's page with Reset connected to 10k and 4.7uF and CE connected to GND

That all worked well with the libs provided in this thread.

Lately I have got "same" LCDs, but these LCDs do not work at all in the same circuit. They work OK if I use all pins to drive, but shows nothing in my circuit.

So I had to modify LIB in the line 48: Temperature setting to &H08, it was &H06. After that some displays started to work however, I could not change contrast.

So I was wondering if anyone of you had same experience with these changed LCDs?

Best regards
Jure

O-Family · Joined: 23 May 2010 Posts: 320 Location: Japan

The PCD8544 datasheet states that &H08 is an unused command.
There are four types of temperature coefficients: &H04, &H05, &H06, &H07.
There seem to be many compatible controllers for the PCD8544, so there may be differences in commands.

Similarly, we have confirmed that some modules cannot use contrast instructions due to differences in compatible PCD8544 controllers.
This is especially true for the red board type.
However, the contrast command is not available, but the contrast is automatically adjusted even if the power supply voltage changes.

jure_m · Joined: 14 Jan 2005 Posts: 68 Location: Ljubljana

Thanks for explanation O-Family!