You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2021. It is now read-only.
STM32CubeIDE has a feature that shows the received time of an ITM data,
and it seems to be provide a convenient way for profiling embedded apps.
I thought this feature could be useful when added to the itm-dump tool.
I'm not an expert with ITM or embedded stuff, so I first wanted to ask whether this feature would fit well with the itm-dump tool.
I can try implementing the feature in the near future.
I've come to think that rather than implementing this functionality on the itmdump side, it might be better to create an API like iprint_with_timestamp in the cortex_m crate.. I'll close this issue..
sorry for the delay. this seems like a super interesting idea! would definitely come in handy for some timing-specific debugging i have been doing. i haven't used ITM much but would expect this to be a combination of support for receiving timestamps in itmdump as well as itm client extensions.
as to where to put this i would be inclined to fork itmdump for the receiver side to support receiving timestamps, and maybe look at feature for itm_logger or cortex-m-log to support client-side-timestamping? (disclaimer: i have not used either of itm_logger or corex-m-log they just seem roughly in line with your goals). whatever you do manage, keep us posted!
STM32CubeIDE has a feature that shows the received time of an ITM data,
and it seems to be provide a convenient way for profiling embedded apps.
I thought this feature could be useful when added to the
itm-dump
tool.I'm not an expert with ITM or embedded stuff, so I first wanted to ask whether this feature would fit well with the
itm-dump
tool.I can try implementing the feature in the near future.
Reference
Thank you for reading 🦀
The text was updated successfully, but these errors were encountered: