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

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

Parents Reply
  • Flashed asset_tracker.

    Booting with link monitor open.

    Log part

    SPM: NS image at 0x8000
    SPM: NS MSP at 0x2002a4a8
    
    
    
    
    SPM: NS reset vector at 0xfd6d
    
    
    
    
    SPM: prepare to jump to Non-Secure image.
    
    
    
    
    ***** Booting Zephyr OS v1.14.99-ncs1-rc2 *****
    
    
    
    
    Application started
    
    
    
    
    LTE LC config ...
    
    
    
    
    NRF_CLOUD_EVT_TRANSPORT_CONNECTED

    -------

    Nothing more happens here.
    I'll go to the cloud and add the LTE-device now.
    And hopefully it will then get a pairing request.

Children
Related