Multiple start of MC service #25
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
- ems v3.38 release date 2021 mar 22 @ 18:24
- mc4plus v3.31 release date 2021 mar 22 @ 18:26
- mc2plus v3.22 release date 2021 mar 22 1 @ 18:27
- built on 2021 mar 23 using icub-firmware w/ SHA-1: 8931b94b0175205b9d7ad1e2107e39d19d7bbd41 and icub-firmware-shared devel w/ SHA-1: b163ba92d48d5ee7d816e7b51396ec70bbcb7b88
- main changes from previous release are:
- fixed behaviour when multiple init() / deinit() of the MC service is called (i.e., yarprobotinterface started and stopped many times in a row).
that avoids the boards executing in the fatal error handler which causes their disappearance from the interna ETH network.
In particular:
- removed memory leaks due to EOCurrentsWatchdog / hal_spiencoder when multiple init() / deinit() are called.
- protected hal_quadencoder_init_indexes_flags() so that it does not interfere w/ associated IRQ Handler even if executed multiple times
This was referenced Mar 23, 2021
- ems v3.38 release date 2021 mar 22 @ 18:24
- mc4plus v3.31 release date 2021 mar 22 @ 18:26
- mc2plus v3.22 release date 2021 mar 22 1 @ 18:27
- built on 2021 mar 23 using icub-firmware w/ SHA-1: abf002d1983e9e1fa98ef1fce5e38ab18e56df2c and icub-firmware-shared devel w/ SHA-1: b163ba92d48d5ee7d816e7b51396ec70bbcb7b88
- main changes from previous release are:
- fixed behaviour when multiple init() / deinit() of the MC service is called (i.e., yarprobotinterface started and stopped many times in a row).
that avoids the boards executing in the fatal error handler which causes their disappearance from the interna ETH network.
In particular:
- removed memory leaks due to EOCurrentsWatchdog / hal_spiencoder when multiple init() / deinit() are called.
- protected hal_quadencoder_init_indexes_flags() so that it does not interfere w/ associated IRQ Handler even if executed multiple times
|
tested on the robot iCubGenova04 once more on 24 mar 2021 as i had to rebase the source code. |
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 is associated to robotology/icub-firmware#176.
ems v3.38 release date 2021 mar 22 @ 18:24
mc4plus v3.31 release date 2021 mar 22 @ 18:26
mc2plus v3.22 release date 2021 mar 22 1 @ 18:27
built on 2021 mar 23 using icub-firmware w/ SHA-1: 8931b94b0175205b9d7ad1e2107e39d19d7bbd41 and icub-firmware-shared devel w/ SHA-1: b163ba92d48d5ee7d816e7b51396ec70bbcb7b88
main changes from previous release are:
that avoids the boards executing in the fatal error handler which causes their disappearance from the interna ETH network.
In particular: