DFU on nRF Master Control Panel (andriod version)

[oceanide]

Dear all.

I have some test result on DFU feature. Please any comment on this issue.

test condition

• Mater control panel (64-bit version)

• nRFgo studio (64-bit version) : 1.19.0.7

• Smart Beacon Kit : PCA20006

• Pre-compiled binary within Smart Beacon Kit v1.1.0

test result

• With PCA10000 dongle : The DFU is successful with all binaries.

• nRF Master Control Panel v2.1.1 (android version)

  Only application DFU is successful. The DFU with bootloader and softdevice is NOT successful. Remote DFU Invalid CRC error happen so that I captured log files for two cases.

dfu-android-bootloader-Log 2015-06-01 210155.txt

dfu-android-sd-Log 2015-06-01 210410.txt

BR

oceanide

[Hung Bui]

@Oceanide: I'm sorry indeed for the late response.

Regarding the issue, which .zip file did you use to update the softdevice and bootloader ? Could you attach them to your question?

Have you tried to do DFU with nRFToolbox and nRFBeacon app ?

The nRFMaster Control Panel may not be compatible with the new .zip file standard (with .json file). We are releasing a new version of the Master Control Panel in the next few days.

bootloader.hex

bootloader.dat

[oceanide]

Thank you for response.

I did not used .zip file with Master control panel. I tried to use each hex file to update softdevice, bootloader and application binary.

Using nRFToolbox, I also tried to update with each hex binary, but I got failed.

I just want to know if softdevice and bootloader files can update with master control panel(android version) using each hex files, not .zip file.

Thanks in advance

oceanide

[Hung Bui]

@Oceanide: Have you make sure you have included the .dat file after you select the .hex file ?

How did you generate the .dat file ?

You should use nrf.exe tool to generate the .zip file and then unzip, take out the .dat file inside the zip.

Init file is required on the bootloader for Beacon v1.1 (equivalent to the DFU on SDK v7.1 for nRF51) I attached in my answer the bootloader.hex and bootloader.dat that you can try.

I tested here and got no problem to update the bootloader with nRF Master Control Panel on Android .

[oceanide]

@Hung Bui

When I tried to use your bootloader hex file, it looks like bootloader downloading is done successfully. But, I got a error message as "Error (0x85): GATT ERROR", so I attached a log file.

log.txt

When I pressed a button to enter DFU mode again, I never entered into DFU mode and just stayed in normal beacon mode.

Could you please .dat file for all pre-compiled binaries (softdevice, bootloader, application) of beacon v1.1? I would like to compare if my .dat files are correct or not.

Thanks in advance

oceanide

[Aleksander Nowakowski]

Hi, all Android apps (nRF MCP, Toolbox and Beacon) support all features of DFU. You should be able to update only softdevice or only bootloader using the hex file (with providing .dat file, if required by the bootloader). You should also be able to update softdevice and bootloader by putting them to a ZIP file and naminig the files softdevice.hex, bootloader.hex (and optionally system.dat with the init packet for combined files). However, as Hung said, we now recommend you to use the nrf.exe tool from the PC version on Master Control Panel. I have written some documentation how to do that here: github.com/.../init packet handling