dfu failed by Master control Panel(PC version).

RE: dfu failed by Master control Panel(PC version).

Hung Bui — Mon, 26 Sep 2016 11:26:49 GMT

How do you generate your .zip ? Note that on MCP on PC you have an option to choose the .hex file directly without the .zip. What happen after step 7 ? Do you see any error reported back ? Could you capture a sniffer trace ?

You can send the .zip file (by editing your question) so that I can check .

RE: dfu failed by Master control Panel(PC version).

sosse — Sat, 24 Sep 2016 13:51:06 GMT

Thank you for your answer. I can see "DFUTarg" after step 7, and I never successfully update by manual command,,but I can update using Master Control Application (from smart phone). I just wanted to check my generated zip is correct or not. Thank you.

RE: dfu failed by Master control Panel(PC version).

Hung Bui — Fri, 02 Sep 2016 11:02:35 GMT

Hi Sosse,

Have you made sure you do a complete erased of the chip before you test with "Testing the example manually (without bonding)" ?

Do you see the device advertise as "DFUTarg" after step 7 ? If you don't please test with the precompiled hex file provided in the \examples\ble_peripheral\ble_app_hrs\hex folder.

It's true that it's doesn't really mater which type of firmware types you send to switch from application to bootloader (01-01 or 01-04 etc). That command is only to tell the application to switch to the bootloader. When in bootloader mode, it's important as the bootloader check this to know which type of image it's receiving.