# Taiyo Yuden EYSHJNZXZ (nRF52832) not working when using softdevice

asked 2017-03-16 20:37:53 +0100

I am able to run nRF5_SDK_12.2.0/examples/peripheral/blinky using the armgcc toolchain without any issues but any example with a soft device enabled (e.g. nRF5_SDK_12.2.0/examples/ble_peripheral/ble_app_beacon) does not show up using LightBlue or nRF Toolbox. If I modify the sample code to turn on an LED as the first instruction in the program, it never gets there.

I have the same problem running the mbed5 blinky example (using mbed-cli instead of nordic SDK/armgcc). This works fine on a nRF52-DK but not on the EYSHJNZXZ. I am aware that mbed5 includes the s132 2.0.0 soft device, which tells me that the moment a program image includes the softdevice it won't run on the EYSHJNZXZ module.

What am I missing? Are there any special considerations for using the Taiyo Yuden module compared to a stock nRF52832? I'm at a loss. Any assistance would be greatly appreciated.

edit retag close delete

Sort by » oldest newest most voted

answered 2017-03-20 09:15:13 +0100

All the SDK examples are set up to by default use external 32 kHz crystal. If the modules doesn't have an external 32 kHz crystal, you need to change the LFCLK clock source in ble_stack_init().

more

answered 2017-03-20 14:22:13 +0100

Hello Kristin,

Thanks for the feedback. For the benefit of others, when using MBED (OS5), I determined that the define MBED_CONF_NORDIC_LF_CLOCK_SRC needed to be changed to NRF_LF_SRC_SYNTH so that it derives a 32KHz clock from the 32MHz crystal. This seems to work for all MBED examples, including "blinky" and "ble-LED".

targets.json: (MCU_NRF52 section)

"config": {
"lf_clock_src": {
"value": "NRF_LF_SRC_SYNTH",
"macro_name": "MBED_CONF_NORDIC_NRF_LF_CLOCK_SRC"
},


...

more

Another option is to use the internal RC oscillator instead of the synthesized clock. The synthesized clock requires the 32 MHz crystal to run all the time, while the RC oscillator doesn't. The RC oscillator will therefore use less current.

( 2017-03-20 14:31:26 +0100 )editconvert to answer

Good point! In that case the define would be NRF_LF_SRC_RC.

( 2017-03-20 14:41:40 +0100 )editconvert to answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

[hide preview]

## Recent blog posts

• ### Getting started with Nordic's Secure DFU bootloader, a step by step guide

Posted 2017-03-20 17:13:52 by Hung Bui
• ### From Nordic UART Service to MicroPython using PolyMCU and Gattlib

Posted 2017-02-27 16:40:00 by Olivier
• ### Throughput and long range demo

Posted 2017-02-28 16:48:25 by Ole Bauck
• ### nRF52840 long range demo

Posted 2017-02-14 12:46:03 by Ole Bauck
• ### Setup and Running the OpenMesh DFU on the nRF52 DK v2.0

Posted 2017-02-06 22:33:25 by martindavidb

## Recent questions

• ### what kinds of flag Do I set, when I use sdk13 in keil-c debug mode

Posted 2017-03-24 10:41:29 by Vincent
• ### The peak current of nRF52832

Posted 2017-03-24 10:16:17 by Stanley
• ### multiple definition of `SPI1_TWI1_IRQHandler'

Posted 2017-03-24 10:03:43 by ashare
• ### Questions about BLE multirole LESC

Posted 2017-03-24 09:50:09 by Fabien Comte
• ### can i put my nrf51822 in sleep mode..?

Posted 2017-03-24 07:54:34 by iqbalpalemad

## Stats

Asked: 2017-03-16 20:37:53 +0100

Seen: 115 times

Last updated: Mar 20