Porting ble_thread_dyn_mtd_coap_cli from PCA10056 to PCA10059

[Andre]

Hello

I am contacting you because I have 2 problems:

1.
I downloaded the "nRF5_SDK_for_Thread_and_Zigbee_v4.0.0_dc7186b" available at this address: www.nordicsemi.com/.../nRF5-SDK-for-Thread-and-Zigbee
I would like to try the example "ble_thread_dyn_mtd_coap_cli" but there is a problem with the compilation: it says that it cannot find the file "nrf_raal_softdevice.h" but nevertheless it is able to open it if I do: right click - Go to Included File - nrf_raal_softdevice.h
How can I fix it?

 

2.
I have tested the example "ble_thread_dyn_mtd_coap_cli" from "nRF5_SDK_for_Thread_v0.11.0_84a130f" : this example works fine for a PCA10056 but I'd to test it on a PCA10059. When I had tried to make this project work for a PCA10059 (following the instructions given here "devzone.nordicsemi.com/.../nrf52840-dongle -programming-tutorial "), it never worked: once the device programmed (with nRF Connect), nothing happened (the dongle is not detected once plugged into a COM port (if I push on reset button it is detected but it stays in boot mode) )
To migrate a project coming from PCA10056 towards PCA10059, what must be done in addition to only modifying BOARD_PCA10056 to BOARD_PCA10059?

[Edvin]

Hello,

2:

I suspect that you didn't program the softdevice together with the application when you use nRF Programmer, is that correct? You can find the softdevice in SDK\components\softdevice\s140.

1: 

It may be that the path for that file is too long. Try placing the entire SDK closer to the C: drive.

E.g:

C:\Nordic_Semiconductor\SDK (you can also shorten the name of the "nRF5_SDK_for_Thread_and_Zigbee_v4.0.0_dc7186b" to "SDK" or "SDK_4.0.0" or something like that.

Windows has a limit of 255 (or something around that) characters in a path. Try this and let me know if it doesn't work.

Best regards,

Edvin

[Andre]

Hi Edvin

1:
You're right: shortening the name solves the problem :)

2:
I included it but it didn't work ...
Here are the characteristics of my project:

Section Placement Macros:
FLASH_PH_START=0x0
FLASH_PH_SIZE=0x100000
RAM_PH_START=0x20000000
RAM_PH_SIZE=0x40000
FLASH_START=0x27000
FLASH_SIZE=0xd5000
RAM_START=0x20002ae8
RAM_SIZE=0x3d518

Processor Definitions:
APP_TIMER_V2
APP_TIMER_V2_RTC1_ENABLED
APP_UART_DRIVER_INSTANCE=1
BOARD_PCA10059
CONFIG_GPIO_AS_PINRESET
ENABLE_FEM
FLOAT_ABI_HARD
INITIALIZE_USER_SECTIONS
MBEDTLS_CONFIG_FILE="nrf-config.h"
MBEDTLS_USER_CONFIG_FILE="nrf52840-mbedtls-config.h"
MULTIPROTOCOL_802154_CONFIG_PRESENT
NO_VTOR_CONFIG
NRF52840_XXAA
NRFX_PRS_ENABLED=0
NRF_SD_BLE_API_VERSION=7
OPENTHREAD_CONFIG_COAP_API_ENABLE
OPENTHREAD_CONFIG_ENABLE_BUILTIN_MBEDTLS=0
OPENTHREAD_CONFIG_FILE="openthread-config-wrap.h"
OPENTHREAD_MTD=1
S140
SOFTDEVICE_PRESENT
UART0_ENABLED=0
UART1_ENABLED=1

When I compare all this to a project for PCA10059, I notice that there are any differences ...
For example, I saw that there was "USBD_POWER_DETECTION = 1" in the "Processor Definitions" in addition in the PCA10059 and perhaps other things too -> but adding it does not change anything.

Do you have another idea ?

Thank you so much

[Edvin]

2: Try to run it on a DK, and enable logging or debug to see what's going on. Remember that you need to use the USB peripheral (the other USB port than the one that you program it with to power it. 

Does the application use the UART for anything? In that case, remember that the nRF52840 dongle doesn't have anything connected to the TX/RX pins. The TX pin should be fine, but a floating RX pin can cause some issues in form of a communication event on the UART if it is in use.

Best regards,

Edvin

[Andre]

Hello

Sorry for the late response...

Yes my application uses UART ... But for this test, I commented on all the calls to UART functions that I saw.
If I run my modified app for a PCA10059 on my DK PCA10056, I have a problem during the thread_init () on the instruction "otSysInit (0, NULL);" : it never crosses this line (there is nothing more happening and I have no error)

Do you have an idea ?