nrf5340 firmware updates MCUmgr

[DvAgas]

I have and nrf5340 connected to debian system via uart.
I'm trying todo a flash update via the uart and the nrf5340 is unresponsive.

The MCUmgr is not getting any response from the nrf5340, 
The uart port ttyMAX3 is wired and run corrrectly, the prj.conf file has  CONFIG_MCUMGR_TRANSPORT_UART= y but I don't see it being detected in the main.c file.
When the mcumgr request an image list it times out. 

CONFIG_MCUMGR_TRANSPORT_UART=y

#if IS_ENABLED(CONFIG_MCUMGR_TRANSPORT_UART)

    LOG_INF("MCUmgr UART transport enabled on UART3");

#endif

(.venv) root@imx93-var-som:/home/aram/prj# python3 /home/aram/prj/smp_upload.py --port /dev/ttyMAX3 --baud 115200 --list
Listing images on /dev/ttyMAX3...
ERROR: No response. Check connection and MCUmgr UART config on nRF5340.
(.venv) root@imx93-var-som:/home/aram/prj#

SEGGER J-Link V9.24a - Real time terminal output
SEGGER J-Link (unknown) V1.0, SN=960188838
Process: JLink.exe
[00:00:00.000,518] <err> qspi_nor: JEDEC id [ff ff ff] expect [c2 28 17]
*** Booting nRF Connect SDK v2.7.0-5cb85570ca43 ***
*** Using Zephyr OS v3.6.99-100befc70c74 ***
Running NUS main on nrf5340dk
[00:00:00.000,732] <err> aram_app: P1.04 toggle pin not ready
[00:00:00.001,647] <inf> aram_app1: SMS URC handler thread started
[00:00:00.025,909] <inf> aram_app: 230, STARTING
[00:00:00.025,909] <inf> aram_app: Event-driven mode active - waiting for SMS URCs and BLE commands
[00:00:00.038,360] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.038,360] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.038,391] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 214.51162 Build 1926957230
[00:00:00.040,130] <inf> bt_hci_core: Identity: E7:CE:33:51:E0:36 (random)
[00:00:00.040,161] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x21fb, manufacturer 0x0059

[Amanda Hsieh]

Hi Dominic,

Could you refer to this course exercise-1-dfu-over-uart/ to check the required configs with your project?

Regards,
Amanda H. 

[DvAgas]

THank you I'll look into it.

I noticed that this message is not appearing in the log, even though i have the deine  in the prj.conf file

#if IS_ENABLED(CONFIG_MCUMGR_TRANSPORT_UART)

    LOG_INF("MCUmgr UART transport enabled on UART3");

#endif

# --- System and Kernel ---

CONFIG_HEAP_MEM_POOL_SIZE=4096

CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048

CONFIG_SMF=y

CONFIG_HWINFO=y

CONFIG_NRF_APPROTECT_USE_UICR=n

# --- Logging and Console ---

CONFIG_LOG=y

CONFIG_USE_SEGGER_RTT=y

CONFIG_LOG_BACKEND_RTT=y

CONFIG_LOG_DEFAULT_LEVEL=3

CONFIG_CONSOLE=y

# --- Device Drivers ---

CONFIG_GPIO=y

CONFIG_NRFX_SPIM4=y

CONFIG_SERIAL=y

CONFIG_NRFX_UARTE3=y

CONFIG_UART_INTERRUPT_DRIVEN=y

CONFIG_I2C=n

CONFIG_SPI=n

# --- Bluetooth ---

CONFIG_BT=y

CONFIG_BT_PERIPHERAL=y

CONFIG_BT_DEVICE_NAME="ARAM_BLE_DV"

CONFIG_BT_HCI_IPC=y

# --- C Library ---

CONFIG_NEWLIB_LIBC=y

CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y

CONFIG_CBPRINTF_FP_SUPPORT=y

# --- MCUmgr Core ---

CONFIG_MCUMGR=y

CONFIG_ZCBOR=y

CONFIG_BASE64=y

# --- MCUmgr Transport (UART) ---

CONFIG_MCUMGR_TRANSPORT_UART=y

CONFIG_MCUMGR_TRANSPORT_UART_MTU=512

# --- MCUmgr Groups ---

CONFIG_MCUMGR_GRP_IMG=y

CONFIG_MCUMGR_GRP_OS=y

# --- DFU / Flash Management ---

CONFIG_BOOTLOADER_MCUBOOT=y

CONFIG_MCUBOOT_IMG_MANAGER=y

CONFIG_IMG_MANAGER=y

CONFIG_STREAM_FLASH=y

CONFIG_FLASH=y

CONFIG_FLASH_MAP=y

CONFIG_FLASH_PAGE_LAYOUT=y

# --- External QSPI Flash (for MCUboot secondary slot) ---

CONFIG_NORDIC_QSPI_NOR=y

# --- Required for MCUmgr UART framing ---

CONFIG_CRC=y

# --- Driver for uart2 (modem), since overlay enables it ---

CONFIG_NRFX_UARTE2=y