Application is not running after integrating DFU

[Jithin A]

Hi,

I am using BM840 BLE module and I see after integrating the DFU application, the main application is not executing at all.

When I try to debug, I see it is not coming to the main.

If I remove DFU configuration and build the project and program, it is running fine.

Please help me with this as this is high priority

Editor: VS Code

SDK: v2.3.0

[Hieu]

Hello Jithin A,

Could you please give more details on what you have done? 

- How did you enable DFU?
- How do you know that the main application is not executing at all?

Hieu

[Jithin A]

Thank you for the response, Hieu.

Hieu said:

How did you enable DFU?

--> I added below configuration to my prj.conf file.

I did this from the reference: Add DFU support to your application - Software - nRF Connect SDK guides - Nordic DevZone (nordicsemi.com)

# Below configurations to enable DFU
# Enable mcumgr.
CONFIG_MCUMGR=y

# Enable most core commands.
CONFIG_MCUMGR_CMD_IMG_MGMT=y
CONFIG_MCUMGR_CMD_OS_MGMT=y

# Ensure an MCUboot-compatible binary is generated.
CONFIG_BOOTLOADER_MCUBOOT=y

# Allow for large Bluetooth data packets.
CONFIG_BT_L2CAP_TX_MTU=252
CONFIG_BT_BUF_ACL_RX_SIZE=256

# Enable the Bluetooth (unauthenticated) and shell mcumgr transports.
CONFIG_MCUMGR_SMP_BT=y
CONFIG_MCUMGR_SMP_BT_AUTHEN=n

# Some command handlers require a large stack.
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096

Hieu said:

How do you know that the main application is not executing at all?

--> We have an LED which will be turned ON when advertisement start successfully.

Before adding the DFU, the application was working fine.

After adding the above config, LED did not turn ON and when I try to debug, I observe it is not at all calling main.

Please let me know if I am missing anything or doing something wrong.

[Hieu]

Do you have any sort of logs from MCUboot?

[Jithin A]

Sorry we don’t have any logs.

We are not working on any EVK, we have the sample devices and working with them so, I don’t think we can get logs from the device as USART is not connected.

[Hieu]

It is pretty much impossible to work based on just this much information. You need to be able to get some logs.

As you mentioned being able to debug, try reconfiguring MCUboot to log to RTT instead of UART, and get some information.

Another thing you can try is applying DFU to Hello World or Blinky and see if the problem happens again. Based on whether it happens or not, we can have some idea for our next steps. Nonetheless, I recommend you get some development hardware or figure out a way to get logs from your device. It should make your life a lot easier moving forward.

[Jithin A]

One should add a child_image directory and create a file "mcuboot.conf"

In the file place the below lines 

CONFIG_BOOT_UPGRADE_ONLY=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y

This way we are telling MCU Boot code to align with the main application clock source.