Thanks @uweseimet !! Just a couple of comments.

I know I'm slow, but could you avoid changes to gpiobus for the time being? (unless they're bug fixes)

@akuker Regarding the gpiobus changes, these fix SonarCloud issues. Just a few lines are changed. If this is an issue for you, for this PR we can revert the changes in the 'hal' folder to what we currently have in develop. On the other hand, except for a few more changed lines (currently in the feature_more_unit_tests branch) I am done with updating 'hal'. I just merged these pending changes into the PR for feature_memory_management.
So we have two alternatives now:

1. Keep everything in 'hal' as it is right now for this PR, with no other changes planned from my side, because all changes I have planned are now present in this PR.
2. Revert 'hal' to what is currently in develop. In this case I would like to ask you to apply the pending changes, i.e. the 'hal' diffs between develop and what is now in feature_memory_management, as part of your upcoming changes.

I hope it's clear what I mean :). Of course I prefer option 1, because these changes jsut a few lines and because they have already been tested by @rdmark and me.

@akuker Please remember that I would like to merge this PR myself after approval, in order to clean up the merge message.

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
7 Code Smells

27.0% Coverage
2.0% Duplication

I hope it's clear what I mean :). Of course I prefer option 1, because these changes jsut a few lines and because they have already been tested by @rdmark and me.

Option 1 is good for me :-) The changes should be easy enough to merge in to my stuff. Have a great weekend!

@akuker Once more, thank you for taking time to review my numerous changes. Have a great weekend as well!