This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

DFU app bad handling of errors

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.

Parents
  • Hi Frank ,

    Could you let me know the size of your hex ? I don't think it was the size of the hex file that cause the issue. I suspect that it was the rate of transmitting DFU packets was too fast that filled the pstorage queue.

    Do you have a sniffer trace and check for the connection interval when updating the firmware ?

    Which central device did you use for testing ? What was the preferred connection interval you used in the bootloader firmware ?

Reply
  • Hi Frank ,

    Could you let me know the size of your hex ? I don't think it was the size of the hex file that cause the issue. I suspect that it was the rate of transmitting DFU packets was too fast that filled the pstorage queue.

    Do you have a sniffer trace and check for the connection interval when updating the firmware ?

    Which central device did you use for testing ? What was the preferred connection interval you used in the bootloader firmware ?

Children
No Data
Related