52840 NCS UART DFU

RE: 52840 NCS UART DFU

Menon — Thu, 03 Jul 2025 19:00:51 GMT

Hello,

Sorry for the delayed response. Were you able to resolve the issue? If you're still experiencing problems, please share a minimal project with me. I will try to run it on the DK and attempt to reproduce the issue.

I'm not entirely sure what exactly is going wrong, but it’s possible that when you enable CONFIG_MCUMGR_TRANSPORT_UART=y, MCUmanager sets up the UART and installs its own interrupt handler early during boot. If the application later sets its own UART IRQ handler using uart_irq_callback_user_data_set(), it may override the one used by MCUmanager. Since MCUmanager may not be aware that its handler was replaced, it doesn't regain control of the UART. Simply removing the application's handler might not bring DFU back. It may only start working again if you manually forward the UART data to MCUmanager or reboot the device.

Kind regards,
Abhijith

RE: 52840 NCS UART DFU

yi hung wu — Tue, 03 Jun 2025 08:03:28 GMT

Still not working , actually i can see DFU feedback from jlink RTT viewer with my original prj.conf settings.

The only difference between success and fail is whether UART0 irq callback was intiailized by

uart_irq_callback_user_data_set API in the beginning, Is there any way to disable my irq callback? i tried uart_irq_callback_user_data_set(dev_uart0, NULL, NULL) but its not working.

Fail

success

Regards,

RE: 52840 NCS UART DFU

Menon — Mon, 02 Jun 2025 12:53:45 GMT

Hello,

While checking the shared prj.config, I see that you are enabling RTT instead of UART for logs and the console, which disables all console output and logging over UART. So even if DFU starts working, you won't see any feedback on the UART line (used by Auterm), as it's being sent to RTT instead. Only one backend should be active. If you're doing DFU over UART, then UART must be the active log backend. RTT should be disabled during DFU testing. Try using the configuration below:

CONFIG_LOG_BACKEND_UART=y
CONFIG_LOG_BACKEND_RTT=n
CONFIG_UART_CONSOLE=y
CONFIG_RTT_CONSOLE=n

Kind Regards,

Abhijith

RE: 52840 NCS UART DFU

yi hung wu — Thu, 29 May 2025 01:32:10 GMT

Hi,

here is my prj.conf and 52840.overlay

==========================prj.conf=====================


#================LOG================
CONFIG_LOG=y
CONFIG_LOG_MODE_DEFERRED=n
CONFIG_LOG_MODE_IMMEDIATE=y
CONFIG_LOG_MODE_MINIMAL=y

CONFIG_USE_SEGGER_RTT=y 

CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_BACKEND_UART=n

CONFIG_RTT_CONSOLE=y
CONFIG_UART_CONSOLE=n   


#================FLOATING POINT================
CONFIG_FPU=y

#================GPIO================
CONFIG_GPIO=y


#================SPI================
CONFIG_SPI=y
CONFIG_NORDIC_QSPI_NOR=y 

#================UART================
CONFIG_SERIAL=y
CONFIG_UART_USE_RUNTIME_CONFIGURE=y
CONFIG_UART_INTERRUPT_DRIVEN=y      
CONFIG_UART_ASYNC_API=n           

#================I2C================
CONFIG_I2C=y

#================ADC================
CONFIG_ADC=y

#================PWM================
# CONFIG_PWM=y

#================MCU FLASH================
CONFIG_FLASH=y
CONFIG_FLASH_MAP=y
CONFIG_NVS=y 
CONFIG_SOC_FLASH_NRF_EMULATE_ONE_BYTE_WRITE_ACCESS=y 


#================Partition Manager================
CONFIG_PARTITION_MANAGER_ENABLED=y


#================MCU WATCHDOG================
CONFIG_WATCHDOG=y

#================BLUETOOTH================
CONFIG_BT=y
CONFIG_BT_RX_STACK_SIZE=2700 

CONFIG_BT_DEVICE_NAME_MAX=30
CONFIG_BT_DEVICE_NAME="52840_NUS"
CONFIG_BT_DEVICE_NAME_DYNAMIC=y

CONFIG_BT_MAX_CONN=2

