Details
Description
The master status block is only updated if a connection actually opens and in case of a stack reset. Since there is also a field reflecting the number of configured slaves, this is not sufficient.
New design: Since the master status block contents are derived from the CC bitfields (vendor specific attributes of the class) CONFIGURED, DIAGNOSTIC and VALID_DATA_RECEIVED, it should be the best option to notify any changes of these bitfields to teh AP task/GCI and let it update the master status block with each change.
Attachments
Issue Links
- relates to
-
PSEIP-522 [SCANNER] Implement master status block
- Closed