Putting working program from nRF51DK onto a nRF51822 on custom board

RE: Putting working program from nRF51DK onto a nRF51822 on custom board

Hung Bui — Mon, 28 Aug 2017 10:49:02 GMT

@pavan: please try to create a new case and describe your issue. Piggy packing your question is not suggested. You can create a new case and send the OP a private message to the case if you want.

RE: Putting working program from nRF51DK onto a nRF51822 on custom board

pavan — Sat, 26 Aug 2017 06:25:39 GMT

Hello Mr.Andy,

Have you solved the above issue because even i stuck at same place my custom board is not broadcasting anything

RE: Putting working program from nRF51DK onto a nRF51822 on custom board

Hung Bui — Thu, 17 Sep 2015 14:44:54 GMT

@Andy: L2 should be 27nH, could you explain why you used 10nH ? C48 should be 1.0 pF.

My suggestion is to test with the blinky example in the SDK. You can find that we have 2 setup, one with s110 and one is blank. You can test first by erase the chip completely and test the blank one. You may need some modification to match with your hardware setup (the chip and the GPIO pins). After you have your LED blinking, you should try the blinky_s110_pca100028. To test this, you flash the s110 softdevice first, and then flash the application after. You should use the correct softdevice version, for SDK v8.0 and SDK v9.0 you should use S110 v8.0.

After you have the blinky_s110, you can test with other BLE example , such as the ble_app_hrm, make sure you have used :

SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_4000MS_CALIBRATION, NULL);

RE: Putting working program from nRF51DK onto a nRF51822 on custom board

Nguyen Hoan Hoang — Thu, 17 Sep 2015 01:36:30 GMT

Your RAM setting should be 0x4000 not 0x8000. What is your chip revision ? Chip Rev 1 will not work.

RE: Putting working program from nRF51DK onto a nRF51822 on custom board

andy — Wed, 16 Sep 2015 17:21:40 GMT

Hi Hung,

I have attached the schematic for the nRF chip on our custom board. Is the cause of the problem because we are only using one 16MHz crystal? If so, how should I adjust for that?

RE: Putting working program from nRF51DK onto a nRF51822 on custom board

Hung Bui — Tue, 01 Sep 2015 09:12:53 GMT

@andy: Have you made sure you have flashed the softdevice ? IROM1 start at 0x0 is wrong. If the softdevice is flashed, the application should start at 0x18000, IRAM1 should start at 0x20002000. Please try again with an unmodified stock example.

You can edit the question to attach file in the question.

RE: Putting working program from nRF51DK onto a nRF51822 on custom board

andy — Mon, 31 Aug 2015 15:19:39 GMT

Hi Hung,

Unfortunately, changing the Softdevice init did not help. Do I need to select the correct Options for Target in Keil uVision?

Right now these are my settings: Device: nRF51433_xxAC (however I tried changing this to nRF51822_xxAA but it did not help).

Target: Xtal (MHz) -- "12.0" Operating system -- "None" ARM Compiler -- "Use default compiler version" Read/Only Memory Areas -- IROM1 (box is checked) Start-- "0x0" Size -- "0x40000" Startup (circle is checked)
Read/Write Memory Areas -- IRAM1 (box is checked) Start -- "0x20000000" Size -- "0x8000"

C/C++: Define: BLE_STACK_SUPPORT_REQD BOARD_PCA10028 S110 NRF51 SOFTDEVICE_PRESENT SWI_DISABLE0 One ELF Section per Function (box is checked)

Asm: Define: BLE_STACK_SUPPORT_REQD BOARD_PCA10028 S110 NRF51 SOFTDEVICE_PRESENT SWI_DISABLE0

Also, I cannot attach a photo on this thread, so I am not sure how to share my board schematic.

RE: Putting working program from nRF51DK onto a nRF51822 on custom board

Hung Bui — Thu, 27 Aug 2015 11:40:46 GMT

@andy: if you look into the code in main.c you can find this line:

SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_XTAL_20_PPM, NULL);

Change it to

SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_4000MS_CALIBRATION, NULL);

Will make the stack uses the 32kHz RC instead of the 32kHz crystal.

You can send me your board schematic and PCB layout for checking.

RE: Putting working program from nRF51DK onto a nRF51822 on custom board

andy — Wed, 26 Aug 2015 17:53:34 GMT

Here is a note about my setup: The chip on my custom PCB is connected to the SWCLK, SWDIO, GND, VREF pins on the nRF51DK. When I give power to the PCB, nRFgo Studio recognizes the chip is nRF51822 (instead of the nRF51DK chip which is nRF51422). I am using Kiel uVision5 to compile the examples from NRF51_SDK_9.0.0. I then go to nRFgo Studio and do the following: 1) Erase All. 2) In the Program SoftDevice tab, I select "nRF51_SDK_9.0.0_2e23562/components/softdevice/s110/hex/s110_softdevice.hex", and click Program. 3) In the Program Application tab, I select "nRF51_SDK_9.0.0_2e23562/examples/ble_peripheral/ble_app_hrs/pca10028/s110/arm5_no_packs/_build/nrf51422_xxac_s110.hex" and click Program. The nRFgo Log says Softdevice programmed successfully and Application programmed successfully. I open nRF Toolbox on my iPhone, select HRM, and press Connect, but nothing is broadcasting.

RE: Putting working program from nRF51DK onto a nRF51822 on custom board

andy — Wed, 26 Aug 2015 17:46:46 GMT

Hi Hung,

Thank you for your reply.

Following your suggestion, I was able to successfully toggle a pin on my custom board. However, I tried to upload the HRM example from SDK9 with the softdevice110 that is in SDK9. The chip did not broadcast to my phone. I uploaded the same example with the same softdevice to the nRF51DK and it worked fine.

I did not configure the softdevice init to 32kHz, though. Could you tell me how to do that? (I am very new to this). I hope that will solve my problem.

RE: Putting working program from nRF51DK onto a nRF51822 on custom board

Hung Bui — Wed, 19 Aug 2015 13:03:23 GMT

@andy: I would suggest you to start first by uploading a firmware that blink an LED or toggle a GPIO pin on your custom board. Having that you can verify if you can properly flash a hex file on your board and your chip on the board can work properly.

After that you can try flashing the softdevice, and a simple BLE example, HRM for example. It should work regardless the incompatible GPIOTE onthe DK and your board. Make sure you have configure the softdevice init to match with your 32kHz clock source.