15.3.0 NUS based on 13.1.0 BLE android application VUS

[tommy.lane]

Does anyone have experience in porting both embedded and android code from the 13.1.0 SDK to 15.x.x?

I'm running into an issue where the system worked fine on 13.1.0, but doesn't get the nrf's reply's. It would seem that notifications are disabled for the characteristics but, I can't find a quick path forward on this issue. 

I had to change this:

//#define BLE_UUID_NUS_TX_CHARACTERISTIC 0x0003 /**< The UUID of the TX Characteristic. */
//#define BLE_UUID_NUS_RX_CHARACTERISTIC 0x0002 /**< The UUID of the RX Characteristic. */
#define BLE_UUID_NUS_TX_CHARACTERISTIC 0x0F11 /**< The UUID of the TX Characteristic. */
#define BLE_UUID_NUS_RX_CHARACTERISTIC 0x0F12 /**< The UUID of the RX Characteristic. *

and the base service uuid to 0x0f10 for the device to even show up in our application.

Any ideas would be greatly appreciated!

[Vidar Berg]

Hi,

You shouldn't have to port anything on the Android side if the new FW include the same services. Unless the Android app is relying on hardcoded attribute handles. The attribute handles will become different with the new Softdevice, so a new service discovery is required. My suggestion is to try and verify the functionality of the new 52 FW with the nRF connect app on Android first. 

[tommy.lane]

I'm confused as to how the nrfConnect application can help me here. How would I get to the point where I could interrogate the device?

[awneil]

nRF Connect can connect to the device, discover Services & Characteristics, and then lets you read & write Characteristics, receive Notifications, etc ...

[tommy.lane]

When I connect to the device it lists the services, but doesn't allow me to interact with any of them. Does this mean something on the embedded platform exhibits unexpected behavior?

[Vidar Berg]

The point of testing with nRF connect app first was to find out if the 52 FW works as intended without your custom app. Did you try nRF connect with the old FW as well?