nRF9160 Asset Tracker Confusion

[John]

At the time of writing, there are posts suggesting that we should use merged hex to program the Asset Tracker from the Master branch, other posts contradict this by saying that we should insert CONFIG_SPM=n in prj.conf  to make the application run and download SPM elf using the secure version of the board and asset tracker elf using non secure version.

Other posts suggest that we should only use v.0.4.0 tag and others suggest that's broken.

There are many instances of "led3 blinking can't connect", most of which are out of date and no longer relevant and refer to the fact that we should be using the latest release of the modem firmware of which I am.

I would be really grateful if someone is able to suggest a tag that allows the Asset Tracker or lte_ble_gateway to connect and pair with a device being added within nrfcloud 

Is there such a version that functions as expected ?

It would be really great to know please.

I would be most appreciative if someone would suggest where I may obtain the UICR (uicr_tcx0.hex) file, as I have "erased all" using the nRF Connect programmer, I'm not sure if the file I'm using is the current one.

I understand that the process is as to open a command prompt and perform the following:

nrfjprog.exe --program uicr_tcxo.hex -f nrf91 --sectorerase --verify

Then update the modem firmware, by downloading the current version (mfwnrf916007029alpha)

nrf9160_mdm_dfu --update

Please let me know if I'm correct or if there is anything else that I'm missing or need to do.

Thank you.

[Håkon Alseth]

Hi,

 

The current SES for Nordic (v4.16) does not support flashing the merged.hex (SPM + APP), so you have to manually flash the spm project first. This is on the "todo" list, and should come for the next release of SES (v4.17).

 

In addition to the update of the modem fw, could you ensure that you have checked out the correct tag?

cd path/to/ncs/nrf

git checkout v0.4.0

Note that the SPM project requires to use board type nrf9160_pca10090:

 

While the asset_tracker (and all other applications that communicates with the modem) require the board type nrf9160_pca10090ns:

 

Could you try to load the SPM project first, then the asset_tracker to see if this helps?

 

Kind regards,

Håkon

[John]

I've done that several times with no difference.

However what I'm trying to do is load on my board a merged.hex that works on Martin's board..

That effectively removes my environment and leaves only the cellular connection and boot loader/SPM and uicr and the hex given to me.

I never get to the point of led 4 turning on to begin the pairing process.

Interestingly I seem to be able to get the mqtt_simple example to indicate that it has a connection.

A real puzzle.

My board as mentioned is 0.8.5 and did work when I first turned it on with whatever default software had been loaded on it.

When installing the SDK according to the "getting started" instructions.

pip3 install -r zephyr\scripts\requirements.txt

Usual stuff....

Then

You are using pip version 19.0.3, however version 19.1.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command

Is the above important to upgrade?

pip3 install -r nrf\scripts\requirements.txt

Usual stuff...

Then

gitlint 0.11.0 has requirement Click==6.7, but you'll have click 7.0 which is incompatible.

Is the above important to change?

pip3 install -r mcuboot\scripts\requirements.txt

However the above wouldn't affect the merged hex issue that I have.

Especially if I'm using nrfjprog to flash it.

[Håkon Alseth]

Hi,

 

John said:

Is the above important to change?

No, the gitlint is only used if you want to check your git messages, and your pip isn't that old. I have pip v18.1 on my system.

 

I looked at the log you posted in this thread:

https://devzone.nordicsemi.com/f/nordic-q-a/47754/whisper-ware-nrf9160

 

The signal strength you have here is very weak:

2019-06-03T19:46:46.704Z DEBUG modem << +CESQ: 99,99,255,255,255,29\x0D\x0A

A value of 29 gives: -140 + 29 = -111 dBm

This is just below the receiver sensitivity, and you will have connection issues if your signal strength is in this area when testing other examples as well.

 

Are you able to place the kit in another room or outside to see if the signal strength increases?

 

Kind regards,

Håkon