How to enter DFU mode with SR3v1.2

RE: How to enter DFU mode with SR3v1.2

Jørgen Holmefjord — Tue, 25 Sep 2018 07:05:22 GMT

[quote user="Ralph0"]I think so,because as I change it back to 0x20031 in the config file, I can DFU the RCU.[/quote]

I guess you then also change parameter --hw_version 0x20031 when you create the DFU packet? Have you tried not changing the config (set it to 0x20023), and then test with a DFU packet created with --hw_version 0x20031. If it works, the bootloader have the wrong config.

Have you read the Working with Smart Remote 3 for nRF52810 documentation? Due to the limited RAM and Flash sizes of nRF52810, the logger is disabled by default. Having both DFU bootloader and logging enabled at the same time might not work at all.

RE: How to enter DFU mode with SR3v1.2

Ralph — Tue, 25 Sep 2018 02:15:02 GMT

BTW, I can't check the log,seems the size of FLASH and RAM in BT (52810)are too small for log module.

I change the size of FLASH and decrease the size of buffers of log , but RAM keeps overflow.

The only message I can see is the message from nRF connect.

RE: How to enter DFU mode with SR3v1.2

Ralph — Tue, 25 Sep 2018 02:09:33 GMT

I think so,because as I change it back to 0x20031 in the config file, I can DFU the RCU.

But I can try again, so theoretically, the HW_VERSION may be changed in config.h as long as init packet has the same HW_VERSION, right?

RE: How to enter DFU mode with SR3v1.2

Jørgen Holmefjord — Mon, 24 Sep 2018 12:40:20 GMT

Are you sure that sr3_config_nrf52810_pca20031.h is the config file included in your build? If you get this error, the HW_VERSION of bootloader and init packet does not match.

RE: How to enter DFU mode with SR3v1.2

Ralph — Fri, 21 Sep 2018 01:41:18 GMT

I set CONFIG_DFU_HW_VERSION to 0x20023 in sr3_config_nrf52810_pca20031.h and packaged the dfu zip file with parameter --hw_version 0x20023,too.

It said the HW version wrong by secure DFU service's DFU Control Point in nRF connect .

I think the code is at dfu_handle_prevalidate() in dfu_req_handling.c where checkc of init command HW version

RE: How to enter DFU mode with SR3v1.2

Jørgen Holmefjord — Thu, 20 Sep 2018 14:28:56 GMT

The bonds must be created in the main application, see this answer. The FW have CONFIG_DFU_HW_VERSION set to 0x20031 for nRF52810. Where did you set the HW_VERSION, and how did it tell you that the HW version is wrong?

RE: How to enter DFU mode with SR3v1.2

Ralph — Wed, 19 Sep 2018 07:29:44 GMT

Hi, Bjorn,

Sorry for my very late response,too. The notification didn't show up and I also forgot to review this.

Yes, setting NRF_DFU_BLE_REQUIRES_BONDS to 0 resolved the

Client did not have the Service Changed indication set to enabled. Error: 0x00000008

error in the bootloader.

1.So if I set NRF_DFU_BLE_REQUIRES_BONDS to 1, the device have to bond with bootloader(DFU_Target)first, so the whole process of DFU can go down?

2.We recently change our chip from 52832 to 52810, and I find out even changing the HW_VERSION in 52810's config from 0x20031 to 0x20023, Log in secure DFU Service still tells me the hw verson is wrong.

Seems it has to be 0x20031 instead of other values? Isn't hw version relating to the PCB of RCU likes pca63519 and pca20023 with same chip 52832?

RE: How to enter DFU mode with SR3v1.2

bjorn-spockeli — Tue, 24 Jul 2018 14:45:34 GMT

Hi Ralph,

I apologize for the late reply. I've been out of office on vacation.

So setting NRF_DFU_BLE_REQUIRES_BONDS to 0 resolved the

Client did not have the Service Changed indication set to enabled. Error: 0x00000008

error in the bootloader?

Setting NRF_DFU_BLE_REQUIRES_BONDS to 0 means that unbonded devices are able to connect to the bootloade, however, as long as they do not have a signed DFU image to upload they will not be able to perform a DFU of the remote.

Best regards

Bjørn

RE: How to enter DFU mode with SR3v1.2

Ralph — Mon, 16 Jul 2018 03:54:56 GMT

Hi, Bjorn

I passed the issue that using combo key to enter DFU mode .

In bootloader's sdk_config.c ,there is a define called NRF_DFU_BLE_REQUIRES_BONDS

Its default value is 1, I clear it.

Guess SR might only receive the DFU command from paired central if NRF_DFU_BLE_REQUIRES_BONDS is set. If the command is sent from other paths, it omits the command.

Hope there is a better explanation.

Thanks.

RE: How to enter DFU mode with SR3v1.2

Ralph — Mon, 09 Jul 2018 06:08:08 GMT

