Linking problem after enabling CONFIG_BOOTLOADER_MCUBOOT

RE: Linking problem after enabling CONFIG_BOOTLOADER_MCUBOOT

Dymek117 — Tue, 18 Jan 2022 04:24:11 GMT

Final solution was adding this lione to CMakeList.txt:
set(mcuboot_OVERLAY_CONFIG "${CMAKE_CURRENT_SOURCE_DIR}/mcuboot.conf")

And setting option, withing config file mentioned above (i had to create such one)

CONFIG_MULTITHREADING=y

Priyanka, thhank you so much for support :)

RE: Linking problem after enabling CONFIG_BOOTLOADER_MCUBOOT

Dymek117 — Tue, 18 Jan 2022 03:19:37 GMT

OK, so I am pretty sure that mcuboot should gain CONFIG_MULTITHREADING to solve this, thanks 🙂
Before I was only setting this for my app, not bootloader.

But how can I add CONFIG_MULTITHREADING or CONFIG_ADC options to mcuboot?
Before, I was editing .config file in buil/mcuboot/zephyr but it can be only temporary solution.

I've added something like this to my CMakeList.txt:
set(mcuboot_CONF_FILE "${CMAKE_CURRENT_SOURCE_DIR}/mcuboot.conf")
But this wil overwrite all default NCS mcuboot configuration, could you please suggest a proper way to modify one option in mcuboot conifg? I'm using mcuboot from nordic SDK.

RE: Linking problem after enabling CONFIG_BOOTLOADER_MCUBOOT

Priyanka — Mon, 17 Jan 2022 15:11:02 GMT

Hi,

Your error code actually mentions that the ADC library cannot find the 'k_sem_give'. This looks similar to the problem mentioned here. You mention that you need the ADC in your application. So when you try disabling the ADC for mcuboot, doesn't this affect your application too? Also, did you enable the CONFIG_MULTITHREADING for the mcuboot or the application?

Since your error came from the mcuboot, you could try disabling the CONFIG_MULTITHREADING in the mcuboot. You could also disable the ADC if you are not using it.

Regards,

Priyanka

RE: Linking problem after enabling CONFIG_BOOTLOADER_MCUBOOT

Dymek117 — Fri, 14 Jan 2022 16:36:42 GMT

I actually use ADC in my app, therefore I set CONFIG_ADC=y.

CONFIG_MULTITHREADING=y does not help, I see the same error. The only solution that helps is turning off ADC for mcu boot, but is it good solution? I guess mcuboot may use ADC for some purpose (i.e. cryptography, etc) but this is only my guess.

RE: Linking problem after enabling CONFIG_BOOTLOADER_MCUBOOT

Priyanka — Fri, 14 Jan 2022 09:58:09 GMT

Hi,

You could try setting the CONFIG_MULTITHREADING=y. But in case you want the COFIG_MULTITHREADING = , then you could try disabling the CONFIG_ADC in the prj.conf.

Regards,

Priyanka

RE: Linking problem after enabling CONFIG_BOOTLOADER_MCUBOOT

Dymek117 — Thu, 13 Jan 2022 08:29:48 GMT

RE: Linking problem after enabling CONFIG_BOOTLOADER_MCUBOOT

Dymek117 — Thu, 13 Jan 2022 08:29:21 GMT

devzone.nordicsemi.com/.../0257.log.txt

RE: Linking problem after enabling CONFIG_BOOTLOADER_MCUBOOT

Priyanka — Wed, 12 Jan 2022 16:59:06 GMT

Hi,

It would be more helpful if you don't truncate the error message that you get. Would it be possible to share a file of the entire output message that you get in the "Output" terminal of VSCode? And also of the "Problems" window too.

Regards,

Priyanka

RE: Linking problem after enabling CONFIG_BOOTLOADER_MCUBOOT

Dymek117 — Wed, 12 Jan 2022 16:39:39 GMT

I'm working on Windows and build for DK board.

RE: Linking problem after enabling CONFIG_BOOTLOADER_MCUBOOT

Priyanka — Wed, 12 Jan 2022 14:04:24 GMT

Hi,

Are you using the nRF52832 DK, PDK or a custom board? Also, what platform are you working on? (Windows, Linux or MacOS)

Regards,

Priyanka