Board is not defined

RE: Board is not defined

masta — Thu, 14 Dec 2017 13:58:46 GMT

Thank you very much!!!!!!!

RE: Board is not defined

Sigurd — Thu, 14 Dec 2017 12:52:47 GMT

That is correct. The ble_app_uart example is not configured to allow pairing. You will need to add the Peer Manager module to support pairing. If you want test an example that does allow pairing, I would recommend using the ble_app_hrs example.

RE: Board is not defined

masta — Thu, 14 Dec 2017 12:45:58 GMT

Now the phone sees the device(Nordic_UART), but does not allow pairing.

RE: Board is not defined

Sigurd — Thu, 14 Dec 2017 08:59:26 GMT

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.

RE: Board is not defined

masta — Thu, 14 Dec 2017 02:04:41 GMT

The project successfully compiles, but the program does not debug. My past project, which debugged well had the following settings.

https://prnt.sc/hn7487

And this

http://prntscr.com/hn83vg

May be this address need change?

....

If I change the address, the program jump SVC_Handler when ble_stack_init()

RE: Board is not defined

Sigurd — Wed, 13 Dec 2017 22:43:00 GMT

You should have had alot more defines in the Preprocessor Symbols. Please unzip the .zip, and open the Keil project located in <SDK_14_2_InstallFolder>\examples\ble_peripheral\ble_app_uart\pca10040\s132\arm5_no_packs

RE: Board is not defined

masta — Wed, 13 Dec 2017 22:38:47 GMT

http://prntscr.com/hn68jh

Keil gave an error

main.c(60): error: #5: cannot open source input file "nrf_sdh.h": No such file or directory

RE: Board is not defined

Sigurd — Wed, 13 Dec 2017 22:34:59 GMT

You should use BOARD_PCA10040. This should have already been added as a define in the Keil project under "Options for target" -> "C/C++" tab, under "Preprocessor Symbols".

RE: Board is not defined

masta — Wed, 13 Dec 2017 21:49:58 GMT

Thanks, and what board should I choose?

RE: Board is not defined

Sigurd — Wed, 13 Dec 2017 10:10:38 GMT

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.