- DK 0.8.2 in which SB44 is cut, and P1 and P2 are connected- firmware v1.0.0- program : asset_tracker- SIM: iBasis
Before updating firmware, asset_tracker worked fine.
However, after updating, LED3 is always blinking and LED4 is off.What I do is to write the program to DK, push reset button, and wait for more than 5 min.at_client program and LTE Link Monitor works out with v1.0.0.
this is log
SPM: NS image at 0xc000
SPM: NS MSP at 0x2002aa00
SPM: NS reset vector at 0x142f1
SPM: prepare to jump to Non-Secure image.
***** Booting Zephyr OS v1.14.99-ncs2-rc3 *****
Asset tracker started
Connecting to LTE network. This may take several minutes.
Connected to LTE network
Any idea to solve this?
So you say it will print: "Asset tracker started". At the stable tag v1.0.0, asset_tracker will print: "Application started".
What tag are you on in the nrf folder? You can check the tag by doing:
Try to enter the folder 'ncs/nrf' and do:
git checkout v1.0.0
I agree with Hellesvik. Are you on the correct asset tracker tag? I have tested the app myself & it works fine out of the box.
OK. this is symptom.
I bought a new DK 0.8.5. I updated the modem fw to v1.0.0
The old DK v0.8.2 and the new DK v0.8.5 have the same condition; the same modem firmware and the same asset_tracker Intel hex file.
However, the result is different. DK v0.8.5 works fine but DK v0.8.2 doesn't.
I don't know the reason. iBasis SIM may be expired.
Anyway, asset_tracker works out with DK v0.8.5 so I'm good.
That's weird. Do you have another SIM to test with? You programmed the merged.hex file to both, right?
I tried asset_tracker with DK 0.8.5 again and got this error. It had been working before...
***** Booting Zephyr OS v1.14.99-ncs2 *****
LTE LC config ...
nrf_cloud_connect failed: -111
One possible cause to the -111 error is missing certificates. To check if they are still saved on your modem, go to the at_client sample, add
Then open the nRF Connect LTE Link Monitor and do "AT%CMNG=1". If you have the correct certificates it will look something like this:
I did it and got a different result
I erased the original certificates file to install a new certificates for TLS.
How can you recover it?
After programming the nrf91 DK with a few different samples, I am not seeing any certificates in response to the AT%CMNG=1 command (just OK). What causes the certificates to be cleared from the device?
The most obvious reason is that they are overwritten by other certificates. This happens if you write new certificates to the modem using the same sec_tag. Sadly, many of our examples use the same sec_tag, so if you, for instance, have run the aws_fota or google cloud examples, this will be the reason. We have also gotten reports of people losing their certificates when updating their modem firmware.
What can be done if the device hasn't been registered with nRFcloud?
This guide has been deprecated due to an update to the nRF Cloud API.
If you have lost your certificates, I recommend you open a new private ticket, as it is hard to keep track of new comments on this case, due to its length and it having a verified answer.
In the private ticket, you should specify what kind of device you have Thingy:91 or nRF91DK, and in the latter case also provide your IMEI.