CONFIG_BT_CTLR_CONN_RSSI=y

CONFIG_BT_CTLR_TX_PWR_PLUS_8=y
CONFIG_BT_CTLR_TX_PWR_DYNAMIC_CONTROL=y


CONFIG_BT_BUF_ACL_TX_SIZE=251
CONFIG_BT_BUF_ACL_RX_SIZE=251
CONFIG_BT_CTLR_DATA_LENGTH_MAX=251

CONFIG_BT_L2CAP_TX_MTU=247

# #================BLUETOOTH_peripheral================

CONFIG_BT_PERIPHERAL=y

CONFIG_BT_NUS=y # Enable the NUS service

# CONNECTION PARAMETERS
CONFIG_BT_PERIPHERAL_PREF_MIN_INT=30
CONFIG_BT_PERIPHERAL_PREF_MAX_INT=50
CONFIG_BT_PERIPHERAL_PREF_LATENCY=0
CONFIG_BT_PERIPHERAL_PREF_TIMEOUT=40

CONFIG_BT_GAP_AUTO_UPDATE_CONN_PARAMS=y   
 

CONFIG_BT_LIM_ADV_TIMEOUT=40

#====================BT DFU====================
CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y


#====================UART DFU (MCUMGR)====================
# # STEP 5.2 - Enable mcumgr DFU in application
# Enable MCUMGR 
CONFIG_MCUMGR=y

# Enable MCUMGR management for both OS and Images
CONFIG_MCUMGR_GRP_OS=y
CONFIG_MCUMGR_GRP_IMG=y

# Configure MCUMGR transport to UART
CONFIG_MCUMGR_TRANSPORT_UART=y

# Dependencies
# Configure dependencies for CONFIG_MCUMGR  
CONFIG_NET_BUF=y
CONFIG_ZCBOR=y
CONFIG_CRC=y

# Configure dependencies for CONFIG_MCUMGR_GRP_IMG  
CONFIG_FLASH=y
CONFIG_IMG_MANAGER=y

# Configure dependencies for CONFIG_IMG_MANAGER  
CONFIG_STREAM_FLASH=y
CONFIG_FLASH_MAP=y

# Configure dependencies for CONFIG_MCUMGR_TRANSPORT_UART 
CONFIG_BASE64=y


#================BLUETOOTH_central================
# Enable the BLE stack with GATT Client configuration
CONFIG_BT_CENTRAL=y

CONFIG_BT_GATT_CLIENT=y

# Enable the BLE modules from NCS
CONFIG_BT_NUS_CLIENT=y
CONFIG_BT_SCAN=y
CONFIG_BT_SCAN_FILTER_ENABLE=y
CONFIG_BT_SCAN_UUID_CNT=1
CONFIG_BT_SCAN_NAME_CNT=1
CONFIG_BT_GATT_DM=y

CONFIG_BT_SCAN_WITH_IDENTITY=y

#================LOW_FREQ_CLOCK================
CONFIG_CLOCK_CONTROL=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=n
CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_500PPM=y


#================POWER MANAGMENT================
CONFIG_PM_DEVICE=y




#====================PIPES====================
CONFIG_PIPES=y




==========================OVERLAY=====================




&reg0 {
    compatible = "nordic,nrf52x-regulator-hv";
	status = "okay";
};

&reg1 {
    compatible = "nordic,nrf5x-regulator";
	regulator-initial-mode = <NRF5X_REG_MODE_DCDC>;
};

&uicr {

    // NFC
    nfct-pins-as-gpios;

    // Reset pin
	/delete-property/ gpio-as-nreset;
};

/{
    my_output{

        compatible = "gpio-leds";

        led_red: LED_RED {
            gpios = < &gpio0 9 0 >;
            label = "LED_RED";
        };

        led_green: LED_GREEN {
            gpios = < &gpio0 10 0 >;
            label = "LED_GREEN";
        };

    };
};


/{

    my_input {

        compatible = "gpio-keys";

        my_input_0: MY_INPUT_0 {
            gpios = < &gpio0 4 0 >;
            label = "MY INPUT 0";
        };

    };     
};


