Go to file
David B. Kinder 60136f00cb doc: add how to exit from QEMU in samples
While trying out the hello_world sample built for QEMU, I was expecting
the sample app to exit and I'd return to a command prompt.  Nope.  You
need to exit QEMU manually, so add that step to the sample instructions.
Looking around, there are more uses of QEMU like this that could use
this added step after running the sample app.

Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
2019-09-02 12:06:08 -04:00
.github/ISSUE_TEMPLATE templates: Update issue templates 2018-12-07 08:27:20 -05:00
.known-issues doc: introduce final structure 2019-02-05 07:04:40 -05:00
arch arc: interrupts: Explain return from interrupt to cooperative thread 2019-08-30 20:10:14 +02:00
boards doc: add how to exit from QEMU in samples 2019-09-02 12:06:08 -04:00
cmake cmake: Bump min version to 0.10.3 2019-08-19 11:06:55 -05:00
doc doc: add how to exit from QEMU in samples 2019-09-02 12:06:08 -04:00
drivers drivers: uart: Properly configure pins in NRF UARTE power management 2019-08-28 14:04:18 +02:00
dts dts: binding-template.yaml: Fix 'parent/child: bus:' description 2019-09-01 08:58:58 -05:00
ext ext: hal: Make NXP HALs a Zephyr module 2019-08-21 21:05:23 -04:00
include doc: fix doxygen briefs for k_object_xxx APIs 2019-08-30 13:55:38 +02:00
kernel kernel: ignore z_fatal_halt() from code coverage 2019-08-24 23:40:22 +02:00
lib libc: Make libc-nano default for ARM toolchain if newlib 2019-08-28 10:59:29 -05:00
misc license: cleanup: add SPDX Apache-2.0 license identifier 2019-04-07 08:45:22 -04:00
modules ext: hal: Make NXP HALs a Zephyr module 2019-08-21 21:05:23 -04:00
samples doc: add how to exit from QEMU in samples 2019-09-02 12:06:08 -04:00
scripts scripts: elf_helper.py: fix stack declared K_THREAD_STACK_EXTERN 2019-08-29 08:18:54 -04:00
soc soc: arm: ti_simplelink: Fix number of interrupt lines on CC3220SF 2019-08-23 22:39:45 +02:00
subsys nvs: Fix deletion of the last entry added 2019-09-02 12:31:42 +02:00
tests tests/subsys/fs/nvs: extend entry delete test 2019-09-02 12:31:42 +02:00
.checkpatch.conf scripts/checkpatch.pl: fix root dir detection and enable it 2019-05-22 12:40:20 -04:00
.clang-format
.codecov.yml
.editorconfig editorconfig: Set insert_final_newline true 2019-04-10 14:15:38 +02:00
.gitattributes
.gitignore gitignore: ignore Emacs TAGS file 2019-06-27 07:18:35 -04:00
.gitlint gitlint: match max title length restriction with checkpatch 2019-05-29 14:43:16 -04:00
.mailmap mailmap: Fix entry needing both name and email replace 2019-06-26 13:54:03 -04:00
.shippable.yml ci: use v0.9 docker image 2019-08-25 17:47:00 -04:00
.uncrustify.cfg
CMakeLists.txt cmake: Build HEX files if flash runner is openocd 2019-08-16 13:41:56 -05:00
CODE_OF_CONDUCT.md coc: move to markdown format 2019-01-24 15:37:15 -05:00
CODEOWNERS ext: hal: Make NXP HALs a Zephyr module 2019-08-21 21:05:23 -04:00
CONTRIBUTING.rst doc: Fixed a link in CONTRIBUTING.rst 2019-02-28 12:46:04 -08:00
Kconfig
Kconfig.zephyr kconfig: fix name of cmake function in help text 2019-08-15 08:55:45 -04:00
LICENSE
Makefile doc: add clean target to Makefile 2019-02-05 16:58:14 -05:00
README.rst doc: Update Slack invitation link 2019-08-05 16:52:15 +02:00
VERSION release: Zephyr 2.0.0-rc2 2019-08-29 09:16:39 +02:00
version.h.in cmake: explain BUILD_VERSION and KERNEL_VERSION_* 2019-05-09 11:52:05 +02:00
west.yml manifest: update to use mbedTLS v2.16.2 2019-08-28 20:34:06 +02:00
zephyr-env.cmd scripts: remove west from scripts/ 2019-01-29 10:15:01 +01:00
zephyr-env.sh env: ignore unset var 2019-05-20 09:26:31 -04:00

.. 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
***************

Welcome to Zephyr! See the `Introduction to Zephyr`_ for a high-level overview,
and the documentation's `Getting Started Guide`_ to start developing.

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

Community support is provided via mailing lists and Slack; see the Resources
below for details.

Resources
*********

Here's a quick summary of resources to help you find your way around:

* **Help**: `Asking for Help Tips`_
* **Documentation**: http://docs.zephyrproject.org (`Getting Started Guide`_)
* **Source Code**: https://github.com/zephyrproject-rtos/zephyr is the main
  repository; https://elixir.bootlin.com/zephyr/latest/source contains a
  searchable index
* **Releases**: https://zephyrproject.org/developers/#downloads
* **Samples and example code**: see `Sample and Demo Code Examples`_
* **Mailing Lists**: users@lists.zephyrproject.org and
  devel@lists.zephyrproject.org are the main user and developer mailing lists,
  respectively. You can join the developer's list and search its archives at
  `Zephyr Development mailing list`_. The other `Zephyr mailing list
  subgroups`_ have their own archives and sign-up pages.
* **Nightly CI Build Status**: https://lists.zephyrproject.org/g/builds
  The builds@lists.zephyrproject.org mailing list archives the CI
  (shippable) nightly build results.
* **Chat**: Zephyr's Slack workspace is https://zephyrproject.slack.com.  Use
  this `Slack Invite`_ to register.
* **Contributing**: see the `Contribution Guide`_
* **Wiki**: `Zephyr GitHub wiki`_
* **Issues**: https://github.com/zephyrproject-rtos/zephyr/issues
* **Security Issues**: Email vulnerabilities@zephyrproject.org to report
  security issues; also see our `Security`_ documentation. Security issues are
  tracked separately at https://zephyrprojectsec.atlassian.net.
* **Zephyr Project Website**: https://zephyrproject.org

.. _Slack Invite: https://tinyurl.com/y5glwylp
.. _supported boards: http://docs.zephyrproject.org/latest/boards
.. _Zephyr Documentation: http://docs.zephyrproject.org
.. _Introduction to Zephyr: http://docs.zephyrproject.org/latest/introduction/index.html
.. _Getting Started Guide: http://docs.zephyrproject.org/latest/getting_started/index.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/index.html
.. _Security: http://docs.zephyrproject.org/latest/security/index.html
.. _Asking for Help Tips: https://docs.zephyrproject.org/latest/guides/getting-help.html