More RTOS trace for the mc4plus board #213
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
marcoaccame
added a commit
to robotology/icub-firmware-build
that referenced
this pull request
Nov 4, 2021
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.
This PR builds up on the results logged with the mc4plus application generated by a former PR and adds further trace information for the RTOS according to what the analysis of the log has shown (see here).
In particular in here we trace the execution of the function
osal_messagequeue_getquick().We have added for this purpose 16 more variables in which:
A companion PR is being produced in icub-firmware-build for a new binary of the mc4plus.
Tests on a dedicated setup have validate the binary of the mc4plus generated by this PR so we can safely merge this code and associated PR on icub-firmware-build.