Taiyo Yuden EYAGJNZXX - Softdevice Flashing

[CM]

I've experienced some struggles programming for Taiyo Yuden's EYAGJNZXX board. According to the user manual provided its chip is nrf51822 (which supposedly works with s210 softdevice). However, I was able to run one of Nordic's sample ADC projects with uVision's device drop down menu showing "nrf51422_xxac_s130".

Although I was able to send data over BLE and read it in one of our Android devices using the nRF Master Control app I have not been able to use Termine to read any logging data. After such hurdles I though that maybe the softdevice neede some configuration. Based on the initial understanding (as seen by uVision) I downloaded Nordic's s130 softdevice (s130-SD version1.0 and s130-23-v2 version 2.0) and did the following steps

1. Using nRFGO Studio I flashed the 2.0 version of the hex file. Rebuilding my sample project and loading to the board resulted in BLE transmission not showing any data on nRF Master Control app.

2. I proceeded to install version 1.0 hex file and now after rebuilding the project flashing the program into the board results in a failure.

Taiyo Yuden's CD included in the board's box only has PDFs with some board layout description and very simple/lacking user's guide with no softdevice flash (hex) files. Is there no way to revert this board back to its original programming? I haven't found any other softdevice image (hex file) that restores the board to where I at least can re-flash my sample code.

This other question makes it seem that the correct softdevice for my Taiyo Yuden board is s210 (assuming my board is nrf51422 as shown in uVision). Yet, since Taiyo Yuden's included manual only mentions nrf51822 I'm confused as to 1) did I damange the board by flashing the wrong softdevice 2) what is the correct softdevice s210 (if its 422) or s130 (422 or 822).

I'll appreciate some feedback.

Update:

After updating my RAM/ROM settings, as specified in the linked thread of the answer below, I can load the program again into my board. However, the device is not doing BLE advertising since the board is not showing up as a device in either nRF Master Control or nRF Toobox Android apps. No changes were made to the code before/after installing the various softdevices version.

[Vehring]

I´m using the same board and i experience similar problems. There seems to be a problem with the settings

My Taiyo Yuden EBAGJNZXX Evaluation Board has a EYAGJNZXX bluetooth module with a nRF51422 Chip (CFACA00 (0x0088)). I´m using Softdevice S130 2.0.0. and tried to make the ble_app_uart_c example to work.

According to the Taiyo Yuden Manual i set the HFCLK:XTALFREQ register to 32MHz with the cmd prompt: nrfjprog.exe --snr --memwr 0x10001008 --val 0xFFFFFF00

Then the manual says i should set the LFCLK to RC-Oscillator with: SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_250MS_CALIBRATION, false);

That matches Kristin´s proposal. However NRF_CLOCK_LFCLKSRC_RC_250_PPM_250MS_CALIBRATION is unknown. Where should it be defined? So i decided to adjust the settings of NRF_LFCLKSRC in the pca10028.h like described in the nrf_sdm.h to match the settings Taiyo Yuden proposes.

The program is running but the BLE still is not visible in the nRF Toolbox on my iPhone. Via Termite i see that BLE should be advertising (i have no LED´s so i added a uart message to the LED_0 switching).

What is going wrong? Are there also changes in the target settings?

I also wanna mention that i also tried a peripherical ble example (ble_app_cscs). With the changes i did in the uart example i can see the module in the nRF Toolbox App directly after flashing but connection will fail and i don´t see the board anymore, even after reset, on the Toolbox App.

[FormerMember]

This may a little late answer (somehow I didn't see this thread..). With SDK 11 and 12, the LFCLK clock source is set with nrf_clock_lf_cfg_t.