Hi bohdi, I had a bit of time to play with it today. I changed back the bootdelay variable to 10 seconds and did warm reboot just to confirm the behaviour. And indeed, I got "EHCI timed out on TD - token=" messages and the Dockstar eventually (after about 1-2 minutes of EHCI timed out...messages) booted in to the rescue system. Then I rebooted, interupted the boot sequence, chby RomanG - uBoot
Bodhi, Thanks for the suggestion. I do have netconsole as well as serial console working on this one so no big worry if something goes south. And the buspirate in the drawer if something goes really bad. I tried different things today and did some reading on uboot. It looks like this behaviour is not that uncommon. I was also carefully watching what my HDD is doing (or not doing) during warby RomanG - uBoot
Hi guys, I am wondering if you found a solution to this problem. I am facing the same issue, but I am using an external SATA HDD in SATA to USB enclosure. Drive has his own power supply, not powered from the Dockstar. The Dockstar woud boot without any issues from cold start, but would not boot after reboot. When I say cold start it must be completelly cold start, both the Dockstar as wby RomanG - uBoot
Hi davygravy, I have your 3.3.2 kernel on one of mine dockstars: root@MERCURY:~# uname -a Linux MERCURY 3.3.2-kirkwood-dg #1 Mon Apr 23 17:09:27 CDT 2012 armv5tel GNU/Linux and after installing wifi dongle (Realtek TL-WLN725N, chip RTL8192CU) and running: ifup wlan0 I got following messages in the syslog: Nov 3 19:59:01 MERCURY kernel: [12418.266333] ------------[ cut here ]-----by RomanG - Debian
Quote dakkara wrote: ------------------------------------------------------- I crosscompiled lcd4linux, but when I try and install I get this message I did not realize that you are crosscompiling, the script is meant to run on ARM device (dockstar or raspberry pi). Are you crosscompiling on PC linux machine? I suppose if you follow script line by line you will see what it is doing and yoby RomanG - Displays
Hi dakkara, Can you post error message(s) that you are getting? Thanks Romanby RomanG - Displays
dakkara Wrote: ------------------------------------------------------- > Thanks that worked and I have hacked the DPF. > > Now I have another problem, does anyone have an > lcd4linux ipkg with dpf driver support and mpd > plugin or know where I can find a guide to build > it myself? > > Thanks in advance =) Check my post(s) on page 21 of this thread for scripby RomanG - Displays
Markus Wrote: ------------------------------------------------------- > Hello RomanG, > > would you please post your RPi lcd4linux.conf ? > Thanks. Hi Markus, Here is the config file for system statistics. Romanby RomanG - Displays
And here are pictures showing system statistics and mpd player status...by RomanG - Displays
superelchi Wrote: ------------------------------------------------------- > The missing usb.h is part of the libusb > development (header) files. > An > apt-get install libusb-dev may do the > trick. > > superelchi I was not sure since the dpf-ax/source directory contains usb.h as well. After few trials I managed to install it on raspberry pi running Debian wheezby RomanG - Displays
ax206geek Wrote: ------------------------------------------------------- > @RomanG: Thanks for your lcd4linux patch. I'll try it out on both my Pi and dockstar. > @MrLinux: Thanks for your dpfsend program. I'll try it out on both my Pi and dockstar. Hi ax206geek, Did you try to install it on your PI? I tried on mine (under Raspbian as well as Debian) but I am running inby RomanG - Displays
gabychan Wrote: ------------------------------------------------------- > A partner in the Forum Tododream has purchased > this > Frame and can > not get it to work. > Anyone know what Firm is needed? > > Regards I have exactly the same frame from Focalprice, works fine with focal_landscape.bin firmware. Romanby RomanG - Displays
Here is my very crude script that pulls everything together and installs build 1184 of lcd4linux with mpd plugin. The lcd4linux install script from dpf-ax package is configured such that it installs DPF driver only. If you are running multiple displays on your dosckstar like me (I have one graphic dpf display and one 4x20 character USB2LCD display running at the same time), you will need toby RomanG - Displays
Hi ax206geek, It is not my patch, I just searched the internet and found thread at OpenWrt forum with same problem as mine. I was pointed to the patch by user irimi over at OpenWrt forums, so credit should go there. Romanby RomanG - Displays
------------------------------------------------------- > zoolander Wrote: > -------------------------------------------------- > ----- > ... > ... > ... > > So my question is, did anyone succeed to > compile > > latest lcd4linux with DPF support? > > > > Thanks for your replies ... > ... > ... > zoolander, if you apply thisby RomanG - Displays
Following up on my recent post, I checked what I did back in April in order to compile lcd4linux, build 1142 with mpd plugin. While running ./configure, I was getting error message: ... ... checking for mpd_newConnection in -llibmpd... no configure: WARNING: libmpdclient.h header not found: mpd plugin disabled configure: WARNING: get libmpdclient.h from http://www.musicpd.org/libmpdclientby RomanG - Displays
zoolander Wrote: ------------------------------------------------------- ... ... ... > So my question is, did anyone succeed to compile > latest lcd4linux with DPF support? > > Thanks for your replies ... ... ... This may be a late reply as I was not following this forum for a while but I managed to compile version 1192 back in April Here is some info. As I remember,by RomanG - Displays
I should have checked the driver chip datasheet first. The Ilitek ILI9163B driver that is defined for the "white" display can control only displays up to 132x168 pixels resolution, so my suggestion above was wrong. Can you post more information about your display? Where did you buy it, maybe also picture of it? Romanby RomanG - Displays
Looking at config.h in the ../scr directory, it looks like "white" is confirgured for 128x128, so what you are seeing seems to be correct ... ... #if defined (DPFMODEL_white) # define LCD_128x128 # define LCD_CONTROLLER_ILI9163B # define LCD_ORIENTATION_RGB RGB_DOWN # define BUTTON_SWAP # define DEFAULT_ORIENTATION ROT_UP ... ... I wouldl trby RomanG - Displays
buspirate, I am not sure about the mirroring of the image, maybe fw_blue.bin is not the correct firmware for your display? As far as image occupying only 1/4 of the screen, did you try to modify the config file or load an imagge with 320x240size to see if you can cover the whole screen? See my earlier post above. Romanby RomanG - Displays
I take back my statment that the lcd4linux DPF driver is configured for 128x128 resolution. I loaded the background image with 320x240 resolution and it displays correctly. In configuration file, I assume that if length of the widget is 21, it is actually 21x6=126 pixels long, am I correct? Thanks Romanby RomanG - Displays
bulix.org is up and running again so I downloaded build 1192 of the lcd4linux and patched it with patch included in the dpf-ax package When I run lcd4linux with dpf.conf (also included in the dpf-ax package), it runs as if the driver was configured for 128x128 display However, when I kill lcd4linux, the good bye message is displayed correctly, accros the whole screen, centered Have a looby RomanG - Displays
It looks like bulix.org is down at the moment, cannot get source for lcd4linux... Romanby RomanG - Displays
I checked out source of libhid form svn... svn co svn://svn.debian.org/libhid/trunk libhid-svn ...and installed it from source. It was a bit of pain since instructions in README file did not work and I was not sure where shouls be the default installation located. After that, I was able to flash the firmware. Attached are pictures of the initial screen and little scope that uses internal ADby RomanG - Displays
Did some more googling and looks like I will need libhid library installed. Unfortunately it is not available for squeeze armel platform as far as I could find (I am doing this on dockstar itself). Romanby RomanG - Displays
Thanks dpffan for prompt response. I re-read the README in ../src directory and found reference to restore.py script as you suggested. Put the frame in to BL mode (MENU + Reset button) and lsusb detected it as 1908:3318 root@NEPTUNE:/usr/src/dpf-ax# lsusb Bus 001 Device 043: ID 1908:3318 Bus 001 Device 018: ID 0c76:1607 JMTek, LLC. audio controller Bus 001 Device 007: ID 5bcd:5bcd Bus 00by RomanG - Displays
I got one of these AX206 frames form Focal Price abou t a year ago, but did not have time to play with it until now. Item number from focal Price is ED022W. dmesg output is: ... ... usb 1-1.4: new full speed USB device using orion-ehci and address 41 scsi23 : usb-storage 1-1.4:1.0 scsi 23:0:0:0: CD-ROM buildwin Photo Frame 1.01 PQ: 0 ANSI: 2 sr0: scsi3-mmc drive: 40xby RomanG - Displays
I hope someone can help me with this. I have CUPS 1.4.4 running on one of my Dockstar, it was working fine with network attached HP LaserJet printer (attached to the router with parallel port). Main reason for installing CUPS was to have Dockstar configured to share CUPS printer with Google CloudPrint. This enables printing form Android devices through Google CloudPrint. It all worked fine wiby RomanG - Debian
Hi, I think that driver for your chipset is supported since kernel 2.6.32-10. You may consider updating your kernel since you are running 2.6.32-5. Please see this post and subsequent posts for solution. Good luck, Romanby RomanG - Debian