Details
Description
The I&M0FilterData record lists all submodules which have own I&M0 data (plus some more which is irrelevant here). In specific scenario the data record is invalid on the network which is detected e.g. by certification tool ART in testcase DiffAccessWays.
The issue occurs when
- application handles I&M data
- submodules in PNS_IF_READ_IM_RES_T are not strictly sorted by API
It is expected that the order of submodules is not influencing the coding on the network.
Workaround for application:
- application shall sort submodules by API in PNS_IF_READ_IM_RES_T.
Example list opf submodules leading to wrong I&M0FilterData record:
| API | Slot | Subslot |
| 0 | 0 | 1 |
| 0x4E01 | 1 | 1 |
| 0 | 1 | 2 |
| 0x4E01 | 1 | 3 |
Example leading to correct I&M0FilterData record:
| API | Slot | Subslot |
| 0 | 0 | 1 |
| 0 | 1 | 2 |
| 0x4E01 | 1 | 1 |
| 0x4E01 | 1 | 3 |
Attachments
Issue Links
- clones
-
PSPNSV5-316 wrong I&M0FilterData coding may be seen on network if application handles I&M data and uses submodules of multiple API
-
- Closed
-