Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bluetooth: services: ras: Add RREQ implementation to RAS #2

Conversation

sean-madigan
Copy link

Add implementation for Ranging Requestor, a Ranging Service client which can be used to obtain channel sounding ranging data from a Ranging Responder which operates as a Ranging Service server.

This current implementation can perform most mandatory features from the Ranging Profile/Ranging Service
specifications to alert an application of available ranging data and receive the data from the server.

Further work can be done to add support for reading the features from the server, receiving real time ranging data, aborting receive operation, adding filters for ranging data.

NordicBuilder and others added 30 commits November 4, 2024 15:54
Automatically created by Github Action

Signed-off-by: Nordic Builder <[email protected]>
Add info about ZMS in the migration guide.

Signed-off-by: divya pillai <[email protected]>
Automatically created by Github Action

Signed-off-by: Nordic Builder <[email protected]>
RTT is used for interacting with the distributor over shell. Having it
enabled in mcuboot will require a user to manually provide correct
_SEGGER_RTT address otherwise RTT Viewer will pick wrong buffer and
shell will not work.

Signed-off-by: Pavel Vasilyev <[email protected]>
This option is not enabled by default and apparently not enabled through
some other Kconfig options on nRF54L15. Enabling it explicitly to avoid
misconfiguration of the sample.

Signed-off-by: Pavel Vasilyev <[email protected]>
Change warning to debug log when unregistration (AT+CNMI=0,0,0,0) fails
as SMS might have been unregistered due to AT+CFUN=0,
or through AT+CNMI=0,0,0,0.

Jira: NRF91-2238

Signed-off-by: Tommi Rantanen <[email protected]>
Updated GNSS factory almanacs.

Signed-off-by: Tommi Kangas <[email protected]>
Make the MbedTLS threading configuration to depend on
the multithreading Kconfig option. The multithreading
configuration is required by both the PSA crypto
implementation which uses the Zephyr mutexes and
also by the MbedTLS legacy implementation which
may not use Zephyr mutexes for CC3XX.

Signed-off-by: Georgios Vasilakis <[email protected]>
Add clang-format switches in SUIT storage tests.

Ref: NCSDK-29626

Signed-off-by: Tomasz Chyrowicz <[email protected]>
Add tests that verify per-domain SUIT storage purge API.

Ref: NCSDK-29626

Signed-off-by: Tomasz Chyrowicz <[email protected]>
...and ot_rpc_netdata.c

1. Implement missing unit tests for OT API serialization
   implemented in ot_rpc_diag.c and ot_rpc_netdata.c
2. Fix discovered bugs.

Signed-off-by: Damian Krolik <[email protected]>
Improvements to the duration and interrupt latency when writing
to RRAM.

Signed-off-by: Tomi Fontanilles <[email protected]>
Updates to Crypto API maturity table

Signed-off-by: Mia Koen <[email protected]>
The APPCORE_REMOTE_SHELL option is selected by default only for
multicore devices. It is pointless to select this option for single
core devices.

Signed-off-by: Andrzej Kuros <[email protected]>
The app_rpc.c code need to be aware of CONFIG_SOC_NRF54H20_ENGB_CPURAD.

Signed-off-by: Andrzej Kuros <[email protected]>
The `np.float` was removed (it was a deprecated alias for `float`).

Signed-off-by: Marek Pieta <[email protected]>
Change documents CONFIG_DESKTOP_HID_FORWARD_SUBSCRIBER_COUNT Kconfig
option.

Jira: NCSDK-30002

Signed-off-by: Marek Pieta <[email protected]>
Signed-off-by: Pekka Niskanen <[email protected]>
Pulls in a fix for decompression

Signed-off-by: Jamie McCrae <[email protected]>
This test uses P7 for UARTE120 instance

Signed-off-by: Bartosz Miller <[email protected]>
Change introduces documentation for the HID report queue utility.

Jira: NCSDK-28433

Signed-off-by: Marek Pieta <[email protected]>
Signed-off-by: Pekka Niskanen <[email protected]>
Change documents integrating `hid_report_subscriber_event` and HID
report queue utility. Commit contains also some small documentation
alignments.

Jira: NCSDK-28433

Signed-off-by: Marek Pieta <[email protected]>
Signed-off-by: Pekka Niskanen <[email protected]>
Automatically created by Github Action

Signed-off-by: Nordic Builder <[email protected]>
Added nRF connect SDK docker image.

Signed-off-by: divya pillai <[email protected]>
Automatically created by Github Action

Signed-off-by: Nordic Builder <[email protected]>
Now that we use upstream Zephyr fork for hostap, we need to document the
scope of features supported in NCS as it's only a subset of upstream
Zephyr.

Signed-off-by: Chaitanya Tata <[email protected]>
Do not use NRF_GPIOTE register as new platforms may have multiple
GPIOTE instances. Add support to a case when there are GPIO ports
which cannot work with GPIOTE. Pins from that ports cannot be used
for control pins in low power UART.

