Am Donnerstag, 14. Dezember 2006 12:33 schrieb Jan Kandziora:
>
> But from the problems we encounter I think the following is done when
> reading "1F.iiiiiiiiiiii/simultaneous/single"
>
> Byte 0 0x55 ROM Command (Match ROM)
> Byte 1 0x1F Family Code (DS2409)
> Byte 2..7 mmmm ID
> Byte 8 mmmm CRC8
> Byte 9 0xCC Control Command (Smart-On Main)
> Byte 10 0xFF Reset Timing for main branch
> Byte 11 0xFF Reset Timing for main branch
>
> --- Additional reset for whole bus (so the previously selected DS2409
> branch AND the backbone are selected)
>
> Byte +0 0x33 ROM Command (valid only for previously reset main branch)
> Byte +1 ssss Garbage (wired AND of family codes)
> Byte +2..+7 ssss Garbage (wired AND of IDs)
> Byte +8 ssss Garbage (wired AND of CRC8s)
>
Paul, it's like I've written above. Each TRXN_START triggers "BUS_select",
which, in lines 90 and 156 of module/owlib/src/c/ow_select.c issue at least
one "BUS_reset".
That way, we really shot our own foot, as the Smart-On function cannot be used
properly. It's just the same result as Direct-On.
I'm not sure what to do. I tested a little with BUS_send_data and
BUS_readin_data in the DS2409 code, but I couldn't get Smart-On working at
all. The DS2409 doesn't seem to respond to the "reset stimulus" byte by
issuing a reset on its main output.
Kind regards
Jan
--
43rd Law of Computing:
Anything that can go wr
fortune: Segmentation violation -- Core dumped
-------------------------------------------------------------------------
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
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
