SMP DFU function by uart in NRF52820

[Treacy]

Hello guys,

I want to test SMP DFU function by uart. I use "E:\Spec\bluetooth\Nordic\nRF52820\ncs2.5.0\v2.5.0\zephyr\samples\subsys\mgmt\mcumgr\smp_svr" example and add below Macro in prj.conf.

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y

CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL=n

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION=y

# Enable the serial MCUmgr transport.

CONFIG_BASE64=y

CONFIG_MCUMGR_TRANSPORT_UART=y

CONFIG_SERIAL=y

CONFIG_CONSOLE=y

And do below addings

I release and download the .hex to device, but device didn't print "Starting mcuboot\n" in the UART. I'm sure the UART config and hardware part is no problem because when I run direction_finding_connectionless_tx example, it print well. But smp_svr didn't. Now I cannot figure out if the device running well or not because no debug information. Any suggestions for the uart print? Any wrong setting in my above things.

BR,

Treacy

[dejans]

Hi,

I use "E:\Spec\bluetooth\Nordic\nRF52820\ncs2.5.0\v2.5.0\zephyr\samples\subsys\mgmt\mcumgr\smp_svr" example and add below Macro in prj.conf.

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y

CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL=n

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION=y

Have you tried to add these 3 lines also to your child_image\hci_rpmsg.conf file?

Best regards,
Dejan

[Treacy]

Hi Dejan,

I tried add these 3 lines to child_image\hci_rpmsg.conf file, but when I build the project, Visual tool said "no work to do". I think this 3 lines didn't been compiled. And I don't know how to find hci_rpmsg.conf file directly in Visual tool. 

By the way, I only add  these 3 line in prj.conf when in direction_finding_connectionless_tx example, it runs well. Just let you know this information.

BR,

Treacy

[dejans]

Hi Treacy,

Treacy said:

I don't know how to find hci_rpmsg.conf file directly in Visual tool. 

First you make a project using nRF Connect for VS Code extension and then you can examine existing project files in VS Code Explorer view. It is shown below how you can find the hci_rpmsg.conf file in VS Code Explorer view.


Best regards,
Dejan

[Treacy]

Hi Dejan,

I add 3 lines to hci_rpmsg.conf file directly in Visual tool now. But still get "no work to do" when compiled.

BR,

Treacy

[dejans]

Hi Treacy,

You could try to remove the existing build folder from your project and then build again.

Best regards,
Dejan

[Treacy]

Hi Dejan,

I remove the existing build folder and rebuild again. Yes, I got the updated release .hex. But device still didn't run which means cannot output logs via uart.

BR,

Treacy

[dejans]

Hi Treacy,

Treacy said:

I remove the existing build folder and rebuild again. Yes, I got the updated release .hex.

It seems that the build process was successful. Could you confirm?

Treacy said:

But device still didn't run which means cannot output logs via uart.

Was flashing also successful? Did you get any errors during the process?

Best regards,
Dejan

[Treacy]

The build process and flash program are all successful. The only problem is that I can't judge if the FW can run normally, because I think it should output logs when device start but unfortunatelly, no any logs print in UART 

[dejans]

Hi,

You could try to remove hci_rpmsg and add CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y to your child_image\mcuboot.conf file, and rebuild your project.

Best regards,
Dejan