FW update over UART fails when the UART channel is also used for logging.

[akamath-enphase]

Hello,
I am attempting to use the mcumgr-client in my system on a UART channel that is also used for sending logging information. I observed that the update process succeeds when the logging module is disabled, but fails when it is enabled.
I am able to update the firmware with the Go utility when logging is enabled, though.

This was tested with a MacBook, as well as an iMx processor running Linux.

root@imx93-evse-enph:/media/data# ./mcumgr-client -s 2 -m 4096 -l 8192 -d /dev/ttyLP4 upload zephyr.signed\ 3.bin
mcumgr-client 0.0.4, Copyright © 2024 Vouch.io LLC

10:56:52 [INFO] upload file: zephyr.signed 3.bin
10:56:52 [INFO] flashing to slot 2
10:56:52 [INFO] 950612 bytes to transfer
10:56:59 [ERROR] Error: read error, expected: 6, read: 56
root@imx93-evse-enph:/media/data#

[Frank-Buss]

Please upload a simple test project with all the prj.conf for it, so that I can reproduce the problem, haven't used the mcumgr protocol in combination with logging so far. I can test it with nRF or STM32 boards, but I guess it is hardware independent.

[akamath-enphase]

Here's a sample test project, with logging enabled on the same UART as the McuMgr UART channel.
smp_svr.zip