Home
last modified time | relevance | path

Searched refs:run (Results 1 – 25 of 777) sorted by relevance

12345678910>>...32

/Zephyr-Core-3.5.0/tests/drivers/build_all/sensor/
DKconfig5 bool "Compile and run the generic sensor tests"
9 iterate through the device tree and run sample path tests on any
19 range boundaries. The test will run one iteration for each expected
21 sensor range is 0..100, the test will run 5 times with expected values
22 0, 25, 50, 75, and 100. These iterations are run in parallel.
/Zephyr-Core-3.5.0/scripts/west_commands/tests/
Dtest_mdb.py204 mdb_nsim(test_case['i']).run('flash')
212 mdb_nsim(test_case['i']).run('debug')
221 mdb_nsim(test_case).run('flash')
233 mdb_hw_no_hl(test_case['i']).run('flash')
241 mdb_hw_hl(test_case['i']).run('flash')
250 mdb_hw_no_hl(test_case['i']).run('flash')
258 mdb_hw_no_hl(test_case['i']).run('debug')
266 mdb_hw_hl(test_case['i']).run('debug')
275 mdb_hw_no_hl(test_case['i']).run('debug')
284 mdb_hw_no_hl(test_case).run('flash')
[all …]
Dtest_bossac.py182 runner.run('flash')
218 runner.run('flash')
256 runner.run('flash')
297 runner.run('flash')
335 runner.run('flash')
370 runner.run('flash')
404 runner.run('flash')
439 runner.run('flash')
473 runner.run('flash')
509 runner.run('flash')
[all …]
Dtest_pyocd.py170 pyocd(pyocd_args).run('flash')
182 pyocd(pyocd_args).run('debug')
194 pyocd(pyocd_args).run('debugserver')
216 pyocd(pyocd_args).run('flash')
230 pyocd(pyocd_args).run('debug')
244 pyocd(pyocd_args).run('debugserver')
/Zephyr-Core-3.5.0/include/zephyr/
Dsmf.h24 .run = _run, \
41 .run = _run, \
76 const state_execution run; member
/Zephyr-Core-3.5.0/boards/arm/pico_pi_m4/doc/
Dindex.rst11 Zephyr was ported to run on the M4 core. In a later release, it will also
103 The M4 Core is configured to run at a 200 MHz clock speed.
169 Below you will find the instructions to load and run Zephyr on M4 from A7 using
182 Set the u-boot environment variables and run the zephyr.bin from the
190 setenv bootm4tcml 'run m4tcml && run bootm4'
191 run bootm4tcml
194 setenv bootm4tcmu 'run m4tcmu && run bootm4'
195 run bootm4tcmu
198 setenv bootm4ocram 'run m4ocram && run bootm4'
199 run bootm4ocram
[all …]
/Zephyr-Core-3.5.0/scripts/west_commands/
DREADME.txt11 date. The mypy static type checker is also run on the runners package.
13 To run these tests locally on Windows, run:
21 Note that these tests are run as part of Zephyr's CI when submitting
Drun_tests.py36 subprocess.run(mypy, check=True, cwd=here)
40 subprocess.run(pytest, check=True, cwd=here)
/Zephyr-Core-3.5.0/boards/arm/96b_meerkat96/doc/
Dindex.rst11 Zephyr OS is ported to run on the Cortex®-M4 core.
141 The M4 Core is configured to run at a 200 MHz clock speed.
204 Below you will find the instructions to load and run Zephyr on M4 from
209 Set the u-boot environment variables and run the zephyr.bin from the
217 setenv bootm4tcml 'run m4tcml && run bootm4'
218 run bootm4tcml
221 setenv bootm4tcmu 'run m4tcmu && run bootm4'
222 run bootm4tcmu
225 setenv bootm4ocram 'run m4ocram && run bootm4'
226 run bootm4ocram
[all …]
/Zephyr-Core-3.5.0/boards/arm/colibri_imx7d_m4/doc/
Dindex.rst11 Zephyr was ported to run on the M4 core. In a later release, it will also
125 The M4 Core is configured to run at a 200 MHz clock speed.
192 Below you will find the instructions to load and run Zephyr on M4 from A7 using u-boot.
196 Set the u-boot environment variables and run the zephyr.bin from the appropriated memory
204 setenv bootm4tcml 'run m4tcml && run bootm4'
205 run bootm4tcml
208 setenv bootm4tcmu 'run m4tcmu && run bootm4'
209 run bootm4tcmu
212 setenv bootm4ocram 'run m4ocram && run bootm4'
213 run bootm4ocram
[all …]
/Zephyr-Core-3.5.0/boards/arm/warp7_m4/doc/
Dindex.rst11 Zephyr was ported to run on the M4 core. In a later release, it will also
136 The M4 Core is configured to run at a 200 MHz clock speed.
205 Below you will find the instructions to load and run Zephyr on M4 from A7 using
219 Set the u-boot environment variables and run the zephyr.bin from the
227 setenv bootm4tcml 'run m4tcml && run bootm4'
228 run bootm4tcml
231 setenv bootm4tcmu 'run m4tcmu && run bootm4'
232 run bootm4tcmu
235 setenv bootm4ocram 'run m4ocram && run bootm4'
236 run bootm4ocram
[all …]
/Zephyr-Core-3.5.0/scripts/
Drequirements-run-test.txt1 # RUN-TEST: required to do run time tests of zephyr
3 # things used by twister or related in run time testing
/Zephyr-Core-3.5.0/tests/posix/eventfd/
DKconfig8 int "Number of seconds to run the test"
14 eventfd_write() are stable enough to run for an arbitrarily long
18 int "Number of seconds to run the test"
26 The minimal stack size required to run a no-op thread.
/Zephyr-Core-3.5.0/tests/bsim/
DREADME.md1 This folder contains tests meant to be run with BabbleSim's physical layer
2 simulation, and therefore cannot be run directly from twister.
7 You can also run them manually if desired, but be sure to call them setting
8 the variables they expect. For example, from Zephyr's root folder, you can run:
15 Or to run only a specific subset, e.g. host advertising tests:
23 Check the run_parallel.sh help for more options and examples on how to use this script to run these
26 After building the tests' required binaries you can run a test directly with its individual
34 and then directly run one of the tests:
45 of the BabbleSim tests which have been run. Check its help for more info.
/Zephyr-Core-3.5.0/scripts/ci/
Dcheck_compliance.py41 cp = subprocess.run(git_cmd, capture_output=True, cwd=cwd)
196 def run(self): member in CheckPatch
205 subprocess.run((checkpatch, '--mailback', '--no-tree', '-'),
235 def run(self, full=True): member in DevicetreeBindingsCheck
274 def run(self, full=True, no_modules=False): member in KconfigCheck
307 subprocess.run(cmd, check=True, stdout=subprocess.PIPE,
342 subprocess.run(cmd, check=True, stdout=subprocess.PIPE,
732 def run(self): member in KconfigBasicCheck
733 super().run(full=False)
744 def run(self): member in KconfigBasicNoModulesCheck
[all …]
/Zephyr-Core-3.5.0/scripts/kconfig/
Dlint.py158 modpaths = run(("west", "list", "-f{abspath}")).splitlines()
165 defines = run(("git", "grep", "--extended-regexp", regex),
187 print(run(cmd, cwd=modpath, check=False), end="")
223 run((os.path.join("scripts", "zephyr_module.py"),
252 for modpath in run(("west", "list", "-f{abspath}")).splitlines():
253 for line in run(("git", "grep", "-h", "-I", "--extended-regexp", regex),
293 def run(cmd, cwd=TOP_DIR, check=True): function
/Zephyr-Core-3.5.0/cmake/emu/
Dcustom.cmake4 # when building the `run` target. Create this placeholder file so it doesn't complain.
5 # The real 'run' custom_target should be defined in `board.cmake` instead.
/Zephyr-Core-3.5.0/tests/bsim/bluetooth/ll/edtt/
DREADME.txt43 To run these sets of tests you need to compile both of these applications as any
48 To run the tests you can either run one of the provided scripts, or run by
58 #run all tests
61 #or just run one set:
/Zephyr-Core-3.5.0/tests/net/lib/mqtt_packet/
DREADME6 it can be run on almost any board already supported by Zephyr and
14 Build & run:
17 make run
24 make run
/Zephyr-Core-3.5.0/doc/kernel/usermode/
Dindex.rst6 Zephyr offers the capability to run threads at a reduced privilege level
10 For details on creating threads that run in user mode, please see
/Zephyr-Core-3.5.0/drivers/ethernet/
DKconfig.native_posix10 Enable native posix ethernet driver. Note, this driver is run inside
18 interface, requiring ``zephyr.exe`` to be run with root privileges
22 project repo). The ``zephyr.exe`` program can then be run as a
31 This option sets the name of the script that is run when the host TAP
46 This option sets the name of the script that is run when the host TAP
47 network interface is created and setup script has been run.
57 string "Username to run the host startup script"
60 By default the startup script is run as a root user. Set here the
61 username to run the script if running it as a root user is not
63 for the setup script. The setup script needs to be run always as
/Zephyr-Core-3.5.0/tests/posix/pthread_pressure/
DKconfig12 The number of parallel threads to run during the test.
15 int "Number of seconds to run the test"
33 The minimal stack size required to run a minimal thread.
/Zephyr-Core-3.5.0/scripts/west_commands/zspdx/
Dgetincludes.py5 from subprocess import run, PIPE
32 cp = run(cmd, stdout=PIPE, stderr=PIPE, universal_newlines=True)
/Zephyr-Core-3.5.0/doc/services/tfm/
Dtestsuites.rst9 These test suites can be run from Zephyr via an appropriate sample application
15 The regression test suite can be run via the :ref:`tfm_regression_test` sample.
30 Only one of these suites can be run at a time, with the available test suites
42 to the core TF-M module(s). They should generally be run as a coherence check
/Zephyr-Core-3.5.0/samples/modules/thrift/hello/
DREADME.rst62 This application can be run on a Linux host, with either the server or the
63 client in the QEMU environment, and the peer is built and run natively on
119 :goals: run
122 In another terminal, run the ``hello_client`` sample app compiled for the
143 In the client terminal, run ``hello_client.py`` app under the host OS (not
167 In another terminal, run the ``hello_server`` sample app compiled for the
177 Then, in annother terminal, run the corresponding ``hello/client`` sample:
182 :goals: run

12345678910>>...32