data size in PAwR slot response

RE: data size in PAwR slot response

longrain — Fri, 13 Jun 2025 02:38:52 GMT

[quote userid="75669" url="~/f/nordic-q-a/122209/data-size-in-pawr-slot-response/538989"]coded PHY maybe need more time.[/quote]

Try adjust the response_slot_delay

Yanis — Thu, 12 Jun 2025 12:48:06 GMT

When I put a buffer > 55 bytes I also get this error on the advertiser side

ASSERTION FAIL [z_spin_lock_valid(l)] @ WEST_TOPDIR/zephyr/include/zephyr/spinlock.h:136<CR><LF>
<HT> Invalid spinlock 0x20000b80<CR><LF>

And the sync is lost.

Yanis — Thu, 12 Jun 2025 10:18:13 GMT

I am not sure if I understand, are you saying that coded PHY could be the limitation ?

In the code you have sent me, I don't think you are sending 200 bytes when you set :

net_buf_simple_add_mem(&rsp_buf, buf->data, buf->len);

it seems that you are returning the counter you received which is 1 or 2 bytes.

In my case I have :

net_buf_simple_add_mem(&rsp_buf, buffer, ARRAY_SIZE(buffer));

where "buffer" is declared as :

static uint8_t buffer[60] = {0x00};

longrain — Thu, 12 Jun 2025 09:58:48 GMT

Sorry,I misunderstand your error info.

I have test :it is OK to send long packet in NCS 2.9 and NCS 3.0,coded PHY maybe need more time.

I upload a test sample test in NCS 3.0.x with 54L,send over 200 bytes both direction.

Check if it can help

Yanis — Thu, 12 Jun 2025 08:48:57 GMT

When I set the following, it does not solve the problem :

CONFIG_BT_PER_ADV=y

CONFIG_BT_PER_ADV_RSP=y

CONFIG_BT_CTLR_SDC_PAWR_ADV=y

CONFIG_BT_CTLR_SDC_PERIODIC_ADV_RSP_TX_MAX_DATA_SIZE=245

CONFIG_BT_PER_ADV_SYNC_BUF_SIZE=245

still getting the error :

<wrn> bt_hci_core: opcode 0x2083 status 0x45\033[0m
<dbg> beacon: recv_cb: Failed to send response (err -5)

longrain — Thu, 12 Jun 2025 01:28:04 GMT

take a look at

CONFIG_BT_CTLR_SDC_PERIODIC_ADV_RSP_TX_MAX_DATA_SIZE

CONFIG_BT_PER_ADV_SYNC_BUF_SIZE