nRF9160 new SDK integration and build procedure

RE: nRF9160 new SDK integration and build procedure

Øyvind — Thu, 02 Oct 2025 08:40:14 GMT

Hello,

[quote user="sravan.rikka"]1. Is the GPS functionality can be enabled using nRF9160? If yes, can you please share the steps or procedure.[/quote]

Yes, the nRF9160 support GNSS. Have a look at our GNSS sample, and the Modem Library chapter on GNSS. You can also use the Serial LTE Modem application to configure GPS.

Please note: GPS receiver operation is time multiplexed with the LTE modem, and GPS and QZSS position can be received while the LTE modem is in RRC Idle mode, power saving mode (PSM), or completely deactivated. See GPS Receiver chapter in nRF9160 Datasheet

[quote user="sravan.rikka"]2. OTP memory available in nRF9160? if yes, how to access it?[/quote]

Yes, the OTP region of UICR is emulated by placing a write-once per halfword limitation on registers defined here. Please see OTP subsection in Key Management Unit (KMU) chapter and OTP in the UICR register.

[quote user="sravan.rikka"]3. If there is no catM1 or NBIOT network then will it fall back to 2g/3g?[/quote]

No. The nRF91 series support CatM1 and NB-IoT only.

[quote user="sravan.rikka"]4. When used QoS as 1 or QoS 2 and if the broker is down and how many times the nRF9160 retries sending publish message to the broker?[/quote]

/ .5 The application itself does not have built-in Quality of Service (QoS) handling. While the MQTT helper stack supports acknowledging QoS messages, it’s the responsibility of the application layer to implement full QoS behavior. This can be achieved by integrating the Quality of Service (QoS) library, which provides the necessary tools to manage message delivery guarantees.

[quote user="sravan.rikka"]6. nRF9160 subscribe for a topic and went to sleep state and publisher published the message to the broker but subscriber is in sleep state then broker will wait till subscriber wakeup and forwards the publish message? or broker will discard the message?[/quote]

When a device is subscribed to a topic, the broker will immediately deliver any published messages to it, provided the device is awake and connected. If the device is asleep, message delivery depends on whether the cellular network buffers messages during that period. Please note that not all networks support message buffering, so this behavior can vary depending on the operator and configuration.

Kind regards,
Øyvind

RE: nRF9160 new SDK integration and build procedure

sravan.rikka — Tue, 30 Sep 2025 17:09:30 GMT

Hi Øyvind,

1. Is the GPS functionality can be enabled using nRF9160? If yes, can you please share the steps or procedure.

2. OTP memory available in nRF9160? if yes, how to access it?

3. If there is no catM1 or NBIOT network then will it fall back to 2g/3g?

4. When used QoS as 1 or QoS 2 and if the broker is down and how many times the nRF9160 retries sending publish message to the broker?

5. QoS 1 or QoS 2 acknowledgements are handled by stack right? not handled in application level? If application wants to know that publish is successfully received by broker, is it possible, if yes please provide procedure.

6. nRF9160 subscribe for a topic and went to sleep state and publisher published the message to the broker but subscriber is in sleep state then broker will wait till subscriber wakeup and forwards the publish message? or broker will discard the message?

Regards,

Sravan Rikka

RE: nRF9160 new SDK integration and build procedure

Øyvind — Tue, 09 Sep 2025 08:33:32 GMT

Hello,

The MQTT sample documentation has been updated to elaborate around the sample and its usage of system threads

[quote user="sravan.rikka"]Can we take 'at_client' sample code as a starting point to start implementation at least drivers etc and later we will add mqtt related changes to this sample code, is the 'at_client' good to use as a starting sample code or do you suggest any other sample code as a starting point?[/quote]

You’re encouraged to begin with the sample that best fits your development needs. If the MQTT sample appears too advanced, consider exploring other examples available in our SDK and the Zephyr repository. These can be combined or adapted to suit your implementation.

Please note that this particular sample does not include a traditional main.c file. Instead, it follows a modular architecture where each module defines its own thread using the K_THREAD_DEFINE macro. This design removes the need for a central main() function, allowing each module to initialize and operate independently.

Inter-module communication is handled through Zephyr’s zbus message-passing system, resulting in a loosely coupled, event-driven architecture. For a clearer understanding of the application's flow, refer to the Sequence Diagram section.

More information can be found under Zephyr's System Thread chapter

Kind regards,
Øyvind

RE: nRF9160 new SDK integration and build procedure

sravan.rikka — Mon, 08 Sep 2025 12:56:02 GMT

Hi Oyvind,

Awaiting for your response.

Can we take 'at_client' sample code as a starting point to start implementation at least drivers etc and later we will add mqtt related changes to this sample code, is the 'at_client' good to use as a starting sample code or do you suggest any other sample code as a starting point?

'at_client' sample code available at below path in SDK 3.1.0.

C:\ncs\v3.1.0\nrf\samples\cellular\at_client.

Regards,

