Full UUID values for Blood Pressure App

[BMagnan]

I'm using the Nordic nRF Toolbox Blood Pressure Monitor "BPM" app on my phone and I have the development software running.  Things work fine.  However, I'm trying to figure out what exactly the complete UUID is for the information that I'm sending across.

All I have been able to find is:

static ble_uuid_t m_adv_uuids[] =                                       /**< Universally unique service identifiers. */
{
    {BLE_UUID_BLOOD_PRESSURE_SERVICE,     BLE_UUID_TYPE_BLE},
    {BLE_UUID_BATTERY_SERVICE,            BLE_UUID_TYPE_BLE},
    {BLE_UUID_DEVICE_INFORMATION_SERVICE, BLE_UUID_TYPE_BLE}
};

But I want to know what the full 128 bit UUID is so I can begin to write my own program.  Along those same lines, if anyone can point me to the function calls to modify them I would appreciate it, but I would like to know where the default ones are coming from as well.

Thanks for the help!

[BMagnan]

Some follow up info:

I am using soft device s132, SDK 15.0.0 and the chip is an NRF52 device.

Essentially I need to create a new UUID base id, and I can't see in the firmware where I can add in my new custom 128 bit UUID.  I can't find in the documentation how to do this or what files the information would be in.

[haakonsh]

Use ble_app_uart example (UART/Serial Port Emulation over BLE) as a template. The Nordic Uart Service uses a 128-bit Vendor Specific UUID. See NUS_BASE_UUID on line 64 of ble_nus.c. 

The nRF Connect app on android has a detailed log that show the full UUIDs that you interact with when connected to a device. Just swipe right on the main screen to access the logs. 

[BMagnan]

I tried to run the example program, but ran into two issues.  One, I got a compile error for

Building ‘ble_app_uart_pca10040_s132’ from solution ‘ble_app_uart_pca10040_s132’ in configuration ‘Debug’
  Compiling ‘retarget.c’
    conflicting types for '__putchar'
    retarget.c
    previous declaration of '__putchar' was here
Build failed

After trying to work around that, I'm getting an error for:

UART started.
<info> app: Debug logging for UART over RTT started.
<error> app: ERROR 2 [NRF_ERROR_SOFTDEVICE_NOT_ENABLED] at C:\Sandbox\...

Is this example a good one to use?  I'm using SES and board PCA10040, not sure why this is giving me issues when I haven't made any changes to it.

[haakonsh]

The examples should all compile out of the box. Most likely you've inadvertently  made changes to the SDK libraries/drivers, folder structure, or the sdk_config.h file included in the example. It could also be a path issue in windows because it only supports 256 character long paths. 

Either way I suggest you download a new SDK 15.2 and place it as close to the c:/ disk root as possible, and then try to compile the ble_app_uart example.