0> <info> sr3_bootloader: In the bootloader=================
0> <debug> app: In nrf_bootloader_init
0> <debug> app: in weak nrf_dfu_init_user
0> <debug> app: In real nrf_dfu_init
0> <debug> nrf_dfu_settings: Enter nrf_dfu_settings_init
0> <debug> nrf_dfu_flash: Calling nrf_dfu_flash_init(false)...
0> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
0> <debug> dfu_utils: Enter nrf_dfu_continue
0> <debug> dfu_utils: Valid App
0> <debug> app: Application sent bootloader request
0> <debug> dfu_utils: App is valid
0> <debug> app: Running Service Changed config
0> <debug> app: Finished running Service Changed config
0> <debug> app: Enabling SoftDevice.
0> <debug> app: SoftDevice enabled.
0> <debug> app: Device address set
0> <debug> app: Regular adv name
0> <debug> app: ##### Setting adv with peer data ####
0> <debug> app: ##### IRK Found. Setting whitelist ####
0> <debug> app: Finished initializing BLE DFU transport
0> <debug> app: After nrf_dfu_transports_init
0> <debug> nrf_dfu_flash: Calling nrf_dfu_flash_init(true)...
0> <debug> nrf_dfu_flash: dfu_fstorage_evt_handler calls 0x00077025.
0> <info> app: ble_evt_handler m_conn_handle:0----------------------------------------------
0> <debug> app: == conn sec update request
0> <debug> app: Sending Service Changed indication
0> <info> app: service_changed_send M_CONN_HANDLE:0-------------------------------
0> <warning> app: Client did not have the Service Changed indication set to enabled. Error: 0x00000008
0> <debug> app: == We are finished handling conn sec update

These two values of m_conn_handle only show while establishing connection after entering DFU mode.

And then the error : 0x00000008, not upload the zip file yet.

About the sniffer, I can check that later.

RE: How to enter DFU mode with SR3v1.2

bjorn-spockeli — Fri, 06 Jul 2018 10:59:47 GMT

Yes, please to do that.

That is interesting as the SR3 FW uses the S132 v5.1.0 SofDevice and we've not had a lot of compatibility issues with Android devices. Are you able to capture a sniffer trace of the communication between the phones and the SR3?

Bjørn

RE: How to enter DFU mode with SR3v1.2

Ralph — Fri, 06 Jul 2018 09:51:13 GMT

Hi, Bjorn

I will check it next week.

BTW, I also use the third smart phone to try it,and this one can't even show all the GATT services but only the first two services GENERIC Access & Generic Attribute.

Its spec is sony XA Android 7.0 BT 4.1

If you want to know .

Thanks.

Ralph

RE: How to enter DFU mode with SR3v1.2

bjorn-spockeli — Fri, 06 Jul 2018 09:12:53 GMT

OK, so the issue is only present on your phone i.e. Redmi 5, Android 7.1.2 supporting BT 4.2 and not your colleague's LG V10 , Android 5.1.1 supporting BT 4.1.

Could you print the m_conn_handle variable when you get the BLE_GAP_EVT_CONNECTED in ble_evt_handler() in nrf_ble_dfu.c after connecting with the Redmi phone and then print it again in service_changed_send() prior to calling sd_ble_gatts_service_changed?

I would like to see it the connection handle is changed in between these two calls.

Best regards

Bjørn

RE: How to enter DFU mode with SR3v1.2

Ralph — Thu, 05 Jul 2018 10:12:58 GMT

Hi, Bjorn

I borrow another Android smart phone from my colleague,and it works to upload my zip file.

My Android smart phone's specification:

Redmi 5 , Android 7.1.2 BT 4.2

My colleague's specification:

LG V10 , Android 5.1.1 BT 4.1

nRF CONNECT versions I guess are the same, I downloaded it last week,

he downloaded it today.

RE: How to enter DFU mode with SR3v1.2

bjorn-spockeli — Wed, 04 Jul 2018 12:50:44 GMT

I am not seeing any "Client did not have the Service Changed indication set to enabled.ERROR: BLE_ERROR_INVALID_CONN_HANDLE" in service_changed_send() in nrf_ble_dfu.c. error message when performing DFU with nRF Connect for Android and monitoring the RTT log output

No, changing the memory layout should not affect the Service Changed indication. Nor should the nrfutil parameters.

Which version of the nRF Connect app are you using? Could you try to use nRF Connect for Desktop as well and see if you get the same behaviour?

RE: How to enter DFU mode with SR3v1.2

Ralph — Wed, 04 Jul 2018 10:28:50 GMT

Hi, Bjorn

I use both : my own modified project base on example and default example.

nRF Connect would bond it automatically when the device is in application mode, after entering DFU mode,I have to reconnect it, otherwise the DFU icon on the right corner won't show up.

