nrf54l15-dk use ESL

[dede]

Hi,Team,

I am developing Pawr using nrf54l15-dk.

For the Pawr  example I refer to E:\NCS\v2.8.0\zephyr\samples\bluetooth\periodic_adv_rsp and periodic_sync_rsp.

I want to implement pawr one-to-many communication in the periodic_adv_rsp example and for the AP to specify a tag to subscribe to subevents. I refer to the file nrf-esl-bluetooth ( https://github.com/NordicPlayground/nrf-esl-bluetooth/tree/v2.5-branch), but nrf-esl-bluetooth contains so many files that I don't know which ones to refer to.

What should I do?

Thanks.

[Kenneth]

Hello,

If you haven't already I recommend to get a bit familiar with nRF Connect SDK (NCS) and BLE development by following:
https://academy.nordicsemi.com/ 

In specific these two may be a good start:
https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/ 
https://academy.nordicsemi.com/courses/bluetooth-low-energy-fundamentals/ 

That should give you much better confidence to play around with the PAWR examples:
https://docs.nordicsemi.com/bundle/ncs-2.9.1/page/zephyr/samples/bluetooth/periodic_adv_rsp/README.html#ble_periodic_adv_rsp 
https://docs.nordicsemi.com/bundle/ncs-2.9.1/page/zephyr/samples/bluetooth/periodic_sync_rsp/README.html#ble_periodic_adv_sync_rsp 

The ESL example have not been updated since NCS v2.5.x, which means it doesn't support the new nRF54L15. If you want to use PAWR you should instead look at the above examples.

Kenneth

[Lorenzo Amicucci]

we actually added experimental support of nRF54L15DK in this branch for BT ESL. Waiting SDK 3.0 or later releases for complete support  
https://github.com/NordicPlayground/nrf-esl-bluetooth/tree/v2.8-branch 

Please also note this blog on PAwR to get started with simple example: Periodic Advertising with Responses (PAwR): A practical guide  

Note: using PAST procedure, your tag can sync to the Central. However, then you need some application logics to tell which tags should sync to which subevent. In BT ESL, this is done based on the ESL Address (Group ID + ESL ID). These are upper layer logics, you can decide if you start from zero.

We have training on BT ESL Here (see youtube link in this blog):
 Getting started with Bluetooth Electronic Shelf Labels (ESL) and Periodic Advertising with Responses (PAwR) 

since you are in China, we have link also in Bilibili:

In Chinese language : https://www.bilibili.com/video/BV11u4y1r7NF/?spm_id_from=333.1387.search.video_card.click 

and BT ESL Tutorials (same as youtube video mentioned above in the getting started blog):
part 1 https://www.bilibili.com/video/BV12BsZe8Euk/?spm_id_from=333.1387.search.video_card.click 
part 2 https://www.bilibili.com/video/BV1PksZeoEAy/?spm_id_from=333.1387.search.video_card.click 
part 3 https://www.bilibili.com/video/BV1PrsZetECk/?spm_id_from=333.1387.search.video_card.click 

[dede]

Hi,

I have learned ESL related knowledge, but it seems more complicated, it may be more difficult to achieve.

So far I have implemented communication using AP and two tags, but I don't know how to control the AP to communicate with the specified tags. Maybe I should change the code in the periodic_adv_rsp example, but I don't know how.

Maybe I should change "request_cb"(NCS\v2.8.0\zephyr\samples\bluetooth\periodic_adv_rsp). Can you provide a simple example?

static void request_cb(struct bt_le_ext_adv *adv, const struct bt_le_per_adv_data_request *request)
{
	int err;
	uint8_t to_send;
	struct net_buf_simple *buf;

	to_send = MIN(request->count, ARRAY_SIZE(subevent_data_params));

	for (size_t i = 0; i < to_send; i++) {
		buf = &bufs[i];
		buf->data[buf->len - 1] = counter++;

		subevent_data_params[i].subevent =
			(request->start + i) % per_adv_params.num_subevents;
		subevent_data_params[i].response_slot_start = 0;
		subevent_data_params[i].response_slot_count = NUM_RSP_SLOTS;
		subevent_data_params[i].data = buf;
	}

	err = bt_le_per_adv_set_subevent_data(adv, to_send, subevent_data_params);
	if (err) {
		printk("Failed to set subevent data (err %d)\n", err);
	} else {
		printk("Subevent data set %d\n", counter);
	}
}

Thanks.