Sravan Rikka

RE: nRF9160 new SDK integration and build procedure

Øyvind — Thu, 28 Aug 2025 07:38:14 GMT

Hello,

[quote user="sravan.rikka"]The sample does not include a main.c file. To follow the typical flow of the application, see the Sequence diagram section. I found this in architecture webpage.[/quote]

Yes, that is correct. There is no main file. I recommend looking at the nrf connect sdk intermediate course and lesson 1 specifically, which provides more information on this. That said, I've reached out to the developers to discuss the use of main.c or lack off.

[quote user="sravan.rikka"]2. I have kept our modified/updated board files in 'zephyr/boards/arm' folder and also tried by keeping in 'nrf/boards/nordic' folder but still I can't see it under build configuration 'board target' section. In which folder I have to keep board files? and how to select our board files under 'board target' in build configuartion[/quote]

Same as above, have a look at the intermediate course and lesson 3 - Adding custom board support.

I will update you within 3 business days.

Kind regards,
Øyvind

RE: nRF9160 new SDK integration and build procedure

sravan.rikka — Wed, 27 Aug 2025 14:54:56 GMT

Hi Øyvind,

Awaiting for your response, can you please respond to above email.

Regards,

Sravan Rikka

RE: nRF9160 new SDK integration and build procedure

sravan.rikka — Wed, 27 Aug 2025 13:04:37 GMT

Hi Øyvind,

Thank you.

1. I have found the mqtt example code at the specified location and build it successfully. Also I read the document at below webpage.

https://docs.nordicsemi.com/bundle/ncs-3.1.0/page/nrf/samples/net/mqtt/doc/description.html

https://docs.nordicsemi.com/bundle/ncs-3.1.0/page/nrf/samples/net/mqtt/doc/architecture.html

The sample does not include a main.c file. To follow the typical flow of the application, see the Sequence diagram section. I found this in architecture webpage.

Checked in example code folder, observed same that there is no main.c file. Is it possible to provide a main.c file by linking all modules(network, trigger, sampler, transport) it helps to understand the code flow from network registration to publish data over MQTT and start developing our application/features on top of it.

2. I have kept our modified/updated board files in 'zephyr/boards/arm' folder and also tried by keeping in 'nrf/boards/nordic' folder but still I can't see it under build configuration 'board target' section. In which folder I have to keep board files? and how to select our board files under 'board target' in build configuartion.

Regards,

Sravan Rikka

RE: nRF9160 new SDK integration and build procedure

Øyvind — Wed, 27 Aug 2025 12:40:43 GMT

Hello,

The sample is located under nrf\samples\net\mqtt\

Kind regards,
Øyvind

RE: nRF9160 new SDK integration and build procedure

sravan.rikka — Wed, 27 Aug 2025 10:24:17 GMT

Hi Øyvind,

1. I have installed v3.1.0 SDK and looking for MQTT example code but didn't find it in nrf/samples, can you please tell in which folder it is available.

Regards,

Sravan Rikka

RE: nRF9160 new SDK integration and build procedure

Øyvind — Wed, 13 Aug 2025 08:11:51 GMT

Hi,

[quote user="sravan.rikka"]Can you please provide your answers to below queries.[/quote]

Yes, of course! Don't forget to have a look docs.nordicsemi.com as well

[quote user="sravan.rikka"]1. v3.0.2 SDK is the latest on as of today?[/quote]

The latest stable release is nRF Connect SDK v3.0.2, but there is also a release candidate for v3.1.0 available.

[quote user="sravan.rikka"]2. How much frequently SDK versions will be released? (Ex: Every 3 months or every 6 months? etc)[/quote]

I would recommend reaching out to your local sales representative for this information. I do not have this roadmap information, unfortunately.

[quote user="sravan.rikka"]3. We have to use VS Code for the development? No need to use segger embedded studio IDE?[/quote]

You can use which ever environment that you prefer, but Nordic Semiconductor has developed the nRF Connect for Visual Studio code extension which provides an easier, user-friendly GUI to build and configure your embedded systems projects based on the nRF Connect SDK in a single program

Some more information on development can be found under Application Development in the NCS documentation.

Kind regards,
Øyvind

RE: nRF9160 new SDK integration and build procedure

sravan.rikka — Tue, 12 Aug 2025 12:51:21 GMT

Hi Øyvind,

I am going through the links you shared.

Can you please provide your answers to below queries.

1. v3.0.2 SDK is the latest on as of today?

2. How much frequently SDK versions will be released? (Ex: Every 3 months or every 6 months? etc)

3. We have to use VS Code for the development? No need to use segger embedded studio IDE?

Regards,

Sravan Rikka

RE: nRF9160 new SDK integration and build procedure

Øyvind — Fri, 08 Aug 2025 09:15:27 GMT

Hello,

Please see our nRF Connect SDK Fundamentals course in our Developer Academy. This will provide all steps to go forward with NCS and the VS Code extension.

Kind regards,
Øyvind