Hi everyone,
Can anyone help me that can we use analysis ports between the driver and sequencer instead of normal port and export?
In reply to sreekanth reddy undi:
the port-export connection is a 1 to 1 connection. The analysis_port-analysis_export connection is a 0 to many connection.
The methods used for transmitting data are different.
In reply to sreekanth reddy undi:
In addition, why did you want to change it? May you share the problem?
In reply to chr_sue:
hi ,
we can use analysis port and analysis export for 1 to 1 connection,then can i use it in between driver and sequencer and is there any other specific reason of using normal ports?
This was a question asked in an interview.
In reply to sreekanth reddy undi:
The analysis_port/export provides only a non-blocking connection. This not adequate for the sequncer/driver connection and it does not have mnechanism to indicate a seq_item has been processed. This is what you need in the driver/serquencer connection.
In reply to chr_sue:
I am unable to understand regarding this point you have said(it does not have mechanism to indicate a seq_item has been processed),it depends on the type of function or task you call from driver i.e if it is a pull mode.
if you use try_next_item function call from driver then it is also a non blocking call then?
In reply to sreekanth reddy undi:
The analysis_port/export does not have any blocking mechanism per definition. It is assigned to the anlysis path.
The port/export mechanism has blocking and non-blocking mechanism. If you are using there the non-blocking you have to run in a loop until you get the next item.