Failing to advertise Nordic UART Service

RE: Failing to advertise Nordic UART Service

Ulrich Myhre — Mon, 15 Jun 2015 11:54:15 GMT

I see you got your response, but I just want to add that BLE_UUID_TYPE_VENDOR_BEGIN is the index of the first vendor-specific UUID you add. Consecutive VS-UUIDs added will continue to count upwards from this number. If you want to send a request, or receive a response with one of the VS-UUIDs you added, the stack will set the type to the value you got earlier. This means you need to store the ID you got from the stack somewhere if you want to know which VS-UUID this response contained.

RE: Failing to advertise Nordic UART Service

la-ble — Mon, 15 Jun 2015 03:26:41 GMT

@RK Thank you. I've updated the OP to only put the uuids in the scan response instead. I'm able to advertise now, just not able to see TX or RX logs with the mobile app (basically advertises just doesn't work with example app).

RE: Failing to advertise Nordic UART Service

RK — Mon, 15 Jun 2015 03:09:02 GMT

The macro calls a macro which eventually calls an error handling function, normally app_error_handler, which either you defined yourself or a default implementation was used. Put the breakpoint there. Alternatively since the app_error_handler() just spins in a busy loop, hit 'break' and look at the stack trace, it should show how you got there and somewhere have the error code.

Either way it's going to be data too large, you can't fit a 16 byte UUID + more than a small-sized name + the flags into a 31 byte ad packet. Go stuff it in the scan response instead, or use a very short name.

It is rather annoying that when you have to use custom service UUIDs you're very restricted to one, and at the outside 2, in the ad data, and only if you remove just about everything else.

RE: Failing to advertise Nordic UART Service

la-ble — Mon, 15 Jun 2015 02:01:46 GMT

Thank you for the debugging advice. I am not able to put a breakpoint in APP_ERROR_CHECK (it's a macro that gets repeated inline many places). I am also not able to put a breakpoint in assert_nrf_callback even if I define DEBUG macro in the project settings and am sure to compile with optimization level 0. How do you place your breakpoint? Example project is still very unreliable even with a one character name on an nrf51822_xxAA.

RE: Failing to advertise Nordic UART Service

RK — Sun, 14 Jun 2015 05:21:24 GMT

I just answered a very similar question - devzone.nordicsemi.com/.../

and the firmware doesn't 'seem to crash', I'm quite sure the ble_advdata_set() returns an error code and the APP_ERROR_CHECK() then sends you to the error handler, in which you should always put a breakpoint, or when nothing happened hit 'break' in the debugger to see where you were, and that would have pointed to the line of code which generated the error.