mcumgr command line tool setup issue in windows

RE: mcumgr command line tool setup issue in windows

Edvin — Wed, 30 Mar 2022 09:54:15 GMT

mcumgr can't use Bluetooth Low Energy on Windows, but serial works just fine.

So did you install mcumgr? Is there an .exe file somewhere on your computer named mcumgr.exe?

RE: mcumgr command line tool setup issue in windows

Shikamaru — Wed, 30 Mar 2022 07:11:48 GMT

Hi edvin,

I tried but it is saying mcumgr is not recognized. and moreover am using windows system. does it work in windows also. in somewhere in ticket they mentioned this

RE: mcumgr command line tool setup issue in windows

Edvin — Thu, 24 Mar 2022 14:34:37 GMT

PS: If you install mcumgr using go, it will add it to the path for you, if I remember correctly. If you can use the command "where mcumgr", then it is correctly added to your path.

RE: mcumgr command line tool setup issue in windows

Edvin — Thu, 24 Mar 2022 14:33:56 GMT

I don't know how you installed mcumgr. Did you follow some guide on how to install mcumgr-cli?

If you did, please ensure that the path to your mcumgr.exe is added to the environment path on your computer. I don't remember exactly how I installed it, but it looks like I used "Go" to do so:

I think I used this guide:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.7.1/zephyr/guides/device_mgmt/mcumgr.html#mcumgr-cli

And before that, I needed to install Go. I think I found a suitable download here:

https://go.dev/dl/

Best regards,

Edvin

RE: mcumgr command line tool setup issue in windows

Shikamaru — Thu, 24 Mar 2022 06:59:25 GMT

Thanks Edvin ,

COM20 was fine, we got that but after installing mcumgr also , we are facing the issue that 'mcumgr' is not recognized as an internal or external command,

RE: mcumgr command line tool setup issue in windows

Edvin — Wed, 23 Mar 2022 22:06:47 GMT

Hello,

The guide that you refer to claims that it is written in Linux, and hence, the COM ports looks a bit different than what they do in Windows. What you see when you use "nrfjprog --conn" is expected. It means that your DK with the serial number 685999480 (the serial number of the programmer on the DK) is located on your "COM20". In order to use it with mcumgr (if you have mcumgr installed according to the guide), you can use the command:

mcumgr --conntype serial --connstring "COM20" echo hello

It also works without the " around COM20, but if you want to add more parameters, such as "baud=115200", you need the ", like this: "COM20,baud=115200". However, the baudrate is by default set to 115200.

Best regards,

Edvin