Transfer nRF51422 project to nRF51822

[brianbscho]

Hi,

I'm currently testing ble_app_uart on nRF51822 custom board. I connected it to nrf51 DK P19 and was able to program the hex file successfully.

But it doesn't run although it was working perfectly fine with nRF51 DK (which is nRF51422).

I read devzone.nordicsemi.com/.../ thread and it seems it should work as it is. But it doesn't work like that in my case.

Do I need to change any configuration on Keil? Can anyone please help me to fix this issue?

Thanks, Brian

[RK]

You've flashed a softdevice, the correct softdevice for the project you've built?

You have a LF crystal on the board? Right tolerance for the parameters you're starting the softdevice with?

Have you tried a simple no-softdevice project to see if that works?

What does 'doesn't run' mean, where does it go, can you get a debugger on it and see what it's up to?

[brianbscho]

Okay, I found it's working with simple peripheral example without SoftDevice. But as soon as I use any project using SoftDevice, it doesn't response with GPIO input as well as it doesn't advertise. I guess there is some problem of using SoftDevice in my custom board. What can I try to solve this?

[RK]

ok so the board at least works. You didn't answer my question about the LF crystal, do you have one on the board? Check the softdevice is on the chip and the code too, check it's on at the right place use a debugger to read it back and ensure it was programmed. Use a debugger when your code is running to find out where you are, are you in a fault handler? You could try temporarily switching the clock source for the softdevice to NRF_CLOCK_LFCLKSRC_SYNTH_250_PPM to take the LF crystal out of the equation entirely, just remember to put it back.

[brianbscho]

Yes, I used LF crystal and confirmed the schematic with Nordic. With nRFgo Studio, I successfully loaded SoftDevice and Application. In the debug mode, it seems code is running okay. It didn't fall into fault handler and code runs line by line smoothly. Finally I changed clock to NRF_CLOCK_LFCLKSRC_SYNTH_250_PPM but didn't see improvement. It's really frustrating...