SDK and Application Support for Signetik M1-N1

[skar001]

Hello,

I am working with the Signetik M1-N1 module, which is using the nRF9160 chip, as well as the DEV-M1-N1 breakout board, for evaluation and development:

Since this module is using an nRF9160 chip, I was wondering if there was any support by NXP for devices from other manufacturers like Signetik. I have worked with the 9160DK in the past to establish https client connections to various web servers by using the https_client example application from the SDK, and I am attempting to do something similar with these devices.

Any help would be greatly appreciated.

Thanks.

[Charlie]

Hi,

Thanks for checking with us. Nordic nRF Connect SDK doesn't have direct support(samples) for third-party modules, you may check with the module producer or port by yourself for your target application.

Best regards,

Charlie

[skar001]

Hi Charlie,

Thank you for the information. I do have a similar question regarding some devices specific to Nordic as well.

I have been working with the nRF9160DK as well as the Thingy 91. I have been working on the nRF9160DK with the https_client example from the SDK. I have been able to successfully obtain a different X.509 certificate and send different types https requests (GET, POST, etc.) to a website.

I wanted to do the same thing on the Thingy 91, using the 9160DK as a way to flash my application to the Thingy 91. However, I noticed that there was no build configuration for the Thingy 91 in https_client:

Is there a way that I can add the build configuration for the Thingy 91?

Thanks

[Charlie]

Hi Stefanos,

The sample supports boards list under "Requirements" of sample document like following:
https://docs.nordicsemi.com/bundle/ncs-2.7.0/page/nrf/samples/net/https_client/README.html

Thingy91 is a more complex product prototpy platform instead of a simple SDK board, so we currently only support and testing it on limited samples.

If the sample does not depend on led and button too much, it should be quit easy to port to Thingy91 by refering current samples with thingy91 support.

By refering to nrf/samples/net/aws_iot thingy91 configuration and nrf/samples/net/https_client/boards/nrf9161dk_nrf9161_ns.conf, I made changes to make thingy91 work with https_client sample.

Please apply the attched patch file and try.

% cd nrf/samples/net/https_client 
% git status .
Not currently on any branch.
Untracked files:
  (use "git add <file>..." to include in what will be committed)
        https_client_thingy91.patch
% git apply https_client_thingy91.patch 
%  git status .
Not currently on any branch.
Untracked files:
  (use "git add <file>..." to include in what will be committed)
        boards/thingy91_nrf9160_ns.conf
        boards/thingy91_nrf9160_ns.overlay
        https_client_thingy91.patch
        sysbuild/mcuboot/boards/

https_client_thingy91.patch

Best regards,

Charlie