Configuring Multicell Location Without Building an App

[ricanontherun]

Hello,

My company is evaluating the Thingy:91, we're interested in Multicell location lookups. My question is regarding the SDK, specifically if it's possible to configure the location provider without having to write/build/flash a custom program.

Thanks

[Øyvind]

Hello, 

I'm not sure I understand your question. In order to run the Multicell location you will need to build and flash the nRF9160: Multicell location sample. Please note that you should follow the Thingy:91 Getting started guide before starting on other applications or samples.

Kind regards,
Øyvind

[ricanontherun]

Ah, I see. Okay, no problem. I was able to build the multicell_location sample, but trying to flash the build to my Thingy:91 yields the following error:

➜ ✗ west flash --erase                        

-- west flash: rebuilding

[0/11] Performing build step for 'spm_subimage'

ninja: no work to do.

-- west flash: using runner nrfjprog

-- runners.nrfjprog: mass erase requested

FATAL ERROR: "nrfjprog --ids" did not find a board; is the board connected?

I'm on a Macbook Pro (Intel CPU) ... why isn't the board seen? As you can see, the LTE Link Monitor sees the board without an issue.

[ricanontherun]

nrfjprog --version
nrfjprog version: 10.15.2 external
JLinkARM.dll version: 7.60a

[Øyvind]

Thanks for providing this information. This is correct. 

ricanontherun said:

The firmware update process has been smooth

What do you mean firmware update has been smooth?

ricanontherun said:

flash to the device since nrfjprog --ids returns nothing

Do you have a external JLink debugger? Remember that nrfjprog will only see devices connected through a JLink device.

[ricanontherun]

Øyvind said:

What do you mean firmware update has been smooth?

Meaning I've been able to connect my Thingy:91 to my Macbook and update it's firmware using the Programmer tool.

Øyvind said:

Do you have a external JLink debugger? Remember that nrfjprog will only see devices connected through a JLink device.

 Interesting. I have a nrf9160 development kit, does that count as an external debugger? If so, do you have documentation available for how to configure the devices? You can see in the linked image that I can connect them like so:

When I run nrfjprog --ids, I get the following output ... which is that of the development kit I believe.

nrfjprog --ids
960069774

[Øyvind]

ricanontherun said:

When I run nrfjprog --ids, I get the following output ... which is that of the development kit I believe.

Yes, this should reflect the number on the sticker on the back of the DK. When connected to the Thingy:91 with a debug cable, it will automatically program the Thingy:91. Make sure to set SW2 - SWD SELECT to either nR91 or nRF52. 

ricanontherun said:

I have a nrf9160 development kit, does that count as an external debugger?

Yes it does. The onboard interface MCU allows you to program the Thingy:91 as an external debugger. There is more information on the debug out in the nRF9160 DK Hardware guide. 

Hope this helps with your development

[ricanontherun]

Okay, thanks for that information. I see that the PROG/DEBUG switch must be switched to the right target platform (nrf9160 in my case). What about the build target when running west build? Are these arguments appropriate?

west build --pristine -b nrf9160dk_nrf9160_ns

I'm asking because yesterday I tried this exact setup (before you confirmed it would work) and now 1 of my 2 Thingy:91 devices is completely unresponsive.

[ricanontherun]

ricanontherun said:

is completely unresponsive.

Adding some detail here. I had the DK hooked up to the Thingy:91. The DK was receiving power via a UDB cable, the Thingy:91 was NOT receiving external power. I ran the following commands, which resulted in the Thingy:91 showing the red error light, and I haven't been able to use it since. It no longer is recognized by my laptop.

west build -b nrf9160dk_nrf9160

west flash erase

*Thingy:91 displays red LED*

[Øyvind]

Hi Christian, based on the email I received, I see that you have been able to program your Thingy:91. Did this solve your issues?

I'm adding a quick recap from the mail thread with my colleague Joakim.

Method 1: through external debug probe (Through nRF9160DK)

• According to the guide you need to select the nRF9160DK in the Programmer application.
• And you should use merged.hex
• Guide: https://infocenter.nordicsemi.com/topic/ug_thingy91_gsg/UG/thingy91_gsg/updating_fw_ext_probe.html

 

Method 2: through USB, using the already flashed bootloader (MCUboot)

• In this scenario you need to select the Thingy:91 in the Programmer application.
• And use app_signed.hex
• Guide:  https://infocenter.nordicsemi.com/topic/ug_thingy91_gsg/UG/thingy91_gsg/updating_fw_usb.html

 

If you have used method 1 and overwritten the bootloader, you need to use method 1 and flash one of the precompiled images inside the folder img_app_bl (images containing bootloader) found inside the firmware zip on Thingy:91 product page under the download tab, this to recover the bootloader before you can use method 2.

Precompiled images download: https://www.nordicsemi.com/Products/Development-hardware/Nordic-Thingy-91/Download

 

For seeing which hex file to use in the different scenario, please see below table from the “working with Thingy:91” guide:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_thingy91.html#building-and-programming-from-the-source-code

 

---

When you are building a project targeting the Thingy:91, you must always build using build target:

thingy91_nrf9160 for the secure version

thingy91_nrf9160_ns for the non-secure version

Please read the Working with Thingy:91 guide and the Thingy:91 Getting Started fo rmore information

Kind regards,
Øyvind