NRF52832 Problem with/without 32.768kHz X'tal? Or other Problem?

[elangel]

Hello,

I'am working with a Taiyo Yuden Bluetooth Module "EYSHCNZWZ"

This Module include the LC Network for DCDC use and the 32.768kHz X'tal.

I'am using Arduino and the Redbear Library with the Redbear Softdevice S132.

Everything works fine.

Now i changed to the "EYSHSNZWZ" Module from Taiyo Yuden.

It has no 32.768kHz X'tal and no LC Network for DCDC.

Flashing the Softdevice -> No Problem.

Flashing Application -> Warning "Unknown device (HWID 0x000000e3)"

But the Device didn't work at all. No advertise, no Serial, nothing.

The Application is exactly the same for both modules.

Is there a problem with the Softdevice without the 32.768kHz X'tal?

Is there another Problem?

I hope you could help me

[Turbo J]

elangel said:

Is there a problem with the Softdevice without the 32.768kHz X'tal?

Yes, because it will be used in the default configuration. Similar story for the DC/DC. You will need to "recover" the module - that erases the flash.

You will have to change the source code in order to use the syntethised 32kHz clock, and to disable the DC/DC usage.

[elangel]

How can i change the source code of the Softdevice?

Is there no precompiled version for syntethised 32kHz clock and internal LDO?

[MartinBL]

This is a very common problem. 

How can i change the source code of the Softdevice?
You cannot change the Softdevice. You can only change how you choose configure it. How you configure the clock source depends on what SDK version you are using.

Is there no precompiled version for syntethised 32kHz clock and internal LDO?
Not that I am aware.

PS: The nRF52 supports three different 32 kHz clock sources: Crystal, internal RC oscillator, and synthesized. You probably want to use the RC oscillator. A synthesized clock is rarely used since it requires the 32 MHz crystal to run at all times which draws more current than the RC Oscillator.

[elangel]

Thank you Martin.

Now i have to check all 1000 header files to search the right file for the Clock setting and the DCDC setting.

i found a "device.h" file.

/**
 * @brief NRF_LF_SRC_XTAL  2
 *        NRF_LF_SRC_SYNTH 3
 *        NRF_LF_SRC_RC    4
 */
#define MBED_CONF_NORDIC_NRF_LF_CLOCK_SRC 4

There i set the clock source to 4, but it didnt help. i think i have to change the dcdc settings.....

[MartinBL]

The examples in Nordic's SDK don't use DCDC by default. I have no experience with Redbear libraries and examples though, so I don't know what to expect there. It might very well be that DCDC is enabled.

Anyway, maybe it could be an idea to try a basic example without BLE, just to check that the HW works at all.