An error occurs when you use "Flash" in Visual Studio Code

[ppc paper]

Greetings,

I want to write the nRF Connect SDK v2.0.0 sample "nrf9160/https_client" to the nRF9160-DK,
but when I use "Flash" in Visual Studio Code, the following error occurs.

ERROR: The JLinkARM DLL timed out while communicating to the J-Link probe.
ERROR: If the error condition persists, run the same command again with
ERROR: argument -- log, contact Nordic Semiconductor and provide the generated
ERROR: log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 35: nrfjprog --program 'C:\Users\protec\Desktop\https_client\build\zephyr\merged.hex' --chiperase --verify -f NRF91 --snr 960007184

My build settings are as follows, am I doing something wrong?

I would be happy to get your advice.

[Sigurd Hellesvik]

Hi,

How have you connected your nRF9160DK to your computer?

Have you turned the power of your nRF9160DK on?

Regards,
Sigurd Hellesvik

[ppc paper]

Hello,

Thank you for your reply.
I made sure it was powered on and connected to my PC via USB.
After that, when I ran "Flash" again, the following log was displayed.

Flashing build to undefined
west flash -d c:\Users\protec\Desktop\https_client\build --skip-rebuild -r nrfjprog --dev-id 960007184

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: C:\Users\protec\Desktop\https_client\build\zephyr\merged.hex
Parsing image file.
Verifying programming.
Verified OK.
Applying pin reset.
-- runners.nrfjprog: Board with serial number 960007184 flashed successfully.

When I execute AT command with Link Monitor v2.0.1, I get timeout error even if I send it.

Any solution?
We are planning mass production, so it would be helpful if you could give us some advice.

[Sigurd Hellesvik]

Hi

If you want to test the AT commands,I suggest you try our AT Client sample.

Regards,
Sigurd Hellesvik

[ppc paper]

Hello,

thank you for your answer.
I misunderstood that AT commands can be used in all samples.
I want to use "nrf9160/https_client".
It says to use a terminal emulator here, but what does that look like?
Any advice would be appreciated.

[Sigurd Hellesvik]

Hi,

The terminal emulator for the https_client sample would be to see the logs from the sample.

You can enable AT commands in the https_client sample by adding the following lines, which I found in the at_client/prj.conf:

# AT host library
CONFIG_AT_HOST_LIBRARY=y
CONFIG_UART_INTERRUPT_DRIVEN=y

Regards,
Sigurd Hellesvik

[ppc paper]

Thank you for your answer.

How do you use a terminal emulator?
Where can i download it?
I would like to debug the nRF9160-DK to see if the https_client sample is written correctly.

Thank you for your reply regarding the AT command. I'll give it a try.

[Sigurd Hellesvik]

Hi,

There are multiple alternatives for Terminal Emulators. Here are some I suggest:

If you use VS Code, you can use the Integrated Serial Terminal.

Or you can use the LTE Link Monitor in the nRF Connect for Desktop.

Regards,
Sigurd Hellesvik