[riot-notifications] [RIOT-OS/RIOT] cpu/stm32/kconfig: fix rtt/rtc error symbol (#15834)
notifications at github.com
Fri Jan 22 18:49:35 CET 2021
> > It should have a defined value, which is the string indicating the error.
> I tried with nucleo-l073rz and iotlab-m3 and I can find the `ERROR_MODULE_CONFLICT` symbol for both and in both cases it's empty (`ERROR_MODULE_CONFLICT(=)`. I doesn't seem to be correct, I would expect the value set to 1 for iotlab-m3.
> I tried `TEST_KCONFIG=1 make BOARD=iotlab-m3 -C examples/hello-world menuconfig` with the following diff:
> diff --git a/examples/hello-world/Makefile b/examples/hello-world/Makefile
> index 258d8e9baf..a860204823 100644
> --- a/examples/hello-world/Makefile
> +++ b/examples/hello-world/Makefile
> @@ -12,6 +12,8 @@ RIOTBASE ?= $(CURDIR)/../..
> # development process:
> DEVELHELP ?= 1
> +FEATURES_REQUIRED = periph_rtt periph_rtc
> # Change this to 0 show compiler invocation lines by default:
> QUIET ?= 1
But when the dependency modelling of Kconfig is used (`TEST_KCONFIG=1`), you need to enable the peripheral modules via Kconfig. Either in menuconfig or a `.config` file. In menuconfig navigate to `Drivers -> Peripheral drivers` and you'll see `RTC peripheral driver` and `RTT peripheral driver`. In addition an error comment should appear in the 'root' of menuconfig:
*** !! ERROR: There are conflicting modules active !! ***
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications