DAP Technology 1394, Руководство по эксплуатации

Страница: 215 / 458

Filter/Trigger
215 Copyright © DapTechnology B.V., 2005-2019 - All Rights Reserved., 5/20/2019
changed and the text in the item will indicate the new properties of the item. The properties of all items
are described in more details below.
Now we will discuss the different types of items and describe what happens when they are executed.
· Start: The Start item is the starting point of the trigger program. The item after the Start item will be
executed if the Trigger Sequencer is (re)started. It has no properties and can not be deleted.
·
Wait: A Wait item is used to make the sequencer wait for a packet and/or acknowledge and/or event.
When a Wait item is selected, you can select where to wait for in the properties box. You can select to
wait for a packet, an acknowledge or an event, or any combination of them. When a Wait item is
executed, the program does not continue until the packet, acknowledge or event is detected.
For instance if an Wait item is executed that waits for a packet or event, then the item after the Wait is
executed when a packet or an event is detected on the bus. It does not matter what kind of packet or
event. You can use the Jump item to check what was detected (Packet or Event). If a packet was
detected, the Jump item can also be used to check the packet type, content or errors. And if an event
was detected, the Jump can be used to differentiate on event type.
·
Jump: When a Jump item is selected, you specify a jump-condition in the properties box. The specified
condition is indicated by the text in the Jump item. You can also specify if the sequencer should jump to
the target if the jump-condition is met (true) or if the jump-condition is not met (not true) (indicated with
a Y or N at the jump line). If the jump is taken, the item executed next is the item where the jump line
points to (the line going to the right or left from the Jump item). If the jump is not taken, the item after
the Jump item will be executed next.
The jump-condition refers to the result of the last executed Wait item. So if the last executed Wait item
stopped executing because a CycleStart packet was detected (note that this only can happen if this
Wait item has the 'wait for packet' property included), then the following condition are for instance true:
'was Packet?'
'was CycleStart?'
'was WrBlockReq or RdBlockReq or CycleStart?'
'was Packet from set A or B?' assuming that a CycleStart packet fits set A or set B
And the following are for instance not true:
'was Event?'
'was BusReset Event?'
'was Ack.?'
'was complete or pending Ack.?'
'was WrBlockReq or RdBlockReq?'
'was Packet from set D?' assuming that a CycleStart packet does not fit set D
'was PhySelfID?'
'was any Packet with an error?'
You can use more than one Jump item after a Wait item. For example the execution of the left flow
below will result in a Recorder trigger as soon as a BusReset or PhySelfID packet has been detected.
The Wait will execute until any event or packet has been detected and the two first Jump items will
jump if a BusReset or PhySelfID was detected. It not, the third Jump will make sure the Wait is
executed again.