I use nRF Connect for Android cellphone, the error message doesn't show up in nRF connect but does in RTT viewer.

Will changing the sections' boundary of the memory(APP,BL) cause the problem?

Or nrfutil's parameters like bootloader version ,app version,etc ?

RE: How to enter DFU mode with SR3v1.2

bjorn-spockeli — Wed, 04 Jul 2018 09:10:14 GMT

Hi Ralph,

Yes, the SR3 application FW was present when I performed the DFU. Are you using the SR3 application FW that you have modified or are you using the default example?

The SR3 bootloader requires you to bond with the application in order to perform DFU, so make sure that you have done that prior to starting the DFU.

Did the error message show up in nRF Connect for Desktop /iOS/ Android? Or are you still using nRF Toolbox?

Best regards

Bjørn

RE: How to enter DFU mode with SR3v1.2

Ralph — Wed, 04 Jul 2018 07:37:37 GMT

Hi, Bjorn

When you ran DFU test last time,was the app area empty or not?

After testing, DFU can be done when the device only has softdevice and bootloader.

But after that, I can't run another DFU again with the same error message.

Thanks.

Ralph

RE: How to enter DFU mode with SR3v1.2

Ralph — Fri, 29 Jun 2018 00:40:51 GMT

Alright, I will check again where I did wrong.

Thanks.

Ralph

RE: How to enter DFU mode with SR3v1.2

bjorn-spockeli — Thu, 28 Jun 2018 15:37:59 GMT

Hmm, I did a quick test with a clean install of SR3 and i did not see any issues

Generate a private key with nrfutil using

nrfutil keys generate private_key.pem

and then generated the public key using

nrfutil keys display --key pk --format code --out_file bootloader_key_custom.c private_key.pem

and then I generated a custom DFU image using

nrfutil pkg generate --application PCA20023-SR3_nRF52832_Product_Example.hex --application-version 1 --hw-version 0x20023 --sd-req 0xA5 --key-file private_key.pem sr3_dfu_pkg.zip

I then perform the DFU with nRF Connect for Desktop according to the instructions in the SR3 documentation under Running DFU ( doc found under C:\Nordic Semiconductor\nRFready Smart Remote 3 nRF52 v1.2.1alpha by clicking Firmware Documentation shourtcut

RE: How to enter DFU mode with SR3v1.2

Ralph — Thu, 28 Jun 2018 03:04:35 GMT

Hi,Bjorn

Same error message.

Yes , my hw version is PCA20023.

RE: How to enter DFU mode with SR3v1.2

bjorn-spockeli — Wed, 27 Jun 2018 11:46:06 GMT

Hi Ralph, I recommend using nRF Connect over nRF Toolbox as you get more extensive logs with the first.

When generating a DFU image for the SR3 v1.2 bootloader you need to set a specific hw version if you're using the PCA20023 (Product Example remote), i.e.

nrfutil pkg generate --application <name of app hex>.hex --application-version 0 --hw-version 0x20032 --sd-req 0xA5 --key-file private-key.pem dfu_app.zip

RE: How to enter DFU mode with SR3v1.2

Ralph — Wed, 27 Jun 2018 11:08:23 GMT

Hi, Bjorn

I omit the problem of combo key function first.

I use the same method in sdk13 to package a DFU zip file.

nrfutil pkg generate --hw-version 52 --sd-req 0xA5 --application-version 0x0000 --application my_app.hex --key-file my_key.pem my_zipfile.zip

And then I click uplaod to update the app by nrf_toolbox.

But there is a quick error comes out : "Client did not have the Service Changed indication set to enabled.ERROR: BLE_ERROR_INVALID_CONN_HANDLE" in service_changed_send() in nrf_ble_dfu.c. nrf_toolbox also shows the error message: invalid gatt service handle at the same time.

Did I package the zip file wrong? But the error seems not even validate my package format.

RE: How to enter DFU mode with SR3v1.2

Ralph — Wed, 27 Jun 2018 06:00:11 GMT

Hi Bjorn.

I change the IROM as your suggestion(can see log in bootloader now),and I also use app: nRF connect to send 0x01 to SR3 to put it into DFU mode successfully.

But still can't put SR3 into DFU mode by a combo key function. I go back to check m_coms_ble_dfu_fs_evt_handler(), nrf_atomic_flag_clear(&m_dfu_flash_busy) I didnt add it in my combo key function,should I add it ?

Thanks.

Ralph

RE: How to enter DFU mode with SR3v1.2

bjorn-spockeli — Tue, 26 Jun 2018 11:24:24 GMT

No, you will need to decrease IROM start address and increase the IROM size accordingly in the Keil memory or GCC linker script to fit the Logging module. You will also have to adjust the SR3 firmware so that it soes not overwrite the bootloader. I think that setting the bootloader memory settings to IROM1 Start: 0x77000 Size: 0x7000 should do.