NCS v0.4.0 asset tracker application - "Faulting instruction address = 0x7140"

RE: NCS v0.4.0 asset tracker application - "Faulting instruction address = 0x7140"

Luis — Sun, 02 Jun 2019 11:32:34 GMT

So I checked the version of my local git repos and they all match.

But I did some research on the availability of NB-IOT in my area and found out that my city us one of the last cities in germany with no NB-IOT.

I assumend this would not be a problem because 1nce is stating on their website that NB-IOT is available everywhere in germany.

So I guess there is nothing for me to do but waiting...

https://1nce.com/en/coverage/

https://t-map.telekom.de/tmap/resources/apps/nbiot/index.html?lang=en

RE: NCS v0.4.0 asset tracker application - "Faulting instruction address = 0x7140"

John — Sun, 02 Jun 2019 08:11:00 GMT

My enthusiasm is overstated. I think I may have picked up a new board with old firmware that worked. So ignore my previous comment.

https://devzone.nordicsemi.com/f/nordic-q-a/44816/nrf9160dk-can-not-find-the-cellular-network/189719#189719

However the above looks interesting to try, let me know if it works for you, I'm currently trying it.

RE: NCS v0.4.0 asset tracker application - "Faulting instruction address = 0x7140"

Luis — Sun, 02 Jun 2019 08:02:57 GMT

Is that the master branch or v0.4.0?

I have tried your merged.hex file but LED 3 is still blinking and the board is not connecting.

Is there a way for me to verify that my board is broken as well?

If this helps: I'm (at least trying to be) using NB-IOT from 1nce in Bavaria, Germany.

RE: NCS v0.4.0 asset tracker application - "Faulting instruction address = 0x7140"

John — Sat, 01 Jun 2019 22:01:13 GMT

Hi Luis, I've spent the last 8 hours trying to make the asset tracker work.

Looks like I may have been using a defective nrf9160 DK, tried another one, connected to the master branch, west update.

Looks like they have fixed the need to insert the two things I mentioned inside prj.conf.

So clean, rebuild (asset tracker), erase all and download merged.hex.

Almost fell of my chair when it worked.

devzone.nordicsemi.com/.../merged.hex

Here's a copy just in case, have fun, just sharing the excitement.

RE: NCS v0.4.0 asset tracker application - "Faulting instruction address = 0x7140"

Luis — Sat, 01 Jun 2019 21:58:49 GMT

So I'll just clone the repo but don't checkout the tagged commit?

Which result did you get after doing that?

I'll do that tomorrow, thanks for the help!

RE: NCS v0.4.0 asset tracker application - "Faulting instruction address = 0x7140"

John — Sat, 01 Jun 2019 21:49:07 GMT

Good.

🙂

Oh I forgot to mention that the "clever one" also explained that v0.4.0 was broken.

Upgrade to the Master branch.

Try again...let me know if same result please.

RE: NCS v0.4.0 asset tracker application - "Faulting instruction address = 0x7140"

Luis — Sat, 01 Jun 2019 21:27:37 GMT

Will do! I did a quick test just now but it didn't seem to connect. (LED 3 blinking problem 😞)

RE: NCS v0.4.0 asset tracker application - "Faulting instruction address = 0x7140"

John — Sat, 01 Jun 2019 21:19:57 GMT

Please let me know if you gain a connection to nrfcloud and complete the pairing process.

That would be very interesting to me as obviously I've done something silly.

RE: NCS v0.4.0 asset tracker application - "Faulting instruction address = 0x7140"

Luis — Sat, 01 Jun 2019 20:55:28 GMT

This worked like a charm!

Thanks for the quick help and good luck getting you connection issue sorted out! 🙂

RE: NCS v0.4.0 asset tracker application - "Faulting instruction address = 0x7140"

John — Sat, 01 Jun 2019 20:24:16 GMT

Edit with Segger prj.conf which you will find as you open the project.

Inside this add (anywhere) the following:

CONFIG_FP_SHARING=y

CONFIG_SPM=n

Someone smarter than me worked out that there was a problem with floating point, first one seems to fix that, another fellow worked out that the merged.hex is pointing to wrong addresses

The CONFIG_SPM=n stops the merging of SPM and the application, therefore you will have to clean and rebuild the project the old way by loading SPM using nrf9160_pca10090 and downloaded the elf

Then clean and rebuild build the asset tracker using nrf9160_pca10090ns and download the elf

At least then it will run.

My problem :( is that it still may not connect to nrfcloud.com, however at east you'll be able to have some fun with AT commands.

Hope that helps.