case about nRF52820 uart dfu

RE: case about nRF52820 uart dfu

Edvin — Wed, 31 Aug 2022 06:02:11 GMT

I don't know how much point there is as long as we are using different hardware.

Can you please try the debug version of the bootloader project, to see whether the nRF receives any of the UART packets. What does the RTT log say?

(since you probably don't have a *_debug version of your bootloader project, try to increase the flash size, and add RTT logging to your project. What does the log say?

BR,
Edvin

RE: case about nRF52820 uart dfu

peter.min — Thu, 25 Aug 2022 08:47:03 GMT

Hi Edvin,

1.I test you this script does not work

2. Note: My own UART DFU scripts are all validated and usable on nRF52840 nRF52833 nRF52832 nRF52810. If you need verification, I can send all the scripts to you for verification.

3. It is important that you find an nRF52820 device to verify the UART DFU example.

Thank you for all your assistance.
Kind regards,
Peter.Min

RE: case about nRF52820 uart dfu

Edvin — Thu, 21 Jul 2022 12:45:27 GMT

Hello Perer.Min. I will be working today and tomorrow, before returning in august. If this is more urgent, please open a new case with where you summarize your new question, since this is no longer about the issue in the title.

[quote user="Edvin Holmseth"]The scripts that are used are a bit too complicated. If you provide something that I can use to replicate this with an 820 device when I return to the office in August, I can test it. Ideally just one script with hardcoded paths and names.[/quote]

Since you can replicate it on an nRF52833, I will try to provide you a script that I used to test on the nRF52833 without any issues. Can you please provide a simiar script? Preferably for the nRF52833, since we don't have any proper nRF52820 DKs that I can test on.

1:
generate a key pair in the folder SDK17.1.0\examples\dfu with the private key named private.key and the public key named dfu_public_key.c (or rename the ones that you already have).

2: Unzip the following folder so that you get the path SDK17.1.0\examples\dfu\secure\bootloader\pca10100_uart(custom)\armgcc\

devzone.nordicsemi.com/.../pca10100_5F00_uart_2800_custom_2900_.zip

3: Unzip the following folder so that you have the path: SDK17.1.0\examples\peripheral\blinky\pca10100(custom)\mbr\armgcc\

devzone.nordicsemi.com/.../pca10100_2800_custom_2900_.zip

Then run the .bat script called test.bat in SDK17.1.0\examples\dfu\secure_bootloader\pca10100_uart(custom)\armgcc\test.bat

You can see the last line in test.bat that is commented out:

::nrfutil dfu serial -pkg files\dfu_img.zip -p COM11 -b 115200

run it when the script is done (without the semi columns) and remember to change to whatever com port you are using.

If that succeeds without errors, please provide a similar sample that fails (on the same format).

Best regards,

Edvin

RE: case about nRF52820 uart dfu

peter.min — Thu, 07 Jul 2022 01:42:01 GMT

Hi Edvin,

1. Nonetype 'to object' must be connected to nRF52820 or nRF52833 device.

2.You can test the nRF52820 example on nRF52833.

3.It can wait until after the holidays.

4.I can verify any code for you.

5. This case is to obtain a SAMPLE of nRF52820 UART DFU. If you think it is not appropriate to continue, I can open another case.

Kind regards,
Peter.Min

RE: case about nRF52820 uart dfu

Edvin — Wed, 06 Jul 2022 12:53:24 GMT

I don't have an nRF52820 to test on (I am on home office during the summer), and it is 3 months since this case went silent, so I didn't bring any nRF52820 devices. I tried to just plug an nRF52840 DK programmed with a standard bootloader, and it gave the response that it was an invalid object, which it is. Does the "'nonetype' to object" error come regardless whether it is connected to the nRF52820 device or not? Should I be able to replicate that error without a device connected?

The scripts that are used are a bit too complicated. If you provide something that I can use to replicate this with an 820 device when I return to the office in August, I can test it. Ideally just one script with hardcoded paths and names.

If this is more urgent, and can't wait until August, please create a new ticket, and it will be assigned to someone who is working this summer. The subject of this ticket has deviated enought from the original title/question, so it might be time to start a new case either way.

Best regards,

Edvin

RE: case about nRF52820 uart dfu

peter.min — Wed, 06 Jul 2022 10:02:12 GMT

Hi Edvin

I test nRF52840 nRF52832 nRF52833 nRF52810 ble dfu uart dfu OK

example:https://pan.olib.cn/%EF%BC%887%EF%BC%89%EF%BC%9A%E6%B5%8B%E8%AF%95%E4%BE%8B%E7%A8%8B%EF%BC%88%E5%8A%9F%E8%80%97%20%E5%A4%96%E8%AE%BE%20DFU%20FDS%20AT%EF%BC%89/nRF52/nRF5_SDK_17.1.0_ddde560_dfu.zip

bootloader:

#define RX_PIN_NUMBER 28
#define TX_PIN_NUMBER 6

change nRF5_SDK_17.1.0_ddde560_dfu\dfu_nrf52820\0_env.cmd

SET KEIL_UVISION5_PATH="C:\Program Files (x86)\Keil_v5\UV4\UV4.exe"
SET NRFUTIL_PATH="..\external\micro-ecc\nrfutil.exe"
SET MERGEHEX_PATH="C:\Program Files (x86)\Nordic Semiconductor\nrf-command-line-tools\bin\mergehex.exe"
SET NRFJPROG_PATH="C:\Program Files (x86)\Nordic Semiconductor\nrf-command-line-tools\bin\nrfjprog.exe"

You can use scripts 1-6

Kind regards,
Peter.Min

RE: case about nRF52820 uart dfu

Edvin — Tue, 05 Jul 2022 07:48:40 GMT

Does this happen with all applications that you have tried?

Does it work on a standard example using another chip, e.g. the nRF52840dk or nRF52832/nRF52833?

Can you please upload the image you are using, together with the bootloader project and the application project so that I can try to replicate the issue?

Also, can you please try to use at least two "-v" flags to get more verbose output:

e.g.: nrfutil -v -v dfu serial -pkg files\dfu_img.zip -p COM20 -b 115200 (but with your image and COM port)

Best regards,

Edvin

RE: case about nRF52820 uart dfu

peter.min — Tue, 05 Jul 2022 01:07:53 GMT

Hi Edvin,

Sorry, transcription error

Here are the instructions

nrfutil pkg generate --key-file private.pem --hw-version 52 --sd-req 0x0103 --application APP.hex --application-version 0xFF APP.zip

Kind regards,
Peter.Min

RE: case about nRF52820 uart dfu

Edvin — Mon, 04 Jul 2022 10:47:45 GMT

[quote user="peter.min"]-application APP.zip[/quote]

APP.zip should not be the --application argument. You should be able to generate the image without the image being present, meaning. Try to delete APP.zip, and you would see that this wouldn't work.

Try using the application .hex file in the --application argument instead.

Best regards,

Edvin

RE: case about nRF52820 uart dfu

peter.min — Mon, 04 Jul 2022 09:45:10 GMT

Hi Edvin,

nrfutil pkg generate --key-file private.pem --hw-version 52 --sd-req 0x0103 --application APP.zip --application-version 0xFF APP.zip

nrfutil version 6.1.0

Kind regards,
Peter.Min

RE: case about nRF52820 uart dfu

Edvin — Mon, 04 Jul 2022 08:39:13 GMT

Hello Peter,

Can you also please show what command you used to generate the image?

It should start with "nrfutil pkg generate ..."

And what version of nrfutil have you installed?

"nrfutil version"

BR,

Edvin

RE: case about nRF52820 uart dfu

peter.min — Sat, 02 Jul 2022 08:39:15 GMT

Hi Edvin,

The NRFUTIL code is shown below:

Kind regards,
Peter.Min

RE: case about nRF52820 uart dfu

Edvin — Fri, 01 Apr 2022 06:57:38 GMT

I can't see what arguments you are using in your nrfutil call. Can you try it without your script that you sent in the last reply?
e.g.
"nrfutil dfu usb-serial ..."

This error looks to come from nrfutil, and not the bootloader. I guess that one of the nrfutil arguments are not populated properly, so I suggest you get it working with a raw command before you add your long script that abstracts everything away.

BR,

Edvin

RE: case about nRF52820 uart dfu

peter.min — Fri, 01 Apr 2022 01:19:45 GMT

Hi Edvin,

The following data appears

Thank you for all your assistance.
Kind regards,
Peter.Min

RE: case about nRF52820 uart dfu

Edvin — Thu, 31 Mar 2022 12:28:11 GMT

[quote user="peter.min"]

1. I modified the following macro definition, and the bootloader did not report any more errors

FLOAT_ABI_SOFT xNRF52 xNRF52_PAN_74

[/quote]

Does that mean that your bootloader is starting up as expected? (running to main()?)

What does nrfutil say when you try to update the image?

BR,
Edvin

RE: case about nRF52820 uart dfu

peter.min — Thu, 31 Mar 2022 09:01:14 GMT

Hi Edvin,

1. I modified the following macro definition, and the bootloader did not report any more errors

FLOAT_ABI_SOFT xNRF52 xNRF52_PAN_74

2. Read data as follows

C:\Windows\system32>nrfjprog --memrd 0x10001014
0x10001014: 00038000 |....|

C:\Windows\system32>nrfjprog --memrd 0x10001018
0x10001018: 0003E000 |....|

3. I failed to execute the DFU command again

devzone.nordicsemi.com/.../nRF52820-uart-dfu.zip

4.www.dreamsourcelab.com/.../

https://www.dreamsourcelab.com/download/

5.We can see that the last instruction nrFUtil sent was 0x04 0xC0

6.Why cannot the DFU command continue

7.The configuration is as follows:

@echo off
echo "==================================================================================================================="
echo "The following parameters need to be reset as needed"
echo "set the dfu tools path"
SET KEIL_UVISION5_PATH="C:\Program Files (x86)\Keil_v5\UV4\UV4.exe"
SET NRFUTIL_PATH="..\external\micro-ecc\nrfutil.exe"
SET MERGEHEX_PATH="C:\Program Files (x86)\Nordic Semiconductor\nrf-command-line-tools\bin\mergehex.exe"
SET NRFJPROG_PATH="C:\Program Files (x86)\Nordic Semiconductor\nrf-command-line-tools\bin\nrfjprog.exe"

echo "set the dfu project path"
SET DFU_PROJECT_PATH_BOOTLOADER_BLE="..\examples\dfu\secure_bootloader\pca10100e_s112_ble\arm5_no_packs\secure_bootloader_ble_s112_pca10100e.uvprojx"
SET DFU_PROJECT_PATH_BOOTLOADER_UART="..\examples\dfu\secure_bootloader\pca10100e_uart\arm5_no_packs\secure_bootloader_uart_mbr_pca10100e.uvprojx"
SET DFU_PROJECT_PATH_BOOTLOADER_USB="..\examples\dfu\secure_bootloader\pca10100e_usb\arm5_no_packs\secure_bootloader_usb_mbr_pca10100e.uvprojx"
SET DFU_PROJECT_PATH_APPLICATION="..\examples\ble_peripheral\ble_app_buttonless_dfu\pca10100e\s112\arm5_no_packs\ble_app_buttonless_dfu_pca10100e_s112.uvprojx"
rem SET DFU_PROJECT_PATH_APPLICATION="..\examples\ble_peripheral\ble_app_uart\pca10100e\s112\arm5_no_packs\ble_app_uart_pca10100_s112.uvprojx"

echo "set the dfu hex path"
SET DFU_HEX_PATH_SD="..\components\softdevice\s112\hex\s112_nrf52_7.2.0_softdevice.hex"
SET DFU_HEX_PATH_BL_BLE="..\examples\dfu\secure_bootloader\pca10100e_s112_ble\arm5_no_packs\_build\nrf52820_xxaa_s112.hex"
SET DFU_HEX_PATH_BL_UART="..\examples\dfu\secure_bootloader\pca10100e_uart\arm5_no_packs\_build\nrf52820_xxaa_mbr.hex"
SET DFU_HEX_PATH_BL_USB="..\examples\dfu\secure_bootloader\pca10100e_usb\arm5_no_packs\_build\nrf52820_xxaa.hex"
SET DFU_HEX_PATH_APP="..\examples\ble_peripheral\ble_app_buttonless_dfu\pca10100e\s112\arm5_no_packs\_build\nrf52820_xxaa.hex"
rem SET DFU_HEX_PATH_APP="..\examples\ble_peripheral\ble_app_uart\pca10100e\s112\arm5_no_packs\_build\nrf52820_xxaa.hex"

echo "set the dfu hex version"
SET DFU_IC_FAMILY="NRF52"
SET DFU_HEX_HW_FAMILY="NRF52QFAB"
SET DFU_HEX_VERSION_APP="3"
SET DFU_HEX_VERSION_BL="2"
SET DFU_HEX_VERSION_ST="2"

echo "set the dfu packaged version"
SET DFU_PKG_HW_FAMILY="52"
SET DFU_PKG_VERSION_SD_ID="0x0103"
SET DFU_PKG_VERSION_SD_REQ="0x0103"
SET DFU_PKG_VERSION_APP="0xFF"
SET DFU_PKG_VERSION_BL="0xFF"

echo "if you have more then one jlink you can use this parameters to specify one of a jlink"
SET DFU_JLINK_SNR="683054148"

echo "if use dfu from com or usb com you must set this com port and baudrate"
SET DFU_COM_BAUD="115200"
SET DFU_COM_PORT="COM14"
SET DFU_USB_COM_PORT="COM38"

echo "if use dfu from ble base ble name you must set this name"
SET DFU_IC_NAME="Nordic_Buttonless"

echo "if use dfu from ble base ble mac you must set this mac"
SET DFU_IC_MAC="D3:F1:96:04:74:0A"

echo "==================================================================================================================="
echo "The following parameters retain the default Settings"
set CRLF=^& echo.
SET DFU_KEY_BACKUP_TIME=%date:~0,4%-%date:~5,2%-%date:~8,2%-%time:~0,2%-%time:~3,2%-%time:~6,2%-%time:~9,2%
SET MICRO_ECC_FOLDER_SOURCE_PATH=".\micro-ecc"
SET MICRO_ECC_FOLDER_TARGET_PATH="..\external\micro-ecc"
SET MICRO_ECC_LIB_PATH="..\external\micro-ecc\nrf52hf_keil\armgcc\micro_ecc_lib_nrf52.lib"

SET DFU_PUBLIC_KEY_NAME="dfu_public_key.c"
SET DFU_PUBLIC_KEY_PATH="..\examples\dfu\"
SET DFU_PRIVATE_KEY_NAME="private.pem"
SET DFU_KEY_BACKUP_DIRECTORY_NAME="backup"
SET DFU_KEY_BACKUP_DIRECTORY_PATH=".\backup\"

SET DFU_HEX_NAME_SD="SD.hex"
SET DFU_HEX_NAME_BL="BL.hex"
SET DFU_HEX_NAME_APP="APP.hex"
SET DFU_HEX_NAME_APP_NEW="APP_NEW.hex"

SET DFU_HEX_NAME_ST="ST.hex"
SET DFU_HEX_NAME_SD_APP="SD_APP.hex"
SET DFU_HEX_NAME_SD_APP_BL="SD_APP_BL.hex"
SET DFU_HEX_NAME_MERGED="MERGED.hex"

SET DFU_PKG_NAME_BL="BL.zip"
SET DFU_PKG_NAME_SOFTDEVICE="SD.zip"
SET DFU_PKG_NAME_APP="APP.zip"

SET DFU_PKG_NAME_BL_SD="BL_SD.zip"
SET DFU_PKG_NAME_BL_SD_APP="BL_SD_APP.zip"
SET DFU_PKG_NAME_SD_APP="SD_APP.zip"

echo "==================================================================================================================="

@echo off & setlocal EnableDelayedExpansion
SET CRLF=^& echo.
echo "==================================================================================================================="
echo "dfu packaged from uart"
CALL "%~dp0\0_env.cmd"
echo "dfu app from uart"
%NRFUTIL_PATH% dfu serial -pkg %DFU_PKG_NAME_APP% -p %DFU_COM_PORT% -b %DFU_COM_BAUD%

echo "==================================================================================================================="
pause

8. The test code is as follows

devzone.nordicsemi.com/.../8233.ble_5F00_app_5F00_buttonless_5F00_dfu.zip

devzone.nordicsemi.com/.../nRF52820-bootloader.zip

9.The configuration is as follows:

#define RX_PIN_NUMBER 28
#define TX_PIN_NUMBER 6

#define NRF_DFU_SERIAL_UART_USES_HWFC 0

#define NRF_BL_DFU_ENTER_METHOD_BUTTON_PIN 20

Thank you for all your assistance.
Kind regards,
Peter.Min

RE: case about nRF52820 uart dfu

Edvin — Wed, 30 Mar 2022 12:31:30 GMT

I believe you should set your RAM settings:

start: 0x20000008

size: 0x7FF8.

After programming the bootloader and MBR, can you please run the following command:

nrfjprog --memrd 0x10001014

and

nrfjprog --memrd 0x10001018

What do they output?

BR,

Edvin

RE: case about nRF52820 uart dfu

peter.min — Tue, 29 Mar 2022 10:01:03 GMT

Hi Edvin,

1. I make sure I set up the correct addresses

2. During the debug process, it is found that the program does not run to the main entrance of the bootloader

3. I used nRF52820 module for testing

4. Is there anything else that needs to be changed?

5. Other s112 + MBR = 100 KB

6.Calculate the application available space

settings = 4kb

mbr data = 4kb

bootloader =24kb

application = ?

softdevice = 96kb

mbr = 4kb

Application free space: 256-4-4-24-96-4= 124KB

7.The address before the error was reported is as follows:

Thank you for all your assistance.
Kind regards,
Peter.Min

RE: case about nRF52820 uart dfu

peter.min — Tue, 29 Mar 2022 09:51:42 GMT

Hi Edvin,

1. I make sure I set up the correct addresses

2. During the debug process, it is found that the program does not run to the main entrance of the bootloader

3. I used nRF52820 module for testing

4. Is there anything else that needs to be changed?

5. Other s112 + MBR = 100 KB

6.Calculate the application available space

settings = 4kb

mbr data = 4kb

bootloader =24kb

application = ?

softdevice = 96kb

mbr = 4kb

Application free space: 256-4-4-24-96-4= 124KB

7.The address before the error was reported is as follows:

Thank you for all your assistance.
Kind regards,
Peter.Min

RE: case about nRF52820 uart dfu

Edvin — Mon, 28 Mar 2022 18:46:49 GMT

Hello,

It seems I never tried to build a bootloader for the nRF52820 (at least with Keil), because I was not able to compile your project. Do you happen to know where to get the file that it claims to be missing (It is evening, and I am sitting at home. I can reach out to some colleagues tomorrow if I don't find it). I assume that you have what you need to compile, other than the

However, I see that the array that you refer to is missing the nRF52820. However, the nRF52820 has different flash and RAM sizes from the other devices. As you can see here, it has 256 kB flash and 32kB RAM. This means that the flash is on the address:

0x0000 0000 -> 0x0004 0000

And the RAM is on the address:

0x2000 0000 -> 0x2000 8000

So an appropriate set of the bootloader's memory segments should be somthing like:

Bootloader settings: 0x0003 F000 -> 0x0004 0000

MBT parameter storage: 0x0003 E000 -> 0x0003 F000

Bootloader: 0x0003 8000 -> 0x0003 E000

Application area (depending on the softdevice that you use, but if you are using only MBR) : 0x0001 0000 -> however large you need, but less than 0x0003 F000. You don't need to specify the top.

Master Boot Record (MBR) 0x0000 0000 -> 0x0000 1000

SoftDevice -

If you intend to have a softdevice, your softdevice will replace the MBR, and the application will start after the softdevice. E.g. if you use the S112 from SDK17.1.0:

Softdevice: (which includes MBR) 0x0000 0000 -> 0x0002 8000

This leaves this flash for the application: 0x0002 8000 -> 0x0003 8000 (NB: Only 64kB).

I hope this clears things up a bit. Let me know if anything was unclear.

BR,

Edvin