Not able to run the nrf Mesh SDK 3.0.0 for nrf52832 (PCA10040)

RE: Not able to run the nrf Mesh SDK 3.0.0 for nrf52832 (PCA10040)

AndreasF — Wed, 02 Jan 2019 05:34:36 GMT

Hi.

[quote user="AshokY"]Also I didn't understand why my code is hanging in [/quote]

What error do you get? You have to check that in order to know whats wrong.

/**@brief Enables the SoftDevice and by extension the protocol stack.
 *
 * @note Some care must be taken if a low frequency clock source is already running when calling this function:
 *       If the LF clock has a different source then the one currently running, it will be stopped. Then, the new
 *       clock source will be started.
 *
 * @note This function has no effect when returning with an error.
 *
 * @post If return code is ::NRF_SUCCESS
 *       - SoC library and protocol stack APIs are made available.
 *       - A portion of RAM will be unavailable (see relevant SDS documentation).
 *       - Some peripherals will be unavailable or available only through the SoC API (see relevant SDS documentation).
 *       - Interrupts will not arrive from protected peripherals or interrupts.
 *       - nrf_nvic_ functions must be used instead of CMSIS NVIC_ functions for reliable usage of the SoftDevice.
 *       - Interrupt latency may be affected by the SoftDevice  (see relevant SDS documentation).
 *       - Chosen low frequency clock source will be running.
 *
 * @param p_clock_lf_cfg Low frequency clock source and accuracy.
                         If NULL the clock will be configured as an rc source with rc_ctiv = 16 and .rc_temp_ctiv = 2
                         In the case of XTAL source, the PPM accuracy of the chosen clock source must be greater than or equal to the actual characteristics of your XTAL clock.
 * @param fault_handler Callback to be invoked in case of fault.
 *
 * @retval ::NRF_SUCCESS
 * @retval ::NRF_ERROR_INVALID_STATE SoftDevice is already enabled, and the clock source and fault handler cannot be updated.
 * @retval ::NRF_ERROR_SDM_INCORRECT_INTERRUPT_CONFIGURATION SoftDevice interrupt is already enabled, or an enabled interrupt has an illegal priority level.
 * @retval ::NRF_ERROR_SDM_LFCLK_SOURCE_UNKNOWN Unknown low frequency clock source selected.
 */
SVCALL(SD_SOFTDEVICE_ENABLE, uint32_t, sd_softdevice_enable(nrf_clock_lf_cfg_t const * p_clock_lf_cfg, nrf_fault_handler_t fault_handler));

Check which error code you have and match it to the errors listed in the API description.

Best regards,

Andreas

RE: Not able to run the nrf Mesh SDK 3.0.0 for nrf52832 (PCA10040)

AshokY — Mon, 31 Dec 2018 19:01:08 GMT

Yes. To get Mesh topology I will add more nodes once I am OK with one.

My question is in 3.0.0 I wanted to use the Light switch server (Proxy enables) example and the Mobile app for both provsioning and latter on/off.

Also I didn't understand why my code is hanging in

ret_code = sd_softdevice_enable(&clock_lf_cfg, app_error_fault_handler); which is at line number 214, file nrf_sdh.c.

Thanks,

Ashok. Y

RE: Not able to run the nrf Mesh SDK 3.0.0 for nrf52832 (PCA10040)

awneil — Mon, 31 Dec 2018 18:03:57 GMT

You can't have a MESH - of any sort - with just one one node!

RE: Not able to run the nrf Mesh SDK 3.0.0 for nrf52832 (PCA10040)

AshokY — Mon, 31 Dec 2018 17:49:11 GMT

Hi,

Thanks for the reply.

I am using Segger embedded studio to connect to target and flash both the Softdevice and image (light_switch_server_nrf52832_xxAA_s132_6.1.0.elf). Here I am using Light switch server example. Also, I am planning to use the nRF Mesh mobile app as provisioner .

In mesh 2.2.0, I don't need one development board for client. Here in 3.0.0 is it mandatory to have separate client board?

Thanks,

Ashok Y

RE: Not able to run the nrf Mesh SDK 3.0.0 for nrf52832 (PCA10040)

awneil — Sat, 29 Dec 2018 17:29:37 GMT

Have you programmed the SoftDevice?

[quote userid="74806" url="~/f/nordic-q-a/42020/not-able-to-run-the-nrf-mesh-sdk-3-0-0-for-nrf52832-pca10040"]I was able to build and flash the image[/quote]

What do you mean, "the image" ?

You need at least three images:

One development board for a client.
One development board for the provisioner
One or more development boards for the servers.