/Zephyr-latest/modules/thrift/src/thrift/ |
D | config.h | 15 /* Define to 1 if you have the <arpa/inet.h> header file. */ 18 /* Define to 1 if you have the `clock_gettime' function. */ 24 /* Define to 1 if you have the <fcntl.h> header file. */ 27 /* Define to 1 if you have the `gethostbyname' function. */ 30 /* Define to 1 if you have the `gettimeofday' function. */ 33 /* Define to 1 if you have the `inet_ntoa' function. */ 36 /* Define to 1 if you have the <inttypes.h> header file. */ 39 /* Define to 1 if you have the <limits.h> header file. */ 45 /* Define to 1 if you have the `memmove' function. */ 48 /* Define to 1 if you have the <memory.h> header file. */ [all …]
|
/Zephyr-latest/drivers/disk/nvme/ |
D | Kconfig | 22 Do not touch this unless you know what you are doing. 30 Do not touch this unless you know what you are doing. 38 Do not touch this unless you know what you are doing. 45 Do not touch this unless you know what you are doing. 53 Do not touch this unless you know what you are doing.
|
/Zephyr-latest/doc/build/dts/ |
D | troubleshooting.rst | 45 You thus get a linker error, because you're asking for a pointer to a device 48 To fix it, you need to make sure that: 67 To find the devicetree node you need to check, use the number ``<N>`` from the 71 the node you are interested in is ``/soc/i2c@deadbeef``: 95 If the node has ``status = "disabled";`` in :file:`zephyr.dts`, then you need 106 Then you should put this into your devicetree overlay and 115 Make sure that you see ``status = "okay";`` in :file:`zephyr.dts` after you 121 your devicetree node and allocating devices for it. To do this, you need to 125 If you're not familiar with how devices are allocated from devicetree nodes 135 devicetree compatibles they are associated with. You will have to figure this [all …]
|
/Zephyr-latest/doc/develop/west/ |
D | without-west.rst | 8 particular, you will have to do work "by hand" to replace these 20 If you have previously installed west and want to stop using it, 34 you will need to manually clone the additional projects listed in the 45 As you pull changes in the zephyr repository, you will also need to 52 You can build a Zephyr application using CMake and Ninja (or make) directly 53 without west installed if you specify any modules manually. 65 If you don't have west installed and your application does not need any of 68 If you don't have west installed and your application *does* need one 69 of these repositories, you must set :makevar:`ZEPHYR_MODULES` 74 Similarly, if your application requires binary blobs and you are not using [all …]
|
D | troubleshooting.rst | 36 If you're behind a corporate firewall and may have proxy or other issues, 40 If you can get the ``git fetch`` command to run successfully without prompting 41 for a password when you run it directly, you will be able to run ``west 51 First, make sure you've installed west; see :ref:`west-install`. Then try 55 You need to find the directory containing :file:`west.exe`, then add it to your 56 :envvar:`PATH`. (This :envvar:`PATH` change should have been done for you when 57 you installed Python and pip, so ordinarily you should not need to follow these 76 #. If you see ``west.exe`` in the ``scripts`` directory, add the full path to 83 #. Close your ``cmd.exe`` window and open a new one. You should be able to run 121 packages, so you may need to do some additional work to get it installed on [all …]
|
D | extensions.rst | 6 West is "pluggable": you can add your own commands to west without editing its 13 Some commands you can run when using west with Zephyr, like the ones used to 38 globally for whenever you run west, use: 44 If you want to, you can then re-enable them in a particular :term:`west 72 supported versions of Python). You can put it in anywhere in any project 77 Here is a basic skeleton you can use to get started. It contains a subclass of 79 details on the west APIs you can use, see :ref:`west-apis`. 101 You can split this up into multiple paragraphs and they'll get 102 reflowed for you. You can also pass 104 parser_adder.add_parser() below if you want to keep your line [all …]
|
/Zephyr-latest/.github/workflows/ |
D | greet_first_time_contributor.yml | 21 Hi @${{github.event.issue.user.login}}! We appreciate you submitting your first issue 25 Even though I'm a bot, I can assure you that the whole community is genuinely grateful 29 Hello @${{ github.event.pull_request.user.login }}, and thank you very much for your 33 … commit messages and code, and you are expected to address any failures by updating the PR. 37 If you haven't already, please make sure to review the project's [Contributor 41 … If you are stuck or need help please join us on [Discord](https://chat.zephyrproject.org/) 42 …and ask your question there. Additionally, you can [escalate the review](https://docs.zephyrprojec… 49 fantastic achievement, and we're thrilled to have you as part of our community! 52 To celebrate this milestone and showcase your contribution, we'd love to award you the 53 Zephyr Technical Contributor badge. If you're interested, please claim your badge by [all …]
|
/Zephyr-latest/doc/develop/getting_started/ |
D | installation_win.rst | 11 If you are running a recent version of Windows 10 you can make use of the 13 command-prompt. This allows you to use software such as the :ref:`Zephyr SDK 24 For the Zephyr SDK to function properly you will need Windows 10 25 build 15002 or greater. You can check which Windows 10 build you are 27 If you are running an older Windows 10 build you might need to install
|
D | installation_linux.rst | 18 .. note:: If you're working behind a corporate firewall, you'll likely 19 need to configure a proxy for accessing the internet, if you haven't 65 documentation. If you need to add a dependency only required for building 70 Note that both Ninja and Make are installed with these instructions; you only 113 other and Clear Linux is no exception. If you need a more flexible 128 version you have by using ``cmake --version``. If you have an older version, 131 * On Ubuntu, you can follow the instructions for adding the 168 you'll need to add ~/.local/bin to your PATH. (See :ref:`python-pip` 174 * On Ubuntu you can also use snap to get the latest version available: 182 You might also want to uninstall the CMake provided by your package manager to [all …]
|
/Zephyr-latest/doc/develop/toolchains/ |
D | gnu_arm_embedded.rst | 11 On Windows, we'll assume for this guide that you install into the directory 12 :file:`C:\\gnu_arm_embedded`. You can also choose the default installation 13 path used by the ARM GCC installer, in which case you will need to adjust the path 18 On macOS Catalina or later you might need to :ref:`change a security 28 #. To check that you have set these variables correctly in your current 38 /home/you/Downloads/gnu_arm_embedded 48 …On macOS, if you are having trouble with the suggested procedure, there is an unofficial package o…
|
D | zephyr_sdk.rst | 37 from there. You can enforce this by setting the environment variable 40 If you install the Zephyr SDK outside any of the default locations (listed in 41 the operating system specific instructions below) and you want automatic discovery 42 of the Zephyr SDK, then you must register the Zephyr SDK in the CMake package registry 43 by running the setup script. If you decide not to register the Zephyr SDK in the CMake registry, 47 You can also set :envvar:`ZEPHYR_SDK_INSTALL_DIR` to point to a directory 49 example, you can set ``ZEPHYR_SDK_INSTALL_DIR`` to ``/company/tools``, where the 77 .. note:: You can change |sdk-version-literal| to another version in the instructions below 81 .. note:: If you want to uninstall the SDK, you may simply remove the directory 82 where you installed it. [all …]
|
D | designware_arc_mwdt.rst | 6 #. You need to have `ARC MWDT <https://www.synopsys.com/dw/ipdir.php?ds=sw_metaware>`_ installed on 9 #. You need to have :ref:`Zephyr SDK <toolchain_zephyr_sdk>` installed on your host. 18 that allows you to avoid toolchain related issues while building Zephyr. 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 41 /home/you/ARC/MWDT_2023.03/
|
/Zephyr-latest/doc/build/kconfig/ |
D | menuconfig.rst | 18 If you try to enable a symbol with unsatisfied dependencies in 22 To make a setting permanent, you should set it in a :file:`*.conf` file, as 65 If you get an import error for ``tkinter`` when trying to run 66 ``guiconfig``, you are missing required packages. See 67 :ref:`installation_linux`. The package you need is usually called 87 If you prefer to work in the ``guiconfig`` interface, then it's a good 88 idea to check any changes to Kconfig files you make in *single-menu 91 ``config`` and symbols defined with ``menuconfig``, showing you what 110 You can also press :kbd:`Y` or :kbd:`N` to set a boolean configuration 132 filename (:file:`zephyr/.config`). You will typically save to the default [all …]
|
/Zephyr-latest/ |
D | LICENSE | 23 "You" (or "Your") shall mean an individual or Legal Entity 67 this License, each Contributor hereby grants to You a perpetual, 74 this License, each Contributor hereby grants to You a perpetual, 81 with the Work to which such Contribution(s) was submitted. If You 86 granted to You under this License for that Work shall terminate 89 4. Redistribution. You may reproduce and distribute copies of the 91 modifications, and in Source or Object form, provided that You 94 (a) You must give any other recipients of the Work or 97 (b) You must cause any modified files to carry prominent notices 98 stating that You changed the files; and [all …]
|
/Zephyr-latest/drivers/ieee802154/ |
D | Kconfig.cc1200 | 25 you know what you are doing. Beware cc1200 requires gpio and spi to 73 SmartRF tool. Do not touch this unless you know what you are doing. 84 Set the RF preset you want to use. 111 more information. Do not touch this unless you know what you are doing. 118 more information. Do not touch this unless you know what you are doing. 120 # Do no touch below settings unless you know what you are doing
|
/Zephyr-latest/doc/develop/ |
D | env_vars.rst | 34 This is best for experimentation. If you close your terminal window, use 38 Using options 2 or 3 is recommended if you want to keep using the setting. 55 You can use the ``setx`` program in ``cmd.exe`` or the third-party RapidEE 72 You can then run ``rapidee`` from your terminal to launch the program and set 74 -- otherwise, you have to run RapidEE as administrator. Also make sure to save 76 you make in RapidEE will be available whenever you open a new terminal window. 83 Choose this option if you don't want to make the variable's setting available 85 your environment when you are using Zephyr. 98 To get this value back into your current terminal environment, **you must 102 The value will be lost if you close the window, etc.; run ``source [all …]
|
/Zephyr-latest/boards/beagle/beaglev_fire/doc/ |
D | index.rst | 10 Black allowing you to stack your favorite BeagleBone cape on top to expand it’s capability. 34 In order to upload the application to the device, you'll need OpenOCD and GDB 36 You can get them as a part of SoftConsole SDK. 41 You will also require a Debugger such as Microchip's FlashPro5/6. 44 Now you can run ``tio <port>`` in a terminal window to access the UART debug port connection. Once … 45 are connected properly you can press the Reset button which will show you a progress bar like: 51 Once you see that progress bar on your screen you can start pressing any button (0-9/a-z) which 54 With the necessary tools installed, you can connect to the board using OpenOCD. 64 the board. You can use the RISC-V GDB from the Zephyr SDK. 88 …ps://github.com/polarfire-soc/hart-software-services>`_ along with Zephyr, you need to use the `hs… [all …]
|
/Zephyr-latest/doc/connectivity/bluetooth/shell/host/ |
D | gap.rst | 15 :kconfig:option:`CONFIG_BT_ID_MAX`. To create a new identity, use :code:`bt id-create` command. You 16 can then use it by selecting it with its ID :code:`bt id-select <id>`. Finally, you can list all the 22 Start scanning by using the :code:`bt scan on` command. Depending on the environment you're in, you 26 Here is an example of what you can expect: 43 As you can see, this can lead to a high number of results. To reduce that number and easily find a 44 specific device, you can enable scan filters. There are four types of filters: by name, by RSSI, by 46 command followed by the type of filters. You can add multiple filters by using the commands again. 48 For example, if you want to look only for devices with the name *test shell*: 54 Or if you want to look for devices at a very close range: 61 Finally, if you want to remove all filters: [all …]
|
/Zephyr-latest/drivers/wifi/winc1500/ |
D | Kconfig.winc1500 | 32 WINC1500 HAL callbacks. Do not touch it unless you know what you are 40 callbacks. Do not touch it unless you know what you are doing. 55 Do not modify it unless you know what you are doing.
|
/Zephyr-latest/samples/boards/phytec/reel_board/mesh_badge/ |
D | README.rst | 23 #. Connect to the device. You'll see a single service - select it 30 wide text. You can force line breaks with a comma. 34 #. Once pairing is complete the board will show the text you sent. If 35 you're not happy with it you can try writing something else. 36 #. When you're happy with the text, disconnect from the board (exit the app or 38 #. Once disconnected the board switches over to Bluetooth Mesh mode, and you 41 If you configure multiple boards like this they can communicate with
|
/Zephyr-latest/boards/intel/adsp/doc/ |
D | chromebooks_adsp.rst | 20 first, to ensure you have two working OS images. 33 that you really mean it. Select "Boot from Internal Storage" at the 34 bootloader screen. You will see this screen every time the machine 35 boots now, telling you that the boot is unverified. 45 You will at some point wreck your device and need a recovery stick. 49 You can actually do this on any machine (and any OS) with Chrome 54 root filesystem and /usr/local customizations you have made**. So 55 plan on a strategy that can tolerate data loss on the device you're 68 user. Finally (in developer mode) a simple "sudo su -" will get you a 77 Now you need to turn of signature verification in the bootloader [all …]
|
D | intel_adsp_generic.rst | 32 otherwise stated. You will be referred to the documentation for your specific 41 You can only flash Zephyr to the ADSP by using Zephyr's Python tool in a Linux 45 the binary sent over the network by West and flashes it. You should install a 50 Note that if you plan to use SOF on your board, you will need to build and 52 recommended you follow the `SOF instructions`_ to build and run SOF on Zephyr. 61 you will also need to set up the SOF rimage signing tool and key. 71 your system. You can either copy the executable to a directory in your PATH or 74 makes you less likely to use an obsolete rimage version by mistake. 77 subdirectory. For a different configuration directory you can use: 87 `Cadence`_ instead. The following instructions assume you have purchased and [all …]
|
/Zephyr-latest/samples/subsys/mgmt/updatehub/ |
D | overlay-prj.conf.example | 7 #Example of product_uid, you must set you product uid. 10 #If you use the autorandler, need set UPDATEHUB_POLL_INTERVAL. 18 #You need set the updatehub-ce ip Address.
|
/Zephyr-latest/doc/contribute/ |
D | guidelines.rst | 21 As a contributor, you'll want to be familiar with the Zephyr project, how to 26 You should be familiar with common developer tools such as Git and CMake, and 29 If you haven't already done so, you'll need to create a (free) GitHub account 36 tools yourself, you will need to rely on the Continuous Integration (CI) 37 service using Github Actions, which runs automatically on GitHub when you submit 38 your Pull Request (PR). You can see any failure results in the workflow 58 contribution and allowing you to use the software however you would like 60 allows you to freely use, modify, distribute and sell your own products 71 A license tells you what rights you have as a developer, as provided by the 179 - ``your.email@example.com`` with the same email address you are using to [all …]
|
/Zephyr-latest/doc/services/storage/fcb/ |
D | fcb.rst | 6 Flash circular buffer provides an abstraction through which you can treat 7 flash like a FIFO. You append entries to the end, and read data from the 22 Storage of entries in flash is done in a FIFO fashion. When you 24 used area. When you start reading, the first entry served is the 28 exhausted. You have control over what happens next; either erase oldest 44 this fails due to lack of space, you can call :c:func:`fcb_rotate` to erase 55 :c:func:`flash_area_read`. You can tell when all data from within a sector 56 has been read by monitoring the returned entry's area pointer. Then you 57 can call :c:func:`fcb_rotate`, if you're done with that data.
|