DFU app bad handling of errors

[Frank Zhao]

I am trying to bootload an extremely large hex file using a slightly modified DFU (modified from SDK v5.2.0's example)

The problem is that the hex is so large that eventually, pstorage's task queue is filled, and returns a no-memory error

The Android app "nRF Toolbox" v1.5.2 simply spits out a reset command back, which makes it impossible to load my hex

Please fix the app or the firmware example such that it actually waits for the previous flash write to complete, or gracefully handle busy conditions.

[Hung Bui]

@Frank: You are correct that the bootloader send the notification when it receives and queue the packet, not when it actually finish flashing the packet. I am sorry for the confusion.

However, it pretty strange that you have the queue full when receiving only one packet per connection interval (I assume so because the notification usually's sent in the next connection interval)

Have you tried to use our stock DFU example ? Would the same issue occur ?

Actually we haven't seen this issue when using DFU with 10 packet notification on various central devices tested here, including iPad mini, iPhone 5S, Samsung S4, S3, Nexus 4, 7 etc.

Could you send us your DFU firmware ? It would be easier to identify the issue if we could reproduce here