missing header files#2

[jsayed]

Sorry I am reposting this issue as by mistake I closed my previous question.

Hi, I have following issue and need some help.
I am using SEGGER Embedded studio for ARM Release 3.4 build 2018052200 36079 with latest nRF_SDK_for_Thread_v0.11.0_84a130f on window 10 (64). 

I can compile <Thread SDK>/examples/thread/experimental/cli/usb without any errors BUT When I run it by pressing <Go command> on SES studio the File explorer window pops up, indicating "missing file". Add or remove for future. It shows up for several files. Which some o these file don't even exists.

Upon search i found following post "Debugging OpenThread example with Segger"

https://devzone.nordicsemi.com/f/nordic-q-a/35344/debugging-openthread-examples-with-segger/135942#135942.

Per this post it indicates there are some issues with the latest SES development environment and suggest ignoring these messages as these source file are not needed for already compiled libraries.

I was able to follow this and run the program.

On running (<Thread SDK>/examples/thread/experimental/cli/usb). The program display messages:

<info> app: Thread version: OPENTHREAD/ga89eb88-dirty; NRF52840; Nov 17 2017 09:01:26
<info> app: Network name: OpenThread
<info> app: State changed! Flags: 0x00001311 Current role: 0

But I don't get a command line, which I need to configure the network by inputing commands. such as panid, ifconfig up, thread start etc. what I am missing? need some assistance understanding this.

My understanding is that I don't need an border router in the CLI example, I should be able to run two device and
send/receive local messages between them. Is this accurate?

Thanks

[jsayed]

Hi- can anyone please help me understand this -- thx

[Edvin]

Hello,

Sorry for the late reply,

The Segger Embedded Studio (SES) command line doesn't work on my computer either. Exactly what the problem is I am not sure. I suspect it has to do with SES or the JLINK version. And I also get the popup windows in SES. 

 

But what you can do is to program the example, and then use an external UART terminal like Putty (Remember to use the UART and not the USB version of the project) to write the CLI commands. Then it works fine on my computer.

 

Does that work for you?

Best regards,

Edvin

[jsayed]

Thanks Edvin, appreciate your response. I will post the question of missing header fpop-up on Segger forum.  I was able to communicate with CLI when I compiled the UART version and used Putty.

I have one more simple question.  Sorry I am still learning about Thread,

Right now, my environment, is BLE. I have several Clients(Central) and one single server (Peripheral).  My Clients are event driven data collectors and sleep 95% while my server is alway awake, adversing and ready to connect with clients. My server is also connected to a PC on a serial port. Which locally stores information.

I like to move this to a Thread environment.  Can I do this with Two nRF52840 DK running Thread CLI (as in my above posts) with minor/none modification. They will both be connected to two PC's. Meaning without a border router, I do understand the concept of border router but is it absolutely necessary to have a border router in my environment as I am local and don't need to go to INTERNET.  If this is  not possible can you please suggest a simple Thread architecture, where it is possible, thx....jsayed 

[Edvin]

Hello,

I see. The quick answer is no, you don't need a border router if you are only operating locally, and don't need access to the cloud. A thread network can operate just fine on it's own.

Thread is a bit new to us in customer support as well, but I think the CLI example should be quite suited for your need. 

If you program 2 DKs with the CLI example, you can use them to communicate with one another. You can read about how to test this here.

 

Best regards,

Edvin