mfw_nrf9160_1.3.2.zip - behavior change on lost network?

RE: mfw_nrf9160_1.3.2.zip - behavior change on lost network?

Hakon — Thu, 04 Aug 2022 13:24:38 GMT

Okay, thanks for the feedback.

RE: mfw_nrf9160_1.3.2.zip - behavior change on lost network?

Achim Kraus — Sun, 31 Jul 2022 10:25:56 GMT

> So the left question for me is, what are the users/developers considered to do on such an update. Trying to compare the documentation? Really?

I'm only evaluating the nRF9160.

Anyway, the answer on how such updates should be handled by users is not that irrelevant. At least I consider the "network reconnect/search" as critical for products.

There are also related issues pointing into that direction:

How to recover a nRF9160 from sporadic ENETDOWN

LTE-M Reconnect after LoS

Maybe, there are better ideas than using the errno. If so, maybe they get documented

(Just mention: I know it's summer, and for now my stuff runs again. But maybe over the next month Nordic considers to document the ideas to implement such a "save reconnect".)

Other issues, caused by unaware changes with the update from 1.9.1 to 2.0.0:

upgrade sdk 1.9.1 to 2.0.0

So, I can only recommend, that the "change notes" may get more complete.

RE: mfw_nrf9160_1.3.2.zip - behavior change on lost network?

Hakon — Thu, 28 Jul 2022 13:38:29 GMT

Modem team;

"Before that (1.3.1), my experience was to get a ENETDOWN, when calling "sendto" while the device has lost some the network"
This behavior is unchanged.

If the customer sees ESHUTDOWN is because of another reason, that is, the sendto() call was interrupted because the Modem was turned off by an application call to nrf_modem_lib_shutdown().

RE: mfw_nrf9160_1.3.2.zip - behavior change on lost network?

Achim Kraus — Mon, 25 Jul 2022 12:36:01 GMT

Thanks for refer to "nrf_socket.h".

The diff between v1.9 branch and the v2.0 branch is:

v1.9

@return The number of bytes that were sent on success.
-1 on error, and errno indicates the reason for failure.

v2.0

In addition, the function shall return -1 and set the following errno:
[NRF_ESHUTDOWN] Modem was shut down.

So the left question for me is, what are the users/developers considered to do on such an update. Trying to compare the documentation? Really?

RE: mfw_nrf9160_1.3.2.zip - behavior change on lost network?

Hakon — Mon, 25 Jul 2022 11:17:45 GMT

Modem team;

Changes are likely related to new modem library rather than new modem firmware.

ESHUTDOWN means - Modem was shutdown. That means, either the application shut down the modem or the modem has crashed.
ENETDOWN still means - PDN was deactivated. Socket must be destroyed and re-created (and optionally reconnected).

ESHUTDOWN return value is documented in the send()/sendto() function doxygen in the nrf_socket.h header.

RE: mfw_nrf9160_1.3.2.zip - behavior change on lost network?

Achim Kraus — Fri, 22 Jul 2022 12:42:18 GMT

Thanks!

In the meantime I got also ENETUNREACH.

I'm not sure, if I tested the 1.3.1 too lazy (by the way, more then for 3 weeks with th3 1.3.1), or if that has changed.

RE: mfw_nrf9160_1.3.2.zip - behavior change on lost network?

Hakon — Fri, 22 Jul 2022 12:37:56 GMT

Hello,

I have asked the modem team to comment on this.