Board is not defined

[masta]

Hello everyone, I want to run project ble_uart on NRF52832 in Keil. At the beginning of the main.c I add #define BOARD_NRF6310

But get error C:\Keil_v5\ARM\PACK\NordicSemiconductor\nRF_Examples\11.0.0-2.alpha\bsp\boards.h(44): error: #35: #error directive: "Board is not defined"

main.c(334): error: #20: identifier "nrf_clock_lf_cfg_t" is undefined nrf_clock_lf_cfg_t clock_lf_cfg = NRF_CLOCK_LFCLKSRC; main.c(337): error: #94-D: the size of an array must be greater than zero SOFTDEVICE_HANDLER_INIT(&clock_lf_cfg, NULL);

[Sigurd]

Hi,

As of SDK 11.0.0 the CMSIS pack system is deprecated. The reason is explained in this blog: Deprecating support for CMSIS Pack in nRF5 SDK. The SDK is now delivered as a .zip archive. The latest SDK version for the nRF52-series is SDK 14.2. Please update to this version. You can download this SDK from this link.

You can find the source code and the project file of the ble_app_uart example in the following folder: <SDK_14_2_InstallFolder>\examples\ble_peripheral\ble_app_uart

The old nRF6310 motherboard was designed to be used with the nRF51 series. If you are using the nRF52832, you should not use the nRF6310.

[Sigurd]

The address is correct. Make sure that you have flashed the S132 V.5 SoftDevice. You can find this in the folder SDK_folder\components\softdevice\s132\hex.

In nRFGO Studio it should look something like this:

Note that the BLE link will get disconnected when hitting a breakpoint, because the radio will be halted, and the radio will therefore not be able to transmit the necessary packets to keep the BLE connection. The link will disconnected after a timeout given in the connect request (or a connection parameter update), and you will get a fault when debugging.

Debugging when the SoftDevice is active can be tricky. Using the logging system (nrf_log), logging messages over Segger RTT or UART is recommended when you try to find root cause of issues. Step-by-step debugging is not recommended when in an active BLE connection. We have something called Monitor Mode Debugging that can be used, but it can be a bit cumbersome to setup.