nRF9160 Connectivity issue

RE: nRF9160 Connectivity issue

Øyvind — Wed, 27 Jan 2021 10:38:39 GMT

Thank you Dirk. I am working with our Trace Collector developer and will get back to you as soon as possible.

I'm sorry for the inconvenience this is causing.

Kind regards,
Øyvind

RE: nRF9160 Connectivity issue

dhandzic — Wed, 27 Jan 2021 09:59:03 GMT

Hi Öyvind,

the modem trace DOES NOT show in Trace Collector and yes the screenshots are taken according to your request from Device Manager and the developer console in Trace Collector.

Kind regards

Dirk

RE: nRF9160 Connectivity issue

Øyvind — Wed, 27 Jan 2021 09:51:10 GMT

Hi Dirk,

Sorry for the delayed answer.

From the screenshot of LTE Link Monitor, the information is very similar to what you would see from the modem trace. If you disconnect the device from LTE Link Monitor, will it show in Trace Collector?

The screenshot of the developer console, was this taken in the Trace Collector?

Thanks!

Kind regards,
Øyvind

RE: nRF9160 Connectivity issue

dhandzic — Thu, 21 Jan 2021 13:51:00 GMT

RE: nRF9160 Connectivity issue

dhandzic — Thu, 21 Jan 2021 13:46:40 GMT

RE: nRF9160 Connectivity issue

Øyvind — Thu, 21 Jan 2021 13:41:00 GMT

Also, can you please provide information from Device Manager regarding the connection? I.e. the COM ports and FTDI cable. Please include VIDs and PIDs

Try the following in the Trace Collector:
Ctrl+Shift+I to enter developer console. Then in the console please enter the following command:

require('serialport').list().then(a => a.forEach(p => console.log(p.path, p.vendorId, p.productId)))

This should output info on the left hand side under "info". The following was outputed in mine:

RE: nRF9160 Connectivity issue

Øyvind — Thu, 21 Jan 2021 13:26:25 GMT

When connecting to LTE Link Monitor with your device, can you please screenshot what shows in Window? Please screenshot the whole LTE Link Monitor window.

RE: nRF9160 Connectivity issue

dhandzic — Thu, 21 Jan 2021 10:31:33 GMT

devzone.nordicsemi.com/.../Q3IoT_5F00_zephyr_5F00_boards_5F00_arm.zip

devzone.nordicsemi.com/.../Q3IoT210121.zip

Hi Öyvind,

here are my board def files and the entire project map.

Best regards

Dirk

RE: nRF9160 Connectivity issue

Øyvind — Thu, 21 Jan 2021 10:12:12 GMT

Can you please share your current project with me?

Thanks!

Kind regards,
Øyvind

RE: nRF9160 Connectivity issue

dhandzic — Wed, 20 Jan 2021 15:17:55 GMT

Hi Öyvind,

I have changed the uart in bsd_os.c to uart2 but the problem is still the same. Trace Collector shows "No device available" and after a while the screen turns white. A couple of weeks ago there has been a similar problem with the LTE Link Monitor. I think it is the same bug when the app has to talk to a non DK board. The FTDI cables are usually no problem.

Best regards

Dirk

RE: nRF9160 Connectivity issue

Øyvind — Wed, 20 Jan 2021 08:32:52 GMT

Hi Dirk,
Thanks for verifying the information. Yes, it sounds like you should change the UART output of the trace. Please change it to UART2.

Kind regards,
Øyvind

RE: nRF9160 Connectivity issue

dhandzic — Tue, 19 Jan 2021 15:20:49 GMT

Hi Öyvind,

the FTDI TTL-232R-3V3 is pecified to support up to 3 Mbaud. I have also been able to use this cable and LTE Link Monitor to see LOG_INFO output from the board.

In LTE Link Monitor the FTDI cable shows up regardless if it is connected to the board or not. In Trace Collector it does not show up at all. I have checked the trace_uart_init function in bsd_os.c and it it points to the UART1 which also is used and is working for LOG_INFO outputs. Is there maybe a conflict? Do I need to change the trace output UART to UART2?

