Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures.
Go to file
Alexander Wachter 7b1e9e9b34 drivers: hwinfo: Add shell command for device id
This commit adds support for device id shell command.
Example:
uart:~$ hwinfo devid
Length: 12
ID: 0x1b0320d51485330313420

Signed-off-by: Alexander Wachter <alexander.wachter@student.tugraz.at>
2019-02-04 14:53:50 -05:00
.github/ISSUE_TEMPLATE templates: Update issue templates 2018-12-07 08:27:20 -05:00
.known-issues doc: add peripherals reference 2019-01-30 18:38:48 -05:00
arch arch: posix: Bugfix in POSIX cheats header 2019-02-03 13:16:30 -05:00
boards disk: sdhc: Convert to new DT_<COMPAT>_<INSTANCE> defines 2019-02-04 00:52:32 -05:00
cmake cmake: Run dts before kconfig 2019-02-01 10:16:06 -06:00
doc doc: subsystem: nvs Added troubleshooting paragraph 2019-02-02 10:28:46 -05:00
drivers drivers: hwinfo: Add shell command for device id 2019-02-04 14:53:50 -05:00
dts display: ssd1673: add support for ssd16xx monochrome controllers 2019-02-02 10:28:11 -05:00
ext debug: CTF Tracing with POSIX backend 2019-02-01 08:56:02 -05:00
include power: Make power_state enum global 2019-02-04 13:36:29 +01:00
kernel kernel/sched: CPU mask affinity/pinning API 2019-02-01 21:37:24 -05:00
lib misc: assert_post_action: Treat POSIX arch like others 2019-02-03 10:28:51 -08:00
misc printk: move into lib/os 2019-01-22 07:45:22 -05:00
samples samples: watchdog: Remove stm32 iwdg sample 2019-02-01 19:16:59 -05:00
scripts sanitycheck: coverage: Tolerate missing source files 2019-02-03 15:28:53 -05:00
soc power: Remove sys_is_valid_power_state() interface 2019-02-04 18:08:47 +01:00
subsys power: Remove sys_is_valid_power_state() interface 2019-02-04 18:08:47 +01:00
tests drivers: hwinfo: Add shell command for device id 2019-02-04 14:53:50 -05:00
.checkpatch.conf
.clang-format clang-format: add support for clang-format 2018-11-19 09:31:44 -05:00
.codecov.yml
.gitattributes
.gitignore gitignore: ignore IDE files 2018-11-21 15:05:07 +01:00
.gitlint gitlint: do not start with subsys: 2018-11-28 09:22:01 -08:00
.mailmap
.shippable.yml ci: do not send CI messages to slack 2019-02-01 19:04:55 -05:00
.uncrustify.cfg
CMakeLists.txt Build: Offsets lib as OBJECT not STATIC 2019-02-04 13:14:09 -05:00
CODEOWNERS CODEOWNERS: Add @pfalcon for POSIX-related things 2019-02-01 05:28:55 -06:00
CODE_OF_CONDUCT.md coc: move to markdown format 2019-01-24 15:37:15 -05:00
CONTRIBUTING.rst
Kconfig
Kconfig.zephyr dts: stop generating CONFIG_FLASH_LOAD_{OFFSET,SIZE} 2019-02-01 10:16:06 -06:00
LICENSE
Makefile doc: turbo mode for kconfig options 2019-01-23 16:26:19 -05:00
README.rst doc: fix link to contribution guide 2019-01-30 18:38:48 -05:00
VERSION
version.h.in
west.yml west: add west.yml 2019-01-29 10:15:01 +01:00
zephyr-env.cmd scripts: remove west from scripts/ 2019-01-29 10:15:01 +01:00
zephyr-env.sh shell: Piped output of cd to /dev/null when setting ZEPHYR_BASE. 2018-12-06 19:14:50 -05:00

README.rst

.. raw:: html

   <a href="https://www.zephyrproject.org">
     <p align="center">
       <img src="doc/images/Zephyr-Project.png">
     </p>
   </a>

   <a href="https://bestpractices.coreinfrastructure.org/projects/74"><img
   src="https://bestpractices.coreinfrastructure.org/projects/74/badge"></a>
   <img
   src="https://api.shippable.com/projects/58ffb2b8baa5e307002e1d79/badge?branch=master">


The Zephyr Project is a scalable real-time operating system (RTOS) supporting
multiple hardware architectures, optimized for resource constrained devices,
and built with security in mind.

The Zephyr OS is based on a small-footprint kernel designed for use on
resource-constrained systems: from simple embedded environmental sensors and
LED wearables to sophisticated smart watches and IoT wireless gateways.

The Zephyr kernel supports multiple architectures, including ARM Cortex-M,
Intel x86, ARC, Nios II, Tensilica Xtensa, and RISC-V, and a large number of
`supported boards`_.