Signed-off-by: Krzysztof Chruściński <[email protected]>
Low power UART implements asynchronous UART API and uart_rx_enable
has timeout as one of the parameters. However, low power UART has
packets delimited by the control GPIO pin toggling so timeout here
does not make much sense and it is not expected that user will get
data when UART RX timeout occur (it is expected that data is
received when transmitter ends the packet by deasserting control pin.

Given that, timeout provided to the low power UART uart_rx_enable
call must not be used when underneath UART device is controlled.
Low power UART must open receiver without any timeout as reception
is terminated by the control pin deassertion.

Signed-off-by: Krzysztof Chruściński <[email protected]>
Remove enabling of rtc node. RTC node is not used in the sample.

Signed-off-by: Krzysztof Chruściński <[email protected]>
Clean prj.conf and move instance specific configuration to a board
specific conf file.

Signed-off-by: Krzysztof Chruściński <[email protected]>
Add configuration for nrf54l15dk//cpuapp target.

Signed-off-by: Krzysztof Chruściński <[email protected]>
@sean-madigan sean-madigan force-pushed the rreq_initial_implementation branch 3 times, most recently from 26918c4 to 312baac Compare November 11, 2024 13:02
NordicBuilder and others added 18 commits November 11, 2024 14:03
Automatically created by Github Action

Signed-off-by: Nordic Builder <[email protected]>
This is now handled by a SoC level "service".

Signed-off-by: Gerard Marull-Paretas <[email protected]>
Otherwise NRFS can't be disabled.

Signed-off-by: Gerard Marull-Paretas <[email protected]>
Due to missing integration platforms, 54 Series doesn't show in the
auto generated table in the README.

It was broken in 8ae6472 ("samples: wifi: shell: Update
nrf7002eb_interposer tests").

Signed-off-by: Chaitanya Tata <[email protected]>
there is a problem with nanoPb that needs to be resolved

Signed-off-by: Thomas Stilwell <[email protected]>
Make the PSA_NEED symbol for CTR_DRBG with CRACEN
to depend on the PSA_WANT_GENERATE_RANDOM since this
is what it used for.

Signed-off-by: Georgios Vasilakis <[email protected]>
Separate the builtin keys from the key management
driver since the builtin keys don't strictly require
the driver.

Signed-off-by: Georgios Vasilakis <[email protected]>
This makes the KMU driver more configurable in the
sense that it allows the encryption for KMU keys
to be optionally enabled based on the enabled
configurations.

Signed-off-by: Georgios Vasilakis <[email protected]>
Enable the option
PSA_NEED_CRACEN_KEY_TYPE_ECC_TWISTED_EDWARDS_255 when
the KMU driver is enabled since KMU supports storing
keys of this type.

Signed-off-by: Georgios Vasilakis <[email protected]>
The IKG in Cracen only supports one asymmetric key
type, the SECP256R1. This guards the function call
to the IKG with the relevant configuration. This is
important because the PSA signing APIs can be used
with algorithms like EDDSA which have lower footprint
so it can reduce the flash usage when ECDSA is not
needed.

Signed-off-by: Georgios Vasilakis <[email protected]>
…afety

region FLASH overflowed

Signed-off-by: Piotr Kosycarz <[email protected]>
Improve the text formatting and add "Configuration" and
"Reliability" sections. Also, remove the information that
nRF RPC IPC is used in BLE RPC library, as the latter can
now use both IPC and UART transports.

Signed-off-by: Damian Krolik <[email protected]>
Add a documentation page about OpenThread RPC.

Signed-off-by: Damian Krolik <[email protected]>
suit-generator with default ImageCreator adresses for nRF54H20 engC

Ref: NCSDK-30031

Signed-off-by: Krzysztof Szromek <[email protected]>
pip-compile-cross-platform==1.4.2+nordic2 fixes issues with
unnecessary updates of python packages when they are
available in PYPI.

Signed-off-by: Jan Gałda <[email protected]>
Order of input files matter in pip-compile-cross-platform.
The latter file has higher priority and overrides version of
package set in former file.

Signed-off-by: Jan Gałda <[email protected]>
items as per UX session

Signed-off-by: Anna Wojdylo <[email protected]>
Implement the ranging responder (RRSP) server role of the
Ranging Service draft specification.
This allows a ranging requestor (RREQ) to retrieve channel sounding
ranging data from the local device.

This implementation contains support for all mandatory features,
as well as using notifications for data transfer.

Signed-off-by: Aleksandar Stanoev <[email protected]>
@sean-madigan sean-madigan force-pushed the rreq_initial_implementation branch 4 times, most recently from c94bda9 to a6d7b4f Compare November 12, 2024 16:54
Add implementation for Ranging Requestor, a Ranging Service
client which can be used to obtain channel sounding ranging
data from a Ranging Responder which operates as a Ranging
Service server.

This current implementation can perform most mandatory
features from the Ranging Profile/Ranging Service
specifications to alert an application of available ranging
data and receive the data from the server.

Further work can be done to add support for reading the
features from the server, receiving real time ranging data,
aborting receive operation, adding filters for ranging data

Signed-off-by: Sean Madigan <[email protected]>
@sean-madigan sean-madigan force-pushed the rreq_initial_implementation branch from a6d7b4f to 3fcbceb Compare November 13, 2024 15:56
Copy link

This pull request has been marked as stale because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 7 days. Note, that you can always re-open a closed pull request at any time.

@github-actions github-actions bot added the Stale label Dec 14, 2024
@github-actions github-actions bot closed this Dec 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.