//==================UART==================//


&pinctrl {

    uart0_default: uart0_default {

        group1 {
            psels = <NRF_PSEL(UART_TX, 0, 6)>,
                    <NRF_PSEL(UART_RX, 0, 8)>;
        };
    };

    uart0_sleep: uart0_sleep {

        group1 {
            psels = <NRF_PSEL(UART_TX, 0, 6)>,
                    <NRF_PSEL(UART_RX, 0, 8)>;
            low-power-enable;
        };
    };
};

&uart0 {

    compatible = "nordic,nrf-uarte";
    status = "okay";
    current-speed = < 115200 >;
    pinctrl-0 = < &uart0_default >;
    pinctrl-1 = < &uart0_sleep >;
    pinctrl-names = "default", "sleep";

};


&pinctrl {

	i2c0_default: i2c0_default {
		group1 {
			psels = <NRF_PSEL(TWIM_SDA, 1, 14)>,
                    <NRF_PSEL(TWIM_SCL, 0, 12)>;
            nordic,drive-mode = <NRF_DRIVE_S0D1>; // standard 0, disconnect 1
            bias-pull-up; // internal pull-up is too weak, only for 100kHz or lower  
            
		};
	};

	i2c0_sleep: i2c0_sleep {
		group1 {
			psels = <NRF_PSEL(TWIM_SDA, 1, 14)>,
                    <NRF_PSEL(TWIM_SCL, 0, 12)>;
			low-power-enable;
		};
	};
};

&i2c0 {

    compatible = "nordic,nrf-twim";
    status = "okay";
    clock-frequency = <I2C_BITRATE_STANDARD>;
    pinctrl-0 = <&i2c0_default>;
    pinctrl-1 = <&i2c0_sleep>;
    pinctrl-names = "default", "sleep";

    lis3dh: lis3dh@19 
    {
        compatible = "vendor,i2cdevice";
        reg = <0x19>;
    };

};

&pinctrl {

    spi1_default: spi1_default {
        group1 {
            psels = <NRF_PSEL(SPIM_SCK,  0, 22)>,
                    <NRF_PSEL(SPIM_MOSI, 0, 30)>,
                    <NRF_PSEL(SPIM_MISO, 0, 23)>;
        };
    };
    spi1_sleep: spi1_sleep {
        group1 {
            psels = <NRF_PSEL(SPIM_SCK,  0, 22)>,
                    <NRF_PSEL(SPIM_MOSI, 0, 30)>,
                    <NRF_PSEL(SPIM_MISO, 0, 23)>;
            low-power-enable;
        };
    }; 
};

&spi1 {

    compatible = "nordic,nrf-spim";
    status = "okay";
    pinctrl-0 = <&spi1_default>;
    pinctrl-1 = <&spi1_sleep>;
    pinctrl-names = "default", "sleep";
    cs-gpios = <&gpio0 24 GPIO_ACTIVE_LOW>,
               <&gpio0 25 GPIO_ACTIVE_LOW>;

    m95p16: m95p16@0
    {
        compatible = "vendor,spidevice";
        reg = < 0 >;
        spi-max-frequency = < DT_FREQ_M(8) >;
        wp-gpios = <&gpio0 26 GPIO_ACTIVE_LOW>;
    };

    at45db041: at45db041@1
    {
        compatible = "vendor,spidevice"; 
        reg = < 1 >;
        spi-max-frequency = < DT_FREQ_M(8) >;
        wp-gpios = <&gpio0 18 GPIO_ACTIVE_LOW>;
    };
};


