Document# SCT-UM026FVC Page 17 of 46 Confidential
# execute the Queued commands and exit Buffer Mode.
B>trigger_in 1
# Prompt returns to the Standard Prompt.
# 10 Bytes of data are available in the Data Queue.
->status
...
Data Queue
Queue Full : False
Bytes Queued : 10
# Read 5 Bytes, using stream formatting, from Data Queue.
# Data returned is 0x01FF348900.
->read 5 1
Data: 01FF348900
# 5 Bytes of data remain in the Data Queue.
->status
...
Data Queue
Queue Full : False
Bytes Queued : 5
3.2.6 Events
An Event is the occurrence of an action that is not a direct result of a user’s interaction with the Programming
Interface. Such events may occur in order to communicate protocol related bus errors, protocol interrupts, or
unexpected system related errors or warnings. The types of events that may occur largely depend on the protocol
Mode enabled.
Events are only communicated to the Programming Interface during idle time when a command is not being processed.
An Event is identified by the use of the Event Prompt as indicated by Table 3.2.1-1.
Due to the non-deterministic nature of Events, care must be taken to ensure that automated applications are able to
appropriately handle the occurrence of an event. In most cases, event messages can be disabled from being reported
to the Programming Interface. Refer to Section 3.3 for additional detail and about mode specific event and how to
configure them.
To Next Page
Loading...
Need help?
General