DHB improvements, possible bug #472
Closed
muellerr
wants to merge 5 commits from
eive/fsfw:mueller/dhb-bugfixes-improvements into development
pull from: eive/fsfw:mueller/dhb-bugfixes-improvements
merge into: :development
:master
:spahr/fixCompileError
:development
:mohr/romeo
:development-doc-deployment
:development-doc-test0
:switch-doc-theme-to-rtd
:action-update
:obj-manager-tweak
:mohr_introspection
:mohr/windows
:mohr/GCC13
:mohr/timetag_fix
:mohr/relsease_helper
:mohr/warnings
:mohr/rtems
:mohr/freeRTOS
:mueller/new-cfdp-update-with-handlers
:mohr/dhb2normal
:mueller/obj-man-remove-weird-proc-func
:mohr/documentation_ci
:mueller/fsfw-from-zero
:mueller/data-wrapper
:mueller/dhb-handle-device-tm
:mueller/refactor-tmtc-stack-with-retval-refactoring
:mueller/refactor-logging-with-fmt
:meier/upstream-pus-distributor-bugfix
:mueller/clang-improvements
No Reviewers
Labels
Clear labels
API Change
Breaking API Change
bug
build
cosmetics
Documentation
duplicate
feature
help wanted
hotfix
invalid
question
Refactor
Tests
wontfix
Changes the API, so Users need to adapted
Changes the API in a non backwards compatible way
Something is not working
Issues related to the buildsystem, including CI
Small change most users won't notice
Improvement of code documentation
This issue or pull request already exists
New feature
Need some help
Quick or important fix that is merged directly into master, causing a new revision
#worksforme
More information is needed
Contains a refactoring of some code
Issues related to testing code
This won't be fixed
Milestone
No items
No Milestone
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: fsfw/fsfw#472
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I found it a bit confusing after using DHB again after a long time how external commanding and the generation of verification messages is handled. These changes clarify the behaviour of DHB for external commanding a bit.
Additional diagnostic output for invalid commands was added as well.
Also, Iam not sure whether this is a bug, but a FDIR event will be trigged if
getSendSuccessreturnsNO_REPLY_EXPECTEDDHB improvementsto DHB improvements, possible bugI think there is a misunderstanding here:
NO_REPLY_EXPECTEDis not returned bygetSendSuccess()but byenableReplyInReplyMap(). Thus, it will not trigger an FDIR event as it is returned in theifbranch, while the check is located in theelsepath.result == NO_REPLY_EXPECTEDis handled correctly inreplyToCommand().OKay, I'll check this
#474 fixes actual problem, remaining is the misunderstanding (#wontfix) and a possible bug in eive FSW which needs to be confirmed.
Pull request closed