AT Host FAILED: Cannot connect to J-Link.

RE: AT Host FAILED: Cannot connect to J-Link.

dejans — Tue, 09 Jul 2024 14:03:36 GMT

Hi,

Guide for downloading and provisioning nRF Cloud certificate can be found in the documentation.

Best regards,
Dejan

RE: AT Host FAILED: Cannot connect to J-Link.

parappapj — Tue, 09 Jul 2024 00:04:13 GMT

Thank you. Do you have any resources on how to complete the step "Generate and provision the device certificate" using Cellular Monitor in nRF desktop? The previous step 'Generate a CA certificate' creates a .pem, .key, and .srl files along with a document titled 'currentCA'.

RE: AT Host FAILED: Cannot connect to J-Link.

dejans — Thu, 04 Jul 2024 08:16:35 GMT

Hi,

Thank you for additional information.

Based on system requirements, MacOS is not supported. You could try to flash certificates manually using nRF Connect for Desktop. Regarding MacOS support, you can upvote this topic.

Best regards,
Dejan

RE: AT Host FAILED: Cannot connect to J-Link.

parappapj — Wed, 03 Jul 2024 20:36:30 GMT

Hi Dejan,

Yes, I updated the connectivity bridge, modem firmware and application firmware following the guide you posted. In nRF cloud I can see my thingy91 with the following device info:

App Version:

0.0.0-development

Board:

thingy91_nrf9160

Hw Ver:

nRF9160 SICA B1A

Modem Firmware:

mfw_nrf9160_1.3.6

Sdk Ver:

v2.6.0-3-gaf2b60d2148e

Zephyr Ver:

v3.5.99-ncs1

Running './cli.sh create-and-provision-device-cert --debug' to create device credentials per the Asset Tracker v2 setup guide produces this output:

Flashing certificate /dev/tty.usbmodem1104
Connecting to /dev/tty.usbmodem1104
Inactivity timeout 10 seconds
/dev/tty.usbmodem1104 connected
AT Host h
w4 4001e504 2
w4 4001e50c 1
sleep 100
rx 1000
h
w4 4001e504 1
loadfile /Users/user/nrf-asset-tracker/aws/node_modules/@nordicsemiconductor/device-helpers/at_host/thingy91_at_host_increased_buf.hex
rx 1000
g
exit
AT Host SEGGER J-Link Commander V7.94e (Compiled Jan 15 2024 15:15:51)
AT Host DLL version V7.94e, compiled Jan 15 2024 15:15:39
AT Host J-Link Command File read successfully.
AT Host Processing script file...
AT Host J-Link>h
AT Host J-Link connection not established yet but required for command.
AT Host Connecting to J-Link via USB...
AT Host FAILED: Cannot connect to J-Link.
AT Host J-Link>w4 4001e504 2
AT Host J-Link connection not established yet but required for command.
AT Host Connecting to J-Link via USB...
AT Host FAILED: Cannot connect to J-Link.

and so on....

RE: AT Host FAILED: Cannot connect to J-Link.

dejans — Wed, 03 Jul 2024 15:07:36 GMT

Hi,

Have you tried updating Thingy91 firmware using Programmer or running separate updates on nrf52840 and nrf9160? Do you see the same error after this?

Best regards,
Dejan

RE: AT Host FAILED: Cannot connect to J-Link.

parappapj — Tue, 02 Jul 2024 15:22:08 GMT

Hi Dejan,

I’m on a M2 MacBook Pro with MacOS Sonoma 14.

I’m using J-Link 7.96q. I’ve tried with 7.95, 7.94 and 7.88 as well. Same error with each.

The board I have is the Thingy91.

RE: AT Host FAILED: Cannot connect to J-Link.

dejans — Tue, 02 Jul 2024 13:32:49 GMT

Hi,

Which operating system do you use?

Which J-Link version do you use?

Which board do you use?

Best regards,
Dejan