&adc {

    compatible = "nordic,nrf-saadc";
	#address-cells = <1>;
	#size-cells = <0>;
	status = "okay";
    /* 52840 adc channel */
    /* P0.02、03、04、05、28、29、30、31 */
	channel@0 
    {
		reg = <0>;
		zephyr,gain = "ADC_GAIN_1_6";
		zephyr,reference = "ADC_REF_INTERNAL";
		zephyr,acquisition-time = <ADC_ACQ_TIME_DEFAULT>;
		zephyr,input-positive = <NRF_SAADC_AIN0>;
        // zephyr,input-negative = <NRF_SAADC_AIN3>; // 负输入
		zephyr,resolution = <12>;
	};

    channel@1 
    {
		reg = <1>;
		zephyr,gain = "ADC_GAIN_1_6";
		zephyr,reference = "ADC_REF_INTERNAL";
		zephyr,acquisition-time = <ADC_ACQ_TIME_DEFAULT>;
		zephyr,input-positive = <NRF_SAADC_AIN1>; 
		zephyr,resolution = <12>;
	};

    channel@2
    {
		reg = <2>;
		zephyr,gain = "ADC_GAIN_1_6";
		zephyr,reference = "ADC_REF_INTERNAL";
		zephyr,acquisition-time = <ADC_ACQ_TIME_DEFAULT>;
		zephyr,input-positive = <NRF_SAADC_VDD>;
		zephyr,resolution = <12>;
	};
};

/{
	zephyr,user 
    {
		io-channels = <&adc 0>, 
                      <&adc 1>,
                      <&adc 2>;
	};
};

&wdt0 {

    compatible = "nordic,nrf-wdt";
    status = "okay";
    
};

/{

    aliases
    {

        io-led-red     = &led_red;
        io-led-green   = &led_green;

        io-but0        = &my_input_0;

        spi-m95p16     = &m95p16;
        
        i2c-lis3dh     = &lis3dh;

        uart-0         = &uart0;


        m-watchdog     = &wdt0;

    };

};


&mx25r64 {

	status = "disabled";

};

Regards,

RE: 52840 NCS UART DFU

Menon — Tue, 27 May 2025 12:23:56 GMT

Hello,

Sorry for the confusion, and thank you for clarifying it. In this case, what you have done, disabling the UART IRQs is correct. Have you enabled MCUmgr for UART DFU? I recommend checking the prj.conf file from the sample I shared in my previous response; you can find it here. If you are enabling all these configurations, please share your prj.conf and device tree overlay files so I can take a look.

Kind regards,
Abhijith

RE: 52840 NCS UART DFU

yi hung wu — Thu, 22 May 2025 06:59:24 GMT

Hi ,

Sorry I didn’t explain it clearly,my project had uart0 to communicate with my external device originally , now I need to ADD uart dfu in application also use uart0, how can I do that?

Regards,

RE: 52840 NCS UART DFU

Menon — Thu, 22 May 2025 06:24:52 GMT

Hello,

If you are only doing UART DFU, then you don't need to initialize or deinitialize UART0. Take a look at this sample from the Academy course, it explains DFU over UART. Also, make sure you have included all the necessary configurations.

Kind Regards,

Abhijith

RE: 52840 NCS UART DFU

yi hung wu — Wed, 21 May 2025 10:00:07 GMT

Hi Menon:

Thanks for reply.

I disabled the CONFIG_SHELL=n and CONFIG_MCUMGR_TRANSPORT_SHELL=n , cuz seem like its not needed if i am using Auterm.

According to what you replied, if i want to process uart dfu, i need to deinit uart0 right?so i added this two

uart_irq_callback_user_data_set( dev_uart0, NULL, NULL );

uart_irq_rx_disable( dev_uart0 );

after that i use Auterm to get Image again , and it seems not getting any data from Auterm.

i was expeting to get this LOG <inf> mcuboot_util: Image index: 0, Swap type: none , but i seems not working at all.

is there any way to solve it?

Regards,

RE: 52840 NCS UART DFU

Menon — Wed, 21 May 2025 07:28:16 GMT

Hello,

I believe this is expected behavior when you use UART0 simultaneously for two independent purposes, your own IRQ-driven application code and the MCUmgr Shell. UART hardware allows only one handler to be active per UART at a time.

When you enable CONFIG_SHELL=y and CONFIG_MCUMGR_TRANSPORT_SHELL=y, it allows MCUmgr to handle DFU commands through the shell interface over UART. However, if your application also sets up its own UART interrupt handler (like uart0_irq_callback), it takes control of the UART and prevents the shell and MCUmgr from receiving data. That’s why the incoming data is going to your uart0_irq_callback instead of being handled by the MCUmgr shell.

Kind Regards,

Abhijith