Uploading test code onto custom pcb with nRF51 chip

RE: Uploading test code onto custom pcb with nRF51 chip

Ole Bauck — Thu, 10 Dec 2015 10:37:16 GMT

If you are using packs some of the files will be locked yes. You can add your custom pinout by adding a file "custom_board.h" to your project with the pin definitions (see pca10028.h that is used for the DK) and change BOARD_PCA10028 to BOARD_CUSTOM in preprocessor symbols defines (options for target->C/C++->Preprocessor Symbols). See this tutorial and the board.h file for more information.

RE: Uploading test code onto custom pcb with nRF51 chip

Ole Bauck — Thu, 10 Dec 2015 10:28:53 GMT

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

RE: Uploading test code onto custom pcb with nRF51 chip

esb — Thu, 10 Dec 2015 05:10:38 GMT

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.

RE: Uploading test code onto custom pcb with nRF51 chip

Ole Bauck — Wed, 09 Dec 2015 16:34:50 GMT

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);

RE: Uploading test code onto custom pcb with nRF51 chip

esb — Wed, 09 Dec 2015 04:16:08 GMT

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.

RE: Uploading test code onto custom pcb with nRF51 chip

Nick Pelis — Wed, 09 Dec 2015 01:26:07 GMT

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.