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

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

Johan — Thu, 16 May 2019 09:41:56 GMT

And the way to replace them, is to get the certificates from Martin or an engineer, and then use asset tracker, and enable provisioning in the project-> configure nrf connect sdk project -> enable "nRF Cloud library provision of certificate".
Put the certificates in the certificates.h in the application folder. Build and run, and certs will be flashed, and replaced. nrfCloud now works again.

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

Martin Lesund — Tue, 14 May 2019 13:44:24 GMT

The issue in this case was that the default nrf cloud certificates was overwritten so it would not connect to nrf cloud.

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

Johan — Tue, 14 May 2019 12:16:11 GMT

Question is:

How do I log in?
Via private account, or via the devzone.

I have no idea Martin.

Did you find my units via the IMEI-number?

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

Johan — Tue, 14 May 2019 12:02:09 GMT

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.

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

Johan — Tue, 14 May 2019 11:41:44 GMT

Ok, I was wrong.

The downloaded zipfile from "Download All" - was EMPTY.

So still I have no file.
You can email it to me if this server is broken for downloading attachments.
My email is in my account.

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

Johan — Tue, 14 May 2019 11:40:38 GMT

I managed to download them now.
THe only download that works is, right side of the screen "Attachments (2) Download All".

The other options with separate files, gives me "permission denied".

There is some configuration problem with your devzone server.
Can you pass that on, so someone solves this?

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

Johan — Tue, 14 May 2019 09:47:45 GMT

Martin:

Trying to download your attachment : (asset_tracker.hex)
You do not have permission to view this directory or page.

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

Martin Lesund — Tue, 14 May 2019 09:11:55 GMT

Following up the new issue in this thread: https://devzone.nordicsemi.com/f/nordic-q-a/47247/nrfcloud-pairing-is-broken-when-removing-and-adding-lte-device-nrf9160-ble_lte_gateway-application-again

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

Johan — Tue, 14 May 2019 09:06:24 GMT

Martin, the pairing has worked before.
It has stopped working.

Your cloud solution doesn't send pairing commands back to my DK anymore.

This is the problem.

I dont have problem with getting an LTE-connection, as you are suggesting.
I dont need to try those steps you put below.

Look at this log:
***** Booting Zephyr OS v1.14.99-ncs1 *****
Application started
Initializing Bluetooth..
Establishing LTE link (this may take some time) ...
Bluetooth ready
Scanning...
Device found: c7:ed:e7:7e:0f:f0 (random)
Connected: c7:ed:e7:7e:0f:f0 (random)
Orientation: 0
NRF_CLOUD_EVT_TRANSPORT_CONNECTED

It's connected to the nRFCloud, but the cloud sends NRF_CLOUD_EVT_TRANSPORT_CONNECTED.
Even If go through the pairing, It STILL sends NRF_CLOUD_EVT_TRANSPORT_CONNECTED ONLY.

The code needs to receive: NRF_CLOUD_EVT_USER_ASSOCIATION_REQUEST

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

Martin Lesund — Tue, 14 May 2019 08:58:53 GMT

Hi Johan,

I assume that you know you can get a network connection ?

This can be verified sending AT commands to the modem when running LTE Link Monitor.

We can now try the "asset_tracker" application which will connect to the nrf cloud.

I am adding the precompiled .hex file of the "Asset_tracker" merged with the "Secure Partition Manager" (SPM):

asset_tracker.hex

To flash this .hex file please use the following command in the command line:

nrfjprog --program asset_tracker.hex -f nrf91 --sectorerase -r --verify

Note: You can use the LTE Link Monitor as a standard serial output Terminal if you deselect the "Automatic requests" setting:

This will prohibit that the LTE Link Monitor will run through the script sending AT commands when sending for example "AT+CFUN?". (it will only send it once)

Please have the LTE Link Monitor open while testing the "asset_tracker" application to easier see what is actually going on.

Here you can see the output after the "asset_tracker" got a connection with the nrf cloud server.

- "LTE LC config ..." is showing while the kit is trying to get a network attachment, and the following output is from the application itself saying it found and got access to the nrf cloud server.

If you get the same output, you can now go into www.nrfcloud.com and pair your nRF91DK with your account following the steps on the nrf cloud webpage. (you do not need to register the iBasis SIM card more than once)

After you have followed the Pairing sequence given by nrfcloud you should see this verified in the output terminal as well.

Now you should be connected to nrfcloud.

Extra tip:

For faster attachment with the network the next time you power on the board is to save the information about the network in the modem flash.

To do this just send the AT command "AT+CFUN=0".

This will Power off the modem as well as saving the network information in the modem flash.

(note that you need to power cycle the board after this command to turn on the modem)

Please share some logs/snippets if you have further issues.

Best Regards,
Martin L.

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

Johan — Tue, 14 May 2019 08:43:03 GMT

I tried with another e-sim card and I get the same reaction. led 3 blinks, not led 4 (which should also blink).

In the code:

/**@brief Callback for nRF Cloud events. */
static void cloud_event_handler(const struct nrf_cloud_evt *evt)
{
int err;

switch (evt->type) {

case NRF_CLOUD_EVT_TRANSPORT_CONNECTED:
printk("NRF_CLOUD_EVT_TRANSPORT_CONNECTED\n");
break;

case NRF_CLOUD_EVT_USER_ASSOCIATION_REQUEST:
printk("NRF_CLOUD_EVT_USER_ASSOCIATION_REQUEST\n");
on_user_association_req(evt);
break;

I need the 2nd case to be triggered, but the nrfCloud doesn't send out the request, just instead sends connected - which is useless, since I have deleted the LTE device from the web - so it should send the user association request. Or is there something I need to do to disassociate the e-sims with the cloud which is an option I missed in your nrfCloud-site?

I'm stuck here Martin.

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

Johan — Tue, 14 May 2019 08:33:44 GMT

Martin, my unit doesn't get into pairing state.
I follow the instructions on your cloud and boot up my DK but it connects to the cloud, but no pairing.
So If im right, the nrfCloud doesn't send "goto pairing" mode to the DK.

I need help here.

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

Johan — Mon, 13 May 2019 14:57:55 GMT

Thanks for the other 2 answers.
I will look into them, and make use for them - tomorrow!
Have a good day!

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

Johan — Mon, 13 May 2019 14:56:56 GMT

Ok, I might be tired, but what's the practical use for this security tag, with the BSD-secure socket?
Can I use the same tag as already there, or I need a new one?
What's the penetration risk? Is it a key for encryption?

I can use the same tag for every unit or is that creading a risk I don't see?
I'm new at this nrf-cloud things, so I'm asking rather more than too little.

I'm guessing a different key for every device I'm making is the way to go.
But, I don't need to put them in a database right, it's just a local key, one time made, or can be recreated upon each boot?

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

Johan — Mon, 13 May 2019 14:50:10 GMT

Ok, I'll tell him to ignore that email then :-)

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

Johan — Mon, 13 May 2019 14:48:35 GMT

I have requested a security tag from my cloud guy. Let's see if he manages to create one from the AWS console and such.

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

Martin Lesund — Mon, 13 May 2019 14:47:58 GMT

Hi Johan,

1) Since the LTE_Gateway uses the LTE_LINK_CONTROL library, you can actually enable a config so the Application will set the modem in the correct mode at startup.

So you could enable this configs in the prj.conf file, either:

CONFIG_LTE_NETWORK_MODE_NBIOT=y

to enable NB-IoT mode, or:

CONFIG_LTE_NETWORK_MODE_LTE_M=y

to enable LTE-M mode at startup.

It is also worth noting that if you want to store the connection mode permanently in the Modem flash you can set it with the AT-command: AT%XSYSTEMMODE=<mode>

then send the command: AT+CFUN=0

to set the modem in power off mode and store the settings in the modem flash.

Quick tip: note that you can set up a socket and send AT-Commands directly in your application similarly to what is done in the LTE Link Control library

The security tag in the nrf_inbuilt_key_write() function is documented as such:

"Application defined tag for this credential to be referred

to in setting up a BSD Secure Socket or to manage the credential"

The security tag used in the tls_credential_add() function:

"A security tag that credential will be referenced with."

So it is not something you need to request from your AWS guy.

3) Yes I think that should be fine. If you are referring to what I think you are referring to.

Since for our solution when we are connecting to the nrfcloud we use the IMEI number for the nrf91 SIP as clientID.

Please use the nrf_cloud_transport.c file as reference.

Managing Device certification AWS Documentation

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

Johan — Mon, 13 May 2019 14:46:21 GMT

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

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

Johan — Mon, 13 May 2019 14:02:21 GMT

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 ?

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

Martin Lesund — Mon, 13 May 2019 13:53:36 GMT

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.

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

Johan — Mon, 13 May 2019 13:50:37 GMT

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?

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

Johan — Mon, 13 May 2019 09:03:47 GMT

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

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

Johan — Mon, 13 May 2019 09:02:38 GMT

I got it to accept, with leaving out the last 2 digits.
Device registered.

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

Johan — Mon, 13 May 2019 08:45:01 GMT

Hi martin!

BLE connects now. I made the mistake of not selecting the right board when flashing.

Other problem.
I'm trying to register my IOT-simcard, from Swedish Telia.com

The ICCID doesn't fit in the input field of your nrf-cloud website.
The last 2 numbers are refused due to the limit of characters in the field, when adding a LTE device.
Im reading the ICC: -field on my sim card and it is 5x4 = 20 numbers long.
You only accept 18 numbers.

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

Martin Lesund — Fri, 10 May 2019 12:00:49 GMT

Hi Johan,

The NCS tag v0.4.0 just got released! https://developer.nordicsemi.com/nRF_Connect_SDK/doc/0.4.0/nrf/doc/release-notes-0.4.0.html

Please go to:

cd ncs/nrf
git checkout master
git pull
git checkout v0.4.0
west update

To get the stable release.

Remember that you need to flash the nrf52 (nrf52840_pca10090) on the nRF91 DK with the HCI_UART sample.

as described here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/nrf9160/lte_ble_gateway/README.html

Best Regards,

Martin L.