Other Parts Discussed in Thread: UNIFLASH
Dear all,
I have a Simplelink BLE SDK application working well on a CC26x2r-based design.
I have received back one device from a customer because it was not working. Problem was a firmware snippet writing 7 bytes using osal_snv_write started to fail. I reflashed the firmware, tried again, same error. Only after using Uniflash Flash mass erase and reflashing the firmware, the device worked again.
On a fresh device, I did a test where I wrote 2000 times the same 7-byte value without a single error. I don't think the first device has been written any near 2000 times. In the application, the BLE client reads the 7-bytes value from internal flash, increments it and updates it back to internal flash. This happens once a day at most. The only functions used are osal_snv_write and osal_snv_read. No fancy stuff here. So the osal manager should take care of everything.
I have seen other threads such as this one experimenting the same issue.
Can you please indicate any possible explanation, past experience and/or source of error (power?, 7-bytes length?).
Thanks a lot.
