• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 16 subscribers
  • Views 440 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

LP-CC1352P7: Wrong address

Laurent van Poppelen69
Expert 1020 points
Part Number: LP-CC1352P7


Hi,

I have 2 x LP-CC1352P7, followed the academy_5_40_00_00 and succesfully setup the network and a connection.

However the address returned by 'connecteddevices' reports:

2020:abcd::212:4b00:14f9:66be

so I guess something in the code is wrong!

Where do I need to look?

rgds,

Laurent

  • 0
    TI__Mastermind 20412 points

    Hi Laurent, 

    Is this a recurring issue? Does this happen every time the network forms? 

    Also, please can you try reproducing the issue with another device? If you do not have another set of devices, switch the device used for border router and router node. This will help us isolate where the issue could lie.

    Regards,

    Sid

  • 0
    Expert 1020 points

    Hi Sid,

    happens each time! I will perform your suggestion s.a.p.

    I switched both BR and BR_COAP, and the issue remains. So I guess it's in the software! Could you tell me were to look?

    rgds,

    Laurent

  • 0 in reply to Laurent van Poppelen69
    TI__Mastermind 20412 points

    Hi laurent, 

    I am really sorry for the earlier oversight. It is the correct address that is getting displayed.

    It is just a shortened notation.
    2020:abcd::212:4b00:14f9:66be is just the shortened version of 2020:abcd:0000:0000:212:4b00:14f9:66be. 
    This is according to convention. You can either use the short address or the full length address to ping the device and it will have the same destination. 

    Regards,

    Sid

  • 0 in reply to Sid
    Expert 1020 points

    Hi Sid,

    thanks, but I tried both methods, "::" and "0000:0000" and neither results in a responds!

    Maybe my problem is in the ns_coap_node since at startup, with Putty connnected There is no output??

    Wher should I look?

    rgds,

    Laurent

  • 0 in reply to Laurent van Poppelen69
    TI__Mastermind 20412 points

    Hi Laurent, 

    The ns_coap_node is not in the network coprocessor mode. It is a fully embedded application. You just have to power it up (no putty session). Once it joins the network, try the ping command with its address. And make sure that the node is not disconnected.

    The spinel-cli needs access to the COM port the border router is connected to. Please can you send a screenshot of your spinel-cli.py output?

    I would expect something similar to this. 

    Regards,

    Sid 

  • 0 in reply to Sid
    Expert 1020 points

    Hi Sid,

    most challenges are solved! The ping is working and I can set the leds on/off. I'm now playing around to get the sniffer operational with shark v3.0.6. In my case I note that spinel-cli doesn't show its command prompt but, everything else works fine!

    Thanks for your help!

    Is there any info if I want to connect an external MCU for the coap? Or is another approach required?

    rgds,

    Laurent

  • 0 in reply to Laurent van Poppelen69
    TI__Mastermind 20412 points

    Hi Laurent, 

    Really good that you are able to solve the issues. 
    The idea of the coap example was to demonstrate a completely embedded application. 
    The router node is an example which works as a network processor and thus, can support and external MCU as host. 
    Please can you elaborate on how you intend to add the external MCU.


    Regards,

    Sid