Using an nRF52 Dev Kit to communicate to an Android phone via BLE

RE: Using an nRF52 Dev Kit to communicate to an Android phone via BLE

Simonr — Thu, 09 Dec 2021 11:18:07 GMT

The output file will indeed not include the SoftDevice. To get one full output file you can use the nRF Command Line Tools mergehex command to merge .hex files. The SoftDevice .hex files can be found under /YOUR_SDK_FOLDER/components/softdevice you can then merge your project's output file with the SoftDevice to have one .hex file.

Regarding your application, please check out the battery service that is included in numerous example projects in the nRF5 SDK, for example the heart rate application, where the device sends heart rate notifications every second and battery level notifications every 2 seconds. If you use just the battery level notifications, you can set the interval between this to whatever you'd like and set the device to sleep in the meantime. Waking up every X second/minute to notify the central of its battery level.

Best regards,

Simon

RE: Using an nRF52 Dev Kit to communicate to an Android phone via BLE

AllenS — Wed, 08 Dec 2021 20:15:49 GMT

Hello Simon,

The ble_app_uartdid compile in the Segger Studio and the output hex file was only 47K. The application did not work when the hex file was placed on the USB Drive for the Dev Kit. However, the precompiled version that was sent with the SDK, the hex file size is 498K. When I put that hex file into the Dev Kit USB Drive, it worked. That brings up the question, why did the S132 not compile with the project and how do I make it do that? Also, my project requires to come up from a sleep mode, send out the battery level and then go back to sleep. I wanted to make the interval time programmable from 5 to 9 seconds. Is there an example project of something similar that I could look at for ideas?

Thanks,

Allen

RE: Using an nRF52 Dev Kit to communicate to an Android phone via BLE

Simonr — Wed, 08 Dec 2021 09:26:03 GMT

When using SEGGER Embedded Studios and our example projects, it's not necessary to flash the SoftDevice separately. I would recommend using the nRFConnect app on your Android phone, as nRFgo Studio is very old at this point.

After that building and flashing most BLE peripheral example projects in the nRF5 SDK v17.1.0 should be able to connect to an Android phone using nRFConnect. I would suggest the ble_app_uart example, which lets you print messages to a UART terminal from the phone using the Nordic UART Service?

Best regards,

Simon