Different behavior with and without --sysbuild

[gwa-simon]

I am porting my application from zephyr 3.5 to 3.7 and I have updated the boards structure according to the new standards. My project folder structure looks something like the following:

<home>
├── boards/plank
|	├── board.yml
|	├── plank_0_5_0_defconfig        
|	├── plank_0_5_0.overlay          
|	├── plank.dts    
|	├── plank.yml  
|	├── Kconfig.defconfig
|	├── Kconfig.plank
|	└── plank_defconfig 
|
├── app
	├── CMakeLists.txt
	├── prj.conf
	├── sysbuild.conf
	└── sysbuild
    		└── mcuboot.conf

I have revisions for my board and since it allows to add configuration linked to boards on the boards folder, I have done so by moving some config that I had previously in prj.conf to plank_defconfig and plank_0_5_0_defconfig.

If I run west build -p always -b [email protected] \app it works perfectly, even if I select other revisions.

But my problem starts when I try running it with sysbuild. If I run west build -p always -b [email protected] \app --sysbuild the compilation works for mcuboot, but fails for my application because the Kconfigs get messed up. It complains that s dependencies for configs in the board folder are missing (this dependencies are defined in the prj.conf).

Therefore my question is, what is the right procedure to use sysbuild while having board revisions and sub-configs defined at boards folder?

[nordicjm]

The board folder like that only works for applications, not sysbuild (since sysbuild itself is actually an application), you would need to add your board root in a module file e.g. see example application here https://github.com/zephyrproject-rtos/example-application/blob/main/zephyr/module.yml#L16

[gwa-simon]

Hello @nordicjm, thanks for the fast answer.

Although I already have my board as a module imported by west and in the app module.yml I have the config as following, since my boards modules is 2 levels above the app:

build:
  settings:
    board_root: ..
    dts_root: ..

The dts and overlay it can find, it just can not link both prj.conf and board specific configs (plank_0_5_0_defconfig) to the final configs at the same time.

[nordicjm]

the only place a module.yml file can go is zephyr/module.yml from the root directory of the git repo, and it needs to be either the manifest repo itself or a module referenced in a west manifest

[gwa-simon]

Yes, I have the module.yml inside a zephyr folder for the main project and on my modules.

Hmm, now I noticed I don't have it on the boards module because I point to it in the CMakeLists. Should I have a zephyr/module.yml also in my boards folder?

[nordicjm]

it should be in your boards repo yes, since the folder has to be named boards for the build system to find it and having a boards folder inside of a boards folder isn't ideal, you should have this in your board folder zephyr/module.yml file:

build:
  settings:
    board_root: ..

[gwa-simon]

Thanks for the tip, I did it and I was able to remove an include in my CMakeLists. But I still have my initial problem.
An example, I have CONFIG_SENSOR=y in my prj.conf file and in my boards module I have my sensors enabled on the plank_defconfig (e.g. CONFIG_SHT3XD=y).

With normal application it builds fine, but with sysbuild it does not see CONFIG_SENSOR=y when including CONFIG_SHT3XD=y

warning: SHT3XD (defined at drivers/sensor/sensirion/sht3xd/Kconfig:6) was assigned the value 'y'
but got the value 'n'. Check these unsatisfied dependencies: SENSOR (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_SHT3XD and/or look up SHT3XD in the
menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration Values,
and Kconfig - Tips and Best Practices sections of the manual might be helpful too.

Although, if I look in the autoconf.h, it is there:

Aaaa, now I notice something, the warning is while building the mcuboot, where the prj.conf is not included, but the plank_defconfig (I guess), generating the dependency error, even dough I don't need this on the mcuboot.

If it is a hardware related config, that can change with the revision, but is needed only in the app, and not in the mcuboot, where is the best place to add the CONFIG_xx?

[gwa-simon]

So it turns out that the dependency warning is only for the mcuboot build, and does not really affect it. My real problem is that while sysbuild builds the app my own modules are not finding the CONFIGs definitions

But CONFIG_SENSOR_LOG_LEVEL is present on the app/autoconf.h, so it looks the module is not including this definitions

[nordicjm]

Having a sensor enabled in a board defconfig is frankly wrong, if a project needs it, the project should enable it in the prj.conf (or boards/<board>.conf)

[gwa-simon]

Thanks @nordicjm for the tips.

I have updated my code to enable the sensors in the prj.conf and added to my own drivers the dependency to DT_HAS_'SENSOR'_ENABLED, so that the config changes automatically when I have different overlay compiled.

But I am still having the problem to find the CONFIG_SENSOR_LOG_LEVEL on my drivers when I build with --sysbuild

Any idea why would my drivers not find the CONFIG_SENSOR_LOG_LEVEL definition when I build with --sysbuild?

[gwa-simon]

I have my app config defined in the prj.conf and with sysbuild it is added to app/zephyr/include/zephyr/autoconf.h. But it looks my drivers are referencing the path from the mcuboot config (mcuboot/zephyr/include/zephyr/autoconf.h) while building the app, where CONFIG_SENSOR_LOG_LEVEL is no defined. Why would it happen?