1---
2name: Bug report
3about: Create a report to help us improve Zephyr
4title: ''
5labels: bug
6assignees: ''
7
8---
9<!--
10**Notes**
11Github Discussions (https://github.com/zephyrproject-rtos/zephyr/discussions)
12are available to first verify that the issue is a genuine Zephyr bug and not a
13consequence of Zephyr services misuse.
14
15This 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
17fork (such as NCS) specific feature, please open an issue in the fork project
18instead.
19-->
20
21**Describe the bug**
22<!--
23A clear and concise description of what the bug is.
24
25Please also mention any information which could help others to understand
26the problem you're facing:
27 - What target platform are you using?
28 - What have you tried to diagnose or workaround this issue?
29 - Is this a regression? If yes, have you been able to "git bisect" it to a
30   specific commit?
31 - ...
32-->
33
34**To Reproduce**
35<!--
36Steps to reproduce the behavior:
371. mkdir build; cd build
382. cmake -DBOARD=board\_xyz
393. make
404. See error
41-->
42
43**Expected behavior**
44<!--
45A clear and concise description of what you expected to happen.
46-->
47
48**Impact**
49<!--
50What impact does this issue have on your progress (e.g., annoyance, showstopper)
51-->
52
53**Logs and console output**
54<!--
55If applicable, add console logs or other types of debug information
56e.g Wireshark capture or Logic analyzer capture (upload in zip archive).
57copy-and-paste text and put a code fence (\`\`\`) before and after, to help
58explain the issue. (if unable to obtain text log, add a screenshot)
59-->
60
61**Environment (please complete the following information):**
62
63 - OS: (e.g. Linux, MacOS, Windows)
64 - Toolchain (e.g Zephyr SDK, ...)
65 - Commit SHA or Version used
66
67**Additional context**
68<!--
69Add any other context that could be relevant to your issue, such as pin setting,
70target configuration, ...
71-->
72