Tom,
Your observations are correct. All you need to do is write the low level driver with function names matching what is expected with graphics.lib (just use SED133F.lib as a template). No changes are needed to graphic.lib or glmenu.lib.
I think it is real neat how this is arranged, i.e. someone’s actually put a fair bit of thought into it.
Regards,
Nathan
-----Original
Message-----
From: r...@yahoogroups.com
[mailto:r...@yahoogroups.com] On
Behalf Of Tom Collins
Sent: Wednesday,
29 June 2005
10:16
AM
To: r...@yahoogroups.com
Subject: [rabbit-semi] Using
GRAPHIC.LIB with non-Zworld display
I'm currently modifying my hardware to use a 128x64 graphic display instead of the current 20x4 character display. As I was planning the interface to the LCD, I noticed that DC includes some libraries related to graphic displays.
My display uses a Epson S1D10605 controller, which appears to be a fairly common memory-mapped interface where I can simply read and write to either a control or data address. I've checked the timing diagrams, and they appear to be compatible with the RCM2200 I'm using. I'll find out soon enough when my dev hardware is complete.
It would appear that I can simply write my own version of MSCG12232.lib/SED133F.LIB and then make use of the GRAPHIC.LIB library and fonts. I've printed up documentation for Zworld's LCD/Keypad module which gives a pretty decent overview of the functions in GRAPHIC.LIB.
Can anyone offer feedback on using GRAPHIC.LIB, or in creating the glue code between it and the actual display? How about GLMENU.LIB?
Is there more Zworld documentation, possibly including screen shots of GRAPHIC.LIB and GLMENU.LIB in action?
--
Tom Collins - t...@tomlogic.com
Certified Rabbit Semiconductor Consultant based in Napa, California
Info on the Sniffter, a rechargeable, hand-held Network Tester
powered by the RCM2210: http://sniffter.com/