Hello,
it would be useful if RTT may supports SVC calls to interrupt device application about availability of new host data in RTT down buffer.
This allows reading host data from ISR without polling.
SVC number could be configured using RTT control block. When SVC is raised, parameters (down buffer number) may be passed in registers or SVC should be configured only for one down buffer.
From host point of view (host API) one should be able to control when SVC would be raised (i.e. flushing). This allows sending data one by one (useful for input consoles) or by data block (SVC then would be called when down buffer is full or at end of data).
For backward compatibility without using new host API, SVC would be called as quickly as new data is available.
it would be useful if RTT may supports SVC calls to interrupt device application about availability of new host data in RTT down buffer.
This allows reading host data from ISR without polling.
SVC number could be configured using RTT control block. When SVC is raised, parameters (down buffer number) may be passed in registers or SVC should be configured only for one down buffer.
From host point of view (host API) one should be able to control when SVC would be raised (i.e. flushing). This allows sending data one by one (useful for input consoles) or by data block (SVC then would be called when down buffer is full or at end of data).
For backward compatibility without using new host API, SVC would be called as quickly as new data is available.