Re: [lcd4linux] T6963 High CPU Usage....

[Michael R. <re...@eu...>]

Hi Juergen,

sorry for the delay, I've been on a business journey...

>> Could you try running lcd4linux with debug enabled (lcd4linux -Fvv) 
>> and check for some strange errors?
>>
> Yes i do. See at the end of the Mail.

> Version 0.10.0 starting
Fine. This is the CVS version

> lcd4linux.c: initializing driver T6963
Ok
> T6963: using model 'generic'
Ok
> udelay.c: using gettimeofday() delay loop
not that good. But you are using an old processor without TSC...

> drv_generic_parport.c: using raw port 0x378
Again, try to switch to ppdev (but this has nothing to do with your problem)

> T6963: wiring: [DISPLAY:CE]<==>[PARPORT:AUTOFD]
> T6963: wiring: [DISPLAY:CD]<==>[PARPORT:INIT]
> T6963: wiring: [DISPLAY:RD]<==>[PARPORT:SELECT]
> T6963: wiring: [DISPLAY:WR]<==>[PARPORT:STROBE]
Is this ok? Please triple-check your wiring, 98% of all error reports I 
get come from wrong wirings...

> drv_T6963.c: hang in status1
> drv_T6963.c: hang in status2
> drv_T6963.c: bug occured at byte 0 of 320

Here we are: This means that the "busy check" does not work for you. The 
T6963 requires this busy checking, which means it has to read values 
back from the parallel port. The message "hang in status.." is emitted 
when the busy-check does not success after a certain amount of time

>> Another point may be that the T6963 is very sensitive to signal 
>> levels. It uses TTL levels (0V/5V), where many newer parallel ports 
>> provide 3.3V only. I built a special circuits with two additional IC's 
>> for this...
> 
> I check this! On my Athlon 1800+ / Epoxboard is no Problem, but with 
> Windows an LCDHype. The Parallel port on this Board provide 5V.

Can you test lcd4linux on this machine?


bye, Michael

-- 
Michael Reinelt                                   Tel: +43 676 3079941
Geisslergasse 4                                   Fax: +43 316  692343
A-8045 Graz, Austria                          e-mail: re...@eu...