Support

Search this documentation before you report a problem. When you open a report, include enough information for another developer to reproduce the problem. If the problem affects security, do not report it in a public bug: follow How to report a security vulnerability instead.

Technical problems

Include this information in a technical report:

  • The source tag:

    $ git -C zephyr-manifest describe --tags --exact-match
    
  • The Zephyr repository revision:

    $ git -C zephyr rev-parse HEAD
    
  • The output of workshop info:

    $ workshop info zephyr-26-10
    
  • The board name and board revision.

  • The complete command that failed.

  • The complete error output as text.

  • A small application that reproduces the problem, when possible.

File public source defects in the Zephyr RTOS Launchpad bug tracker.

See also

Explanation:

How-to guides:

Reference: