Go to file
Eugeniy Paltsev 9858893ea8 ARC: runner: mdb: tweak searching for cld process pid
mdb binary starts several subproceses and one of them is cld process.
In runners/mdb.py we record process id of cld on each mdb launch
to terminate simulator correctly later. However we can finish test
and terminate mdb before the cld process was found (so cld won't
be terminated correctly by sanitycheck infrastructure). It may happen
if we launch mdb on fast host machine.

That leads to several issues. First of all we get ugly error in
sanitycheck output:
------------------------>8--------------------------------
FileNotFoundError: [Errno 2] No such file or directory: '/xxxx/mdb.pid'
------------------------>8--------------------------------

Secondly (and it's more important) we terminate simulator incorrectly.
We terminate mdb leaving cld process alive, running and consuming one
cpu core permanently (until we kill it manually)

So, let's increase granularity of lookups and don't wait extra 0.5
seconds before the first lookup.

Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
2020-12-02 14:08:26 -05:00
.buildkite Revert "BK: Tmp increase number of jobs (DNM)" 2020-11-17 07:47:50 -06:00
.github actions: manifest: Update to latest action revision 2020-11-27 20:12:46 +01:00
.known-issues doc: update known-issues for Sphinx==3.3.0 2020-11-03 15:27:37 +01:00
arch arch: arm: aarch32:cortex_m: timing.c: cortex M7 may need DWT unlock 2020-12-02 10:58:08 +02:00
boards boards: arm: sam4l_ek: Enable gpio tests 2020-12-02 11:48:43 -06:00
cmake cmake: manual handling of CMakeCheckCompilerFlag.cmake inclusion 2020-12-01 08:46:41 -06:00
doc devicetree: gpio: provide accessors for controller phandle 2020-12-01 15:19:22 -05:00
drivers drivers: gpio: sam: Add sam4l SoC support 2020-12-02 11:48:43 -06:00
dts dts: gpio: Add atmel sam4l GPIO bindings 2020-12-02 11:48:43 -06:00
include shell: api description update 2020-12-02 08:07:55 -05:00
kernel kernel: Add K_DELAYED_WORK_DEFINE 2020-11-27 20:08:30 -05:00
lib lib/os/heap: minimize initial overallocation in the aligned case 2020-11-30 14:50:07 -05:00
misc
modules modules: tfm: add required selection and dependencies 2020-12-01 14:19:03 +02:00
samples Samples: Add SMP pktqueue application 2020-12-02 07:09:21 -05:00
scripts ARC: runner: mdb: tweak searching for cld process pid 2020-12-02 14:08:26 -05:00
share
soc drivers: gpio: sam: Add sam4l SoC support 2020-12-02 11:48:43 -06:00
subsys bluetooth: controller: nrf: Provide info about used DPPI resources 2020-12-02 16:44:40 +01:00
tests drivers: modem: Add support for quectel bg95 2020-12-01 17:43:59 -05:00
.checkpatch.conf checkpatch: disable PREFER_SECTION 2020-10-30 15:51:46 +01:00
.clang-format
.codecov.yml
.editorconfig
.gitattributes
.gitignore
.gitlint
.mailmap
.uncrustify.cfg
CMakeLists.txt kernel: add common bits to support TLS 2020-10-24 10:52:00 -07:00
CODE_OF_CONDUCT.md
CODEOWNERS CODEOWNERS: add code owners for Kconfig.tfm 2020-12-01 14:19:03 +02:00
CONTRIBUTING.rst
Kconfig
Kconfig.zephyr cmake: ensure shields can be placed in other BOARD_ROOTs 2020-11-13 13:36:48 +01:00
LICENSE
MAINTAINERS.yml MAINTAINERS: Add myself to watchdog collaborators. 2020-12-02 07:52:39 -06:00
Makefile
README.rst
VERSION release: Update patch level to 99 after the 2.4.0 release 2020-09-27 15:15:49 -05:00
version.h.in
west.yml bluetooth: controller: nrf: Provide info about used DPPI resources 2020-12-02 16:44:40 +01:00
zephyr-env.cmd
zephyr-env.sh

.. 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>
   <a href="https://buildkite.com/zephyr/zephyr">
   <img
   src="https://badge.buildkite.com/f5bd0dc88306cee17c9b38e78d11bb74a6291e3f40e7d13f31.svg?branch=master"></a>


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.

.. _project-resources:

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://github.com/zephyrproject-rtos/zephyr/releases
* **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/index.html
.. _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