Modem FW 1.3.4 Error 0x10

RE: Modem FW 1.3.4 Error 0x10

Achim Kraus — Tue, 01 Apr 2025 11:46:03 GMT

From the experience in the past years, I guess there is just not enough information, that Nordic will be able to check something. As I wrote two years ago, the users will in many cases not be able to provide traces for issues, which occurs only rarely.

I also answered on your new ticket. I recommend that you try to use a newer mfw and NCS versions, though that may have fixed your issue in the meantime (even if the 1.3.5/2.5.0 used by you is already newer than the one of this ticket).

In my case mfw 1.3.6/7 and NCS 2.6.0-4 runs pretty stable, I haven't seen the "modem crashed" with them.

(NCS 2.9.1 runs so far also well on my side, but that's too short to say too much.)

RE: Modem FW 1.3.4 Error 0x10

David Bassil — Tue, 01 Apr 2025 11:34:15 GMT

Please check the error we are getting also before you get from us the traces. There are devices that are stopping that are customer site with this error. this comes from Nordic site. its not an application error

RE: Modem FW 1.3.4 Error 0x10

dejans — Tue, 01 Apr 2025 08:12:46 GMT

Hi,

[quote user="David Bassil"]we do not have a modem trace right now. we will try to get it[/quote]

Hopefully, you will be able to capture it. When you have it, please upload it to your other ticket and continue discussion there.

Best regards,
Dejan

RE: Modem FW 1.3.4 Error 0x10

David Bassil — Mon, 31 Mar 2025 11:39:01 GMT

we do not have a modem trace right now. we will try to get it

RE: Modem FW 1.3.4 Error 0x10

dejans — Mon, 31 Mar 2025 11:36:40 GMT

Hi,

[quote user="David Bassil"]I already did. this is the my Case ID : 343162[/quote]

Thank you for letting me know.

[quote user="David Bassil"]could you please check it[/quote]

One of our engineers will look into this issue soon.
Please do not forget to upload modem trace.

Best regards,
Dejan

RE: Modem FW 1.3.4 Error 0x10

David Bassil — Mon, 31 Mar 2025 11:30:57 GMT

hey Dejans,

I already did. this is the my Case ID : 343162

could you please check it

RE: Modem FW 1.3.4 Error 0x10

dejans — Mon, 31 Mar 2025 11:29:29 GMT

Hi David Bassil ,

This ticket is quite old. Please open new ticket and provide all relevant information (including logs) there. In addition, please provide modem trace for investigating the issue.

Best regards,
Dejan

RE: Modem FW 1.3.4 Error 0x10

David Bassil — Sat, 29 Mar 2025 11:44:22 GMT

Hey,

We seem to have the same problem . I would like to report an error that is happening with devices that have very low sleep time intervals ( 3 min or 5 min). After a while of normaly working those devices are crashing with an error shown in screen shot below (UART Logs). I also attached the UART logs in a file, the devices were working fine an after a while they crash ( all cases are with devices with very low sleep time). Once we reset the device it works again. The devices with very low sleep time intervals( 3 to 5minutes) are crashing again. Could you help us here please? we are currently in series production

devzone.nordicsemi.com/.../serial_2D00_terminal_2D00_29032025_5F00_113456.txt

RE: Modem FW 1.3.4 Error 0x10

barbiz — Sun, 25 Feb 2024 20:04:34 GMT

Hello,

we may have a similar issue. Can you please detail what was the issue here and is there any related issue/commit in the git?

Marco

RE: Modem FW 1.3.4 Error 0x10

Achim Kraus — Wed, 13 Sep 2023 07:05:30 GMT

Thanks!

So no "left overs" in the flash config, a factory reset will not clean up?

And no mechanisms, which prevents from downgrade with the 1.3.x line?

RE: Modem FW 1.3.4 Error 0x10

emdi — Wed, 13 Sep 2023 07:03:41 GMT

Sure, in case you have the nRF91 connected to a PC you can use the desktop tools to flash any modem firmware version you want.

RE: Modem FW 1.3.4 Error 0x10

Achim Kraus — Tue, 12 Sep 2023 19:23:40 GMT

My question is about using the official Nordic download of the modem firmware.

e.g. the modem was updated to 1.3.3, but I feel, it's better to got back to 1.3.2.

I use normally the "nRF Connect for Desktop => Programmer" and a Jlink.

RE: Modem FW 1.3.4 Error 0x10

emdi — Tue, 12 Sep 2023 13:55:35 GMT

Hello Achim Kraus , as long as you have the _original_ patch you updated from, you can rollback.

If you have updated the device over the air using `nrf_modem_delta_dfu` APIs, it is possible to rollback as long as you don't erase erase the modem firmware patch (using `nrf_modem_delta_dfu_erase()`).

The rollback process is documented here: Delta firmware updates — nrfxlib 2.4.99 documentation (nordicsemi.com)

RE: Modem FW 1.3.4 Error 0x10

Didrik Rokhaug — Thu, 13 Apr 2023 14:10:58 GMT

Hi, and sorry for the late reply.

I understand that it is not always easy/practical/possible to gather modem traces, especially for devices out in the field.

However, it is not always possible for us to recreate the same conditions in a lab, or even know what the conditions were. There can be quite a lot of differences in how a cellular network is configured, and sometimes, the problem is caused by the network itself.

We do test our modem FW in different networks, to try to avoid network specific problems, and to test the modem FW in different environments. But, even within the same network, there might be differences between different regions, or even between different cell towers. So it is not possible for the testing to account for everything.

Where did you experience these problems (the more specific location, the better. If you don't want to post the location here, you can send it to me in a private message)? We are currently planning a new field-test trip, and might be able to visit that location to try to reproduce this problem.

Best regards,

Didrik

RE: Modem FW 1.3.4 Error 0x10

mrks115 — Wed, 22 Mar 2023 12:54:05 GMT

Regarding this error I also won't investigate further. Seems to be not reproducible.

I'm happy to help where I can, but I also want to emphasize what Achim Kraus is saying. As a developer, if I see a bug on my desk by chance, I'm glad to provide a modem trace. On field test devices or when colleagues report such an error to me, I unfortunately don't always have the opportunity to reproduce it and I see Nordic as being more obliged here.

RE: Modem FW 1.3.4 Error 0x10

Achim Kraus — Fri, 17 Mar 2023 17:34:39 GMT

With almost 4 decades of software development, trying to catch a sporadic error as this one (once in a couple of weeks) in a "black box approach" (without the sources to see potential causes and be able to focus tests on that) is a waste of time. In my opinion, this make only sense with sources and the possibility to focus on some weakness or obscurities. With that someone may have a chance to catch it. So, it's up to Nordic and your software development to go for it. Or not.

Therefore my question, if It's generally possible to downgrade from 1.3.4 to 1.3.3. ?

(Just to mention: therefore I gave up reporting such very rare or long term issues. With the Nordic policy of "user provided logs" that doesn't make sense and is very ineffective.)

RE: Modem FW 1.3.4 Error 0x10

Didrik Rokhaug — Fri, 17 Mar 2023 16:41:48 GMT

Hi mrks115 and Achim Kraus,

Unfortunately, we are not able to find the cause of the "Modem error: 0x10, PC: 0x7ce68"-error without a modem trace.

Are either of you able to capture a modem trace where that error occurs?

Best regards,

Didrik

RE: Modem FW 1.3.4 Error 0x10

Achim Kraus — Mon, 13 Mar 2023 18:32:46 GMT

Today I got the same "<err> nrf_modem: Modem error: 0x10, PC: 0x7ce68" message.

Is it possible to downgrade the modem back 1.3.3 ?

RE: Modem FW 1.3.4 Error 0x10

Didrik Rokhaug — Fri, 10 Mar 2023 17:42:18 GMT

Hello again,

The modem team has identified the issue in the modem trace, and are working on implementing a fix for it.

I don't know all the details, but it has something to do with cells having an invalid band indicator value.

As a workaround, you can disable band 66 with the %XBANDLOCK AT command.

RE: Modem FW 1.3.4 Error 0x10

Didrik Rokhaug — Tue, 07 Mar 2023 15:38:12 GMT

A quick update: The issue in the modem trace you provided seems to be a different issue than in your original ticket. However, it did provide the modem team some information about the original ticket as well, and they are currently investigating both issues.

RE: Modem FW 1.3.4 Error 0x10

Didrik Rokhaug — Mon, 06 Mar 2023 17:15:52 GMT

Hi, and sorry for the slow response, but I was out of office last week.

I have forwarded your modem trace to the modem team.

They usually answer quite fast, and I'll come back to you when they are done with their analysis of the trace.

Best regards,

Didrik

RE: Modem FW 1.3.4 Error 0x10

mrks115 — Mon, 27 Feb 2023 10:36:08 GMT

Hey,

now I can provide you a Modem Trace, but I'm not sure whether this is related to my original post.

Conditions changed:

NB-IoT
Connect to Cellular
Connect to our LwM2M Server
Stay connected forever
After about 4 minutes modem error occurs
- It is reproducible in most cases

devzone.nordicsemi.com/.../trace_2D00_2023_2D00_02_2D00_27T10_2D00_24_2D00_52.749Z.bin

[00:00:14.773,803] <inf> lwm2m: EVT_CONNECTED
[00:00:25.052,734] <wrn> modem: RRC idle
[00:04:23.321,899] <err> Modem error: 0x10, PC: 0x9af46

Please let me know if you need more details.

RE: Modem FW 1.3.4 Error 0x10

Didrik Rokhaug — Fri, 03 Feb 2023 12:23:54 GMT

Unfortunately, there isn't much we can do without a modem trace, but they did offer some thoughts:

This comes from the library (based on some trigger from modem), but "Failed to set functional mode. Please check XSYSTEMMODE" kind of hints that in system mode there would be some systems active that are not supported by the HW version. Or, that there is a band lock active and none of the locked bands are supported by the currently activated system mode. These are just initial guesses without a modem log. Should be easy to resolve if a modem log is received.

RE: Modem FW 1.3.4 Error 0x10

mrks115 — Tue, 31 Jan 2023 16:16:02 GMT

The error unfortunately only occurred occasionally during testing (without tracing).

We'll try to reproduce this error with modem trace. But this might need some time to set this up.

RE: Modem FW 1.3.4 Error 0x10

Didrik Rokhaug — Tue, 31 Jan 2023 13:35:41 GMT

Hi,

I'll check with the modem team if they know what the error means.

However, as Torje says, a modem trace will probably be very helpful.

Best regards,

Didrik