[nRF Connect SDK]Questions for porting.

[Tim Hwang]

Hello.

Target nRF52832(nrf52dk_nrf52832)

SDK NCS v1.9.1

Build : SES for win 10 (5.68)

1. Support BT5.3

My project used nRF5_SDK_17.1.0_ddde560. Recently I found That SDK cannot support 5.3. (5.1 limited)

So I heard that have to use NCS(nRF Connect SDK), is it correct? 

2. Build mcuboot

Following is my base project.

C:\Users\user\ncs\v1.9.1\nrf\samples\bluetooth\peripheral_hids_keyboard

1) In order to build mcuboot, I add that in prj.conf, but I don't think mcuboot has no changes. no hex(bin)

CONFIG_BOOTLOADER_MCUBOOT=y

How I can build mcuboot?

2) I will use DFU via UART. How to add UART implementation in mcuboot? Can you give me good sample for me? 

3. Make my own pem for sign

: done. (C:\Users\user\ncs\v1.9.1\bootloader\mcuboot>scripts\imgtool.py getpub -k mykey.pem)

Now I have to put rsa_pub_key into keys.c. What keys.c should I use?

4. Make dfu image

Using MCUboot in nRF Connect SDK — MCUboot 1.8.99 documentation (nordicsemi.com)

I cannot find any bin in my project. Maybe I failed to build mcuboot, right?

[Amanda Hsieh]

Hi, 

So I heard that have to use NCS(nRF Connect SDK), is it correct? 

Yes, see the Bluetooth QDIDs for nRF52832. 

How I can build mcuboot?

Enable CONFIG_BOOTLOADER_MCUBOOT in the prj.conf to include as the child image in the build script, see Updating the build scripts.

2) I will use DFU via UART. How to add UART implementation in mcuboot? Can you give me good sample for me? 

Here is the example for v1.6.1 in this post. The flow is the same as that guide, but it transmits via UART. 

Now I have to put rsa_pub_key into keys.c. What keys.c should I use?

set to rsa_pub_key in bootloader/mcuboot/boot/zephyr/keys.c

I cannot find any bin in my project. Maybe I failed to build mcuboot, right?

The mcuboot child image is under \build\mcuboot\zephyr, and it will be merged with the app image to program.

Regards,
Amanda 

[Tim Hwang]

Thnaks for your reply.
I will do your guide and update the result.

(3/21)I'm still working on it.

[Tim Hwang]

I could manage to build both SW. (Bootloader+app)

I'm testing DFU (mcuboot + UART) using mcumgr. 

The problem is transferring file is too slow.

I used "nrfutil dfu" in Previous SDK. It was good. How can I fix it?

[command]

mcumgr --conntype=serial --connstring=COM10 image upload build\zephyr\app_update.bin

[Amanda Hsieh]

Hi, 

The management subsystem is provided by MCUmgr instead of Nordic, an open source project that provides a management subsystem that is portable across multiple real-time operating systems. You can pull a request here. 

-Amanda

[Tim Hwang]

I don't have to use mcumgr. I just want to update bin file with good performance.

I found following link. I cannot find pynrfjprog example to update. Can you give me a sample for DFU?

DFU speed over UART on NCS/Zephyr - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)

[Amanda Hsieh]

Hi, 

Here is the https://github.com/NordicSemiconductor/pynrfjprog 

-Amanda

[Tim Hwang]

Hello.

I could install pynrfjprog. But I'm expecting real sample.

here is my old sample. But it is not compatible with mcuboot.

nrfutil dfu serial -pkg dfu_application.zip -p COM30 -b 115200 -t 1 -cd 0 -prn 0

mcumgr is too slow. pynrfjprog don't have example.

How can I update my app via uart? I'm okay anything if it has good speed.

[Amanda Hsieh]

Hi, 

Python wrapper around the nrfjprog dynamic link libraries (DLL). The use of this API allows developers to program/debug nRF SOC. The nrfutil is another tool that is only supported by the nRF5 bootloader. Seems Zephyr doesn't have other tools than mcumgr to support mcuboot.

-Amanda