@m_K_o:
There's a test screen in the menu. Can you try that? I'll update your dpf's details to superelchi for a code commit. I believe the usb errors you are facing is due to the rpi's... is yours a revision 1 of the board and do you have sufficient power supply (1A and more) or many peripherals plugged to the usb ports?
Photo keyring as screen
- Posts: 52
- Joined: Sat Jun 16, 2012 2:55 pm
ax206geek wrote:mm1804 wrote:I tried several times to get this working (pearl DPF @ Raspberry PI) but all of the howtos are not working/ have errors in the steps and so on.
Thanks a lot!
MM1804
And what errors did you encounter?
all I tried did not really lead to any sucess because I got stuck somewhere with different problems (so no specific error message)
Thats why I was wondering if somebody could briefly note down his steps how he got this working...
- Posts: 4
- Joined: Sun Jul 15, 2012 2:54 pm
Hi all,
I'm here now once registered for 2 days because I also have a RaspberryPi.
Wanted my already finished patched display (from Pearl.de the AX206), which had been running perfectly on my Fritzbox connect to the RPi but unfortunately I get the same error as "mm1804". I have tried everything what is suggested in the thread.
So a Y-USB cable I used to run and I get the following error from LCD4Linux ...
I have even compiled lcd4linux me download a pre-built version, but always the same error.
I hope anybody can help me
Sorry for my not perfect English. I am from Germany.
greetz bimmi
I'm here now once registered for 2 days because I also have a RaspberryPi.
Wanted my already finished patched display (from Pearl.de the AX206), which had been running perfectly on my Fritzbox connect to the RPi but unfortunately I get the same error as "mm1804". I have tried everything what is suggested in the thread.
So a Y-USB cable I used to run and I get the following error from LCD4Linux ...
- Code: Select all
pi@raspberrypi ~/dpf $ sudo ./lcd4linux -Fvv -f lcd.conf
LCD4Linux 0.11.0-SVN-1168 starting
Dump of lcd.conf:
Display 'DPF'
Display:DPF.Background '000000'
Display:DPF.Basecolor '000099'
Display:DPF.Driver 'DPF'
Display:DPF.Font '6x8'
Display:DPF.Foreground 'ffffff'
Display:DPF.Port 'usb0'
Display:DPF.Size '128x128'
Layout 'Simple'
Layout:Simple.Row01.Col01 'HELLO'
Widget:HELLO.align 'L'
Widget:HELLO.Background 'ffffff'
Widget:HELLO.class 'Text'
Widget:HELLO.expression 'Hello World.'
Widget:HELLO.Foreground '000000'
Widget:HELLO.update 5000000
Widget:HELLO.width 12
lcd4linux.c: initializing driver DPF
Found AX206 DPF
Got LCD dimensions: 320x240
bulk write: Resource temporarily unavailable
initializing layout 'Simple'
layout.c: Layout:Simple: migrating 'row01.col01' to 'Layer:1.row01.col01'
Creating new timer group (0 ms)
widget 'HELLO': Class 'text', Parent '<root>', Layer 1, Row 0, Col 0 (to 0,0)
lcd4linux.c: starting main loop
Removing timer group (0 ms)
Timer #0 skipped 2147483647 interval(s) or 0 ms.
Huh? Not even a single timer left? Dazed and confused...
lcd4linux.c: leaving main loop
DPF: shutting down.
[b]bulk write: Resource temporarily unavailable
bulk write: Resource temporarily unavailable
bulk write: Resource temporarily unavailable
bulk write: Resource temporarily unavailable[/b]
drv_dpf.c: closing connection
I have even compiled lcd4linux me download a pre-built version, but always the same error.
- Code: Select all
bulk write: Resource temporarily unavailable
I hope anybody can help me
Sorry for my not perfect English. I am from Germany.
greetz bimmi
- Posts: 8
- Joined: Sun Oct 14, 2012 5:21 pm
Try a powered USB hub. / Versuch's mit einem stromgespeisten USB-Hub.
mit Eiskrem
mit Eiskrem
with ice cream wrote:Try a powered USB hub. / Versuch's mit einem stromgespeisten USB-Hub.
mit Eiskrem
Thank you, the Display is on a active Hub. At the moment I'll try to flash the new 0.3 Firmware / Ohne aktiven Hub startet der Display gar nicht... Gerade Kompilier ich die neue Firmware und teste dann nochmal...
Edit: no funktion. same problem. / Keine funktion, selbes Problem.
- Posts: 8
- Joined: Sun Oct 14, 2012 5:21 pm
I've tried two different active USB hub, felt 20 cable and it does not work as before. Slowly, I think it is really the Pi I have the first revision. (02 CPU code). Also tried two different power supplies tested at Pi.
Ich hab zwei verschiedene aktive USB Hubs versucht, gefühlte 20 Kabel und es funktioniert nach wie vor nicht. Langsam glaub ich es liegt wirklich am Pi. Ich habe die erste Revision. (02 CPU Code). Auch hab ich zwei verschiedene Netzteile am Pi ausprobiert.
Ich hab zwei verschiedene aktive USB Hubs versucht, gefühlte 20 Kabel und es funktioniert nach wie vor nicht. Langsam glaub ich es liegt wirklich am Pi. Ich habe die erste Revision. (02 CPU Code). Auch hab ich zwei verschiedene Netzteile am Pi ausprobiert.
- Posts: 8
- Joined: Sun Oct 14, 2012 5:21 pm
superelchi has released a major upgrade to dpf-ax, please see this from changelog:
He had to change the init code for all dpfs. Because he have access only to a limited number of frames, most of the changes were done "blind".
So: please test the new version with your dpfs and post any findings (working / not working) for the different models: http://forum.doozan.com/read.php?9,9915
http://dpf-ax.svn.sourceforge.net/ to grab the changes.
Support for model specific contrast init.
* Dpf type definition moved from config.h to ./lcd/TYPE/dpfmodel.h.
* New: knowntypes_builder.py builds type info from definitions in lcd/$(TYPE)/dpfmodel.h:
- fw/knowntypes.py - for use by identify.py
- fw/knowntypes.html - simple html page listing all supported dpfs.
* Identify.py rewrite:
- Commandline options (-v = verbose, -d = developer support) replace manual dev_mode editing.
- Extended developer support by putting dump-snipppets and disassembler-scripts in folder fw/identify.out.
- Detection of default brightness / contrast value.
- Better identification of models mit non-standard init ("fake" CRC generation).
- Replaced knowdpfs.py with autogenerated knowntypes.py (see knowtypes_builder.py).
* Shebang added to all python scripts in folder fw.
* Hint to use hiddetach if dpf is claimed by hid added to rawusb.c
* Modelname change:
- pearl -> pearl_portrait
- pearl_landscape -> pearl
- focal -> focal_portrait
- focal_landscape -> focal
* New model:
- acme_2
- delightdigi_black_portrait
- jovisa
- linkdelight_2
- linkdelight_3
- pearl_custom
He had to change the init code for all dpfs. Because he have access only to a limited number of frames, most of the changes were done "blind".
So: please test the new version with your dpfs and post any findings (working / not working) for the different models: http://forum.doozan.com/read.php?9,9915
http://dpf-ax.svn.sourceforge.net/ to grab the changes.
- Posts: 52
- Joined: Sat Jun 16, 2012 2:55 pm
bimmi wrote:
- Code: Select all
Widget:HELLO.update 5000000
Creating new timer group (0 ms)
widget 'HELLO': Class 'text', Parent '<root>', Layer 1, Row 0, Col 0 (to 0,0)
lcd4linux.c: starting main loop
Removing timer group (0 ms)
Timer #0 skipped 2147483647 interval(s) or 0 ms.
Huh? Not even a single timer left? Dazed and confused...
The lcd4linux line for HELLO.update makes no sense and hence lcd4linux complained about the timer.
- Posts: 52
- Joined: Sat Jun 16, 2012 2:55 pm
mm1804 wrote:
Thats why I was wondering if somebody could briefly note down his steps how he got this working...
http://geekparadise.de/2011/04/digitale ... -dockstar/
has slightly outdated instructions. You can try to find my earlier posts in this same thread.
- Posts: 52
- Joined: Sat Jun 16, 2012 2:55 pm
ax206geek wrote:bimmi wrote:
- Code: Select all
Widget:HELLO.update 5000000
Creating new timer group (0 ms)
widget 'HELLO': Class 'text', Parent '<root>', Layer 1, Row 0, Col 0 (to 0,0)
lcd4linux.c: starting main loop
Removing timer group (0 ms)
Timer #0 skipped 2147483647 interval(s) or 0 ms.
Huh? Not even a single timer left? Dazed and confused...
The lcd4linux line for HELLO.update makes no sense and hence lcd4linux complained about the timer.
The problem is not the HELLO.update. The problem is "bulk write: Resource temporarily unavailable".
I tested this with several lcd4linux.conf - same problem.
- Posts: 8
- Joined: Sun Oct 14, 2012 5:21 pm
- Posts: 52
- Joined: Sat Jun 16, 2012 2:55 pm
Thank you.
There are many many errors. Tooo much befor i can press CtrlC to brake them. This is the log from putty.
The Display will reboot when the message "bulk write: Resource temporarily unavailable" came.
There are many many errors. Tooo much befor i can press CtrlC to brake them. This is the log from putty.
The Display will reboot when the message "bulk write: Resource temporarily unavailable" came.
- Code: Select all
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2012.10.17 17:02:45 =~=~=~=~=~=~=~=~=~=~=~=
sudo ./lcd4linux -Fvv -f lcd.conf
LCD4Linux 0.11.0-SVN-1168 starting
Dump of lcd.conf:
Display 'DPF'
Display:dpf.Background '000000'
Display:dpf.Backlight backlight
Display:dpf.Basecolor '000000'
Display:dpf.Driver 'DPF'
Display:dpf.Font '6x8'
Display:dpf.Foreground 'ffffff'
Display:dpf.Orientation 3
Display:dpf.Port 'usb0'
Layout 'mylayout'
Layout:mylayout.Layer:2.X1.Y1 'Bgnd'
Layout:mylayout.Row01.Col01 'OS'
Layout:mylayout.Row02.Col02 'CPU'
Layout:mylayout.Row03.Col10 'RAM'
Layout:mylayout.Row05.Col01 'Busy'
Layout:mylayout.Row06.Col01 'BusyBar'
Layout:mylayout.Row07.Col01 'Load'
Layout:mylayout.Row08.Col01 'LoadBar'
Layout:mylayout.Row09.Col01 'Disk'
Layout:mylayout.Row10.Col01 'DiskBar'
Layout:mylayout.Row11.Col01 'Eth0'
Layout:mylayout.Row12.Col01 'Eth0Bar'
Layout:mylayout.Row16.Col01 'Uptime'
Variables.backlight 2
Variables.minute 60000
Variables.tack 200
Variables.tick 500
Widget:Busy.align 'R'
Widget:Busy.Background 'FFFFFF00'
Widget:Busy.class 'Text'
Widget:Busy.expression proc_stat::cpu('busy', 500)
Widget:Busy.Foreground 'ffffff'
Widget:Busy.postfix '%'
Widget:Busy.precision 1
Widget:Busy.prefix 'Busy'
Widget:Busy.update tick
Widget:Busy.width 10
Widget:BusyBar.Background '00000080'
Widget:BusyBar.BarColor0 '5f5fff'
Widget:BusyBar.BarColor1 'ff5f5f'
Widget:BusyBar.class 'Bar'
Widget:BusyBar.direction 'E'
Widget:BusyBar.expression proc_stat::cpu('busy', 500)
Widget:BusyBar.expression2 proc_stat::cpu('system', 500)
Widget:BusyBar.Foreground 'ffffff'
Widget:BusyBar.length 21
Widget:BusyBar.update tack
Widget:CPU.align 'L'
Widget:CPU.Background 'FFFFFF00'
Widget:CPU.class 'Text'
Widget:CPU.expression uname('machine')
Widget:CPU.prefix 'CPU '
Widget:CPU.update tick
Widget:CPU.width 10
Widget:Disk.align 'R'
Widget:Disk.Background 'FFFFFF00'
Widget:Disk.class 'Text'
Widget:Disk.expression diskstats('hd.', 'read_sectors', 500) + diskstats('hd.', 'write_sectors', 500)
Widget:Disk.Foreground 'ffffff'
Widget:Disk.postfix ' '
Widget:Disk.precision 0
Widget:Disk.prefix 'disk'
Widget:Disk.update tick
Widget:Disk.width 10
Widget:DiskBar.Background '00000080'
Widget:DiskBar.BarColor0 '5f5fff'
Widget:DiskBar.BarColor1 'ff5f5f'
Widget:DiskBar.class 'Bar'
Widget:DiskBar.direction 'E'
Widget:DiskBar.expression diskstats('sd.', 'read_sectors', 500)
Widget:DiskBar.expression2 diskstats('sd.', 'write_sectors', 500)
Widget:DiskBar.Foreground 'ffffff'
Widget:DiskBar.length 21
Widget:DiskBar.update tack
Widget:Eth0.align 'R'
Widget:Eth0.Background 'FFFFFF00'
Widget:Eth0.class 'Text'
Widget:Eth0.expression (netdev('wlan0', 'Rx_bytes', 500)+netdev('wlan0', 'Tx_bytes', 500))/1024
Widget:Eth0.Foreground 'ffffff'
Widget:Eth0.postfix ' '
Widget:Eth0.precision 0
Widget:Eth0.prefix 'wlan0'
Widget:Eth0.update tick
Widget:Eth0.width 10
Widget:Eth0Bar.Background '00000080'
Widget:Eth0Bar.BarColor0 '5f5fff'
Widget:Eth0Bar.BarColor1 'ff5f5f'
Widget:Eth0Bar.class 'Bar'
Widget:Eth0Bar.direction 'E'
Widget:Eth0Bar.expression netdev('wlan0', 'Rx_bytes', 500)
Widget:Eth0Bar.expression2 netdev('wlan0', 'Tx_bytes', 500)
Widget:Eth0Bar.Foreground 'ffffff'
Widget:Eth0Bar.length 21
Widget:Eth0Bar.update tack
Widget:Load.align 'R'
Widget:Load.Background 'FFFFFF00'
Widget:Load.class 'Text'
Widget:Load.expression loadavg(1)
Widget:Load.Foreground 'ffffff'
Widget:Load.postfix loadavg(1)>1.0?'!':' '
Widget:Load.precision 1
Widget:Load.prefix 'Load'
Widget:Load.update tick
Widget:Load.width 10
Widget:LoadBar.Background '00000080'
Widget:LoadBar.BarColor0 '5f5fff'
Widget:LoadBar.BarColor1 'ff5f5f'
Widget:LoadBar.class 'Bar'
Widget:LoadBar.direction 'E'
Widget:LoadBar.expression loadavg(1)
Widget:LoadBar.Foreground 'ffffff'
Widget:LoadBar.length 21
Widget:LoadBar.max 2.0
Widget:LoadBar.update tack
Widget:OS.align 'M'
Widget:OS.Background '008000'
Widget:OS.class 'Text'
Widget:OS.expression '*** '.uname('sysname').' '.uname('release').' - dpf driver by hackfin ***'
Widget:OS.Foreground 'ffffff'
Widget:OS.speed 200
Widget:OS.update tick
Widget:OS.width 21
Widget:RAM.align 'R'
Widget:RAM.Background 'FFFFFF00'
Widget:RAM.class 'Text'
Widget:RAM.expression meminfo('MemTotal')/1024
Widget:RAM.postfix ' MB RAM'
Widget:RAM.precision 0
Widget:RAM.update tick
Widget:RAM.width 11
Widget:Uptime.align 'R'
Widget:Uptime.Background 'FFFFFF00'
Widget:Uptime.class 'Text'
Widget:Uptime.expression uptime('%d days %H:%M:%S')
Widget:Uptime.prefix 'Up '
Widget:Uptime.update 1000
Widget:Uptime.width 20
plugin_cfg.c: Variable backlight = '3.70249e-314' (3.70249e-314)
plugin_cfg.c: Variable minute = '3.34104e-313' (3.34104e-313)
plugin_cfg.c: Variable tack = '1.64345e-313' (1.64345e-313)
plugin_cfg.c: Variable tick = '1.85565e-313' (1.85565e-313)
lcd4linux.c: initializing driver DPF
Found AX206 DPF
Got LCD dimensions: 320x240
bulk write: Resource temporarily unavailable
initializing layout 'mylayout'
layout.c: Layout:mylayout: migrating 'row01.col01' to 'Layer:1.row01.col01'
layout.c: Layout:mylayout: migrating 'row02.col02' to 'Layer:1.row02.col02'
layout.c: Layout:mylayout: migrating 'row03.col10' to 'Layer:1.row03.col10'
layout.c: Layout:mylayout: migrating 'row05.col01' to 'Layer:1.row05.col01'
layout.c: Layout:mylayout: migrating 'row06.col01' to 'Layer:1.row06.col01'
layout.c: Layout:mylayout: migrating 'row07.col01' to 'Layer:1.row07.col01'
layout.c: Layout:mylayout: migrating 'row08.col01' to 'Layer:1.row08.col01'
layout.c: Layout:mylayout: migrating 'row09.col01' to 'Layer:1.row09.col01'
layout.c: Layout:mylayout: migrating 'row10.col01' to 'Layer:1.row10.col01'
layout.c: Layout:mylayout: migrating 'row11.col01' to 'Layer:1.row11.col01'
layout.c: Layout:mylayout: migrating 'row12.col01' to 'Layer:1.row12.col01'
layout.c: Layout:mylayout: migrating 'row16.col01' to 'Layer:1.row16.col01'
bad 'Widget:OS.speed' value '0' in lcd.conf, minimum is 10
Creating new timer group (0 ms)
widget 'OS': Class 'text', Parent '<root>', Layer 1, Row 0, Col 0 (to 0,0)
widget 'CPU': Class 'text', Parent '<root>', Layer 1, Row 1, Col 1 (to 1,1)
widget 'RAM': Class 'text', Parent '<root>', Layer 1, Row 2, Col 9 (to 2,9)
widget 'Busy': Class 'text', Parent '<root>', Layer 1, Row 4, Col 0 (to 4,0)
bad 'Widget:BusyBar.update' value '0' in lcd.conf, minimum is 10
Creating new timer group (10 ms)
widget 'BusyBar': Class 'bar', Parent '<root>', Layer 1, Row 5, Col 0 (to 5,-1)
widget 'Load': Class 'text', Parent '<root>', Layer 1, Row 6, Col 0 (to 6,0)
bad 'Widget:LoadBar.update' value '0' in lcd.conf, minimum is 10
widget 'LoadBar': Class 'bar', Parent '<root>', Layer 1, Row 7, Col 0 (to 7,-1)
widget 'Disk': Class 'text', Parent '<root>', Layer 1, Row 8, Col 0 (to 8,0)
bad 'Widget:DiskBar.update' value '0' in lcd.conf, minimum is 10
widget 'DiskBar': Class 'bar', Parent '<root>', Layer 1, Row 9, Col 0 (to 9,-1)
widget 'Eth0': Class 'text', Parent '<root>', Layer 1, Row 10, Col 0 (to 10,0)
bad 'Widget:Eth0Bar.update' value '0' in lcd.conf, minimum is 10
widget 'Eth0Bar': Class 'bar', Parent '<root>', Layer 1, Row 11, Col 0 (to 11,-1)
widget 'Uptime': Class 'text', Parent '<root>', Layer 1, Row 15, Col 0 (to 15,0)
error: widget 'Bgnd' has no class!
lcd4linux.c: starting main loop
loadavg(0): index out of range!
loadavg(0): index out of range!
Removing timer group (0 ms)
Timer #0 skipped 2147483647 interval(s) or 0 ms.
Timer #1 skipped 3 interval(s) or 30 ms.
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'LoadBar': new scale 0 - 3.70249E-314
Timer #2 skipped 2 interval(s) or 20 ms.
Timer #1 skipped 2 interval(s) or 20 ms.
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
Timer #2 skipped 2 interval(s) or 20 ms.
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
widget_bar.c: Bar 'BusyBar': new scale 0 - 100
loadavg(0): index out of range!
.
.
.
loadavg(0): index out of range!
Timer #1 skipped 2 interval(s) or 20 ms.
loadavg(0): index out of range!
Timer #2 skipped 2 interval(s) or 20 ms.
loadavg(0): index out of range!
Timer #1 skipped 1 interval(s) or 10 ms.
loadavg(0): index out of range!
Timer #2 skipped 1 interval(s) or 10 ms.
loadavg(0): index out of range!
loadavg(0): index out of range!
...
...
...
loadavg(0): index out of range!
loadavg(0): index out of range!
^Clcd4linux.c: got signal 2
lcd4linux.c: leaving main loop
DPF: shutting down.
drv_dpf.c: closing connection
]0;pi@raspberrypi: ~/lcd[01;32mpi@raspberrypi[00m [01;34m~/lcd $[00m
- Posts: 8
- Joined: Sun Oct 14, 2012 5:21 pm
@bimmi:
Are you using Raspbian? What other USB peripherals are plugged into the r-pi?
Are you using Raspbian? What other USB peripherals are plugged into the r-pi?
- Posts: 52
- Joined: Sat Jun 16, 2012 2:55 pm
ax206geek wrote:@bimmi:
Are you using Raspbian? What other USB peripherals are plugged into the r-pi?
Yes, I use 2012-09-18-wheezy-raspbian. Nothing other USB peripherals plugged into the r-pi. I think is the USB power problem. The Display will show "Low Battery" bevor it reboots. Already tried with 2 powered hubs and a Y-USB Cable from my mobile harddrive, too. Same problem. Also I tried with a second frame. No chance.
I bought a new RPI with the 512 MB Ram, because I hope there is no problem with the USB power. I'll wrote here when it deliver soon. Thanks for your help!!!
- Posts: 8
- Joined: Sun Oct 14, 2012 5:21 pm
bimmi wrote:ax206geek wrote:@bimmi:
Are you using Raspbian? What other USB peripherals are plugged into the r-pi?
Yes, I use 2012-09-18-wheezy-raspbian. Nothing other USB peripherals plugged into the r-pi. I think is the USB power problem. The Display will show "Low Battery" bevor it reboots. Already tried with 2 powered hubs and a Y-USB Cable from my mobile harddrive, too. Same problem. Also I tried with a second frame. No chance.
I bought a new RPI with the 512 MB Ram, because I hope there is no problem with the USB power. I'll wrote here when it deliver soon. Thanks for your help!!!
Hello there,
now I have a new Rpi here and there is the same problem.
- Code: Select all
lcd4linux.c: initializing driver DPF
Found AX206 DPF
Got LCD dimensions: 320x240
bulk write: Resource temporarily unavailable
I do not go on.
- Posts: 8
- Joined: Sun Oct 14, 2012 5:21 pm
bimmi wrote:bimmi wrote:ax206geek wrote:@bimmi:
Are you using Raspbian? What other USB peripherals are plugged into the r-pi?
Yes, I use 2012-09-18-wheezy-raspbian. Nothing other USB peripherals plugged into the r-pi. I think is the USB power problem. The Display will show "Low Battery" bevor it reboots. Already tried with 2 powered hubs and a Y-USB Cable from my mobile harddrive, too. Same problem. Also I tried with a second frame. No chance.
I bought a new RPI with the 512 MB Ram, because I hope there is no problem with the USB power. I'll wrote here when it deliver soon. Thanks for your help!!!
Hello there,
now I have a new Rpi here and there is the same problem.![]()
- Code: Select all
lcd4linux.c: initializing driver DPF
Found AX206 DPF
Got LCD dimensions: 320x240
bulk write: Resource temporarily unavailable
I do not go on.
Problem is done. This helped:
http://www.digital-eliteboard.com/showt ... ost1611459
Das hat mir bei dem Problem geholfen!
- Posts: 8
- Joined: Sun Oct 14, 2012 5:21 pm
- Code: Select all
lcd4linux.c: initializing driver DPF
Found AX206 DPF
Got LCD dimensions: 320x240
bulk write: Resource temporarily unavailable
I do not go on.
Problem is done. This helped:
http://www.digital-eliteboard.com/showt ... ost1611459
Das hat mir bei dem Problem geholfen!
dwc_otg.speed=1 has helped, but this means, that USB speed is only full speed.
I want to use a USB webcam, take a snapshot with fswebcam and show this image on the DPF by using lcd4linux. But the USB webcam does not work with USB full speed (error messages with not enough bandwidth).
So I can either use the USB webcam with USB high speed or the DPF and lcd4linux with USB full speed.
Any ideas how to solve the problem? (German language also welcome)
Thanks.
- Posts: 1
- Joined: Sun Nov 04, 2012 12:49 pm
Hi bimmi,
after 5 weeks of waiting my new frame arrived from China (one of the dx104838 kind). Half a day of fighting to flash the firmware (ended up doing it under Windows with SPIProgrammer) and half a day of fighting with my lcd4linux setup I was about to give up. I also ran into the error with "bulk write: Resource temporarily unavailable". The cmdline fixes only messed with my Pi and didn't really help.
This morning with a fresh start I found the solution (here): start lcd4linux with option -q.
TL;DR (German); Stelle für die cmdline wieder den Normalzustand her und erweitere den lcd4linux-Aufruf um "-q".
Good luck!
after 5 weeks of waiting my new frame arrived from China (one of the dx104838 kind). Half a day of fighting to flash the firmware (ended up doing it under Windows with SPIProgrammer) and half a day of fighting with my lcd4linux setup I was about to give up. I also ran into the error with "bulk write: Resource temporarily unavailable". The cmdline fixes only messed with my Pi and didn't really help.
This morning with a fresh start I found the solution (here): start lcd4linux with option -q.
TL;DR (German); Stelle für die cmdline wieder den Normalzustand her und erweitere den lcd4linux-Aufruf um "-q".
Good luck!
with ice cream wrote:Hi bimmi,
after 5 weeks of waiting my new frame arrived from China (one of the dx104838 kind). Half a day of fighting to flash the firmware (ended up doing it under Windows with SPIProgrammer) and half a day of fighting with my lcd4linux setup I was about to give up. I also ran into the error with "bulk write: Resource temporarily unavailable". The cmdline fixes only messed with my Pi and didn't really help.
This morning with a fresh start I found the solution (here): start lcd4linux with option -q.
TL;DR (German); Stelle für die cmdline wieder den Normalzustand her und erweitere den lcd4linux-Aufruf um "-q".
Good luck!
Hi,
I got the same problem. It worked fine on a PC but on the PI the screen rebooted shortly after starting lcdd4linux. Now with the -q option it works find.
Thank You - I was about to give up on this problem.
Thomas
- Posts: 5
- Joined: Wed Dec 05, 2012 10:37 am