Uploading test code onto custom pcb with nRF51 chip

[esb]

I have made a basic pcb for a school project, with just the nRF51422 chip, a J-LINK programmer and and antenna on it. I am trying to test the functionality of it. I have gotten the blinky example to work, but I cannot seem to get any of the other example codes to work properly. I am mainly interested in getting the Bluetooth to advertise. Are there some modifications I need to make in the code when switching from the DK to my own board/chip configuration?

[Nick Pelis]

That really depends on the differences between your custom board and the nRF51 DK. For instance, if you have buttons mapped to different GPIOs then you'll need to edit your code to get those to work.

[esb]

The mapping seems to be working fine. In testing the GPIOs, the 4 pins associated with the leds on the DK board are high, which is partially correct (one should be blinking). I'm wondering if any of the example code utilizes the MCU on the DK, which I do not have on my board. Also, in trying to change the pins being used for the GPIO outuputs, it appears that many of the .c files and .h files are locked. Is there a way to unlock these files for editing? This is after I copy an example into my own directory.

[Ole Bauck]

Do you use an external 32 khz crystal? The examples use this and if you don't have it, the code will be stuck in sd_softdevice_enable(...) waiting for the crystal to start. If you don't have external clock change the softdevice init call to this:

SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_RC_250_PPM_TEMP_4000MS_CALIBRATION, NULL);

[esb]

We do have an external 32kHz and an external 16MHG oscillator on our board, but neither of them seem to be working correctly. I switched the SOFTDEVICE_HANDLER_INIT() to what you suggested, and the board at least attempts to advertise. Because of this, I am leaning towards the issue being in hardware.

[Ole Bauck]

Could you update the question with the hardware files (schematic and layout)?