Thomas,
In your init-ds1621 word, you send a zero as the control protocol
byte immediately after the ds1621 acknowledges the correct address for a
write. Looking at the data sheet on pages there are no valid command
protocols with a value of zero so the ds1621 does not acknowledge, just
as your logic trace shows. The PIC waits indefinitely for that ACK,
until the watchdog resets the MCU.
The example in the datasheet on page 12 sends the byte $AC as the
"Access Config" command, followed by other bytes. Maybe you should do
the same. Doing that whole example and checking the trace with the
logic analyzer will probably be enlightening. Those logic analyzers are
amazingly good tools.
Cheers,
Peter J.
On 05/07/14 00:49, Thomas Buschhardt wrote:
> Hallo,
>
> I receive an Logic analyzer to solve my I2C problem, but I cant find a
> error.
> I import successfully asm.txt and i2cbase.txt. The PIC reboot fast
> after a short timeperiode (maybe the watchdog).
> The two I2C-Ports are electrical in good condition (I test a LED-Flash
> Script on both).
>
> Here my files:
> http://www.buschhardt.de/flashforth/
> - Schematic
> - Logic-Sessionfile
> - Logic Output as Picture
> - My Flashforth File (I used a copy of that from the wounderfull tutorial)
>
> Link <http://datasheets.maximintegrated.com/en/ds/DS1621.pdf> to
> DS1621-Datasheet
>
> Thank you very much.
> Thomas
|
