This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMDS64EVM: TMDS64EVM: Issue with Profinet-Pre-Cert-Test regarding OEM Device ID

Part Number: TMDS64EVM

Hello,

during development with the TMDS64EVM we ran the Profinet Profinet-Pre-Cert-ARTester and every DCP related test failed. This is caused by an unexpected DCP-Block for "Device/OEM Device ID". In our current application we are using IM1 to IM4. We do not support IM5, therefore this DCP-Block should not be sent.

We already seen some complaint/issue in the "Arm-based micocontollers forum" with the same problem. Here is the Link to the issue:  TMDS243EVM: Profinet pre-certification test

At the moment only our DAP module is configured as PN_API_IOD_Im0Device + PN_API_IOD_Im0Submodule. All other PDEVs are configured as PN_API_IOD_Im0Nothing.
Regarding the IM0 List for the stack startup: we configure the DAP with imXSupported = PN_API_IOD_SUPPORT_IM1234.
Changes in pn_app_iod_cfg.h to PN_API_IOD_INCLUDE_IM5 have no effect on this, which was explained in the above thread due to beeing statically configured.

For futher development we are needing a fix and support regarding this issue.

Thank you very much and best regards.

 

  • Hello Severin,

    as stated in the other issue you shared, the current config parameters are statically compiled within the library. Therefore, it is unfortunately not yet possible to disable IM5 support on the application side. Nevertheless, we are currently changing this and the customers will gradually get the possibility to dynamically modify any of these parameters. This will first be included in our next release in October. In case you are in a hurry and require an early custom delivery, you may reach out to your regional sales representatives and we can take it from there.

    Kind regards,
    Kamil