Analyzing CLI project

RE: Analyzing CLI project

Amanda Hsieh — Fri, 05 Aug 2022 11:24:21 GMT

Hi,

Have a look at

https://openthread.io/reference

https://openthread.io/codelabs/openthread-apis#0

Basically, each CLI command is tied to an OpenThread API call

-Amanda

RE: Analyzing CLI project

kaushalyasat — Tue, 02 Aug 2022 06:33:14 GMT

Hi Amanda,

Many thanks for your reply.

1. I do understand about preceding the commands with 'ot'. That is like application level. What I want is like back end. How the commands are executed under the hood of CLI program. My requirement is to come up with a simple program which handles the commissioning part by itself. So I am trying to lift the code sections from CLI instead of developing everything from scratch.

2. I have looked into this, but this is again explanation of the commands and the result in application level isnt it? As I mentioned before, I am after the inner working of the CLI program.

I tried using Debug mode to trace the program execution path. Still it seems a long way to do it like this.

I am thinking that the coap_client/server projects may be more useful for me for this task. What is your opinion?

Thanks,

RE: Analyzing CLI project

Amanda Hsieh — Mon, 01 Aug 2022 13:15:50 GMT

Hi,

1. OpenThread CLI is integrated into the Zephyr shell. To indicate a Thread command, the ot keyword needs to precede the command.

2. Have a look at OpenThread commissioning.

Regards,
Amanda