ESB, Radio Test: Add support for new 4Mbit mode configurations

[maje-emb]

Adds support for new 4Mbit PHY configurations including
RADIO_MODE_MODE_Nrf_4Mbit_0BT6 and RADIO_MODE_MODE_Nrf_4Mbit_0BT4.

[NordicBuilder]

CI Information

^{To view the history of this post, clich the 'edited' button above}
Build number: 7

Inputs:

Sources:

sdk-nrf: PR head: 268762e585394ac8c2e4039340ab05a22693540f

more details

sdk-nrf:

PR head: 268762e585394ac8c2e4039340ab05a22693540f
merge base: 858a047e118aac8a330b86896272f0c0d77d88ef
target head (main): 678514e395cf54968863bdbe878aa1314856c69b
Diff

Github labels

Enabled	Name	Description
	ci-disabled	Disable the ci execution
	ci-all-test	Run all of ci, no test spec filtering will be done
	ci-force-downstream	Force execution of downstream even if twister fails
	ci-run-twister	Force run twister
	ci-run-zephyr-twister	Force run zephyr twister

List of changed files detected by CI (4)

include
│  │ esb.h
samples
│  ├── peripheral
│  │  ├── radio_test
│  │  │  ├── src
│  │  │  │  ├── radio_cmd.c
│  │  │  │  │ radio_test.c
subsys
│  ├── esb
│  │  │ esb.c

Outputs:

Toolchain

Version: 9583beca34
Build docker image: docker-dtr.nordicsemi.no/sw-production/ncs-build:9583beca34_81ed5a52d6

Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped; ⚠️ Quarantine

• ◻️ Toolchain - Skipped: existing toolchain is used
• ✅ Build twister
  • sdk-nrf test count: 75
• ✅ Integration tests
  • ✅ test-fw-nrfconnect-ble_samples
  • ✅ test-fw-nrfconnect-proprietary_esb

Disabled integration tests

• • desktop52_verification
  • doc-internal
  • test_ble_nrf_config
  • test-fw-nrfconnect-apps
  • test-fw-nrfconnect-ble_mesh
  • test-fw-nrfconnect-boot
  • test-fw-nrfconnect-chip
  • test-fw-nrfconnect-fem
  • test-fw-nrfconnect-nfc
  • test-fw-nrfconnect-nrf-iot_cloud
  • test-fw-nrfconnect-nrf-iot_libmodem-nrf
  • test-fw-nrfconnect-nrf-iot_lwm2m
  • test-fw-nrfconnect-nrf-iot_mosh
  • test-fw-nrfconnect-nrf-iot_nrf_provisioning
  • test-fw-nrfconnect-nrf-iot_positioning
  • test-fw-nrfconnect-nrf-iot_samples
  • test-fw-nrfconnect-nrf-iot_serial_lte_modem
  • test-fw-nrfconnect-nrf-iot_thingy91
  • test-fw-nrfconnect-nrf-iot_zephyr_lwm2m
  • test-fw-nrfconnect-nrf_crypto
  • test-fw-nrfconnect-ps
  • test-fw-nrfconnect-rpc
  • test-fw-nrfconnect-rs
  • test-fw-nrfconnect-tfm
  • test-fw-nrfconnect-thread
  • test-fw-nrfconnect-zigbee
  • test-low-level
  • test-sdk-audio
  • test-sdk-dfu
  • test-sdk-find-my
  • test-sdk-mcuboot
  • test-sdk-pmic-samples
  • test-sdk-sidewalk
  • test-sdk-wifi
  • test-secdom-samples-public

Note: This message is automatically posted and updated by the CI

[NordicBuilder]

You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds.

Note: This comment is automatically posted by the Documentation Publishing GitHub Action.

[stephen-nordic]

We have a test PR to add this to CI, and would appreciate if you could rebase with latest sdk-nrf main, since this branch is out of date 🙂 https://projecttools.nordicsemi.no/bitbucket/projects/NCS-TEST/repos/test-fw-nrfconnect-proprietary/pull-requests/77/overview

[doki-nordic]

Those two #if defined conditions defines single enum item with a different value. Are the conditions always mutually exclusive?

[maje-emb]

RADIO_MODE_MODE_Nrf_4Mbit0_5 exists for the nRF54H20, while RADIO_MODE_MODE_Nrf_4Mbit_0BT6 exists for the nRF54L15.