Searched +full:zephyr +full:- +full:bugs +full:- (Results 1 – 25 of 50) sorted by relevance
12
| /Zephyr-latest/.github/workflows/ |
| D | bug_snapshot.yaml | 2 # SPDX-License-Identifier: Apache-2.0
4 # Make a snapshot of open bugs as a python pickle file, compressed
14 - cron: '5 14 * * *'
18 name: Make bugs pickle
19 runs-on: ubuntu-22.04
20 if: github.repository_owner == 'zephyrproject-rtos'
23 - name: Checkout
26 - name: Install Python dependencies
28 pip install -U pygithub
30 - name: Snapshot bugs
[all …]
|
| /Zephyr-latest/doc/project/ |
| D | release_process.rst | 6 The Zephyr project releases on a time-based cycle, rather than a feature-driven
7 one. Zephyr releases represent an aggregation of the work of many contributors,
10 A time-based release process enables the Zephyr project to provide users with a
12 roughly 4-month release cycle allows the project to coordinate development of
17 The Zephyr release model was loosely based on the Linux kernel model:
19 - Release tagging procedure:
21 - linear mode on main branch,
22 - release branches for maintenance after release tagging.
23 - Each release period will consist of a development phase followed by a
29 - Development phase: all changes are considered and merged, subject to
[all …]
|
| D | project_roles.rst | 37 * Right to report defects (bugs) and suggestions for enhancement.
46 * Responsibility for issues and bugs introduced by one’s own contributions.
51 (https://github.com/zephyrproject-rtos/zephyr/blob/main/CODE_OF_CONDUCT.md)
54 ….github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-permiss…
55 access to the Zephyr GitHub repository. Specifically, at the Read access level,
58 the `Zephyr devel mailing list <https://lists.zephyrproject.org/g/devel>`_ or on
59 the `Zephyr Discord Server <https://chat.zephyrproject.org>`_.
62 level to the Zephyr GitHub repository.
80 of Zephyr source code. Their opinions weigh more when decisions are made, in a
98 the Zephyr repository.
[all …]
|
| /Zephyr-latest/scripts/release/ |
| D | bug_bash.py | 4 # SPDX-License-Identifier: Apache-2.0
6 """Query the Top-Ten Bug Bashers
8 This script will query the top-ten Bug Bashers in a specified date window.
11 ./scripts/bug-bash.py -t ~/.ghtoken -b 2021-07-26 -e 2021-08-07
12 GITHUB_TOKEN="..." ./scripts/bug-bash.py -b 2021-07-26 -e 2021-08-07
26 parser.add_argument('-a', '--all', dest='all',
27 help='Show all bugs squashed', action='store_true')
28 parser.add_argument('-t', '--token', dest='tokenfile',
30 parser.add_argument('-s', '--start', dest='start', help='start date (YYYY-mm-dd)',
32 parser.add_argument('-e', '--end', dest='end', help='end date (YYYY-mm-dd)',
[all …]
|
| /Zephyr-latest/scripts/ |
| D | make_bugs_pickle.py | 5 # SPDX-License-Identifier: Apache-2.0
17 # other zephyr/scripts modules
23 def parse_args() -> argparse.Namespace:
27 A helper script which loads all open bugs in the
28 zephyrproject-rtos/zephyr repository using the GitHub API, and writes
33 - GitHub API: https://docs.github.com/en/rest
34 - github.Issue.Issue:
36 - pickle: https://docs.python.org/3/library/pickle.html
44 def get_open_bugs() -> List[Issue]:
45 zephyr_repo = get_github_object().get_repo('zephyrproject-rtos/zephyr')
[all …]
|
| /Zephyr-latest/tests/drivers/i2c/i2c_target_api/ |
| D | README.txt | 9 controllers on a common bus. The test is supported by a test-specific
11 is pre-loaded into the simulated devices outside the I2C API, and the
12 Zephyr application issues commands to one controller that are responded
17 I2C controllers, so this behavior is now opt-in using
23 * Use API specific to the simulated EEPROM to pre-populate the simulated
24 devices with device-specific content.
40 or the controller driver has bugs, the test will fail one or more I2C
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 001_bug_report.md | 1 ---
3 about: Create a report to help us improve Zephyr
8 ---
9 <!--
11 Github Discussions (https://github.com/zephyrproject-rtos/zephyr/discussions)
12 are available to first verify that the issue is a genuine Zephyr bug and not a
13 consequence of Zephyr services misuse.
15 This issue list is only for bugs in the main Zephyr code base
16 (https://github.com/zephyrproject-rtos/zephyr/). If the bug is for a project
19 -->
[all …]
|
| /Zephyr-latest/tests/boards/intel_adsp/smoke/src/ |
| D | hostipc.c | 2 * SPDX-License-Identifier: Apache-2.0
4 #include <zephyr/kernel.h>
5 #include <zephyr/ztest.h>
61 /* Do exactly the same thing again to check for state bugs in ZTEST()
|
| /Zephyr-latest/soc/microchip/mec/common/ |
| D | soc_i2c.c | 4 * SPDX-License-Identifier: Apache-2.0
7 #include <zephyr/kernel.h>
8 #include <zephyr/sys/sys_io.h>
9 #include <zephyr/sys/__assert.h>
16 /* Too many MEC1501 HAL bugs */
72 return -EINVAL; in soc_i2c_port_lines_get()
79 return -EINVAL; in soc_i2c_port_lines_get()
82 if (regs->CTRL[idx_scl] & BIT(MCHP_GPIO_CTRL_INPAD_VAL_POS)) { in soc_i2c_port_lines_get()
85 if (regs->CTRL[idx_sda] & BIT(MCHP_GPIO_CTRL_INPAD_VAL_POS)) { in soc_i2c_port_lines_get()
|
| /Zephyr-latest/boards/native/native_posix/doc/ |
| D | index.rst | 21 which will set its configuration to mimic a native_posix-like configuration.
24 Just like with :ref:`native_sim<native_sim>` you can build your Zephyr application
25 with the Zephyr kernel, creating a normal Linux executable with your host tooling,
54 applications with the :ref:`Zephyr POSIX OS abstraction<posix_support>`, as there would be symbol
64 .. zephyr-app-commands::
65 :zephyr-app: samples/hello_world
66 :host-os: unix
71 Now you have a Linux executable, ``./build/zephyr/zephyr.exe``, you can use just like any
88 This mimics the ABI of most embedded systems Zephyr targets,
89 and is therefore normally best to test and debug your code, as some bugs are
[all …]
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | qemu_user_setup.rst | 11 using QEMU SLIRP with Zephyr.
30 Using SLIRP with Zephyr
33 In order to use SLIRP with Zephyr, the user has to set the Kconfig option to
36 .. code-block:: cfg
41 In the default configuration, Zephyr only enables User Networking, and does
52 * Tell QEMU to start DHCP server at user-defined IP address.
56 with good defaults that work for all. Therefore, Zephyr Implementation
61 .. code-block:: cfg
63 CONFIG_NET_QEMU_USER_EXTRA_ARGS="net=192.168.0.0/24,hostfwd=tcp::8080-:8080"
65 This option is appended as-is to the QEMU command line. Therefore, any problems with
[all …]
|
| /Zephyr-latest/arch/x86/zefi/ |
| D | README.txt | 4 Run the "zefi.py" script, passing a path to a built zephyr.elf file
5 (NOT a "zephyr.strip" intended for grub/multiboot loading -- we need
7 "zephyr.efi" file in the current directory. Copy this to your target
14 This works by creating a "zephyr.efi" EFI binary containing a zephyr
15 image extracted from a built zephyr.elf file. EFI applications are
17 Instead, the stub code will copy the embedded zephyr sections to the
18 appropriate locations at startup, clear any zero-filled (BSS, etc...)
24 copies. But then, the biggest Zephyr application binaries we have on
32 The code and link environment here is non-obvious. The simple rules
45 Linux toolchain. EFI binaries are relocatable PE-COFF files --
[all …]
|
| /Zephyr-latest/boards/intel/socfpga_std/cyclonev_socdk/doc/ |
| D | index.rst | 10 The Zephyr kernel is supported on the Intel® Cyclone® V SoC Development Kit,
37 * J26: Short pins 1-2
38 * J27: Short pins 2-3
39 * J28: Short pins 1-2
40 * J29: Short pins 2-3
41 * J30: Short pins 1-2
48 * SW3: ON-OFF-ON-OFF-ON-ON
49 * SW4: OFF-OFF-ON-ON
51 Other switches are user switches, their position is application-specific.
58 ….intel.com/content/www/us/en/software-kit/684215/intel-quartus-prime-lite-edition-design-software-…
[all …]
|
| /Zephyr-latest/boards/st/sensortile_box/doc/ |
| D | index.rst | 1 .. zephyr:board:: sensortile_box
6 The STEVAL-MKSBOX1V1 (SensorTile.box) is a ready-to-use box kit for wireless
9 The SensorTile.box board fits into a small plastic box with a long-life rechargeable
20 - Ultra low-power STM32L4R9ZI System on Chip
22 - LQFP144 package
23 - Core: ARM |reg| 32-bit Cortex |reg|-M4 CPU with FPU, adaptive
24 real-time accelerator (ART Accelerator) allowing 0-wait-state
27 - Clock Sources:
29 - 16 MHz crystal oscillator
30 - 32 kHz crystal oscillator for RTC (LSE)
[all …]
|
| /Zephyr-latest/doc/develop/flash_debug/ |
| D | nordic_segger.rst | 5 Nordic nRF5x Segger J-Link
14 * Segger J-Link firmware and desktop tools
16 * Mass Storage device for drag-and-drop image flashing
21 Segger J-Link Software Installation
24 To install the J-Link Software and documentation pack, follow the steps below:
26 #. Download the appropriate package from the `J-Link Software and documentation pack`_ website
28 #. When connecting a J-Link-enabled board such as an nRF5x DK, PDK or dongle, a
31 nRF5x Command-Line Tools Installation
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
[all …]
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 1 .. _bin-blobs:
12 Zephyr supports downloading and using third-party binary blobs via its built-in
15 `upstream (vanilla) Zephyr <https://github.com/zephyrproject-rtos/zephyr>`_.
18 the support for binary blobs in forks or third-party distributions of Zephyr. In
19 fact, Zephyr’s build system supports arbitrary use cases related to blobs. This
21 therefore free to create Zephyr-based downstream software which uses binary
30 click-through or other EULA-like workflow when users fetch and install blobs.
35 Blobs must be hosted on the Internet and managed by third-party infrastructure.
39 The Zephyr Project does not host binary blobs in its Git repositories or
45 Blobs are fetched from official third-party sources by the :ref:`west blobs
[all …]
|
| /Zephyr-latest/doc/develop/languages/cpp/ |
| D | index.rst | 6 C++ is a general-purpose object-oriented programming language that is based on
12 Zephyr supports applications written in both C and C++. However, to use C++ in
13 an application you must configure Zephyr to include C++ support by selecting
17 and the included compiler must be supported by the Zephyr build system. The
19 is supported by Zephyr, and the features and their availability documented
20 here assume the use of the Zephyr SDK.
23 compiler flags passed) for Zephyr apps is C++11. Other standards are
26 tested in Zephyr is C++98.
36 has to be selected. Zephyr ignores the return value from main, so applications
45 Zephyr currently provides only a subset of C++ functionality. The following
[all …]
|
| /Zephyr-latest/subsys/debug/ |
| D | Kconfig | 4 # SPDX-License-Identifier: Apache-2.0
24 module-str = thread analyzer
65 the interrupts for a long time - long enough to disconnect when
90 on cache-incoherent architectures.
131 Builds Zephyr with Address Sanitizer enabled. This is currently
133 recent-ish compiler with the ``-fsanitize=address`` command line option,
136 Note that at exit leak detection is disabled for 64-bit boards when
170 Builds Zephyr with Undefined Behavior Sanitizer enabled.
172 architecture, and requires a recent-ish compiler with the
173 ``-fsanitize=undefined`` command line option.
[all …]
|
| /Zephyr-latest/boards/altr/max10/doc/ |
| D | index.rst | 1 .. zephyr:board:: altera_max10
6 The Zephyr kernel is supported on the Altera MAX10 Rev C development kit, using
28 Other switches are user switches, their position is application-specific.
37 For your convenience using the SDK tools (such as ``nios2-configure-sof``),
42 .. code-block:: console
48 II peripheral, which is the built-in JTAG interface for this device.
52 .. code-block:: console
54 # For Altera USB-Blaster permissions.
73 .. code-block:: console
76 1) USB-BlasterII [1-1.2]
[all …]
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | index.rst | 8 - Set up a command-line Zephyr development environment on Ubuntu, macOS, or
11 - Get the source code
12 - Build, flash, and run a sample application
23 .. group-tab:: Ubuntu
28 .. code-block:: bash
33 .. group-tab:: macOS
39 <https://support.apple.com/en-us/HT201541>`_.
41 .. group-tab:: Windows
46 .. _install-required-tools:
55 .. list-table::
[all …]
|
| /Zephyr-latest/boards/native/doc/ |
| D | bsim_boards_design.rst | 50 The main purpose of these bsim boards is to be test-benches for
53 least, run with the Zephyr RTOS just like for any other
80 - Unit tests:
83 Zephyr provides a unit testing target (unit_testing) which is not related to
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
98 - Using bsim boards with the BabbleSim Physical layer simulation allows
102 - Using bsim boards, and the `EDTT`_ framework: With the EDTT framework we can
108 - Using Zephyr's :ref:`native_sim <native_sim>` board: It also allows integration testing of
[all …]
|
| /Zephyr-latest/boards/st/sensortile_box_pro/doc/ |
| D | index.rst | 1 .. zephyr:board:: sensortile_box_pro
6 The STEVAL-MKBOXPRO (SensorTile.box PRO) features an ARM Cortex-M33 based STM32U585AI MCU
7 and is a ready-to-use box kit for wireless IoT and wearable sensor platforms to help using
10 The SensorTile.box PRO board fits into a small plastic box with a long-life rechargeable
23 - Pedometer optimized for belt positioning
24 - Baby crying detection with Cloud AI learning
25 - Barometer / environmental monitoring
26 - Vehicle / goods tracking
27 - Vibration monitoring
28 - Compass and inclinometer
[all …]
|
| /Zephyr-latest/doc/kernel/services/smp/ |
| D | smp.rst | 6 On multiprocessor architectures, Zephyr supports the use of multiple
7 physical CPUs running Zephyr application code. This support is
9 default. Any processor is capable of running any Zephyr thread, with
10 access to all standard Zephyr APIs supported.
13 this feature. If there are two Zephyr application threads runnable on
26 non-Zephyr code).
31 At the application level, core Zephyr IPC and synchronization
36 At the lowest level, however, Zephyr code has often used the
52 needed to wait for the other CPU to exit the lock. The default Zephyr
54 on top of the pre-existing :c:struct:`atomic_` layer (itself usually
[all …]
|
| /Zephyr-latest/doc/kernel/services/timing/ |
| D | clocks.rst | 6 Zephyr provides a robust and scalable timing framework to enable
46 ----------
48 Zephyr provides an extensively enumerated conversion library with
66 word, these conversions expand to a 2-4 operation sequence, requiring
87 The Zephyr kernel provides many APIs with a "timeout" parameter.
127 being 32 bits. Large uptime counts in non-tick units will experience
129 timing-sensitive applications with long uptimes will be configured to
142 -------------
144 All Zephyr :c:type:`k_timeout_t` events specified using the API above are
146 a double-linked list, with an attendant delta count in ticks from the
[all …]
|
| /Zephyr-latest/scripts/west_commands/completion/ |
| D | west-completion.bash | 1 # Bash auto-completion for west subcommands and flags. To initialize, run
3 # source west-completion.bash
7 __west_previous_extglob_setting=$(shopt -p extglob)
8 shopt -s extglob
12 # bash_completion - programmable completion functions for bash 3.2+
14 # Copyright © 2006-2008, Ian Macdonald <ian@caliban.org>
15 # © 2009-2010, Bash Completion Maintainers
16 # <bash-completion-devel@lists.alioth.debian.org>
33 # http://bash-completion.alioth.debian.org/
41 # if test "${words_[cword_-1]}" = -w
[all …]
|
12
