Build fail using MCUBOOT and SPI on ncs 1.7.1

RE: Build fail using MCUBOOT and SPI on ncs 1.7.1

Håkon Alseth — Thu, 16 Dec 2021 13:20:29 GMT

Hi Eva,

[quote user="eva_c"]Unselecting spi and i2c configs in mcuboot.conf solves the problem, thank you![/quote]

I'm glad to hear!

[quote user="eva_c"]If I understand correctly, configs in the prj.conf affect only application, while configs in defconfig files are applied to both application and MCUBoot. Due to nature of this project with several board configurations, we have many configs placed in defconfig files. Is it possible to have defconfig file that does not affects MCUBoot?[/quote]

You can add a conditional on "depends on !MCUBOOT" for the specific sensor, and set this up in your board in a similar fashion as done in the nrf9160dk:

https://github.com/nrfconnect/sdk-zephyr/blob/v2.7.0-ncs1/boards/arm/nrf9160dk_nrf9160/Kconfig.defconfig#L58-L59

Kind regards,

Håkon

RE: Build fail using MCUBOOT and SPI on ncs 1.7.1

eva_c — Wed, 15 Dec 2021 08:57:56 GMT

Unselecting spi and i2c configs in mcuboot.conf solves the problem, thank you!

If I understand correctly, configs in the prj.conf affect only application, while configs in defconfig files are applied to both application and MCUBoot. Due to nature of this project with several board configurations, we have many configs placed in defconfig files. Is it possible to have defconfig file that does not affects MCUBoot?

Best,

Eva

RE: Build fail using MCUBOOT and SPI on ncs 1.7.1

Håkon Alseth — Wed, 15 Dec 2021 08:14:36 GMT

Hi,

Do you need i2c in mcuboot? ie. should mcuboot be able to interface over i2c/spi?

If not, I would recommend that you n-select the peripherals in mcuboot.

This can be done by creating the folder, in your application:

child_image/mcuboot.conf

And place your override configuration in the above file.

Kind regards,

Håkon

RE: Build fail using MCUBOOT and SPI on ncs 1.7.1

eva_c — Wed, 15 Dec 2021 06:57:18 GMT

Adding CONFIG_MULTITHREADING=y did indeed solve this error, thank you!

However, now I get a similar error in the lis2dw12 driver, again when using MCUBoot:

In file included from C:/Users/Eva/ncs/v1.7.1/zephyr/drivers/sensor/lis2dw12/lis2dw12.c:25:
C:/Users/Eva/ncs/v1.7.1/zephyr/drivers/sensor/lis2dw12/lis2dw12.h:63:32: error: field 'i2c' has incomplete type
   63 |   const struct stmemsc_cfg_i2c i2c;
      |                                ^~~
In file included from C:/Users/Eva/ncs/v1.7.1/zephyr/include/sys/util_macro.h:34,
                 from C:/Users/Eva/ncs/v1.7.1/zephyr/include/sys/util.h:17,
                 from C:/Users/Eva/ncs/v1.7.1/zephyr/include/kernel/sched_priq.h:9,
                 from C:/Users/Eva/ncs/v1.7.1/zephyr/include/kernel_includes.h:23,
                 from C:/Users/Eva/ncs/v1.7.1/zephyr/include/kernel.h:17,
                 from C:/Users/Eva/ncs/v1.7.1/zephyr/include/init.h:11,
                 from C:/Users/Eva/ncs/v1.7.1/zephyr/drivers/sensor/lis2dw12/lis2dw12.c:13:
C:/Users/Eva/ncs/v1.7.1/zephyr/drivers/sensor/lis2dw12/lis2dw12.c:380:25: error: 'stmemsc_i2c_read' undeclared here (not in a function); did you mean 'stmemsc_spi_read'?
  380 |       (stmdev_read_ptr) stmemsc_i2c_read,  \
      |                         ^~~~~~~~~~~~~~~~

I use the following config options for lis2dw sensor:

CONFIG_I2C=y
CONFIG_SENSOR=y
CONFIG_LIS2DW12=y

And the sensor is added in the devicetree as:

&i2c0 {
	compatible = "nordic,nrf-twi";
    status = "okay";
	sda-pin = <6>;
	scl-pin = <7>;
    lis2dw12_accel: lis2dw12-accel@19 {
        compatible = "st,lis2dw12";
        label = "LIS2DW12-ACCEL";
        reg = <0x19>;
    };
};

Am I again missing some config?

RE: Build fail using MCUBOOT and SPI on ncs 1.7.1

Håkon Alseth — Tue, 14 Dec 2021 14:30:02 GMT

Hi,

Looks like it is mcuboot that fails to build on your side.

the "spi" driver depends on a multithreaded system, and the errors in linking indicate that your mcuboot config does not have "CONFIG_MULTITHREADING=y" set?

Kind regards,

Håkon