Kconfig - Revision history

Ted: Clean up errant text.

2025-08-25T15:42:03Z

Clean up errant text.

Ted: Add and explain shell script to find duplicate Kconfig symbols across two overlay files.

2025-08-25T15:41:37Z

Add and explain shell script to find duplicate Kconfig symbols across two overlay files.

Ted: Add link to Satisfiability Solvers document

2025-08-25T15:34:05Z

Add link to Satisfiability Solvers document

Ted: /* ^ Starting Points and Good References */

2025-08-25T15:29:14Z

^ Starting Points and Good References

Ted: Minor formatting.

2025-08-25T15:28:49Z

Minor formatting.

Ted: Update section "Kconfig references"

2025-08-25T15:27:59Z

Update section "Kconfig references"

Ted: /* ^ Starting Points and Good References */

2025-08-25T15:14:27Z

^ Starting Points and Good References

Ted: /* ^ Kconfig Build Time Artifacts */

2025-07-21T19:59:34Z

^ Kconfig Build Time Artifacts

Ted: Add subsection "Kconfig select to conditionally set symbol"

2023-07-19T22:00:48Z

Add subsection "Kconfig select to conditionally set symbol"

Ted: /* ^ To Invoke Menuconfig From Other Than Project Root */ - add content

2023-05-12T18:52:08Z

^ To Invoke Menuconfig From Other Than Project Root: - add content

@@ Line 339: / Line 339: @@
 exit $?
 </pre>
 <!-- comment -->

← Older revision		Revision as of 15:41, 25 August 2025
Line 319:		Line 319:

	Ahh and from this we see token `zephyr,sram-cpu1-partition` is not a device tree alias but rather a "Zephyr chosen". This looks like it may be similar to a device tree alias. Must confirm . . .		Ahh and from this we see token `zephyr,sram-cpu1-partition` is not a device tree alias but rather a "Zephyr chosen". This looks like it may be similar to a device tree alias. Must confirm . . .
		+
		+	2025-08-25
		+
		+	Script to find duplicate symbols in Kconfig overlay. Compares tokens between two Kconfig overlay files. Searches for CONFIG_ pattern in first file, builds a list of tokens with that beginning pattern, search second overlay for each symbol in turn.
		+
		+	<pre>
		+	1 #!/bin/bash
		+	2
		+	3 KCONFIG_OVERLAY_TO_CHECK="../prj.conf"
		+	4
		+	5 for token in `grep '^CONFIG_' ./prj.conf`
		+	6 do
		+	7 # echo "found token ${token}"
		+	8 symbol=`echo ${token} \| cut -d "=" -f 1`
		+	9 echo "checking for symbol ${symbol} . . ."
		+	10 grep -n ${symbol} ${KCONFIG_OVERLAY_TO_CHECK}
		+	11 done
		+	12
		+	13 exit $?
		+	</pre>
		+
		+
		+	Script to

	<!-- comment -->		<!-- comment -->

@@ Line 47: / Line 47: @@
 A different section format . . .
-<ul>
 (1) https://docs.zephyrproject.org/latest/build/kconfig/tips.html<br />
@@ Line 57: / Line 57: @@
 (5) https://docs.kernel.org/kbuild/kconfig-language.html<br />
-</ul>
 <!-- comment -->

@@ Line 48: / Line 48: @@
 A different section format . . .
 <ul>
-(1) https://docs.zephyrproject.org/latest/build/kconfig/tips.html
+(1) https://docs.zephyrproject.org/latest/build/kconfig/tips.html<br />
-(2) https://github.com/ulfalizer/Kconfiglib/issues/38
+(2) https://github.com/ulfalizer/Kconfiglib/issues/38<br />
-(3) [https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/guides/build/kconfig/menuconfig.html Interactive Kconfig Interfaces]
+(3) [https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/guides/build/kconfig/menuconfig.html Interactive Kconfig Interfaces]<br />
-(4) https://interrupt.memfault.com/blog/practical_zephyr_kconfig
+(4) https://interrupt.memfault.com/blog/practical_zephyr_kconfig<br />
-(5) https://docs.kernel.org/kbuild/kconfig-language.html
+(5) https://docs.kernel.org/kbuild/kconfig-language.html<br />
 </ul>
 <!-- comment -->

@@ Line 49: / Line 49: @@
 <ul>
 (1) https://docs.zephyrproject.org/latest/build/kconfig/tips.html
 (2) https://github.com/ulfalizer/Kconfiglib/issues/38
 (3) [https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/guides/build/kconfig/menuconfig.html Interactive Kconfig Interfaces]
 (4) https://interrupt.memfault.com/blog/practical_zephyr_kconfig
 (5) https://docs.kernel.org/kbuild/kconfig-language.html
 </ul>

