Re: auto-detecting the resolution of HD44780-based LCD modules ?
- From: whygee <yg@xxxxx>
- Date: Thu, 12 Nov 2009 02:15:00 +0100
Hello,
and thank you for the answer :-)
D Yuniskis wrote:
whygee wrote:So during power-up, the host CPU/uC can hold the data bus in HiZ,You haven't described *what* you are "reading".
read the 4 bits of data and determine the dimensions.
The handling routines are then updated with correct values
(start addresses etc.).
I.e., is this *the* data bus? Or, a port dedicated
to the display? Or, something else?
I am speaking about a dedicated port.
Very very often, the HD44780-like LCD modules are tied
to the microcontroller with dedicated wires.
The controllers are AFAIK made with very low power,
and slow, silicon, so they are unsuitable for
general purpose communications (the timings are
too slow and could interfere with other faster devices).
Eventually, when the CPU does not have dedicated I/Os,
an external latch is used : look at the LCD tied to
the parallel printer port as an example.
yes, that's the point that was inherent and implicit in myWhat do the readers think about this ? Is there something similar
in the wild ? Is it worth it to modify my modules to implement this
method ? Am I going to get annoying side effects ? (like different
addresses with different makers of modules)
If you are reading a port (or a buffer explicitly decoded)
dedicated to the display, then you have some control over
what else is on that bus.
original post.
If you are just trying to read *the* data bus while (inSure.
theory) *nothing* is on the bus, then you are subject to
whatever else happens to be *on* that bus.
You have to pick your pup/pdn values so that everything<snip>
that might *want* to drive that portion of the bus can handle
the added DC load. You also have to make sure the other
things on the bus don't bias the bus unexpectedly.
Bottom line: the bus isn't a DC device. Make sure youAnother post on Usenet pointed me to the fact that the
understand its AC characteristics as well as the DC impact
of your proposed change.
LCD controller has 125uA pull-ups. I knew I missed a fact or two :-)
This makes my system a bit more power-hungry.
There is the LCD pull-up (equivalent to 40K), then
eventually the configuration SMT resistor (about 10K or less)
and then the CPU/microcontroller must provide more than 1mA
to reverse the data again when needed.
However, detection becomes easier because unmodified modules
will read "1111" and can be handled with certainty. On top of that,
the integrated pull-up make external pull-ups unnecessary
and only pull-downs are needed.
Can't you just burn a byte in your FLASH/ROM that representswith a microcontroller, this amounts to reflashing the memory
the display being used and let your code interpret *that*?
after a recompile, so I see no advantage for field upgrades.
For example, a technician has to carry a computer with
the programming tool, or even bring a new board with new
firmware, just because the LCD module is upgraded :-/
Anyway thank you for the remarks,
I just hoped that my idea was not completely stupid
and it looks almost feasible (at least when power
consumption is not an issue).
YG
--
http://ygdes.com / http://yasep.org
.
- Follow-Ups:
- Re: auto-detecting the resolution of HD44780-based LCD modules ?
- From: D Yuniskis
- Re: auto-detecting the resolution of HD44780-based LCD modules ?
- References:
- auto-detecting the resolution of HD44780-based LCD modules ?
- From: whygee
- Re: auto-detecting the resolution of HD44780-based LCD modules ?
- From: D Yuniskis
- auto-detecting the resolution of HD44780-based LCD modules ?
- Prev by Date: Re: va_args (va_start, va_end, va_list ) souce?
- Next by Date: Re: auto-detecting the resolution of HD44780-based LCD modules ?
- Previous by thread: Re: auto-detecting the resolution of HD44780-based LCD modules ?
- Next by thread: Re: auto-detecting the resolution of HD44780-based LCD modules ?
- Index(es):
Relevant Pages
|