LP-CC1352P7: Issue building LP-CC1352P7-1 ns_coap_node for Wi-SUN project interoperability with Silabs Border router

Part Number: LP-CC1352P7
Other Parts Discussed in Thread: WI-SUN,

Tool/software:

Hi,

I'm currently working on a Wi-SUN project where I'm using the LP-CC1352P7-1 as a router node. The goal is to achieve interoperability with a Silabs Border router. However, I'm encountering an issue when trying to build the project, as shown in the captures,

Thanks in advance,

Mahdi

  • Hi Mahdi,

    We have documented how to switch the certificates in the example in the User's Guide. Please try to follow these steps to add your custom certificate.

    https://dev.ti.com/tirex/explore/content/simplelink_cc13xx_cc26xx_sdk_7_41_00_17/docs/ti_wisunfan/html/wisun-stack/networklayer.html#certificates-for-certification

    Cheers,

    Marie H

  • Hi Marie,

    I have reviewed the following two links to try to understand the steps involved, but I'm still stuck: 

    1. https://dev.ti.com/tirex/explore/content/simplelink_cc13xx_cc26xx_sdk_7_41_00_17/docs/ti_wisunfan/html/wisun-stack/networklayer.html#certificates-for-certification
    2. sunmaysky.blogspot.com/.../interoperability-test-between-silicon.html

    From the documentation and examples I’ve gone through, I am unsure whether I should simply modify the wisun_certificates.h file to add the Silabs certificates, or if it is necessary to integrate the following code to manage the certificates because it's not mentionned in the first link :

    #define MBED_CONF_APP_OWN_CERTIFICATE WISUN_CLIENT_CERTIFICATE_SL
    #define MBED_CONF_APP_OWN_CERTIFICATE_KEY WISUN_CLIENT_KEY_SL
    #define MBED_CONF_APP_ROOT_CERTIFICATE WISUN_ROOT_CERTIFICATE_SL
    
    wisun_tasklet_remove_trusted_certificates();
    wisun_tasklet_set_trusted_certificate(MBED_CONF_APP_ROOT_CERTIFICATE, strlen((const char*)MBED_CONF_APP_ROOT_CERTIFICATE) + 1);
    wisun_tasklet_remove_own_certificates();
    wisun_tasklet_set_own_certificate(MBED_CONF_APP_OWN_CERTIFICATE, strlen((const char*)MBED_CONF_APP_OWN_CERTIFICATE) + 1, 
                                      MBED_CONF_APP_OWN_CERTIFICATE_KEY, strlen((const char*)MBED_CONF_APP_OWN_CERTIFICATE_KEY) + 1);
    

    I am completely lost about what steps to take to ensure the interoperability of the two systems. Could you please help me clarify this?

    Any help or suggestions you can provide would be greatly appreciated.

    Best regards,

    Mahdi.

  • Hi Madhi,

    Yes you will need to use the wisun_tasklet APIs to add your certificate. I have mentioned this in step 4 in the first link.

    Are you seeing any issue when using this code snippet that you posted?

    Cheers,

    Marie H

  • Hi Marie,

    Yes, that's exactly what I need. Your question addresses my current challenge perfectly, and I appreciate your help

    Regards,

    Mahdi.

  • Hi Marie,

    I hope you're doing well. I have some questions regarding what I'm currently facing, and I hope you could help me with the following:

    1. I've noticed that the path for 'mbed_config_app.h' is in the 'Application' folder, not in the path mentioned in the documentation, which is 'mbed\nanostack\sal-stack-nanostack\source\configs'. Could you clarify this discrepancy?

     

    1. Also, in step 4, you mentioned adding wisun_tasklet APIs, which are defined in wisun_tasklet.h. I'm unsure if I should define them in application.c. If not, where and how exactly should they be added ? 

      -PS: I am working on simplelink_cc13xx_cc26xx_sdk_7_41_00_17

    I would appreciate your guidance on these points.

    Regards,

    Mahdi.

  • Yes, I am encountering an issue when using the code snippet that I posted. The problem is that I am unsure of how and where to integrate this code properly. This probably lead to the before mentioned observed issues

     

    I have successfully achieved communication between different vendors other than TI boards. However, when testing the TI board LP-CC1352P7

     for performance comparison and evaluation mainly interoperability tests, I am blocked and stuck at the current step.

    This is quite urgent, so I would really appreciate it if you could reply to me as soon as possible.

    Regards,

    Mahdi.

  • Hi Mahdi,

    Thank you for pointing out the mbed_config_app.h wrong path in the documentation. I'll make a ticket and we will update the documentation.

    Your build error looks like you're missing an "import" statement for wisun_tasklet.h in application.c.

    Cheers,

    Marie H

  • Hi Marie,

    Thanks for addressing the mbed_config_app.h path issue.

    Regarding the build error, wisun_tasklet.h is already imported in application.c, but the issue persists. Could there be another cause?

    Best regards,

    Mahdi

  • Hi Mahdi,

    If you're following the blog post that you posted, you can use the same strategy as this blog post where they define the certificates and keys in application.c. This should solve your build error. 

    I am able to reproduce your build error. I will re-write the section to avoid this.

    Cheers,

    Marie H