Asset tracker project build fails with cannot move location counter backwards

[maaya_tech]

I am able to load the project.. I have followed all the instructions from nrf connect helkp and have verified it.  

tag v1.1.0 (have done west update)

using SES 4.30c  as suggested by nrf connect (latest SES did not work for me either)

verify all on nrf connect was successful.

After the project loading if i clean and rebuild, I get the following error.. It looks like linker has some errors but I have not changed anything and using the project as is.

7> Compiling ‘system_work_q.c’
3> Compiling ‘thread.c’
2> Compiling ‘thread_abort.c’
4> Compiling ‘version.c’
6> Compiling ‘work_q.c’
8> Compiling ‘smp.c’
5> Compiling ‘timeout.c’
7> Compiling ‘timer.c’
4> Compiling ‘poll.c’
1> Archiving ‘libkernel.a’
Rebuilding ‘zephyr/zephyr_prebuilt.elf’ from solution ‘build’ in configuration ‘Common’
1> Compiling ‘empty_file.c’
1> Linking ‘zephyr_prebuilt.elf’
1> c:/gnuarmemb/bin/../lib/gcc/arm-none-eabi/8.3.1/../../../../arm-none-eabi/bin/ld.exe:zephyr/linker.cmd:70 cannot move location counter backwards (from 0001843c to 00018400)
1> collect2.exe: error: ld returned 1 exit status
Build failed

[Heidi]

Hi,

Have you made sure the paths in Tools -> Options -> nRF Connect -> Directories are correct? 

Are you able to build the project using west?

west build -b nrf9160_pca10090ns -d build -p

Best regards,

Heidi

[maaya_tech]

yes I have... looks like the issue is when I have more than one SES application running at the same time.. If I have only one SES running with asset tracker, the error goes away (I made zero other changes). BUt the system keeps resetting.. I have the Sim card connected.. All I really need to see is the GPS working ?9LTE is only a bonus at this time).. what else do I have to do get the asset tracker sample application to work reasonably ?

[00:00:00.349,304] <inf> mcuboot: Bootloader chainload address offset: 0xc000
[00:00:00.356,964] <inf> mcuboot: Jumping to the first image slot
*** Booting Zephyr OS version 2.1.99 ***
Flash region Domain Permissions
00 0x00000 0x08000 Secure rwxl
01 0x08000 0x10000 Secure rwxl
02 0x10000 0x18000 Secure rwxl
03 0x18000 0x20000 Non-Secure rwxl
04 0x20000 0x28000 Non-Secure rwxl
05 0x28000 0x30000 Non-Secure rwxl
06 0x30000 0x38000 Non-Secure rwxl
07 0x38000 0x40000 Non-Secure rwxl
08 0x40000 0x48000 Non-Secure rwxl
09 0x48000 0x50000 Non-Secure rwxl
10 0x50000 0x58000 Non-Secure rwxl
11 0x58000 0x60000 Non-Secure rwxl
12 0x60000 0x68000 Non-Secure rwxl
13 0x68000 0x70000 Non-Secure rwxl
14 0x70000 0x78000 Non-Secure rwxl
15 0x78000 0x80000 Non-Secure rwxl
16 0x80000 0x88000 Non-Secure rwxl
17 0x88000 0x90000 Non-Secure rwxl
18 0x90000 0x98000 Non-Secure rwxl
19 0x98000 0xa0000 Non-Secure rwxl
20 0xa0000 0xa8000 Non-Secure rwxl
21 0xa8000 0xb0000 Non-Secure rwxl
22 0xb0000 0xb8000 Non-Secure rwxl
23 0xb8000 0xc0000 Non-Secure rwxl
24 0xc0000 0xc8000 Non-Secure rwxl
25 0xc8000 0xd0000 Non-Secure rwxl
26 0xd0000 0xd8000 Non-Secure rwxl
27 0xd8000 0xe0000 Non-Secure rwxl
28 0xe0000 0xe8000 Non-Secure rwxl
29 0xe8000 0xf0000 Non-Secure rwxl
30 0xf0000 0xf8000 Non-Secure rwxl
31 0xf8000 0x100000 Non-Secure rwxl
Non-secure callable region 0 placed in flash region 2 with size 32.


