[Lcdproc] lcdserializer problems

[Christian Kruft]

Matteo Pillon schrieb:

>On Mon, Aug 07, 2006 at 12:17:48AM +0200, Christian Kruft wrote:
>  
>
>>I'm going to expand the ASM to work with LCDs which have 4 lines - i.e. 
>>2 Enable-Pins. Do u have any suggestions how  to do?
>>    
>>
>
>Do you really need 2 controllers? 4x20 is usually built with only one
>controller (one enable pin).
>
>  
>
Because my answer tonight was rather short, here a new one. ;) Yes, I 
need this. I got a 20x4 HD44780 compatible with two controllers. Each 
for two lines.

>>I think the driver should send another new byte to select Enable of
>>controller 1 or Enable of controller 2- can u make such a driver?
>>    
>>
>
>I think that wouldn't be too hard to do. Do you really need it?
>
>  
>
>>U can name it "vdr-lcd" and please drop the reinit.
>>    
>>
>
>I tink reinit is useful, because there are not only hd44780 displays
>out there, but also almost-compatible ones, that need a different init
>to work well (like the extended mode of ks0073). Only if you implement a
>way to choose init in the hardware (a jumper, for example), software
>reinit doesn't make sense anymore.
>
>  
>
I don't really know why. The PIC initalizes it with 0x38 or 0x28 like 
lcdproc does. I did a short-circuit of RX/TX and logged the data 
transfered by lcdproc with lcdserializer driver and los-panel. The Init 
sequence ist the same, only the 4/8 bit thing is different (0x28/0x38).

>>Also a full refresh after some time would be great (but pls send a
>>clear before any text).
>>    
>>
>
>Why do you want this?
>  
>
One transmission failure and theres crap on LCD. Maybe it's not really 
needed, but I think it would be great if u can choose it in config.

>>When the driver is working, I could do it easily and make it
>>public. Maybe 0xFC Enable (controller 1) and 0xFD Enable (controller
>>2) ? 0xFE is command mode and 0xFF I use for another thing.
>>    
>>
>
>  
>
Ok, I what do u recommend? I did a hardware-wakeup for a media-pc using 
VDR. While Shutdown, a perl script converts the next recording time and 
the actual time to strings which are send throug the serial line. The 
lcd shows the next wakeup time and the clock. When VDR is up and runnig, 
it could display channel data and so on to the lcd. Theres a lcdproc 
plugin out there. Because of 0xFE is coammand mode, I made the PIC 
reacting to this and switching modes. It now knows if it is data for the 
lcd or a command to set timer. Currently I use 0xFF as escape from 
lcdproc. The PIC now does all incoming data understand as commands. 
Before sending wakeup time and time I kill LCDd and send 0xFE (echo -ne 
'\xFF' > /dev/ttyS0).
This works great at the moment.  But I don't know if 0xFF is ok. I 
thought that wouldn't get used in "normal" transfers to LCD.
I hope u understand what I did - my written English isn't very well.