dfu problem with my own mobile application

RE: dfu problem with my own mobile application

Hung Bui — Mon, 14 Sep 2015 11:33:04 GMT

Hi,

10-02-01 means the nRF51 accepted the "initialize DFU parameter" command (ReqOpcode 0x02) you sent. Next step is to send the write command to DFU Control Point characteristic with OpCode 0x03 to start transmitting the image. Then you can send the image to DFU Packet characteristic. You can have a look at the sequence chart called "Transfer of an image to the DFU target" in the documentation here.

RE: dfu problem with my own mobile application

Mohamed O.Abouzeid — Sun, 13 Sep 2015 14:02:39 GMT

any help !!!

RE: dfu problem with my own mobile application

Mohamed O.Abouzeid — Sat, 12 Sep 2015 14:25:40 GMT

I sent 0x0104 & then sent the file size format recieved 10-01-01 which is correct then I sent 0x0200 and then the info in the dat file to dfu packet then 0201 to control point I revceived 10-02-01

what should I do next

RE: dfu problem with my own mobile application

Aleksander Nowakowski — Thu, 10 Sep 2015 08:47:38 GMT

Sending a byte array should work. As far as I remember I do the same in the DFU Library.

RE: dfu problem with my own mobile application

Hung Bui — Thu, 10 Sep 2015 08:41:27 GMT

@mohamed: I have a suggestion that you capture a correct DFU session by the sniffer when using our Master Control Panel app to do DFU. Then you compare it to what you do with your mobile app. Then you can find the difference and can modify your app to match.

RE: dfu problem with my own mobile application

Mohamed O.Abouzeid — Wed, 09 Sep 2015 20:08:05 GMT

I'm sending the command in array of bytes not a one word I mean I send 0x0104 by uint8_t command[]={0x01,0x04} which one is true ? ? or it doesn't a matter

RE: dfu problem with my own mobile application

Mohamed O.Abouzeid — Wed, 09 Sep 2015 19:07:38 GMT

okay I'll try that & ask you again thank you for help

RE: dfu problem with my own mobile application

Aleksander Nowakowski — Wed, 02 Sep 2015 09:03:08 GMT

Hi, Instead of writing this yourself I recommend you to use the DFU Library instead. You'll find them on GitHub: github.com/.../Android-DFU-Library (Android) and github.com/.../DFU (iOS). They are well tested and handle all errors and events. You may include them in your application easily and modify if needed (but should work out of the box). However, coming back to your question. Please check the following things:

The DFU Start 0x0104 is used to upload an application. It is supported since the DFU Bootloader from SDK 6.0.0. Before that it was not possible to update a Soft Device or a Bootloader and the DFU Start command was only 0x01.
If you send 0x0104 you should send the file size in 12 bytes, where the first 8 are zeros. The last 4 bytes are the size as Int32 written in Little Endian. For example, if your application is 4 bytes the packet would be 0x000000000000000004000000.
The file size must be dividable by 4.

I hope that helped. I'll try to come up with 4. if you did everything like above.