mc4plus-trace-rtos v3.40 #37
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
also added the related .map files which tell mapping of assembly instructions
and functions into the code space. these files can be used to locate the hex
addresses contained in the diagnostics
- built:
- mc4plus v3.40, build 02 nov 2021 @ 12:11
- main changes from previous release are:
- the fatal error handler which forces the the restart sends even more advanced diagnostics able to trace
further actions inside the RTOS (see robotology/icub-firmware#213).
these diagnostics are to be decoded w/ relevant .map file.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
also added the related .map files which tell mapping of assembly instructions
and functions into the code space. these files can be used to locate the hex
addresses contained in the diagnostics
further actions inside the RTOS (see More RTOS trace for the mc4plus board icub-firmware#213).
these diagnostics are to be decoded w/ relevant .map file.