• State Verified Answer
  • Replies 37 replies
  • Subscribers 87 subscribers
  • Views 13723 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 228686
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF9160 Cannot make Kconfig options have an effect in Segger Embedded Studio

Johan

I have a nRF9160 DK and I'm adapting the asset tracker to connect to our own AWS cloud solution.

I see the code nrf_cloud uses defines coming from the Kconfig at \nrf\subsys\net\lib\nrf_cloud\Kconfig.
For example: NRF_CLOUD_HOST_NAME, NRF_CLOUD_PORT, NRF_CLOUD_PROVISION_CERTIFICATES, NRF_CLOUD_CERTIFICATES_FILE etc

How do I make changes to the Kconfig have an effect when building in Segger Embedded Studio? No matter what I do, changes to this Kconfig doesn't have an effect to the built result.

Am I missing the point, how it's supposed to work perhaps?
Anyone who can educate me, how to work "correctly" with this, would be appreciated.

I tried to build from commandline, but couldn't make it work, so I'm sticking with Segger Embedded Studio so far.
Build platform: win7

Johan

  • 0 in reply to Martin Lesund

    Some more questions for you Martin:

    1.How do I know what kind of connection the LTE is using, with the sample BLE_LTE_gateway?
    I want to be in control of and set it to NB-LTE forced, and also read and verify this setting has been taken effect.
    How can I accomplish this?

    2. What is "Security tag to use for nRF Cloud connection"? Is it for AWS or just your own solution? I haven't found any documentation on AWS of this yet.

    Cheers,
    Johan

  • 0 in reply to Johan

    As, well, how do I remove pairing with nrfCloud? 
    I removed my unit from it, but the local device refuses to go into "led 3 and led 4" -blink.
    Just "led 3" - blinking.

    It seems it's receiving this from the cloud, what to do. So the cloud solution tells my unit it doesn't need any paring, but I have removed it, so it does!
    Bug?

  • 0 in reply to Johan

    Hello Johan,
    1. You can get/set that data from a simple AT command: AT%XSYSTEMMODE?

    1,0,0,0 = LTE CAT-M1

0,1,0,0 = LTE CAT-NB1

0,0,1,0 = GNSS

    This has to be set before the modem is turned on (AT+CFUN=1)

    and can be changed if the modem is in Offline mode (AT+CFUN=4) 

    (When you turn on the nRF91 it will default be in Offline mode if the application 

    2. Our nrfcloud solution runs on AWS.

    The security tag you are referring to is used when provisioning the certificates to the nrf91.
    Please see how this is used in nrf_cloud_transport.c.

    So if you are going to provision certificates to the modem you need a security tag.

    Best Regards,

    Martin L.

  • 0 in reply to Martin Lesund

    Hi Martin,

    great you're back, since I need more support to get this ship going.


    1)
    So If I get you, you recommend setting these settings then resetting the modem, for it to boot up in the correct mode ?

    I'm using the "ble_lte_gateway"-example. I'm guessing there is no easy way to put at-commands anywhere in it as it is, without rewriting parts, or? I could just use at_client-example as well, to set them, then put back this ble_lte_gateway to continue testing to get the certificates working. Sounds good to you? 

    2) The security tag, is this something I should request from our AWS-guy then?
    I'm not into the AWS-stuff, just receiving certificates from him, to put in the certificates.h so far.

    3) I see also a clientID, it's probably from AWS. Could it be the numbers in the filename?
    "70ff304fdd-private.pem.key", ie 70ff304ffdd ?

  • 0 in reply to Johan

    ps. I did check the source code for security tag, but there is no explanation, more than function calls using it. ds.

Related
Terms of service