What are the test images for single bank update?

RE: What are the test images for single bank update?

Hung Bui — Thu, 31 Aug 2017 13:38:08 GMT

Hi Jorge,

You only need to apply the modify if you plan to flash the application via Jlink instead of doing OTA DFU.

If you just want to update the bootloader, you don't have to do that, just leave it as it is.

If you plan to flash (and merge maybe) the softdevice + bootloader + application, then you can do that.

You say it doesn't work on your custom board, what exactly the issue ?

RE: What are the test images for single bank update?

Jorge — Thu, 31 Aug 2017 11:49:59 GMT

I found out what was causing this.

I changed in the bootloader_settings.c file the line 19 to uint8_t m_boot_settings[CODE_PAGE_SIZE] __attribute__((at(BOOTLOADER_SETTINGS_ADDRESS))) __attribute__((used)) = {BANK_VALID_APP};

This change was to use this code on the new board since I was seeing that the code was not going through on the file "bootloader.c" in line 114 if (p_bootloader_settings->bank_0 == BANK_VALID_APP)

And this was suggested in this answer

Can you help me on this? If I reverse this change it works on the nrf51 but not on my custom board. Thank you for the help so far.

RE: What are the test images for single bank update?

Jorge — Thu, 31 Aug 2017 10:33:22 GMT

I am testing with the nrf51 DK, I will try with your files then and see if it works here.

RE: What are the test images for single bank update?

Hung Bui — Thu, 31 Aug 2017 10:26:34 GMT

I tested here with your script and have no problem updating the bootloader. Are you testing with our nRF51 DK or your own PCB board ? Do you have 32kHz crystal on the board ? I attached the bootloader hex and .zip file in my answer above so you can test on your side.

RE: What are the test images for single bank update?

Jorge — Thu, 31 Aug 2017 07:56:14 GMT

Yes, I switch to bootloader mode. I do the same when loading the application.

The command I use to create the zip is : nrfutil.exe dfu genpkg [path of the zip] --sd-req 0xFFFE --application-version 0 --dev-type 0 --dev-revision 0 --bootloader [path of the bootloader]

For DFU : nrfutil.exe dfu serial --package=[path of zip] --port=COM6 --baudrate=38400 --flowcontrol

My board is connected to port COM6 and is using flowcontrol with baudrate of 38400.

To create the hex files I use KEIL and just build the codes with optimization -O3, I don't know if you need more specifics for this.

My point is that the only thing I cannot load via serial DFU is the bootloader, and I am not sure why. At your side you can load the single bank bootloader via serial DFU?

RE: What are the test images for single bank update?

Hung Bui — Thu, 31 Aug 2017 07:47:47 GMT

Hi JCosta,

I assume you switch to bootloader mode before you test on step 4 ? (press button 4 and reset)

Could you list the scripts you used to generate the .zip files ?

Could you list the script you used to generate hex

RE: What are the test images for single bank update?

Jorge — Wed, 30 Aug 2017 12:36:00 GMT

What I am trying to do is a serial dfu on a nRF51.

Step 1-I load the Softdevice 130 to the nrf51 board via the nRFgo.

Step 2-I compile the unmodified project of the bootloader on SDK 11 and then load it via nRFgo to the same nrf51 board.

Step 3-To make sure that the DFU is working I load my application via serial DFU using the nRFgo, and the application is correctly loaded since I can see the board advertising the correct services.

Step 4-I try to load via serial DFU on the nRFgo the bootloader file (the same I previously loaded) and it give a timeout error : "Timed out waiting for aknowledgement from device. Failed to upgrade target. Error is: no data received on serial port. Not able to proceed. (...)"

So the error that I am having is that I cannot load the unmodified bootloader example from SDK11 via serial DFU. But I can load the applications and old bootloaders

RE: What are the test images for single bank update?

Hung Bui — Wed, 30 Aug 2017 12:18:36 GMT

When you mention about an error, always describe what exactly the error is. The hex file doesn't include any init packet. Hex file is the application/bootloader image. The init packet is only included in the .zip file.

Please try to describe what you are doing with step by step, starting with flashing the softdevice and so on. Please try testing with unmodified bootloader example.

RE: What are the test images for single bank update?

Jorge — Wed, 30 Aug 2017 10:51:27 GMT

Does the pre compiled ("dfu_test_bootloader_b_hci_s130.hex") image contains the init packet for the dfu?

Is this needed for doing the serial DFU? I was searching for some hints on other questions and found that this init packet could be the issue.

RE: What are the test images for single bank update?

Jorge — Tue, 29 Aug 2017 09:20:10 GMT

I want to make a serial dfu of the bootloader. If I use the bootloader project, I build it and try to load it it give me an error. But if I load the test image of the bootloader there is no error. I am not sure if the test image of the bootloader is suposed to be the image built by the bootloader project.

If it is not what are the differences? If they are the same do you know what can be causing one to not work and the other is working?

RE: What are the test images for single bank update?

Hung Bui — Mon, 28 Aug 2017 09:19:12 GMT

Hi Jorge,

Which exactly image you asking about, we have several images in the hci_dfu_send_hex folder.

The image is generated by using nrfutil tool according to the documentation here.

The name already tell which image/project it has for example dfu_test_app_hrm_s130.zip mean it's the ble heart rate example app inside.

bootloader.zip

bootloader.hex