Unable to connect to Thingy:91 with at_client using Link Monitor

[mdjarv]

I have flashed my Thingy:91 via the nRF9160 DK using the Programmer with the pre-built at_client software, but I am unable to get any AT response when I connect using the Link Monitor.

The Thingy:91 is connected with both the programming cable as well as the USB cable, and I connect directly to it via its COM ports (doesn't make a difference if I have "Auto device/port filter" selected or not). Nothing comes out in the black log window, and if I try to send AT it just times out.

The switch on the device is set to nRF91, and I have tried this on both Windows and Linux with the same result.

I have also tried to install my own built software that I have previously tested on the DK but I can not get any debug logging in the Link Monitor for that software either on the Thingy:91

[Didrik Rokhaug]

Hi.

Is the Link Monitor able to connect to the Thingy, but you do not get any output, or is the Link Monitor unable to connect to Thingy at all?

Have you gotten output from the Thingy before?

Do you get any output if you use a different terminal emulator?

Can you send me the log from the Link Monitor (at the bottom of the screen)?

Can you try to program the default firmware back to both the nRF9160 and the nRF52840?

I have attached the default firmware for both the nRF9160 and the nRF52840.

thingy_firmware.zip

Best regards,

Didrik

[mdjarv]

The Link Monitor can connect, but I get no output. The Link Monitor works well with my DK but not the Thingy:91

I have on two occations seen actual UART output printed from the thingy, one of those times was with the at_client firmware and the other was probably with the default firmware, it still did not respond to AT commands either of those times though.

I've connected both with and without the device port/filter option but it does not make a difference.

Same problem with other terminal emulators.

I'll flash the firmware you provided and generate some logs when I get back to the office on monday, thanks for taking the time to help.

Regards,
Mathias

[mdjarv]

I flashed the nrf52 firmware you attacked to the nRF52840 and the ltem firmware to the nRF9160.

After that I ran some more tests with the Link Monitor, and made a couple of observations.

• If I am really really quick to connect to the Thingy:91 after power on I can see the debug logs it prints out.
• Same goes for the at_client from the v0.2.3 prebuilt hex files
• If I manage to attach the link monitor fast enough I can get an OK response from the AT command, however it eventually stops responding after a few seconds. Could it be some timing issues or does it turn off automatically or something similar?

Below is the logs from the Link Monitor for when I manage to attach to the at_client, get the initialization log output and response to the first few AT commands and then it eventually stops responding after about 10 seconds:

2019-11-18T07:53:34.711Z INFO Application data folder: /home/mdjarv/.config/nrfconnect/pc-nrfconnect-linkmonitor
2019-11-18T07:53:34.769Z DEBUG App pc-nrfconnect-linkmonitor v1.1.1 official
2019-11-18T07:53:34.769Z DEBUG App path: /home/mdjarv/.nrfconnect-apps/node_modules/pc-nrfconnect-linkmonitor
2019-11-18T07:53:34.769Z DEBUG nRFConnect 3.3.0 is supported by the app (^3.2.0)
2019-11-18T07:53:34.769Z DEBUG nRFConnect path: /tmp/.mount_nrfcon45yRdt/resources/app.asar
2019-11-18T07:53:34.769Z DEBUG HomeDir: /home/mdjarv
2019-11-18T07:53:34.769Z DEBUG TmpDir: /tmp
2019-11-18T07:53:35.075Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS0
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS1
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS10
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS11
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS12
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS13
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS14
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS15
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS16
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS17
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS18
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS19
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS2
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS20
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS21
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS22
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS23
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS24
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS25
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS26
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS27
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS28
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS29
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS3
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS30
2019-11-18T07:53:35.076Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS31
2019-11-18T07:53:35.077Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS4
2019-11-18T07:53:35.077Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS5
2019-11-18T07:53:35.077Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS6
2019-11-18T07:53:35.077Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS7
2019-11-18T07:53:35.077Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS8
2019-11-18T07:53:35.077Z VERBOSE Could not fetch serial number for serial port at /dev/ttyS9
2019-11-18T07:53:38.296Z INFO Modem port is opened
2019-11-18T07:53:38.544Z DEBUG modem << IIIêë¥e***** Booting Zephyr OS v1.14.99-ncs2 *****\x0D\x0A
2019-11-18T07:53:38.592Z DEBUG modem << The AT host sample started\x0D\x0A
2019-11-18T07:53:39.622Z DEBUG modem >> AT\x0D\x0A
2019-11-18T07:53:39.640Z DEBUG modem << OK\x0D\x0A
2019-11-18T07:53:40.943Z DEBUG modem >> AT\x0D\x0A
2019-11-18T07:53:40.978Z DEBUG modem << OK\x0D\x0A\x00
2019-11-18T07:53:42.384Z DEBUG modem >> AT\x0D\x0A
2019-11-18T07:53:42.399Z DEBUG modem << OK\x0D\x0A
2019-11-18T07:53:43.951Z DEBUG modem >> AT\x0D\x0A
2019-11-18T07:53:43.967Z DEBUG modem << OK\x0D\x0A
2019-11-18T07:53:45.449Z DEBUG modem >> AT\x0D\x0A
2019-11-18T07:53:45.463Z DEBUG modem << OK\x0D\x0A
2019-11-18T07:53:46.982Z DEBUG modem >> AT\x0D\x0A
2019-11-18T07:53:46.997Z DEBUG modem << OK\x0D\x0A\x00
2019-11-18T07:53:48.450Z DEBUG modem >> AT\x0D\x0A
2019-11-18T07:53:48.465Z DEBUG modem << OK\x0D\x0A\x00
2019-11-18T07:53:51.697Z DEBUG modem >> AT\x0D\x0A
2019-11-18T07:53:52.698Z ERROR Error: 'AT
' timed out

[Didrik Rokhaug]

Hi, and sorry for the long delay, but I have asked the developers for help, and they have not gotten back to me yet.

I will keep you updated when I get a reply.

Best regards,

Didrik

[mdjarv]

No problem, I appreciate the update

Regards,
Mathias