Dear Dialog Support,
I often have to use UART to programm our DA14585. I use the CIB from the DA14583 IOT sensor and at the moment Smart Snippets 5.0.12.
When I program a new binary file, I click "burn and verify", and the procedure is as follows:
- Started erasing from 0x00 to 0x83FFF (132 sectors)
- Reading memory to verify its contents after erase...
- Check if memory empty...
Memory empty. Procceed with burn.
- Started burning memory with 539520 bytes of data at address 0x00.
- Reading memory to refresh table contents....
SPI memory verification succeeded.
It looks to me like the programmer has just combined the function calls for "Erase" and "Burn" - since the "Erase" procedure finishes with verifying the empty flash, and then the "Burn" procedure starts again with verifying the empty flash. So, unnecessarily, this is done twice.
My colleague and I are begging you on our knees to fix this. This drains the life out of us!
On top of that, if I may humbly state another request: Why is the verification not optional? We never encountered a failed verification, so we would like to skip this in the process.
I hope you hear our prayers! :-)