SRAM region Domain Permissions
00 0x00000 0x02000 Secure rwxl
01 0x02000 0x04000 Secure rwxl
02 0x04000 0x06000 Secure rwxl
03 0x06000 0x08000 Secure rwxl
04 0x08000 0x0a000 Secure rwxl
05 0x0a000 0x0c000 Secure rwxl
06 0x0c000 0x0e000 Secure rwxl
07 0x0e000 0x10000 Secure rwxl
08 0x10000 0x12000 Non-Secure rwxl
09 0x12000 0x14000 Non-Secure rwxl
10 0x14000 0x16000 Non-Secure rwxl
11 0x16000 0x18000 Non-Secure rwxl
12 0x18000 0x1a000 Non-Secure rwxl
13 0x1a000 0x1c000 Non-Secure rwxl
14 0x1c000 0x1e000 Non-Secure rwxl
15 0x1e000 0x20000 Non-Secure rwxl
16 0x20000 0x22000 Non-Secure rwxl
17 0x22000 0x24000 Non-Secure rwxl
18 0x24000 0x26000 Non-Secure rwxl
19 0x26000 0x28000 Non-Secure rwxl
20 0x28000 0x2a000 Non-Secure rwxl
21 0x2a000 0x2c000 Non-Secure rwxl
22 0x2c000 0x2e000 Non-Secure rwxl
23 0x2e000 0x30000 Non-Secure rwxl
24 0x30000 0x32000 Non-Secure rwxl
25 0x32000 0x34000 Non-Secure rwxl
26 0x34000 0x36000 Non-Secure rwxl
27 0x36000 0x38000 Non-Secure rwxl
28 0x38000 0x3a000 Non-Secure rwxl
29 0x3a000 0x3c000 Non-Secure rwxl
30 0x3c000 0x3e000 Non-Secure rwxl
31 0x3e000 0x40000 Non-Secure rwxl

Peripheral Domain Status
00 NRF_P0 Non-Secure OK
01 NRF_CLOCK Non-Secure OK
02 NRF_RTC0 Non-Secure OK
03 NRF_RTC1 Non-Secure OK
04 NRF_NVMC Non-Secure OK
05 NRF_UARTE1 Non-Secure OK
06 NRF_UARTE2 Secure SKIP
07 NRF_TWIM2 Non-Secure OK
08 NRF_SPIM3 Non-Secure OK
09 NRF_TIMER0 Non-Secure OK
10 NRF_TIMER1 Non-Secure OK
11 NRF_TIMER2 Non-Secure OK
12 NRF_SAADC Non-Secure OK
13 NRF_PWM0 Non-Secure OK
14 NRF_PWM1 Non-Secure OK
15 NRF_PWM2 Non-Secure OK
16 NRF_PWM3 Non-Secure OK
17 NRF_WDT Non-Secure OK
18 NRF_IPC Non-Secure OK
19 NRF_VMC Non-Secure OK
20 NRF_FPU Non-Secure OK
21 NRF_EGU1 Non-Secure OK
22 NRF_EGU2 Non-Secure OK
23 NRF_DPPIC Non-Secure OK
24 NRF_GPIOTE1 Non-Secure OK
25 NRF_REGULATORS Non-Secure OK

SPM: NS image at 0x18200
SPM: NS MSP at 0x2002e8e8
SPM: NS reset vector at 0x20371
SPM: prepare to jump to Non-Secure image.
*** Booting Zephyr OS version 2.1.99 ***
[00:00:00.305,175] <err> nrf9160_gps: Could not confiugure MAGPIO, error: -8
[00:00:00.313,049] <inf> asset_tracker: Asset tracker started
[00:00:00.320,129] <dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656100028375
[00:00:00.329,406] <dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656100028375/shadow
[00:00:00.341,186] <dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656100028375/shadow/get/accepted
[00:00:00.352,752] <dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656100028375/shadow/get/rejected
[00:00:00.365,417] <dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656100028375/shadow/update/delta
[00:00:00.378,417] <dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656100028375/shadow/update
[00:00:00.390,350] <dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656100028375/shadow/get
[00:00:00.402,740] <inf> asset_tracker: Connecting to LTE network.
[00:00:00.409,545] <inf> asset_tracker: This may take several minutes.
[00:00:00.417,114] <err> asset_tracker: LTE link could not be established.

[Heidi]

It looks like the device isn't able to connect to the network. Are you sure you have coverage in your area and that you are running the correct version of the asset_tracker sample (NB-IoT or LTE-M)?

[maaya_tech]

I had to reflash the modem firmware  mfw_nrf9160_1.1.1 and then it connected.. but Now I see the link getting disconnected pretty quickly and system restarting (and in a cycle)... I am guessing, certificate has to be flashed..

You mentioned using the right version of sample app (NB-IOT vs LTE-M).. My area is supposed to have both coverages.. but how do I select one vs the other..

[maaya_tech]

I have managed to connect the device to nrf cloud via LTE.. after you respond to my nb-iot vs lte-m, you can close the ticket.. thank you for your help

[Heidi]

Hi, sorry I didn't see your comment. When an answer is selected as "Verified", we don't get new notifications on the ticket. 

If your area (and your network provider) has coverage for both, it depends on your SIM card and your subscription.