Can not confirm this message. This is what I get on coldboot (320S DTB) [ 21.764163] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.1 Copyright 2004-2014 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/5c:f4:ab:2f:by superelchi - Debian
With the new DTB: root@debian:~# ifconfig -a lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0by superelchi - Debian
@Bodhi: Nope. Tested with kirkwood-nsa310s.dtb. Coldboot to Debian: GREEN LED on/blinking, Link Up, 10HDX - no network. Reboot to ZyXel OS: GREEN LED goes off during boot, AMBER LED on/blinking, Link Up, 1000FDX - network working. Rebbot to Debian: AMBER LED on/blinking, Link Up, 1000FDX - network working. Powering off: After power off: AMBER LED on/blinking, Link Up, 100FDX .by superelchi - Debian
@JohnnyUSA: as we say in Germany: "Geteiltes Leid ist halbes Leid" (a trouble shared is a trouble halved). :) Made one more test: Changed speed of switch-port from "Auto detect" to "Fixed 1000FDX". Result after Debian coldboot: switch says "Link down". Changed port back to "Auto detect": switch says "Link up, 10HDX". :( So eth0by superelchi - Debian
Hi, @JohnnyUSA: you are not alone! ;) I have the same problem: link is not comming up. What I have: - ZyXel NSA-310S - Root: Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi - Kernel: linux-4.1.0-kirkwood-tld-1-bodhi - uImage generated with kirkwood-nsa320s.dtb - Box is connected to a HP ProCurve 1800 manageable switch My findings: Connecting power (not switched on): GREEN LED on neby superelchi - Debian
Hi Eric, please try attached fw. Don't know why restore.py did not work. Maybe not root? Anyway: you can use the FlashLib.ini from a couple of post above for Windows. superelchiby superelchi - Displays
Hi newmats, work already done. But not in the svn... $ ./identify.py fulldump_20150528-165047.bin Looking for firmware.............: Found (buildwin, 128x128 px). Looking for Openwin..............: Found. Looking for LcdIniTbl............: Found. Looking for backlight & contrast.: Found, Found. Looking for known signatures.....: Found. Your dpf is compatible with model ['by superelchi - Displays
Hi Chris, please try attached FlashLib.ini. superelchiby superelchi - Displays
Hi Tohin, I don't think Appotech will be very helpful - after all we would like to get access to the SDK to HACK the device! Normally such an SDK is only given to paying customers. And they have to sign a NDA (non-disclosure agreement). But if you dare to ask - you are welcome. ;) superelchiby superelchi - Displays
Hi Tohin, that's the page I meant in my previous post. There is the SDK, schemetics and docs for the AX206. For AX208 there is only a flyer... superelchiby superelchi - Displays
Good Question. First thing that comes to mind is the SDK. Hacking the AX206 was only possible (at least for me) because the SDK was availabel on the net. The SDK the AX208 dpfs are based on is not in the public. superelchiby superelchi - Displays
Hi Newmats, Identify.py says:: $ ./identify.py -d fulldump_20150515-132201.bin Looking for firmware.............: Not found. This in no known firmware! Sorry, no matching dpf found. Dpf-ax only works with AX206 chips based on the Buildwin SDK for this chip. Your dpf is not an AX206 or not based an this sdk. Looks like 2.4" dpfs with AX206 are no longer available. :( Sorry, nby superelchi - Displays
Hi, as identify.py said: "This in no known firmware!". A look at your fw-dump shows "AX208 SDK V3.0" - so another one that is AX208 based, not AX206. And dpf-ax only works with AX206 chips based on the Buildwin SDK for this chip. Sorry, nothing I can do. superelchiby superelchi - Displays
Sorry. Did not know that lcd4linux is a bit shy to show it's real version. ;) If the driver is okay, may be it is the usual problem - bad USB connection? You know that the cable that comes with the dpf is crap? Have you tried another USB port and / or a shorter / better USB cable? Also it may be a power problem. You should try to connect the dpf over a powered USB-Hub. superelchiby superelchi - Displays
@Pkrich Please try attached fw. Make sure brightness & contrast setting work. Do you have a name / supplier for this dpf? Else it will stay acme_9. superelchiby superelchi - Displays
@Fireport Your lcd4linux version on the router is out of date. It has an old driver which may not be compatible with the current dfp firmware. The new dpf-driver (written by yours truly) was added in rev 1199. The router has rev 1193. Hope you can find a current version or compile it yourself... superelchiby superelchi - Displays
Hi Fireport, there is a compatible model that I have not yet uploaded to the svn (shame on me). $ ./identify.py fulldump_20150327-152057.bin Looking for firmware.............: Found (buildwin, 128x128 px). Looking for Openwin..............: Found. Looking for LcdIniTbl............: Found. Looking for backlight & contrast.: Found, Found. Looking for known signatures.....: Found.by superelchi - Displays
Fine. So I will add it as "sweex_mv004v4". superelchiby superelchi - Displays
@jon2099 Please try attached fw. superelchiby superelchi - Displays
Okay. Another one working. :) So I will add it as "august_dp150l". superelchi.by superelchi - Displays
Hi Leonjoeann, please try attached fw. superelchiby superelchi - Displays
As I said: an easy one. :) "Pink" was a generic name, which I removed a while ago. So it will stay "acme_8". superelchiby superelchi - Displays
@ Victorclaessen That's an easy one. :) Please try attached fw. Do you have a name for this dpf - else it will stay acme_8... superelchiby superelchi - Displays
Hi Andrejt, yeah - the board looks familiar. :) So it *MAY* be an AX206-chip (I can not see any markings on the chip itself). BUT: the firmware was not build with the Buildwin SDK for AX206. Identify.py needs a fw build with this SDK to extract lcd-access & init routines. Without these infos it's not possible to build a custom fw for your dpf. You could try to flash all existing cuby superelchi - Displays
Hi Andrejt, as identify.py said: "This in no known firmware!". A look at your fw-dump shows "AX208 SDK V3.0" - seems to be AX208 based, not AX206. And dpf-ax only works with AX206 chips based on the Buildwin SDK for this chip. Sorry. superelchiby superelchi - Displays
free8bee Wrote: ------------------------------------------------------- > Fw_sweex_mm004v5_2 works almost perfectly. One > strange thing happens when I turn off dpf by > Menu|Off, and then turn it on by Menu button or > connecting USB cable. It looks like lcd contrast > has been reset to high level (out of usable > range), and almost whole display goes dark. Then > ifby superelchi - Displays
Hi free8bee, here we go: fw_sweex_mm004v5_2 - should work as expected. fw_wh_smith - not sure. Has a *VERY* strange lcd access. Please give it a try and report back. superelchiby superelchi - Displays
Looks like this is not an AX206-based dpf. Please upload the firmware so I can have a closer look. superelchiby superelchi - Displays
Fine. So I will add these two as 'lehoff' and 'bresser'. superelchiby superelchi - Displays
Hi gothbert, sorry about the late answer. Vacation. :) Please try attached fw. Bresser has no detectable contrast routine. Please make sure contrast is okay. Else I have to dig a bit deeper... superelchiby superelchi - Displays