.. below included in doc/introduction/introduction.rst

.. start_include_here

Getting Started
***************

To start developing Zephyr applications refer to the `Getting Started Guide`_
in the `Zephyr Documentation`_ pages.
A brief introduction to Zephyr can be found in the  `Zephyr Introduction`_
page.

Community Support
*****************

The Zephyr Project Developer Community includes developers from member
organizations and the general community all joining in the development of
software within the Zephyr Project. Members contribute and discuss ideas,
submit bugs and bug fixes, and provide training. They also help those in need
through the community's forums such as mailing lists and IRC channels. Anyone
can join the developer community and the community is always willing to help
its members and the User Community to get the most out of the Zephyr Project.

Welcome to the Zephyr community!

Resources
*********

Here's a quick summary of resources to find your way around the Zephyr Project
support systems:

* **Zephyr Project Website**: The https://zephyrproject.org website is the
  central source of information about the Zephyr Project. On this site, you'll
  find background and current information about the project as well as all the
  relevant links to project material.

* **Releases**: Source code for Zephyr kernel releases are available at
  https://zephyrproject.org/developers/#downloads. On this page,
  you'll find release information, and links to download or clone source
  code from our GitHub repository.  You'll also find links for the Zephyr
  SDK, a moderated collection of tools and libraries used to develop your
  applications.

* **Source Code in GitHub**: Zephyr Project source code is maintained on a
  public GitHub repository at https://github.com/zephyrproject-rtos/zephyr.
  You'll find information about getting access to the repository and how to
  contribute to the project in this `Contribution Guide`_ document.

* **Samples Code**: In addition to the kernel source code, there are also
  many documented `Sample and Demo Code Examples`_ that can help show you
  how to use Zephyr services and subsystems.

* **Documentation**: Extensive Project technical documentation is developed
  along with the Zephyr kernel itself, and can be found at
  http://docs.zephyrproject.org.  Additional documentation is maintained in
  the `Zephyr GitHub wiki`_.

* **Cross-reference**: Source code cross-reference for the Zephyr
  kernel and samples code is available at
  https://elixir.bootlin.com/zephyr/latest/source.

* **Issue Reporting and Tracking**: Requirements and Issue tracking is done in
  the Github issues system: https://github.com/zephyrproject-rtos/zephyr/issues.
  You can browse through the reported issues and submit issues of your own.

* **Security-related Issue Reporting and Tracking**: For security-related
  inquiries or reporting suspected security-related bugs in the Zephyr OS,
  please send email to vulnerabilities@zephyrproject.org.  We will assess and
  fix flaws according to our security policy outlined in the Zephyr Project
  `Security Overview`_.

  Security related issue tracking is done in JIRA.  The location of this JIRA
  is https://zephyrprojectsec.atlassian.net.

* **Mailing List**: The `Zephyr Development mailing list`_ is perhaps the most convenient
  way to track developer discussions and to ask your own support questions to
  the Zephyr project community.  There are also specific `Zephyr mailing list
  subgroups`_ for announcements, builds, marketing, and Technical
  Steering Committee notes, for example.
  You can read through the message archives to follow
  past posts and discussions, a good thing to do to discover more about the
  Zephyr project.

* **Chatting**: You can chat online with the Zephyr project developer
  community and other users in two ways:

  * On `Slack`_: Zephyr has dedicated channels on Slack. To register, use the
    following `Slack Invite`_.

  * IRC channel #zephyrproject on the freenode.net IRC server. You can use the
    http://webchat.freenode.net web client or use a client-side application such
    as pidgin (Note that all discussions have moved to Slack, although we still
    have many developers still available on the IRC channel).

.. _Slack Invite: https://tinyurl.com/yarkuemx
.. _Slack: https://zephyrproject.slack.com
.. _supported boards: http://docs.zephyrproject.org/latest/boards/boards.html
.. _Zephyr Documentation: http://docs.zephyrproject.org
.. _Zephyr Introduction: http://docs.zephyrproject.org/latest/introduction/introducing_zephyr.html
.. _Getting Started Guide: http://docs.zephyrproject.org/latest/getting_started/getting_started.html
.. _Contribution Guide: http://docs.zephyrproject.org/latest/contribute/index.html
.. _Zephyr GitHub wiki: https://github.com/zephyrproject-rtos/zephyr/wiki
.. _Zephyr Development mailing list: https://lists.zephyrproject.org/g/devel
.. _Zephyr mailing list subgroups: https://lists.zephyrproject.org/g/main/subgroups
.. _Sample and Demo Code Examples: http://docs.zephyrproject.org/latest/samples/samples.html
.. _Security Overview: http://docs.zephyrproject.org/latest/security/security-overview.html