thanks for answer.

When i do owhttpd --fake=10,22 -p 3000 --foreground --error_level=9

i got this:

CONNECT: Setting up Simulated (Fake) Bus Master (0)
ServerAddr: [(null)] [3000]
CONNECT: ServerListen: socket() [3000]: Address family not supported by
protocol  

And on the web page:

directory

________________________________________________________________________
top
highest level
directory
structure
structure
directory
bus.0
bus.0
directory
uncached
uncached
directory
settings
settings
directory
system
system
directory
statistics
statistics
directory
10.67C6697351FF
DS18S20
1-wire chip
22.4AEC29CDBAAB
DS1822
1-wire chip
alarm
alarm
directory
simultaneous
simultaneous
1-wire c


Sincerely

Marc

Le mercredi 15 novembre 2006 à 14:59 -0500, Paul Alfille a écrit :
> Hi Marc,
> 
> It sounds like more than one issue.
> 
> 1. "CONNECT: ServerListen: socket() [3001]: Address family not
> supported by
> protocol"
> is a little strange.
> Can you try "owhttpd --fake=10,22 -p 3000 --foreground
> --error_level=9" And see if anything shows up on web page?
> 
> 2. the "/structure" directory is a list of supported
> devices/properties. Not what is actually present.
> 
> 3. "CONNECT: Cannot detect DS2480 or LINK interface on /dev/tts/1.
>   CALL: PARSENAME path=[]" is expected for the passive (homebuilt)
> adapter, but not the DS9097U (DS2480B-based) one. Sounds like a serial
> port issue.
> 
> Paul Alfille
> 
> On 11/15/06, marc geonet <[EMAIL PROTECTED]> wrote:
>         hi,
>         
>         I readed the topic of august 2006 about openwrt on linksys
>         wrt54g.
>         
>         I brought a linksys wrt54gl (CLB1F723336).
>         I followed the serial modifications on the web site of John
>         Withby, with
>         the AD233BK Ver5, from Compsys. I did some verifications about
>         the 
>         voltage 3.3V from the wrt and everything seems to be ok.
>         
>         I puted the openwrt firmware "white russian" with jffs2
>         structure and
>         all the owfs packages, and this work perfectly.
>         
>         But i have problems to connect 1wire. 
>         
>         It seems that i have communication with /dev/tts/1. I can send
>         and
>         receive datas.
>         For /dev/tts/0, i can send but not receive ???
>         
>         Here is the result of "cat /proc/tty/driver/serial":
>         
>         
>         0: uart:16550A port:B8000300 irq:3 baud:113636 tx:399 rx:0
>         RTS|CTS|DTR|
>         DSR|CD
>         1: uart:16550A port:B8000400 irq:0 baud:9615 tx:45 rx:28 brk:1
>         CTS|DSR|
>         CD
>         
>         After a look at my "dmesg" command:
>         
>                         CPU revision is: 00029008
>         Primary instruction cache 16kB, physically tagged, 2-way,
>         linesize 16
>         bytes.
>         Primary data cache 8kB, 2-way, linesize 16 bytes.
>         Linux version 2.4.30 ([EMAIL PROTECTED]) (gcc version 3.4.4
>         (OpenWrt-1.0)) #1
>         Sun Mar 26 19:02:04 CEST 2006
>         Setting the PFC value as 0x15
>         Determined physical RAM map:
>         memory: 01000000 @ 00000000 (usable)
>         On node 0 totalpages: 4096
>         zone(0): 4096 pages.
>         zone(1): 0 pages. 
>         zone(2): 0 pages.
>         Kernel command line: root=/dev/mtdblock2
>         rootfstype=squashfs,jffs2
>         init=/etc/preinit noinitrd console=ttyS0,115200
>         CPU: BCM5352 rev 0 at 200 MHz
>         Using 100.000 MHz high precision timer.
>         Calibrating delay loop... 199.47 BogoMIPS
>         Memory: 14268k/16384k available (1412k kernel code, 2116k
>         reserved, 100k
>         data, 80k init, 0k highmem)
>         Dentry cache hash table entries: 2048 (order: 2, 16384 bytes)
>         Inode cache hash table entries: 1024 (order: 1, 8192 bytes) 
>         Mount cache hash table entries: 512 (order: 0, 4096 bytes)
>         Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
>         Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
>         Checking for 'wait' instruction...  unavailable. 
>         POSIX conformance testing by UNIFIX
>         PCI: no core
>         PCI: Fixing up bus 0
>         Linux NET4.0 for Linux 2.4
>         Based upon Swansea University Computer Society NET3.039
>         Initializing RT netlink socket
>         Starting kswapd 
>         devfs: v1.12c (20020818) Richard Gooch ([EMAIL PROTECTED])
>         devfs: boot_options: 0x1
>         JFFS2 version 2.1. (C) 2001 Red Hat, Inc., designed by Axis
>         Communications AB.
>         Squashfs 2.1-r2 (released 2004/12/15) (C) 2002-2004 Phillip
>         Lougher
>         pty: 256 Unix98 ptys configured
>         Serial driver version 5.05c (2001-07-08) with MANY_PORTS
>         SHARE_IRQ
>         SERIAL_PCI enabled
>         ttyS00 at 0xb8000300 (irq = 3) is a 16550A 
>         ttyS01 at 0xb8000400 (irq = 0) is a 16550A
>         b44.c:v0.93 (Mar, 2004)
>         PCI: Setting latency timer of device 00:01.0 to 64
>         eth0: Broadcom 47xx 10/100BaseT Ethernet 00:18:39:bc:77:94
>         Physically mapped flash: Found an alias at 0x400000 for the
>         chip at 0x0 
>         Physically mapped flash: Found an alias at 0x800000 for the
>         chip at 0x0
>         Physically mapped flash: Found an alias at 0xc00000 for the
>         chip at 0x0
>         Physically mapped flash: Found an alias at 0x1000000 for the
>         chip at 0x0 
>         Physically mapped flash: Found an alias at 0x1400000 for the
>         chip at 0x0
>         Physically mapped flash: Found an alias at 0x1800000 for the
>         chip at 0x0
>         Physically mapped flash: Found an alias at 0x1c00000 for the
>         chip at 0x0 
>         Amd/Fujitsu Extended Query Table v3.3 at 0x0040
>         number of CFI chips: 1
>         cfi_cmdset_0002: Disabling fast programming due to code
>         brokenness.
>         Flash device: 0x400000 at 0x1c000000
>         Creating 4 MTD partitions on "Physically mapped flash": 
>         0x00000000-0x00040000 : "pmon"
>         0x00040000-0x003f0000 : "linux"
>         0x000c0000-0x003f0000 : "rootfs"
>         0x003f0000-0x00400000 : "nvram"
>         Initializing Cryptographic API
>         NET4: Linux TCP/IP 1.0 for NET4.0
>         IP Protocols: ICMP, UDP, TCP, IGMP
>         IP: routing cache hash table of 512 buckets, 4Kbytes
>         TCP: Hash tables configured (established 1024 bind 2048)
>         ip_conntrack version 2.1 (5953 buckets, 5953 max) - 328 bytes
>         per 
>         conntrack
>         ip_tables: (C) 2000-2002 Netfilter core team
>         NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
>         NET4: Ethernet Bridge 008 for NET4.0
>         802.1Q VLAN Support v1.8 Ben Greear <[EMAIL PROTECTED]>
>         All bugs added by David S. Miller <[email protected]>
>         VFS: Mounted root (jffs2 filesystem) readonly.
>         Mounted devfs on /dev
>         Freeing unused kernel memory: 80k freed 
>         Algorithmics/MIPS FPU Emulator v1.5
>         diag: Detected 'Linksys WRT54G/GS/GL'
>         Probing device eth0: found!
>         b44: eth0: Link is up at 100 Mbps, full duplex.
>         b44: eth0: Flow control is off for TX and off for RX.
>         jffs2.bbc: SIZE compression mode activated.
>         PCI: Setting latency timer of device 00:05.0 to 64
>         eth1: Broadcom BCM4320 802.11 Wireless Controller 3.90.37.0
>         BFL_ENETADM not set in boardflags. Use force=1 to ignore. 
>         device eth0 entered promiscuous mode
>         vlan0: add 01:00:5e:00:00:01 mcast address to master interface
>         vlan0: dev_set_promiscuity(master, 1)
>         vlan0: dev_set_allmulti(master, 1)
>         device eth1 entered promiscuous mode 
>         br0: port 2(eth1) entering learning state
>         br0: port 1(vlan0) entering learning state
>         br0: port 2(eth1) entering forwarding state
>         br0: topology change detected, propagating
>         br0: port 1(vlan0) entering forwarding state 
>         br0: topology change detected, propagating
>         vlan1: Setting MAC address to  00 18 39 bc 77 95.
>         vlan1: add 01:00:5e:00:00:01 mcast address to master interface
>         fuse init (API version 7.2)
>         fuse distribution version: 2.4.2
>         fuse exit
>         Trying to free nonexistent resource <b8000400-b8000407>
>         
>         
>         
>         Something seems to me strange:
>         
>                 Serial driver version 5.05c (2001-07-08) with
>         MANY_PORTS SHARE_IRQ
>         SERIAL_PCI enabled 
>         ttyS00 at 0xb8000300 (irq = 3) is a 16550A
>         ttyS01 at 0xb8000400 (irq = 0) is a 16550A
>         
>         I have ttyS1 with irq = 0 ???
>         
>         Anyway, i did a "setserial /dev/tts/1 port 0x8000400 irq3"
>                 and a   "stty -F /dev/tts/1 speed 115200" 
>         
>         
>         I have two adaptaters:  -1 DS9097 home made build, and it
>         works
>         perfectly on my pc.
>                                 -1 new DS9097U-S09 from hobby board,
>         it works                            also on my pc.
>         
>         When i connect the passive DS9097, i got with "owhttpd
>         -d /dev/tts/1 -p
>         3001 --foreground --error_level=9" command this result
>         
>         CALL: PARSENAME path=[]
>         CONNECT: Cannot detect DS2480 or LINK interface
>         on /dev/tts/1. 
>            CALL: PARSENAME path=[]
>         ServerAddr: [(null)] [3001]
>         CONNECT: ServerListen: socket() [3001]: Address family not
>         supported by
>         protocol
>         
>         In the 1 wire structure /tmp/1wire/system/adaptater/name.0,
>         it'written DS9097, but it can not detect the DS1820 
>         
>         
>         When i connect the passive DS9097U-S09, i got with "owhttpd
>         -d /dev/tts/1 -p 3001 --foreground --error_level=9" command
>         this result
>         
>         CALL: PARSENAME path=[]
>         CONNECT: Cannot detect DS2480 or LINK interface
>         on /dev/tts/1. 
>            CALL: PARSENAME path=[]
>         DEFAULT: Cannot detect DS9097 (passive) interface
>         on /dev/tts/1.
>         ServerAddr: [(null)] [3001]
>         CONNECT: ServerListen: socket() [3001]: Address family not
>         supported by
>         protocol
>         
>         In the 1 wire structure /tmp/1wire/system/adaptater/name.0,
>         it'written BAD ADAPTATER
>         
>         Somebody could help me to debug this
>         
>         Sincerely
>         
>         Marc
>         
>         
>         
> ------------------------------------------------------------------------- 
>         Take Surveys. Earn Cash. Influence the Future of IT
>         Join SourceForge.net's Techsay panel and you'll get the chance
>         to share your
>         opinions on IT & business topics through brief surveys - and
>         earn cash
>         
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>         _______________________________________________
>         Owfs-developers mailing list
>         [email protected]
>         https://lists.sourceforge.net/lists/listinfo/owfs-developers
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________ Owfs-developers mailing list 
> [email protected] 
> https://lists.sourceforge.net/lists/listinfo/owfs-developers


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to