Embedded 1394 device difficulties...

We have a set of 3 embedded 1394 devices using the TSB12LV32/TSB41AB3.
These devices are implemented using the data mover port and an FPGA.
They are not IRM capable. In addition to the embedded devices, we have
two linux boxes running the 2.6.1 kernel, ieee1394 svn version 1105, and
libraw1394 svn version 139. Two of the embedded devices are spewing
data, one of the linux boxes consumes this data and spews data to the
remaining embedded device. In this situation the remaining linux box
hangs on the 1394 bus but neither generates or consumes 1394 data.

Occasionally, the final embedded device stops receiving data from the
linux box. All the transmitters appear to be transmitting. This seems
to occur after a bus reset. Often it recovers with out intervention,
but sometimes it does not. The syslog messages associated with these
events are:

ieee1394: Node changed: 0-04:1023 -> 0-02:1023
ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting...
ieee1394: The root node is not cycle master capable; selecting a new
root node and resetting...

The "Node changed" message seems most closely tied to the recovery.

Does anyone have any ideas why this would recover sometimes and fail to
recover other times?

Thanks,
Russel Hill

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
mailing list Linux1394-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux1394-user
Received on Fri Jan 23 19:03:07 2004