Menu
▾
▴
lcd4linux-users
|
From: Juergen W. <ju...@wi...> - 2004-03-24 11:32:06
|
Hello, i have some problems with the 0.9.11 Version. Display Hitachi LMG7420 240x128pixel T6963 Chip. Redhat 8 on a 466Celeron Maschine with 256MB Ram lcd4linux.conf: Display TLC1091 Port 0x378 (/dev/ppdev does not work :-( ) Size 40x16 Wire.CE AUTOFD Wire.CD INIT Wire.RD SELECT Wire.WR STROBE Reset on Ground Compilling is ok. But when I start lcd4linux the proggy needs up to 1min to Display something! My CPU Usage is over 50% for lcd4linux!!!! The last 4 columns are only mismatch... :-( When i run LCDproc the CPU Usage is only up to 4%! But the last 4 columns the same mismatch. First I think the Display is not ok. But when i connect the Display to a Windows Maschine and run Lcdhype the complette Display work!!! What's wrong? Greetings Juergen |
|
From: Michael R. <re...@eu...> - 2004-03-26 06:58:04
|
Hi Juergen, > i have some problems with the 0.9.11 Version. > Display Hitachi LMG7420 240x128pixel T6963 Chip. > Redhat 8 on a 466Celeron Maschine with 256MB Ram > lcd4linux.conf: > > Display TLC1091 > Port 0x378 (/dev/ppdev does not work :-( ) It should be /dev/parport0 (old /dev structure) or /dev/parport/0 (devfs) > Compilling is ok. But when I start lcd4linux the proggy needs up to 1min > to Display something! > My CPU Usage is over 50% for lcd4linux!!!! > The last 4 columns are only mismatch... :-( Hmmm... my T6963 works fine, without noticeable CPU load (but I've much faster machines than you). Could you try running lcd4linux with debug enabled (lcd4linux -Fvv) and check for some strange errors? Maybe you want to try the CVS version (but be warned that it is very different from 0.9, take a look at lcd4linux.conf.sample) 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... bye, Michael -- Michael Reinelt Tel: +43 676 3079941 Geisslergasse 4 Fax: +43 316 692343 A-8045 Graz, Austria e-mail: re...@eu... |
|
From: juergen <ju...@wi...> - 2004-03-26 10:56:35
|
Hi Michael, Michael Reinelt wrote: > Hi Juergen, > >> i have some problems with the 0.9.11 Version. >> Display Hitachi LMG7420 240x128pixel T6963 Chip. >> Redhat 8 on a 466Celeron Maschine with 256MB Ram >> lcd4linux.conf: >> >> Display TLC1091 >> Port 0x378 (/dev/ppdev does not work :-( ) > > It should be /dev/parport0 (old /dev structure) or /dev/parport/0 (devfs) > No device! > >> Compilling is ok. But when I start lcd4linux the proggy needs up to >> 1min to Display something! >> My CPU Usage is over 50% for lcd4linux!!!! >> The last 4 columns are only mismatch... :-( > > > Hmmm... my T6963 works fine, without noticeable CPU load (but I've > much faster machines than you). > > 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. > Maybe you want to try the CVS version (but be warned that it is very > different from 0.9, take a look at lcd4linux.conf.sample) > Now, i try the CVS version since Yesterday. It's exact the same Problem. > 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. > > bye, Michael > Bye, Juergen |
|
From: Michael R. <re...@eu...> - 2004-03-31 15:04:33
|
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... |
|
From: juergen <ju...@wi...> - 2004-03-31 19:07:49
|
Hi Michael,
Michael Reinelt schrieb:
> Hi Juergen,
>
> sorry for the delay, I've been on a business journey...
>
no, problem. :-)
>
>> udelay.c: using gettimeofday() delay loop
>
> not that good. But you are using an old processor without TSC...
>
Intel Celeron, 467MHz
>> drv_generic_parport.c: using raw port 0x378
>
> Again, try to switch to ppdev (but this has nothing to do with your
> problem)
It's a long way..... I don't know what's wrong with /dev/ppdev!
>
>> 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...
>
The wiring is from LCDproc and i edit the LCD4linux.conf. The Display
runns with lcdproc too, but with much more CPU-Load an time to display
somethimg....
>> 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
>
I think 150ns for Statuscheck. That's the Problem?
> Can you test lcd4linux on this machine?
>
"I check this! On my Athlon 1800+ / Epoxboard is no Problem, but
with Windows an LCDHype. The Parallel port on this Board provide 5V."
On this maschine runs lcdproc without any Problems (but on both
maschines its only 40x12 possible!) With LCDhype working all "pixel".
But not with Linuxproggys..
At the moment i can't test the Display with lcd4linux on the faster
maschine. The "old" maschine is in the moment really busy with
compilling arts, QT and Kdevelop.....
The Parport on the maschine where the Display works, provide 5V too.
I will test the Display on the faster maschine at the weekend.
bye
Jürgen
|
|
From: Michael R. <re...@eu...> - 2004-04-08 11:19:19
|
Hi Juergen, >>> udelay.c: using gettimeofday() delay loop >> not that good. But you are using an old processor without TSC... >> > Intel Celeron, 467MHz Celerons do not have a TSC? What linux kernel are you using? Could you check the "flags" line from /proc/cpuinfo ? > It's a long way..... I don't know what's wrong with /dev/ppdev! It's not /dev/ppdev, but /dev/parport/0 (devfs) or /dev/parport0, major 99, kernel module ppdev.o > The wiring is from LCDproc and i edit the LCD4linux.conf. The Display > runns with lcdproc too, but with much more CPU-Load an time to display > somethimg.... So lcdproc has the same problem than lcd4linux? >> 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 >> > I think 150ns for Statuscheck. That's the Problem? No, not the 150 ns, but statuscheck does never return, or the status can not be read correctly. >> Can you test lcd4linux on this machine? Did you? bye, Michael -- Michael Reinelt Tel: +43 676 3079941 Geisslergasse 4 Fax: +43 316 692343 A-8045 Graz, Austria e-mail: re...@eu... |
|
From: juergen <ju...@wi...> - 2004-04-08 12:45:38
|
Hi Michael, > > Celerons do not have a TSC? > What linux kernel are you using? Could you check the "flags" line from > /proc/cpuinfo ? > Kernelversion is 2.4.18 on Redhat 8 cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 6 model name : Celeron (Mendocino) stepping : 5 cpu MHz : 467.740 cache size : 128 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr bogomips : 925.52 > It's not /dev/ppdev, but /dev/parport/0 (devfs) or /dev/parport0, > major 99, kernel module ppdev.o modprobe: Can't locate module ppdev.o >> The wiring is from LCDproc and i edit the LCD4linux.conf. The Display >> runns with lcdproc too, but with much more CPU-Load an time to >> display somethimg.... > > So lcdproc has the same problem than lcd4linux? No, no. LCDproc need's only up to 4% >>> 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 >>> >> I think 150ns for Statuscheck. That's the Problem? > > No, not the 150 ns, but statuscheck does never return, or the status > can not be read correctly. > > Can you test lcd4linux on this machine? I Think the last Mail did not reach the right Adress.... :-) > > Did you? > Yes, i did! But its the same Problem! But only up to 25% CPUload...... I don't know what i will do next with this Problem. Since last Weekend i try to make an own Program to check the Problem. But this was not a good Idee.... The only IDE i can use on my faster Maschine is Borlands C++BuilderX. For this i must deinstall Redhat 9 (many Problems with C++BuilderX and Kdevelop 3..) and install SuSE 9.0..... It's a long way to go..... 6 Days work for a C/C++ IDE without problems! Uff! Greetings Jürgen |
|
From: Michael R. <re...@eu...> - 2004-05-22 04:35:14
|
Hi Juergen, sorry for the delay, I've been too busy with my real-life job... >> Celerons do not have a TSC? >> What linux kernel are you using? Could you check the "flags" line from >> /proc/cpuinfo ? >> > Kernelversion is 2.4.18 on Redhat 8 Fine. > /proc/cpuinfo > flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca > cmov pat pse36 mmx fxsr Here we are: TSC is supported. I think the lack of TSC support on your setup comes from the fact that the asm/msr.h file is missing. >> It's not /dev/ppdev, but /dev/parport/0 (devfs) or /dev/parport0, >> major 99, kernel module ppdev.o > > modprobe: Can't locate module ppdev.o try 'modprobe ppdev' (not 'modprobe ppdev.o') You tried to run lcd4linux on another machine. Did you succeed? bye, Michael -- Michael Reinelt Tel: +43 676 3079941 Geisslergasse 4 Fax: +43 316 692343 A-8045 Graz, Austria e-mail: re...@eu... |
|
From: juergen <ju...@wi...> - 2004-03-26 11:07:08
|
Sorry, i've forgotten something.... Version 0.10.0 starting plugin_cfg.c: Variable minute = '60000' (60000.000000) plugin_cfg.c: Variable tack = '100' (100.000000) plugin_cfg.c: Variable tick = '500' (500.000000) lcd4linux.c: initializing driver T6963 T6963: using model 'generic' udelay.c: using gettimeofday() delay loop drv_generic_parport.c: using raw port 0x378 T6963: wiring: [DISPLAY:CE]<==>[PARPORT:AUTOFD] T6963: wiring: [DISPLAY:CD]<==>[PARPORT:INIT] T6963: wiring: [DISPLAY:RD]<==>[PARPORT:SELECT] T6963: wiring: [DISPLAY:WR]<==>[PARPORT:STROBE] drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 ...... *snip* drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 320 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 1 of 320 drv_T6963.c: hang in status2 ...... *snip* drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 319 of 320 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 2560 drv_T6963.c: hang in status2 ...... *snip* drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 2559 of 2560 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 320 drv_T6963.c: hang in status2 ...... *snip* drv_T6963.c: bug occured at byte 319 of 320 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 2560 drv_T6963.c: hang in status2 ...... *snip* drv_T6963.c: bug occured at byte 2559 of 2560 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 initializing layout 'L24x8' lcd4linux.c: starting main loop drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 10, addr=0 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 1 of 10, addr=0 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 2 of 10, addr=0 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 3 of 10, addr=0 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 4 of 10, addr=0 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 5 of 10, addr=0 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 6 of 10, addr=0 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 7 of 10, addr=0 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 8 of 10, addr=0 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 10, addr=40 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 1 of 10, addr=40 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 2 of 10, addr=40 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 3 of 10, addr=40 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 4 of 10, addr=40 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 5 of 10, addr=40 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 6 of 10, addr=40 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 8 of 10, addr=40 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 9 of 10, addr=40 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 10, addr=80 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 1 of 10, addr=80 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 4 of 10, addr=80 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 5 of 10, addr=80 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 6 of 10, addr=80 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 7 of 10, addr=80 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 8 of 10, addr=80 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 9 of 10, addr=80 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 10, addr=120 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 1 of 10, addr=120 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 2 of 10, addr=120 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 3 of 10, addr=120 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 5 of 10, addr=120 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 6 of 10, addr=120 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 7 of 10, addr=120 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 8 of 10, addr=120 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 9, addr=160 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 1 of 9, addr=160 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 2 of 9, addr=160 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 4 of 9, addr=160 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 5 of 9, addr=160 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 6 of 9, addr=160 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 7 of 9, addr=160 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 8 of 9, addr=160 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 9, addr=200 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 1 of 9, addr=200 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 2 of 9, addr=200 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 3 of 9, addr=200 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 4 of 9, addr=200 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 5 of 9, addr=200 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 6 of 9, addr=200 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 7 of 9, addr=200 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 10, addr=240 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 5 of 10, addr=240 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 6 of 10, addr=240 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 1, addr=10 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 1, addr=50 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 1, addr=90 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 1, addr=130 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 1, addr=170 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 1, addr=210 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 1, addr=250 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 ...... *snip* drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 2, addr=55 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 2, addr=95 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 2, addr=135 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in status2 drv_T6963.c: bug occured at byte 0 of 1, addr=15 drv_T6963.c: hang in status2 drv_T6963.c: hang in status1 drv_T6963.c: hang in status1 drv_T6963.c: hang in >>>Break with CNTRL + C Segmentation fault |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X