On PC tool, it can show the logs from ETR in real time.
When one small packet send from STM to ETR, it can be stuck between STM
and ETR.
When the packet stuck happens, it will be flushed to ETR only when some
other packets
generated from STM source or CTI flush commands are sent. If the time is
too long to wait
for next packets coming, user will consider that issue happens with
previous small packet.
And user's requirement is that packet from STM can be flushed to ETR
automatically instead
of sending commands manually.
Is it appropriate to add a sysfs node for STM to generate the trigger
packet periodically for such case ?
There's stm_heartbeat that will send a string via STM on a timer. It
will come on its own channel, so your PC tool should be able to ignore
it. Would that help?