Thread initialization error on pca10059 using multi protocol support for BLE and Thread (works with no problem in pca10056)

RE: Thread initialization error on pca10059 using multi protocol support for BLE and Thread (works with no problem in pca10056)

Rajendra — Wed, 12 Dec 2018 07:05:34 GMT

This worked for me! Now no failure with otInstanceInitSingle() call.

RE: Thread initialization error on pca10059 using multi protocol support for BLE and Thread (works with no problem in pca10056)

haakonsh — Mon, 10 Dec 2018 14:08:26 GMT

In the last release of our SDK we haven’t provided any example that shows how to run multiprotocol example on the PCA10059.

The problem you have experienced is due to incorrect linker configuration.

The ble_thread_dyn_proximity uses linker script which does not assume that bootloader is already flashed. The end result is that bootloader and its settings overlap with Thread non-volatile memory section (which is placed also at the end of the FLASH memory).

Because of that, MPU (Memory Protection Unit) triggers fault state (invalid memory access). For more details about bootloader solution please refer to the following page: https://www.nordicsemi.com/en/DocLib/Content/SDK_Doc/nRF5_SDK/v15-2-0/lib_bootloader

We have prepared a short tutorial on how to modify example to be run on PCA10059 dongle. All in all you need to modify just a few lines.

Download nRF5 SDK for Thread and Zigbee 2.0.0
Download openthread_nrf52840_multiprotocol_pca10059.ld linker script (attached) and copy it to the following folder: \external\openthread\linker_scripts\openthread_nrf52840_multiprotocol_pca10059.ld

Here you can see the diff between the default linker script: (as you see flash length has to be shortened to reserve place for Bootloader).

$ diff --color openthread_nrf52840_multiprotocol.ld openthread_nrf52840_multiprotocol_pca10059.ld
<   FLASH (rx) : ORIGIN = 0x26000, LENGTH = 0xda000
---
>   FLASH (rx) : ORIGIN = 0x26000, LENGTH = 0xba000
9a10,14
>
>   uicr_bootloader_start_address (r) : ORIGIN = 0x10001014, LENGTH = 0x4
>   bootloader_settings_page (r) : ORIGIN = 0x000FF000, LENGTH = 0x1000
>   uicr_mbr_params_page (r) : ORIGIN = 0x10001018, LENGTH = 0x4
>   mbr_params_page (r) : ORIGIN = 0x000FE000, LENGTH = 0x1000
Make following changes in the example Makefile (e.g. examples\multiprotocol\ble_thread\ble_thread_dyn_proximity\uart\pca10056\s140\armgcc) (or usb variant)

$ diff --color Makefile.old Makefile
1c1
< PROJECT_NAME     := ble_thread_dyn_proximity_uart_pca10056_s140
---
> PROJECT_NAME     := ble_thread_dyn_proximity_uart_pca10059_s140
9c9
<   LINKER_SCRIPT := $(SDK_ROOT)/external/openthread/linker_scripts/openthread_nrf52840_multiprotocol.ld
---
>   LINKER_SCRIPT := $(SDK_ROOT)/external/openthread/linker_scripts/openthread_nrf52840_multiprotocol_pca10059.ld
252c252
< CFLAGS += -DBOARD_PCA10056
---
> CFLAGS += -DBOARD_PCA10059
280c280
< ASMFLAGS += -DBOARD_PCA10056
---
> ASMFLAGS += -DBOARD_PCA10059
Run make in the armgcc folder.
Open nRF Connect with Programmer application. (https://www.nordicsemi.com/Software-and-Tools/Development-Tools/nRF-Connect-for-desktop)

(note that the same you could achieve with nrfutil)
Use Add HEX file to add two files

1. Softdevice: components\softdevice\s140\hex\s140_nrf52_6.1.0_softdevice.hex
2. Application: examples\multiprotocol\ble_thread\ble_thread_dyn_proximity\uart\pca10056\s140\armgcc\_build\nrf52840_xxaa.hex
  
  Note that assumption here is that you have dongle with Bootloader and MBR already flashed (stock version). Else if you mess with flash memory then you need to flash Bootloader using JLink programmer.

7. Click the Write button. After couple of seconds, your device is flashed and operational.

You should see similar memory map as presented below.

Red Color – Bootloader

Yellow Color – Application (with OpenThread)

Blue Color – SoftDevice

Orange – MBR (which is incorporated in the SoftDevice)

Gray – Unused memory

8.Testing:

1. Verify that device sends Thread messages by:
  i ) using sniffer e.g. from here (https://github.com/NordicPlayground/nRF-802.15.4-sniffer)
  ii) or connecting Thread Simple CoAP Client
