Command line interface hex file

RE: Command line interface hex file

Edvin — Tue, 26 Apr 2022 19:37:04 GMT

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

RE: Command line interface hex file

roaspey — Tue, 26 Apr 2022 16:33:20 GMT

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

RE: Command line interface hex file

Edvin — Tue, 26 Apr 2022 13:43:11 GMT

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:

devzone.nordicsemi.com/.../7563.nrf52840_5F00_xxaa.hex

Best regards,

Edvin