Trouble connecting https socket second time in nrf9160. And connecting debugger issue

RE: Trouble connecting https socket second time in nrf9160. And connecting debugger issue

Amritpal — Wed, 04 Mar 2020 16:26:46 GMT

Thanks Didrik

RE: Trouble connecting https socket second time in nrf9160. And connecting debugger issue

Didrik Rokhaug — Wed, 04 Mar 2020 16:24:27 GMT

Thanks for the traces and the code.

We are still working on identifying the source of the problem, but it seems like it was introduced in bsdlib v6.1.

If I use v6.0 instead, the problem does not occur for me.

You can revert to v6.0 by replacing the 1.2.0 revision of nrfxlib on line 72 in <ncs>/nrf/west.yml with 3e381d09f1d305e230435f5b6e4c9ef928b6a697, and running "west update".

RE: Trouble connecting https socket second time in nrf9160. And connecting debugger issue

Amritpal — Tue, 03 Mar 2020 18:22:18 GMT

Thanks Didrik,

Sorry for the delay was busy in other stuff

I was able to fix my SES with your files, thanks for that.

Here is the source code with the workaround. It is based on https_client example. The workaround is

//Work around for socekt
        if(fd!=2)
        {
          printk("closing socket: %d\n", fd);
          (void)close(fd);
        }
        else
        {
          printk("skipping closing socket: %d\n", fd);
        }

devzone.nordicsemi.com/.../2626.main.c

to disable workaround just change the if condition to be always true in close

I am also attaching the modem trace files one in which socket is unresponsive and one with the work around

devzone.nordicsemi.com/.../code-stuck.bin

devzone.nordicsemi.com/.../with_2D00_workaround.bin

RE: Trouble connecting https socket second time in nrf9160. And connecting debugger issue

Didrik Rokhaug — Tue, 03 Mar 2020 16:01:55 GMT

Hi.

I have been able to provoke behavior similar to what you are seeing using the cloud_client sample. I have not yet been able to recreate your workaround (simply opening another socket does not work), but I will keep working on it tomorrow. I have captured a modem trace and forwarded it to our R&D team for deeper analysis. However, I would still like a modem trace from you to confirm that we are seeing the same problem.

I'll keep you updated when I know more.

Best regards,

Didrik

RE: Trouble connecting https socket second time in nrf9160. And connecting debugger issue

Didrik Rokhaug — Fri, 28 Feb 2020 15:54:59 GMT

Hi.

We are seeing some issues with SES v4.42. They are reported internally, and we are working on fixing them.

As a workaround, you can downgrade the J-Link version used by SES to v6.50 by copying the files in JLink=6.50.zip to the bin folder in your SES install directory (replacing any previous versions that might be there).

You must also ensure that SES loads the elf files that your application consists of in the correct order (MCUBoot first, then SPM, finally your application). If your application does not use MCUBoot, SPM would be first, then your application.

devzone.nordicsemi.com/.../JLink_5F00_6.50.zip

How do you close, then re-open the socket?

Can you share some code that reproduces the problem?

Can you take a modem trace that captures the problem?

A trace that shows your workaround to compare with would also be useful.

You can follow this guide to learn how to take modem traces: https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/how-to-get-modem-trace-using-trace-collector-in-nrf-connect

Best regards,

Didrik