Best regards

Dirk

RE: nRF9160 Connectivity issue

Øyvind — Tue, 19 Jan 2021 14:08:50 GMT

Dirk, I've discussed this issue with Carl Richard and we were not able to get it working. The output in LTE Link Monitor looks like the modem trace data, but needs to be verified. It looks like your settings for the trace collector is configured incorrectly. Can you please see this thread about a similar issue, and see if this fixes the issue. Make sure that your cable supports 1Mbaud as the modem trace is hard coded to this, you also need to confirm that your configured correct UART for modem trace.

RE: nRF9160 Connectivity issue

dhandzic — Tue, 19 Jan 2021 09:35:15 GMT

Carl Richard Steen Fosse at Nordic has both one of our boards and a cable. I can share my board definition files and the project files if this helps.

I think there might be an issue with latest version of the Trace Collector and the FTDI cable.

Best regards

Dirk

RE: nRF9160 Connectivity issue

dhandzic — Tue, 19 Jan 2021 09:28:56 GMT

I am using a FTDI TTL-232R-3V3 cable. It shows up in the Device Manager, I am able to connect to this VCOM port using LTE Link Monitor, but the port does not show up in Trace Collector!

When connecting with LTE Link Monitor to this port the output looks like this:

Best regards

Dirk

RE: nRF9160 Connectivity issue

Øyvind — Tue, 19 Jan 2021 08:57:02 GMT

How are you connecting the UART ports to your computer? Do they show up in your Device Manager (as COM ports)?

What is the unreadable text that is shown in LTE Link Monitor? What device are you connecting when you see this?

-Øyvind

RE: nRF9160 Connectivity issue

dhandzic — Tue, 19 Jan 2021 08:22:28 GMT

Hi Öyvind,

I have routed UART1 and UART2 to a header. I normally can get LOG_INF output out on UART1. I have however disabled LOG output. My .dts file:

devzone.nordicsemi.com/.../q3iot_5F00_common.dts

My prj.conf:

devzone.nordicsemi.com/.../5618.prj.conf

As reported before. I can connect to the board using LTE Link Monitor and a lot of data is shown in the terminal, but no readable text.

Using Trace Collector only "No device connected" is shown even without port filter checked.

Best regards

Dirk

RE: nRF9160 Connectivity issue

Øyvind — Tue, 19 Jan 2021 07:51:05 GMT

Does your application print anything to terminal? What UART have you configured? The modem trace should be using UART1 by default.

Kind regards,
Øyvind

RE: nRF9160 Connectivity issue

dhandzic — Mon, 18 Jan 2021 16:20:07 GMT

Hi Öyvind,

I am trying to get a trace. I have defined CONFIG_BSD_LIBRARY_TRACE_ENABLED=y but when I try to connect with Trace Collector even with Auto/device port filter uncheck it says no device. When I connect with LTE Link Monitor my USB cable shows up and after connecting a lot of unreadable data comes in. I am using the latest nRF Connect 3.6.1 with Trace Collector 1.0.6.

Best regards

Dirk

RE: nRF9160 Connectivity issue

Øyvind — Mon, 18 Jan 2021 15:29:56 GMT

Hi Dirk,

Can you please provide a log output from your device? Difficult to tell what is going on.

How long have you let it run?

Thanks!

Kind regards,
Øyvind

RE: nRF9160 Connectivity issue

dhandzic — Fri, 15 Jan 2021 13:16:01 GMT

Hi Öyvind,

I am running a LWM2M client application. I dont think the AT client will replicate this behaviour. I am not sure how to get a modem trace while using our LWM2M application.

Best regards

Dirk

RE: nRF9160 Connectivity issue

Øyvind — Fri, 15 Jan 2021 13:09:36 GMT

Hi Dirk,

Can you provide an output from AT client, which shows more information about the connection? Also, it may be required that you also do modem trace.

Kind regards,
Øyvind