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.

[Frank Zhao]

Yes, I already knew it is the fact that the rate of transmitting is causing the pstorage queue to fill, not really the size

The test was done with a hex that exceeded 80KB (which I know exceeds the dual bank limits, but I modified the DFU code to behave as if it was single bank)

In fact, I can get it working by increasing the connection interval, but it ends up taking so long that I don't have the patience to complete the testing

The central device is a Samsung Galaxy Note 3, Android 4.3

I believe the the connection interval was 12 to 15 ms during the tests that failed.