Searched +full:- +full:babblesim (Results 1 – 25 of 66) sorted by relevance
123
| /Zephyr-latest/ |
| D | west.yml | 3 # The per-installation west configuration file, .west/config, sets the
22 - name: upstream
23 url-base: https://github.com/zephyrproject-rtos
24 - name: babblesim
25 url-base: https://github.com/BabbleSim
27 group-filter: [-babblesim, -optional]
31 # zephyr-keep-sorted-start re(^\s+\- name:)
33 - name: acpica
36 - name: babblesim_base
37 remote: babblesim
[all …]
|
| /Zephyr-latest/boards/native/nrf_bsim/doc/ |
| D | nrf52_bsim.rst | 3 NRF52 simulated board (BabbleSim)
18 This uses `BabbleSim`_ to simulate the radio activity, and the
34 * NVMC (Non-Volatile Memory Controller / Flash)
49 https://BabbleSim.github.io
52 https://github.com/BabbleSim/native_simulator/blob/main/docs/README.md
55 https://github.com/BabbleSim/ext_nRF_hw_models/blob/main/docs/README_impl_status.md
65 To target this board you also need to have `BabbleSim`_ compiled in your system.
66 If you do not have it yet, the easiest way to get it, is to enable the babblesim group
69 .. code-block:: console
71 west config manifest.group-filter -- +babblesim
[all …]
|
| D | nrf54l15bsim.rst | 3 NRF54L15 simulated boards (BabbleSim)
18 This uses `BabbleSim`_ to simulate the radio activity, and the
48 * GRTC (Global Real-time Counter)
63 https://BabbleSim.github.io
66 https://github.com/BabbleSim/native_simulator/blob/main/docs/README.md
69 https://github.com/BabbleSim/ext_nRF_hw_models/blob/main/docs/README_impl_status.md
79 TrustZone, TF-M and other security considerations
88 and non-secure images.
91 * TF-M cannot be used.
95 As entropy driver, the :dtcompatible:`zephyr,native-posix-rng` is enabled by default.
|
| D | nrf5340bsim.rst | 3 NRF5340 simulated boards (BabbleSim)
18 These use `BabbleSim`_ to simulate the radio activity, and the
40 * NVMC (Non-Volatile Memory Controller / Flash)
57 https://BabbleSim.github.io
60 https://github.com/BabbleSim/native_simulator/blob/main/docs/README.md
63 https://github.com/BabbleSim/ext_nRF_hw_models/blob/main/docs/README_impl_status.md
77 Unlike in real HW, the net core MCU is set-up to automatically boot at start, to facilitate
80 option ``--cpu1_autostart``.
110 TrustZone, TF-M and other security considerations
119 and non-secure images.
[all …]
|
| /Zephyr-latest/boards/native/nrf_bsim/ |
| D | Kconfig | 2 # SPDX-License-Identifier: Apache-2.0
13 It needs the BabbleSim simulator both in compile time and to execute
24 It needs the BabbleSim simulator both in compile time and to execute
35 It needs the BabbleSim simulator both in compile time and to execute
46 It needs the BabbleSim simulator both in compile time and to execute
63 # which use BabbleSim. When that happens, we can move this to a common
74 Any NRF simulated SOC with BabbleSim, based on the POSIX arch
81 Any NRF52 simulated SOC with BabbleSim, based on the POSIX arch
88 Any NRF53 simulated SOC with BabbleSim, based on the POSIX arch
95 Any NRF54L simulated SOC with BabbleSim, based on the POSIX arch
|
| D | board.yml | 2 - name: nrf52_bsim
3 full_name: nRF52 simulated board (BabbleSim)
6 - name: native
7 - name: nrf5340bsim
8 full_name: nRF5340 simulated boards (BabbleSim)
11 - name: nrf5340
12 - name: nrf54l15bsim
13 full_name: nRF54L15 simulated boards (BabbleSim)
16 - name: nrf54l15
17 # Note the 53 and 54 are referring to the real SOC yamls, but we only use their name and cpu-cluster
|
| D | nrf52_bsim.yaml | 2 name: NRF52 BabbleSim board
6 - name: native
8 - BSIM_OUT_PATH
10 - zephyr
13 - modem
14 - bsim_skip_CI
16 - gpio
17 - counter
|
| D | nrf5340bsim_nrf5340_cpuapp.yaml | 2 name: NRF53 BabbleSim - Application Core target
6 - name: native
8 - BSIM_OUT_PATH
10 - zephyr
13 - modem
14 - bsim_skip_CI
16 - gpio
|
| D | nrf5340bsim_nrf5340_cpunet.yaml | 2 name: NRF53 Net Core BabbleSim board
6 - name: native
8 - BSIM_OUT_PATH
10 - zephyr
13 - modem
14 - bsim_skip_CI
16 - gpio
|
| D | nrf54l15bsim_nrf54l15_cpuapp.yaml | 2 name: NRF54L15 BabbleSim - Application Core target
6 - name: native
8 - BSIM_OUT_PATH
10 - zephyr
12 - counter
13 - gpio
16 - modem
17 - bsim_skip_CI
|
| /Zephyr-latest/cmake/modules/ |
| D | FindBabbleSim.cmake | 2 # SPDX-License-Identifier: Apache-2.0
4 # FindBabbleSim module for locating BabbleSim
9 # Path to the BabbleSim components source folder
12 # Path to the BabbleSim build output root path (under which libraries and binaries) are kept
16 # fetched babblesim using the manifest.
19 # If BabbleSim cannot be found we error right away with a message trying to guide users
32 list babblesim_base -f {posixpath}
46 message(FATAL_ERROR "This board requires the BabbleSim simulator. Please either\n\
47 a) Enable the west babblesim group with\n\
48 west config manifest.group-filter +babblesim && west update\n\
[all …]
|
| /Zephyr-latest/.github/workflows/ |
| D | bsim-tests-publish.yaml | 1 name: Publish BabbleSim Tests Results
5 workflows: ["BabbleSim Tests"]
7 - completed
9 bsim-test-results:
10 name: "Publish BabbleSim Test Results"
11 runs-on: ubuntu-22.04
15 - name: Download artifacts
16 uses: dawidd6/action-download-artifact@v6
20 - name: Publish BabbleSim Test Results
21 uses: EnricoMi/publish-unit-test-result-action@v2
[all …]
|
| /Zephyr-latest/tests/bsim/bluetooth/host/misc/sample_test/ |
| D | README.rst | 3 Bluetooth: Example BabbleSim test
9 This test's purpose is to serve as template for implementing a new BabbleSim Bluetooth test.
16 test library, in order to de-duplicate code that is not relevant to the test in question. Things
20 namespace the babblesim simulator code.
34 https://BabbleSim.github.io
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/ |
| D | README.rst | 1 Bluetooth Mesh BabbleSim tests
5 subsystem. The tests run on the BabbleSim simulator, using the BabbleSim test
13 There's only a single test application for all the Bluetooth Mesh BabbleSim
37 device number with -dXXX to the process.
42 ..code-block::
51 ...code-block::
54 -s=mesh_transport_seg_block -d=0 -RealEncryption=1 \
55 -testid=transport_tx_seg_block
60 The Bluetooth Mesh BabbleSim tests mainly operate on the test framework for the
61 BabbleSim platform, but with some mesh specific additions:
[all …]
|
| /Zephyr-latest/doc/develop/test/ |
| D | bsim.rst | 3 BabbleSim chapter
6 BabbleSim and Zephyr
9 In the Zephyr project we use the `Babblesim`_ simulator to test some of the Zephyr radio protocols,
18 When there is radio activity, this Linux executable will connect to the BabbleSim Phy simulation
21 In the BabbleSim documentation you can find more information on how to
22 `get <https://babblesim.github.io/fetching.html>`_ and
23 `build <https://babblesim.github.io/building.html>`_ the simulator.
43 When there is radio activity, BabbleSim tests require at the very least a physical layer simulation
65 More information about how different tests types relate to BabbleSim and the bsim boards can be
68 Test coverage and BabbleSim
[all …]
|
| /Zephyr-latest/tests/bsim/bluetooth/host/gatt/sc_indicate/ |
| D | CMakeLists.txt | 1 # SPDX-License-Identifier: Apache-2.0
6 message(FATAL_ERROR "This test requires the BabbleSim simulator. Please set \
9 https://babblesim.github.io/folder_structure_and_env.html")
|
| /Zephyr-latest/tests/bsim/bluetooth/ll/cis/ |
| D | CMakeLists.txt | 1 # SPDX-License-Identifier: Apache-2.0
6 message(FATAL_ERROR "This test requires the BabbleSim simulator. Please set\
9 https://babblesim.github.io/folder_structure_and_env.html")
|
| /Zephyr-latest/tests/bsim/bluetooth/host/gatt/ccc_store/ |
| D | CMakeLists.txt | 1 # SPDX-License-Identifier: Apache-2.0
6 message(FATAL_ERROR "This test requires the BabbleSim simulator. Please set \
9 https://babblesim.github.io/folder_structure_and_env.html")
|
| /Zephyr-latest/tests/bsim/bluetooth/host/security/ccc_update/ |
| D | CMakeLists.txt | 1 # SPDX-License-Identifier: Apache-2.0
6 message(FATAL_ERROR "This test requires the BabbleSim simulator. Please set \
9 https://babblesim.github.io/folder_structure_and_env.html")
|
| /Zephyr-latest/tests/bsim/bluetooth/ll/edtt/ |
| D | README.txt | 32 `installed BabbleSim <https://babblesim.github.io/fetching.html>`_.
49 hand the BabbleSim 2G4 Phy, EDTT bridge, EDTT and needed simulated devices.
54 cd ${ZEPHYR_BASE} && source zephyr-env.sh
|
| /Zephyr-latest/boards/native/doc/ |
| D | bsim_boards_design.rst | 29 https://BabbleSim.github.io
35 https://babblesim.github.io/arch_hw_models.html
38 https://github.com/BabbleSim/native_simulator/blob/main/docs/README.md
41 https://github.com/BabbleSim/native_simulator/blob/main/docs/Design.md
44 https://github.com/BabbleSim/ext_nRF_hw_models/blob/main/docs/README_HW_models.md
50 The main purpose of these bsim boards is to be test-benches for
80 - Unit tests:
85 - Integration tests on real HW: Allows testing with the real SW
93 - Integration tests on workstation (what the POSIX arch and these boards enable)
95 - Using bsim boards: Allow testing the embedded SW (or a subset), including
[all …]
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-dev.rst | 1 .. _bluetooth-dev:
26 .. _bluetooth-hw-setup:
38 #. :ref:`Embedded <bluetooth-hw-setup-embedded>`
39 #. :ref:`External controller <bluetooth-hw-setup-external-ll>`
41 - :ref:`QEMU host <bluetooth-hw-setup-qemu-host>`
42 - :ref:`native_sim host <bluetooth-hw-setup-native-sim-host>`
44 #. :ref:`Simulated nRF5x with BabbleSim <bluetooth-hw-setup-bsim>`
46 .. _bluetooth-hw-setup-embedded:
53 All the :ref:`bluetooth-configs` and :ref:`bluetooth-build-types` are supported
54 but you might need to build Zephyr more than once if you are using a dual-chip
[all …]
|
| /Zephyr-latest/tests/bsim/babblekit/include/babblekit/ |
| D | device.h | 4 * SPDX-License-Identifier: Apache-2.0
13 * This returns the device's number in the BabbleSim simulation.
14 * Ie will return 1 if the device was started with the "-d 1" argument.
|
| /Zephyr-latest/tests/bsim/bluetooth/host/scan/start_stop/ |
| D | CMakeLists.txt | 1 # SPDX-License-Identifier: Apache-2.0
12 # This contains babblesim-specific helpers, e.g. device synchronization.
|
| /Zephyr-latest/tests/bsim/bluetooth/host/adv/long_ad/ |
| D | CMakeLists.txt | 1 # SPDX-License-Identifier: Apache-2.0
9 # This contains babblesim-specific helpers, e.g. device synchronization.
|
123