2. Use nRF Toolbox application (https://itunes.apple.com/us/app/nrf-toolbox/id820906058?mt=8) (https://play.google.com/store/apps/details?id=no.nordicsemi.android.nrftoolbox&hl=en)
  Click to Proximity application and connect to Thread Proximity device. Then push button on the dongle to trigger sound alarm on your mobile phone, or push localization button in the mobile application to toggle LED on dongle.

Linker script: devzone.nordicsemi.com/.../openthread_5F00_nrf52840_5F00_multiprotocol_5F00_pca10059.ld

RE: Thread initialization error on pca10059 using multi protocol support for BLE and Thread (works with no problem in pca10056)

Rajendra — Wed, 05 Dec 2018 11:32:06 GMT

Hello Manuel,

Thank you for the reply!

I am still not able to understand, how you came to the conclusion that otInstanceInitSingle() fails?

-Rajendra

RE: Thread initialization error on pca10059 using multi protocol support for BLE and Thread (works with no problem in pca10056)

mrc74 — Mon, 03 Dec 2018 01:05:03 GMT

Hi,

No, unfortunately I did not try to debug the code. I simply flashed it.

Manuel

RE: Thread initialization error on pca10059 using multi protocol support for BLE and Thread (works with no problem in pca10056)

haakonsh — Thu, 29 Nov 2018 13:32:01 GMT

I think you guys need to check out this tutorial:
https://devzone.nordicsemi.com/tutorials/b/getting-started/posts/nrf52840-dongle-programming-tutorial

RE: Thread initialization error on pca10059 using multi protocol support for BLE and Thread (works with no problem in pca10056)

Rajendra — Wed, 28 Nov 2018 04:56:18 GMT

Hello Manuel,

I wonder how you were able to debug the thread application for PCA10059 on USB dongle. Currently, I am using LEDs with different color combinations for debugging. I was not able to debug using the DK board, I have explained this on the forum. The link is: https://devzone.nordicsemi.com/f/nordic-q-a/40701/debugging-on-nrf52840-dongle

Can you please have a look at the post and let me know what is missing from the setup?

Thanks,

Rajendra

RE: Thread initialization error on pca10059 using multi protocol support for BLE and Thread (works with no problem in pca10056)

Rajendra — Wed, 28 Nov 2018 04:48:10 GMT

I used hex file on USB dongle, code was compiled for PCA10059. I could debug the code using different colors of LED till otInstanceInitSingle(). then it stopped. I am using 'nRF5_SDK_for_Thread_and_Zigbee_2.0.0_29775ac\examples\thread\simple_coap_client'.

RE: Thread initialization error on pca10059 using multi protocol support for BLE and Thread (works with no problem in pca10056)

haakonsh — Tue, 27 Nov 2018 13:00:58 GMT

@Rajendra:

Did you use the same hex for both devices?

RE: Thread initialization error on pca10059 using multi protocol support for BLE and Thread (works with no problem in pca10056)

haakonsh — Tue, 27 Nov 2018 12:57:44 GMT

You can use the nRF Connect v2.6.1's Programmer application to read the flash memory and save it as a hex file. You can use the DK to connect to the dongle. Either solder directly to SWDCLK/SWDIO or use debug connectors on the bottom side.

Also does your PCA10056 project use any GPIOs?

RE: Thread initialization error on pca10059 using multi protocol support for BLE and Thread (works with no problem in pca10056)

Rajendra — Mon, 26 Nov 2018 06:58:49 GMT

I am also facing the same problem. Here is the hex file I used for downloading into the device.

devzone.nordicsemi.com/.../5672.nrf52840_5F00_xxaa.hex

RE: Thread initialization error on pca10059 using multi protocol support for BLE and Thread (works with no problem in pca10056)

mrc74 — Thu, 22 Nov 2018 14:55:48 GMT

I am new to your dev tools. Would you mind posting instructions on how to read out the flash contents for both pca10056 and pca10059?

RE: Thread initialization error on pca10059 using multi protocol support for BLE and Thread (works with no problem in pca10056)

haakonsh — Thu, 22 Nov 2018 08:19:32 GMT

Do you mind reading the content of flash of the two devices as hex files, and post them? There should only be minute discrepancies between them.