Questions for nrf connect SDK

[loquat]

I'm planning on using the nrf connect SDK.
And I plan to use the SoftDevice controller. (I want to use TimeSlotAPI)

I have a few questions.

1. Do you have a list of available devices? (TIMER/RTC/PPI etc.)

2. Can I use own-library using TimeSlotAPI implemented for nRF5 SDK as it is?

3.Can use AdvertiseSet? and How many sets can use?

4.Can use Periodic Advertising(with CTE)?

5. If (3.) is yes, How many sets can use Periodic Advertising Send?

6. If (3.) is yes, How many sets can use Periodic Advertising Receive?(CONFIG_BT_PER_ADV_SYNC_MAX=64?)

[Einar Thorsrud]

Hi,

The Timeslot API is provided by the MSL, which sits below the SoftDevice Controller (so when you are using the SoftDevice Controller, you are also using MPSL).

1. Do you have a list of available devices? (TIMER/RTC/PPI etc.)

See the Timeslot API documentation, which lists the resources that are normally used by the SoftDevice Controller and MPSL, but is available in a timeslot:

When a Timeslot request is granted, the application has exclusive and real-time access to the following peripherals:

• TIMER0
• TIMER1 for the nRF53 Series
• RADIO
• TEMP
• PPI channel 19 for the nRF52 Series
• Other peripherals used by protocol stacks using the MPSL

These peripherals can be used freely for the duration (length) of the timeslot.

2. Can I use own-library using TimeSlotAPI implemented for nRF5 SDK as it is?

Not as is, it needs to be ported. But the API and features provided by the MPSL is similar. You can refer to the MPSL timeslot sample to see how.

3.Can use AdvertiseSet? and How many sets can use?

Yes, you can use multiple advertising sets. See the Bluetooth: Multiple advertising sets sample. You can have up to 64 advertising sets.

4.Can use Periodic Advertising(with CTE)?

Yes. There are several periodic advertising samples under Zephyr Bluetooth samples.

5. If (3.) is yes, How many sets can use Periodic Advertising Send?

The maximum number of periodic advertisers is 64 (you may quickly run into practical limitations long before, though).

6. If (3.) is yes, How many sets can use Periodic Advertising Receive?(CONFIG_BT_PER_ADV_SYNC_MAX=64?)

64 is the theoretical maximum, yes. The practical maximum depends on available time on air, memory usage, CPU usage etc, and is application dependent.

[loquat]

LegacySoftDevice uses RNG/ECB/TIMER0/RTC0 in addition to RADIO and was not available in apps.
Also, nRF5 SDK/FreeRTOS used RTC1.
Similarly, ZephyrOS expects to use RTC1.
In addition, I would like to know the device used by the OS.

And,
I found the following comment in the nrf connect SDK documentation.

what does this mean?

For Periodic Advertising Sync Transfer - 
Receiver, the support is experimental, and only one sync transfer reception
may be in progress at any one time per link.
After using LE HCI Set Default Periodic Advertising Sync Transfer Parameters,
there must be a periodic sync available for every new connection established.

[Einar Thorsrud]

Hi,

loquat said:

LegacySoftDevice uses RNG/ECB/TIMER0/RTC0 in addition to RADIO and was not available in apps.

Yes, that is correct. But in a timeslot, all of these except RTC0 would be available back then, so this is basically the same with the SoftDevice controller and MPSL in the nRF Connect SDK as it was with the old SoftDevices.

loquat said:

Also, nRF5 SDK/FreeRTOS used RTC1.
Similarly, ZephyrOS expects to use RTC1.
In addition, I would like to know the device used by the OS.

Generally, that depends on the configuration (Zephyr is large and support logging etc, so you could argue that if enabled, a UART instance is also used by Zephyr, etc). But the main thing is an RTC, yes.

loquat said:

I found the following comment in the nrf connect SDK documentation.

what does this mean?

This is from the nightly build of the SoftDevice Controller release notes. I don't have much to add, really. Can you elaborate on what it is you need explanation about? Generally Periodic Advertising Sync Transfer support is currently being worked on though, and it continues to be experimental for now.

PS: Please make separate cases for separate topics going forward.

[loquat]

sorry.

I didn't understand Periodic Advertising Sync Transfer.

Thank you.