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.

LPSTK-CC1352R: LPSTK-CC1352R and Wi SUN problem

Part Number: LPSTK-CC1352R
Other Parts Discussed in Thread: CC1352R

Dear TI Engineers,

I am working on a CC1352P7-1 launchpad, a CC1352R Launchpad and a CC1352R Sensortag Kit.

I programmed my CC1352P7-1 launchpad as a wi-sun border router and CC1352R Launchpad as router node.  This pair worked together.  From within the wi-sun pyspinel console connected to CC1352P7-1 launchpad, I could ping CC1352R Launchpad successfully.

Then, I repeated the same experiment on CC1352R Sensortag Kit.  My procedures are as following:

I used my old MSP-432P401R Launchpad as the programmer and debugger, connecting to CC1352R Sensortag Kit's XDS 110 socket, programmed it exactly the same as CC1352R Launchpad.  Then, I restarted CC1352R Sensortag Kit's power but my CC1352P7-1 launchpad border router can never detect it.

So how to make CC1352R Sensortag Kit work as router node?

  • Hi Tim,

    When you say you program the CC1352R LaunchPad and sensor tags as router nodes, are they connected to an application processor? Or are you using the WISUN_AUTO_START define?

    If you just program the ns_router example as it is provided, the device will be stuck waiting for a command from the application processor to start the Wi-SUN FAN Stack.

    Cheers,

    Marie H

  • Hello Marie,

    After I programme CC1352R LaunchPad, I will then issue pyspinel commands:

    1. ifconfig up
    2. wisunstack start

    through its COM port.

    But for CC1352R SensorTag Kit, it does not have a COM port.  So there is no way I can start its wisun stack.  Is it the reason why it cannot be detected by my border router?

    And how do I programme it to start its own ifconfig and wisunstack?

  • Yes, it works after I follow your other post discussing about this topic.