download_client: Unexpected HTTP response: 400 bad request when CONFIG_MCUBOOT_IMG_MANAGER=n

[NautDesigner]

If we enable MCUBOOT_IMG_MANAGER, SECURE_BOOT and BUILD_S1_VARIANT, FOTA works fine. However,

there is a constant 150mA power draw. If we disable them, power draw is normal but we then get "400 bad request" error.

Any idea why just enabling those three options causing the power draw or why not configuring them causes the bad request?

[00:00:18.082,580] <inf> download_client: Connecting to www.website.com
[00:00:18.339,508] <err> download_client: Unexpected HTTP response: 400 bad request
[00:00:18.339,996] <err> fota_download: Download client error
Received error from fota_download

# MCUBOOT
CONFIG_BOOTLOADER_MCUBOOT=y #
#CONFIG_MCUBOOT_IMG_MANAGER=y
#CONFIG_SECURE_BOOT=y
#CONFIG_BUILD_S1_VARIANT=y
CONFIG_PM_EXTERNAL_FLASH_MCUBOOT_SECONDARY=n

[Simonr]

Hi

Thank you for sharing. No particular red flags, no. But I did some digging on my end, and this power could point to an issue we've seen where the MCUBoot enables UART instances, so you could make sure that the DT overlay file for MCUBoot that sets the status of all UART nodes to "disabled" so we know that the UART pins aren't configured. I think that's worth giving a try.

Best regards,

Simon

[NautDesigner]

Here is the overlay file in the boards directory and in the child_image/mcuboot/boards directory:

&uart0 {
	status="disabled";
};

&uart1 {
	status="disabled";
};

&uart2 {
	status="disabled";
};

CONFIG_SERIAL=n is set as well.

Any additional thoughts?