DFU Device Firmaware update shows update result for a short period of time

[Boris]

Hi, everyone,
We develope the projects on nordic nrf52832 chip module that include main project and bootloader.
The created update files (".hex" encoded to ".zip") we burn to module via BlueTooth by using the mobile-phone-application "nRF Toolgox Device Firmware update". After update this application shows the result message for a few seconds and than it hides it. In most cases it isn't possible to see the exact error result when burning fails. Even more if the burning is finished when nobody loocked on the screen it not always possible if the burning passed of failed.
Is it possible to configure this application to show the messages constantly without hiding them or at least to increase the timeout delay?

Another question reffers to selecting update file.
Before bufning We have to select the update file and BT-device for apdating in air. But after burning when we need to update the next same device by the same file we must reselect it again. We must reselect the same file even when before retrying to update in case the update failed. How is it possible to configure the application to cause it to remember selected update file?

Best Regards
Boris Fridman

[Hung Bui]

Hi Boris, 

We actually have the nRFLogger app to store and view the log after you used the nRFToolbox DFU profile. You can find the log on the panel on the left menu inside nRFLogger. 

You can also see the log when you use nRFConnect app to do DFU instead of using nRFToolbox DFU. 

[Boris]

Hi, Hung Bui,

I checked the Logger in the right panel, but how you said. This application was installed previously, but there weren't any information in reffering to "nRF ToolBox\DFU" program.

In anycase if you interested in feedback, for my mind the results given in BT flashing should be shown in "DEVICE FINWARE UPDATE" screen dirrectly for a longer period of time or constantly and not in logger only. In addition the program shoud remember the image after burning for case it is burnt to multiple devices to prevent reselection each time.

Thank you forward for paying attention

Best Regards

Boris Fridman

[Hung Bui]

Hi Boris, 

Thanks for your feed back. I have forwarded your case to our app team. You are right that the result should be retain for longer time, maybe until an OK click. 

Have you tried the nRF Connect, the logging should show inside the app, when you swipe fight. 

[Boris]

Hi, Hung Bui,

I tried previously to flash devices via bluetooth by "nRF Connect", but it didn't work. due to this reason I transmit the update images via "nRF Toolbox\DFU". But does the logging work with "nRF Toolbox" too or only with "nRF Connect"?

[Hung Bui]

I just got the information from our app team that nRFLogger doesn't support the DFU profile in nRFToolbox. But in nRFConnect you should see the log. 
Do you have the error all the time ? If you still see the error, could you describe the test setup you have ? Do you see the error if you test with stock example ? For example using our tutorial here. 

Could you capture the log on RTT of the NRF52  ?