← Older revision		Revision as of 15:27, 25 August 2025
Line 42:		Line 42:

	(4) https://interrupt.memfault.com/blog/practical_zephyr_kconfig		(4) https://interrupt.memfault.com/blog/practical_zephyr_kconfig
		+	(5) https://docs.kernel.org/kbuild/kconfig-language.html

		+	----------
		+
		+	A different section format . . .
		+	<ul>
		+	(1) https://docs.zephyrproject.org/latest/build/kconfig/tips.html
		+	(2) https://github.com/ulfalizer/Kconfiglib/issues/38
		+	(3) [https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/guides/build/kconfig/menuconfig.html Interactive Kconfig Interfaces]
		+	(4) https://interrupt.memfault.com/blog/practical_zephyr_kconfig
		+	(5) https://docs.kernel.org/kbuild/kconfig-language.html
		+	</ul>
	<!-- comment -->		<!-- comment -->

@@ Line 27: / Line 27: @@
 This Zephyr documentation page is linked in [https://github.com/ulfalizer/Kconfiglib Ulf Magnusson's kconfiglib homepage] on Github.  This homepage looks to be a good starting point for a full and in depth reading about this Kconfig parser and code generator tool set.
+[ ] Need to revisit this link to identify its specific topics . . .
 *  https://github.com/ulfalizer/Kconfiglib/issues/38
@@ Line 40: / Line 39: @@
 Above Kconfig articles linked to from https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/guides/build/index.html#kconfig.
 <!-- comment -->

← Older revision		Revision as of 19:59, 21 July 2025
Line 147:		Line 147:
	include sources.txt		include sources.txt

		+	2025-07-21 lunes
		+
		+	In addition to a summary report in file of the Kconfig fragments read and parsed at build time, two generated files which combine all project Kconfig are:
		+
		+	(1) build/[effective_top_level_project]/zephyr/.config
		+
		+	(2) build/[effective_top_level_project]/zephyr/include/generated/zephyr/autoconf.h
		+
		+	We note here "effective" top level project because, in Cmake orchestrated projects there can and often are multiple projects in the cmake sense, but only one them is the starting point for cmake's project configuration process. That starting directory in the project may include cmake scripts in parent directories, and thus likely includes other projects which directory wise appear closer to the overall project's directory tree root.
		+
		+	In this discussion "project" has two senses: (1) a project with various sources and directories which taken together build one or more executables, and (2) a project in the sense that cmake supports and recognizes grouping of source files which can be built in customized ways but may not produce a complete executable.

	<!-- comment -->		<!-- comment -->

← Older revision		Revision as of 22:00, 19 July 2023
Line 131:		Line 131:

	<!-- comment -->		<!-- comment -->
		+
		+	=== [[#top\|^]] Kconfig select to conditionally set symbol ===
		+
		+	Kconfig's `select` keyword must be used carefully. It is however used in several Zephyr RTOS out-of-tree drivers for sensors which can be attached, one at a time, to two or more types of communications bus. In a local Zephyr source tree some of these examples may be located by running the following recursive grep search:
		+
		+	$ ~/local_path_to_zephyr_project_root/zephyr$ grep -nr 'select I2C if'
		+
		+	<!-- odne komentar -->

	== [[#top\|^]] Kconfig Build Time Artifacts ==		== [[#top\|^]] Kconfig Build Time Artifacts ==

← Older revision		Revision as of 18:52, 12 May 2023
Line 64:		Line 64:

	In this command invocation "target_board" is one of Zephyr's supported boards, and or possibly Nordic Semi ncs supported boards, or a custom board of the reader's own making. Zephyr supported ARM based boards are located in `[west_workspace]/zephyr/boards/arm`. A few common name examples of these boards include `lpcxpresso55s69`, `nrf9160dk_nrf9160` and `sparkfun_thing_plus_nrf9160`.		In this command invocation "target_board" is one of Zephyr's supported boards, and or possibly Nordic Semi ncs supported boards, or a custom board of the reader's own making. Zephyr supported ARM based boards are located in `[west_workspace]/zephyr/boards/arm`. A few common name examples of these boards include `lpcxpresso55s69`, `nrf9160dk_nrf9160` and `sparkfun_thing_plus_nrf9160`.
		+
		+	Note also that the `BOARD_ROOT` path value passed along to cmake and not to `west` itself, may vary depending upon a given project's structure. Single core Zephyr apps generally have a simpler directory structure, while dual-core and multi-core Zephyr apps often have additional directory trees to organize firmware projects for secondary and successive cores. Sometimes the board root relative path will be just one parent directory from the current working directory. [NEED: to give example project and invocation paths showing how BOARD_ROOT is chosen.]

	In case you are targeting a board or circuit design of your own, then you likely know what you're doing and what this argument needs to express.		In case you are targeting a board or circuit design of your own, then you likely know what you're doing and what this argument needs to express.