Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update: added separate 'log write' event type for OT nodes #162

Merged
merged 2 commits into from
Jun 14, 2024

Conversation

EskoDijk
Copy link
Owner

This simplifies the parsing at OTNS side: not intertwined anymore with UART output.

EskoDijk added 2 commits June 13, 2024 21:42
…fies the parsing at OTNS side: not intertwined anymore with UART output.
@EskoDijk EskoDijk linked an issue Jun 14, 2024 that may be closed by this pull request
@EskoDijk EskoDijk merged commit 675a751 into main Jun 14, 2024
26 of 27 checks passed
@EskoDijk EskoDijk deleted the pr-ot-log-separate branch June 14, 2024 07:55
EskoDijk added a commit that referenced this pull request Sep 24, 2024
* [all] added separate 'log write' event type for OT nodes. This simplifies the parsing at OTNS side: not intertwined anymore with UART output. The otoutfilter package is removed (if in future needed for parsing UART-based OT logs, then it can always be added back in again)
EskoDijk added a commit that referenced this pull request Sep 24, 2024
* [all] added separate 'log write' event type for OT nodes. This simplifies the parsing at OTNS side: not intertwined anymore with UART output. The otoutfilter package is removed (if in future needed for parsing UART-based OT logs, then it can always be added back in again)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fix logging by sending otPlatLog items as separate events
1 participant