Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NRF52 SDK with custom board

Hi,

I am using a custom board which I designed based on the Puck-js board, except that I am only using an I2C based distance sensor instead of the other devices onboard. The Puck-js board uses a Raytac module which uses an nRF52832 device. I am using the J-Link Segger with Segger Embedded Studio v3.34a to program the module via SWD interface. As a starting point, I am using the nRF52 SDK to explore the system using the examples provided. I have been able to run the blinky example inside the examples>peripheral>blinky>pca10040>blank>ses folder with minor modifications to the LED pin numbering.

However, to explore the BLE part of the system, I tried the 'heart rate' example inside the examples>ble_peripheral>ble_app_hrs>pca10040>s132>ses folder. The program successfully downloaded on to the Raytac module, however, the advertising did not start. I entered debug mode to see where the program execution halts. I observed that the program is not getting past the ble_stack_init() function called within the main(), which explains the reason why it is not advertising.

I followed the basic debugging tutorial provided by Nordic Semi to see if I can get an error code to further investigate the problem. I opened the app_error.c file to put a breakpoint inside the app_error_handler_bare() function, however, the breakpoint legend has a question mark inside, and hovering the mouse pointer says 'no code for breakpoint'. What am I missing here?

Also, are there any settings which need to be modified when using a module such as the MDBT42Q instead of an nRF52 DK board while working with the examples provided?

I presume that softdevice 132 doesn't have to be separately flashed for SES release.

Thank you.

Regards,

Arish

Related