Products > Board Support Package (Installation, Licensing, ...)

ETHAPI crash in sipif.cpp

<< < (2/2)

ebarhorst:
Hi Blair,


Arnaud is on vacation as well now  :)


As Arnaud indicated the ethernet interface for the FMC150 reference design is not designed to be a reliable, fail safe interface. It is there to get a quick and easy start with the FMC board and do burst based snapshots to analyse the ADC performance or your aalgorithm It is communicating on the RAW ethernet level with no data protection. Some of the more common reasons for the communication to fail are;
- HOST computer is not able to empty the etherenet receive buffer fast enough => packets are lost
- HOST starts to communicate on the ethernet link to request some global status. If this happens in the middle of a communication with the ML605 the ethernet interface will get stuck. To reduce the chances of this happening all ethernet adapter protocols apart from the 4DSP ethernet protocol driver shoudl be disabled through the adapter properties window.


You can contact the 4DSP sales and receive a license for our PCIecpress core  if you need a more reliable communication with the ML605


Best regards,
Erik

ebarhorst:
Hi Blair,


would you have an update on this topic, or can I close it?


Best regards,


Erik

Blair Fonville:
Go ahead and close it. I'll design an TCP based solution instead. Thanks.

ebarhorst:
This topic is being closed because the issue is considered as resolved by 4DSP. Feel free to create a new topic for any further inquiries.

Navigation

[0] Message Index

[*] Previous page