CC1352P7: CC1352P7

Network name, phy id, channel id are same on both border router and node.

Part Number: LP-CC1352P7

Tool/software:

 Hello,
I'm using CC1352P7 as a route node and running ns_node file to connect with WI SUN border router which is a silicon labs ERF32 board connected with raspberry Pi. I'm using SDK simplelink_cc13xx_cc26xx_sdk_8_30_01_01.
I'm establishing the connection in India but there is no option to select India domain (IN) in the node configuration settings. Only EU, NA, BZ, JP domains are listed as shown in the image below.
The Network name, phy_mode_id:3, chan_plan_id:33, fan_version:FAN 1.1 are same on both border router and node.
 
After flashing the ns_node code the serial monitor (putty) message is showing [INFO][main]: nanostackNetworkHandler: CON_STATUS_CONNECTING.

My questions are:
1. Is it possible to connect to WI SUN running on different border router device (ERF32 board connected with raspberry Pi)?
2. Is it possible to add India domain in node configuration settings? If so, how?
3. What is the procedure to be followed to establish a successful WI SUN network with LP-CC1352P7-1 and border router?
4. Are there any security or certificate dependencies when connecting the TI Wi-SUN node to a non-TI border router (EFR32 + Raspberry Pi)?

Thank you.

Hi Marie,

I have changed the certificates in wisun_certificates.h of ns_coap_node file with corresponding certificates of border router. 

I have changed WISUN_ROOT_CERTIFICATE with wisun_config_ca_certificate, WISUN_SERVER_CERTIFICATE with wisun_config_device_certificate, WISUN_SERVER_KEY with wisun_config_device_private_key of border router. I didn't make any changes in the WISUN_CLIENT_CERTIFICATE, WISUN_CLIENT_KEY in wisun_certificates.h file.

I have included the below code in application.c file:
wisun_tasklet_remove_trusted_certificates();
wisun_tasklet_set_trusted_certificate((uint8_t *)MBED_CONF_MBED_MESH_APP_ROOT_CERTIFICATE ,strlen((const char*) MBED_CONF_MBED_MESH_APP_ROOT_CERTIFICATE ) +1);
wisun_tasklet_remove_own_certificates();
wisun_tasklet_set_own_certificate((uint8_t *)MBED_CONF_MBED_MESH_APP_OWN_CERTIFICATE, strlen((const char*) MBED_CONF_MBED_MESH_APP_OWN_CERTIFICATE +1),(uint8_t *) MBED_CONF_MBED_MESH_APP_OWN_CERTIFICATE_KEY, strlen((const char*) MBED_CONF_MBED_MESH_APP_OWN_CERTIFICATE_KEY) +1);

I also changed the Pre-Shared Network Key with GTK of wisun border router as shown in below image:

I followed the procedure mentioned in this blog: Sun May Sky: Interoperability test between Silicon Labs and Texas Instrument Wi-SUN Stack

I changed the domain to NA, phy_mode_id to 2, chan_plan_id to 1, frequency to 902.2, preamble count to 8 as mentioned in the blog.
After making changes accordingly I'm not able to connect to the WI SUN border router. The [INFO][main]: nanostackNetworkHandler: CON_STATUS_CONNECTING persist. 


Can you have a look and help me out...

Thank you.

Regards,
Sowmya Gurram.

Hi Sowmya,

Pinging YiKai Chen in case you have a comment.

Sowmya, a couple of things:

1. Make sure you do a full flash erase of both devices before starting the test. (This is in order to avoid outdated network information being stored in the device flash.)

2. I believe the blog post is a few years old. The user's guide page I linked is up to date (but is of course not specific to the SiLabs device).

3. Which version of Wi-SUN FAN does your SiLabs device run? (We've seen in some cases that SiLabs devices running Wi-SUN FAN 1.1 are not compatible with FAN 1.0.) We only support FAN 1.0.

4. Can you capture a packet sniffer log of the two devices attempting to connect? This should tell us where in the process they fail. Please follow this guide:

https://dev.ti.com/tirex/content/simplelink_cc13xx_cc26xx_sdk_8_30_01_01/docs/ti_wisunfan/html/wisun-guide/debugging-index.html#packet-sniffer 

Cheers,

Marie H