Searched full:your (Results 1 – 25 of 1040) sorted by relevance
12345678910>>...42
| /Zephyr-latest/.github/workflows/ |
| D | greet_first_time_contributor.yml | 21 Hi @${{github.event.issue.user.login}}! We appreciate you submitting your first issue
26 for your time and effort. ����
29 Hello @${{ github.event.pull_request.user.login }}, and thank you very much for your
32 Our Continuous Integration pipeline will execute a series of checks on your Pull Request
35 …to find out how to format your commit messages, and at [our contribution workflow](https://docs.ze…
36 to understand how to update your Pull Request.
39 and update (by amending and force-pushing the commits) your pull request if necessary.
42 …and ask your question there. Additionally, you can [escalate the review](https://docs.zephyrprojec…
48 Congratulations on getting your very first Zephyr pull request merged ����. This is a
52 To celebrate this milestone and showcase your contribution, we'd love to award you the
[all …]
|
| /Zephyr-latest/samples/net/mdns_responder/ |
| D | Kconfig | 11 The value depends on your network setup.
16 The value depends on your network setup.
21 The value depends on your network setup.
35 The value depends on your network setup.
40 The value depends on your network setup.
45 The value depends on your network setup.
|
| /Zephyr-latest/samples/net/vlan/ |
| D | Kconfig | 11 The value depends on your network setup.
16 The value depends on your network setup.
21 The value depends on your network setup.
35 The value depends on your network setup.
40 The value depends on your network setup.
45 The value depends on your network setup.
|
| /Zephyr-latest/doc/contribute/ |
| D | guidelines.rst | 12 and enhancement requests, and submit patches to the project so your patch will
32 allows you to freely use, modify, distribute and sell your own products
139 Signed-off-by: Your Name <your.email@example.com>
141 For your commits, replace:
143 - ``Your Name`` with your legal name (pseudonyms, hacker handles, and the
146 - ``your.email@example.com`` with the same email address you are using to
149 You can automatically add the Signed-off-by: line to your commit body using
157 your Signed-off-by: line without removing the existing one.
159 - If you forget to add the Signed-off-by: line, you can add it to your previous
162 - If you've pushed your changes to GitHub already you'll need to force push
[all …]
|
| D | index.rst | 7 improving documentation, or proposing new features, your efforts are highly appreciated. This page
8 lists useful resources and guidelines to help you in your contribution journey.
26 how to ensure your contribution can be considered for inclusion in the project and potentially
94 When your first contribution to the Zephyr project gets merged, you'll become eligible to claim your
95 Zephyr Contributor Badge. This digital badge can be displayed on your website, blog, social media
96 profile, etc. It will allow you to showcase your involvement in the Zephyr project and help raise
99 You may apply for your Contributor Badge by filling out the `Zephyr Contributor Badge form`_.
|
| /Zephyr-latest/doc/develop/west/ |
| D | extensions.rst | 6 West is "pluggable": you can add your own commands to west without editing its
10 information on west extension commands, and has a tutorial for writing your
57 There are three steps to adding your own extension:
67 Step 1: Implement Your Command
70 Create a Python file to contain your command implementation (see the "Meta >
73 tracked by your :term:`west manifest`, or the manifest repository itself.
75 this class will be instantiated and used when your extension is run.
89 from west.commands import WestCommand # your extension must subclass this
104 parser_adder.add_parser() below if you want to keep your line
135 Step 2: Add or Update Your :file:`west-commands.yml`
[all …]
|
| D | troubleshooting.rst | 23 === updating your_project (path/to/your/project):
27 …west.manifest: running 'git fetch ... https://github.com/your-username/your_project ...' in /some/…
32 One strategy is to go to ``/path/to/your/project``, copy/paste and run the entire
33 ``git fetch`` command, then debug from there using the documentation for your
42 update`` without entering your password in that same shell.
47 On Windows, this means that either west is not installed, or your :envvar:`PATH`
55 You need to find the directory containing :file:`west.exe`, then add it to your
68 will be different on your computer.
77 ``scripts`` to your :envvar:`PATH` using a command like this::
82 will be different on your system.
[all …]
|
| D | moving-to-west.rst | 6 To convert a "pre-west" Zephyr setup on your computer to west, follow these
22 #. Move your zephyr repository to a new :file:`zephyrproject` parent directory,
45 This creates :file:`zephyrproject/.west`, marking the root of your
53 **Make sure to run this command whenever you pull zephyr.** Otherwise, your
|
| /Zephyr-latest/samples/net/sockets/echo_server/ |
| D | Kconfig | 18 The value depends on your network setup.
23 The value depends on your network setup.
28 The value depends on your network setup.
42 The value depends on your network setup.
47 The value depends on your network setup.
52 The value depends on your network setup.
73 The value depends on your network setup.
110 # tree, you cannot use them in your own application.
|
| /Zephyr-latest/doc/develop/toolchains/ |
| D | other_x_compilers.rst | 10 Examples of such "other cross compilers" are cross toolchains that your Linux
11 distribution packaged, that you compiled on your own, or that you downloaded
19 #. Install a cross compiler suitable for your host and target systems.
35 - Set ``CROSS_COMPILE`` to the common path prefix which your
39 #. To check that you have set these variables correctly in your current
41 ``CROSS_COMPILE`` value may be different on your system):
53 When using this option, all of your toolchain binaries must reside in the same
59 ``-``). If your toolchain is installed in ``/opt/mytoolchain/bin`` with binary
|
| D | designware_arc_mwdt.rst | 7 your host.
9 #. You need to have :ref:`Zephyr SDK <toolchain_zephyr_sdk>` installed on your host.
28 If you have only one ARC MWDT toolchain version installed on your machine you may skip setting
31 #. To check that you have set these variables correctly in your current
33 :envvar:`ARCMWDT_TOOLCHAIN_PATH` values may be different on your system):
|
| /Zephyr-latest/samples/net/prometheus/ |
| D | README.rst | 12 By integrating this library into your code, you can expose internal metrics
13 via an HTTP endpoint on your application's instance, enabling Prometheus to
80 Replace ``'your_server_metrics'`` with a descriptive name for your job,
81 ``'your_server_ip'`` with the IP address or hostname of your server, and
82 ``'your_server_port'`` with the port number where your server exposes Prometheus metrics.
84 Make sure to adjust the configuration according to your server's setup and requirements.
87 Once restarted, Prometheus will start scraping metrics from your server according
88 to the defined scrape configuration. You can verify that your server's metrics are
90 metrics from your server.
|
| /Zephyr-latest/samples/basic/blinky/ |
| D | README.rst | 26 Your board must:
35 Build and flash Blinky as follows, changing ``reel_board`` for your board:
63 To add support for your board, add something like this to your devicetree:
80 The above sets your board's ``led0`` alias to use pin 13 on GPIO controller
90 use the same SoC as your target. See :ref:`get-devicetree-outputs` for details.
95 - If the LED is built in to your board hardware, the alias should be defined in
96 your :ref:`BOARD.dts file <devicetree-in-out-files>`. Otherwise, you can
|
| /Zephyr-latest/samples/net/virtual/ |
| D | Kconfig | 11 The value depends on your network setup.
16 The value depends on your network setup.
28 The value depends on your network setup.
33 The value depends on your network setup.
|
| /Zephyr-latest/doc/develop/ |
| D | env_vars.rst | 16 lifetime of your current terminal window:
34 This is best for experimentation. If you close your terminal window, use
35 another terminal window or tab, restart your computer, etc., this setting
47 Add the ``export MY_VARIABLE=foo`` line to your shell's startup script in
48 your home directory. For Bash, this is usually :file:`~/.bashrc` on Linux
72 You can then run ``rapidee`` from your terminal to launch the program and set
75 your changes by clicking the Save button at top left before exiting. Settings
84 to all of your terminals, but still want to save the value for loading into
85 your environment when you are using Zephyr.
98 To get this value back into your current terminal environment, **you must
[all …]
|
| /Zephyr-latest/samples/net/lldp/ |
| D | Kconfig | 17 The value depends on your network setup.
22 The value depends on your network setup.
36 The value depends on your network setup.
41 The value depends on your network setup.
|
| /Zephyr-latest/tests/net/virtual/ |
| D | Kconfig | 12 The value depends on your network setup.
18 The value depends on your network setup.
24 The value depends on your network setup.
|
| /Zephyr-latest/soc/nordic/nrf53/ |
| D | CMakeLists.txt | 12 Your application may be affected by the anomaly 160 that concerns the
13 nRF5340 SoC. The related workaround cannot be applied, because your
17 At your own risk, you can suppress this warning by setting
|
| /Zephyr-latest/samples/net/sockets/echo_client/ |
| D | Kconfig | 11 The value depends on your network setup.
16 The value depends on your network setup.
30 The value depends on your network setup.
35 The value depends on your network setup.
|
| /Zephyr-latest/doc/develop/flash_debug/ |
| D | nordic_segger.rst | 27 #. Depending on your platform, install the package or run the installer
34 The nRF5x command-line Tools allow you to control your nRF5x device from the command line,
37 To install them, visit `nRF5x Command-Line Tools`_ and select your operating
40 After installing, make sure that ``nrfjprog`` is somewhere in your executable path
51 * Connect the micro-USB cable to the nRF5x board and to your computer
60 * Flash the Zephyr image from the sample folder of your choice:
82 To work around this disable the Mass Storage Device on your board as described in :ref:`nordic_segg…
94 Type the command below to add your user to the dialout group to give it access to the serial port.
103 port for a few seconds, and can make your application misbehave if it reads
104 data from the UART. Before running your application, you might want to
[all …]
|
| /Zephyr-latest/samples/net/telnet/ |
| D | README.rst | 50 At this point, your QEMU guest is up and running. Connect to the telnet
51 console from your linux host this way:
77 local network providing IPv4 address configuration via DHCPv4. Creating your own
91 From your host computer, open a serial console to your board:
117 The above result depends on your local network.
119 On your linux host:
130 your commands and get the output through your telnet client.
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | soc_porting.rst | 7 the upstream Zephyr project or locally in your own repository.
31 Create your SoC directory
43 ``<VENDOR>`` is your vendor subdirectory.
46 A ``<VENDOR>`` subdirectory is mandatory if contributing your SoC
47 to Zephyr, but if your SoC is placed in a local repo, then any folder
48 structure under ``<your-repo>/soc`` is permitted.
59 Your SoC directory should look like this:
71 Replace ``<soc-name>`` with your SoC's name.
107 Write your SoC YAML
145 Write your SoC devicetree
[all …]
|
| D | board_porting.rst | 9 support your :term:`SoC` as well.
50 #. Take the SoC definition from Zephyr v3.6.0 and copy it to your downstream
52 :ref:`zephyr module <modules>` or ``SOC_ROOT``). This will allow your board,
55 When converting your board from the previous to the current hardware model, we
180 Make sure your SoC is supported
183 Start by making sure your SoC is supported by Zephyr. If it is, it's time to
184 :ref:`create-your-board-directory`. If you don't know, try:
188 - asking your SoC vendor
218 files to avoid duplication. If there is no support for your vendor yet, you can
219 add it in a new directory ``zephyr/soc/<VENDOR>/<YOUR-SOC>``; please use
[all …]
|
| /Zephyr-latest/samples/net/gptp/ |
| D | Kconfig | 20 The value depends on your network setup.
25 The value depends on your network setup.
39 The value depends on your network setup.
44 The value depends on your network setup.
|
| /Zephyr-latest/dts/bindings/i2c/ |
| D | nordic,nrf-twi.yaml | 23 your SoC:
26 section of your SoC's Product Specification document.
30 2. Open your SoC's .dtsi file and look for a node definition that
40 If your SoC only has TWIM and TWIS I2C peripherals, you cannot use
|
12345678910>>...42
