Serialization Function packet format for nRF5 SDK v15.2.0

[gokul]

Hi,

Am working on serialization where we have already developed code using nRF5 SDK v11.0.0 but now we started to use nRF5 SDK v15.2.0 SDK.

My problem is am getting the response for some function which I can frame through terminal but i need to generate event using new SDK is there  Function packet format for nRF5 SDK v15.2.0 ?

If not there may I know the alternative to advertise and get the event?

here is the  nRF5 SDK v11.0.0 link for BLE S13x GAP Functions

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.s132.api.v2.0.0%2Fstructble__gap__adv__params__t.html&anchor=ae87243568d5b9a272a15df0cd4673cdb

Software Development Kit > Previous versions of nRF5 SDK > nRF5 SDK v11.0.0 > Libraries > BLE serialization > Serialization Codecs> SoftDevice S13x > BLE S13x GAP Functions

Please provide such documentation for  nRF5 SDK v15.2.0 SDK.

[Hung Bui]

Hi,

You can find the documentation about the serialization protocol here: https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/lib_serialization.html?cp=5_1_3_42

If you are doing UART you can find the explanation and raw value break down here. 

You can find the function ID (for example SD_BLE_CFG_SET = 0x69) in the code of in the softdevice header file. 

[gokul]

hi , 

am asking about BLE S13x GAP Functions format for sdk 15.02  check this link infocenter.nordicsemi.com/.../ble_serialization_s130_functions_gap.html

[gokul]

for example 

0x73 - sd_ble_gap_adv_start  

frame format is needed for sdk 15.02 there is no documentation like sdk 11

[gokul]

I know the function ID by code, I just want to know the whole frame format for that ID, I want to advertise using command ID directly instead of using application board through uart command for serialization. May i know the frame format and flow for sending command ids?

[Hung Bui]

The frame format is explained here: https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.3.0/serialization_codecs.html?cp=5_1_3_42_2

You can find it at General rules for encoding data.

Please be aware that you still need to initialize the stack before you can ask the connectivity chip to start advertising. I would suggest to try with the example we have in the SDK and capture a logic analyzer trace of the UART communication. You will have a closer look at the communication between the chips.