Command line interface hex file

[roaspey]

Hi,

I have previously compiled the zigbee command_line_agent for the PCA10059 which I use for testing.

It worked when uploaded so I have one working PCA10059.

Recently I upgraded the windows software for Nordic's nRF Connect for Desktop to v3.11.0.

Having recompiled the hex file for /examples/zigbee/experimental/cli/cli_agent_router

via pca10059/mbr/armgcc

e.g.) make clean ; make erase

I find when flashing the dongle with the hex file (e.g. ../pca10059/mbr/armgcc/_build/nrf52840_xxaa.hex

and now I am unable to see it as a serial device in windows.

Is there a pre-compiled "known working" version of this hex file I can keep for reference?

I want a few PCA10059 flashed as command_line_agent and currently I cannot get the hex file

to work the same as previous

[Edvin]

Hello,

I don't think the version of nRF Connect for Desktop should matter, since it is not related to the nRF5 SDK. The only thing it should be related to is the way you program the dongle (if you are using nRF Connect for Desktop -> Programmer).

Do you see the dongle in nRF Connect for Desktop -> Programmer? If you press the reset button (not SW1) when the dongle is powered, does it start to blink (breathe) the red LED?

You can test with the attached .hex file. I couldn't test it right now, because I don't have a dongle on my desk, but it should be an unmodified CLI example:

7563.nrf52840_xxaa.hex

Best regards,

Edvin

[roaspey]

I agree the nRF Connect version should not make any difference. Yes it breathes red ok, it programs ok

but when the hex you provided uploaded I don't get a '>' prompt or a COM port showing up.

I have another dongle that I programmed previously and that enumerates ok, gremlins I expect.

Any ideas - below is what Device Manager yields - the device seems to be a com port at 9600 but it does

not allow me to connect via terminal, while the older device does. I use either termite or an older program

terraterm. Neither work !

Device USB\VID_1915&PID_1337&MI_00\7&5a8ff6d&0&0000 was configured.

Driver Name: usbser.inf
Class Guid: {4d36e978-e325-11ce-bfc1-08002be10318}
Driver Date: 06/21/2006
Driver Version: 10.0.19041.1202
Driver Provider: Microsoft
Driver Section: UsbSerial_Install.NT
Driver Rank: 0xFF2000
Matching Device Id: USB\Class_02&SubClass_02&Prot_01
Outranked Drivers: usbser.inf:USB\Class_02&SubClass_02:00FF2001
Device Updated: false
Parent Device: USB\VID_1915&PID_1337\D444C0989042

[Edvin]

Hello,

Just needed to check in on something (it's evening here now), and I saw that you had replied. 

Remember that the Dongle may change the COM port when you have programmed it. 

Also, please try to use the baudrate 115200, as listed here:

https://infocenter.nordicsemi.com/topic/sdk_tz_v4.2.0/zigbee_example_cli_agent.html?cp=8_3_3_8_5_1_0#zigbee_example_cli_agent_interfaces

And for how to set up putty (You say that you are using terraterm, but perhaps you can check whether you can access it using putty, just for the sake of debugging/testing), please see:

https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.1.0/lib_cli.html#lib_cli_terminal_settings

If that doesn't work, I will get my hands on a dongle and test this tomorrow.

Best regards,

Edvin