Flash memory on nRF52832

[Pham Nam]

hello, i have a question, i use sdk15.3 for nRF52832, i run for example flash_fds, sometimes it will not be able to erase or write to memory, after restarting the device, it can be written or erased. , but soon after seeing such a case again, can you give me a solution, thanks a lot!

[Einar Thorsrud]

Hi,

Can you provide more details on how you are testing and how it fails? Please remember that FDS write and erase operations are asynchronous, so you need to wait for an event indicating that the operation has completed.

[Pham Nam]

Thanks for the feedback.
I run the flash_fds example in sdk15.3, using the UART log on Hercules software.

I run the write command to flash memory, about 30 times maybe 35 times I started not receiving the message of successful writing on Hercules, but after resetting the kit via the reset button on the kit, I can write 1 more Again.

That's the process I made and saw the error, I tried on sdk15.2 and the result was similar, maybe I missed some important part that I didn't realize.

I look forward to hearing from you soon.

thank you!

[Einar Thorsrud]

Hi,

I have not been able to reproduce this, but I don't have exact steps so that may affect things. (I tested with PuTTY rather than Hercules, but which serial terminal you use should not be relevant.). Can you explain in full detail how you test? This may not be relevant, but since I am unable to reproduce and do not understand what could be going on it would be good to test the exact same setup.

• Which exact example project do you use? <SDK15.3>\examples\peripheral\flash_fds\pca10040\s132\ses\, or another one?
• Which file ID, record ID, and data do you write? Is it the same every time or not? If not, what is the pattern? Please describe accurately enough that I can duplicate your test on my side.
• After how many times do things fail (see printed Record ID)? In what way does it fail? Can you explain and show the terminal output you have at that point?
• Do you test on the nRF52 DK?

[Pham Nam]

I have recorded a video about the test process experiencing errors, I also encountered the same error on my product.

This is the link of KIT that I tested:

https://item.taobao.com/item.htm?spm=a230r.1.14.24.1b726b1esqEGU2&id=538662293049&ns=1&abbucket=15#detail

Looking forward to receiving feedback from you.
thank you very much!

[Einar Thorsrud]

Hi,

I do not have any explanation. I tried to replicate this doing the exact same way as you, using the same project from SDK 15.3 and the Hercules terminal, but I am not able to reproduce it. Can you provide a new link to the kit you were using, since it is dead?

[Pham Nam]

Hello,

this is the image of the kit I use

This is the image of the module I use in my product.

on the module I got the same error as on KIT

I bought them in China. The link I gave you is still good.

https://item.taobao.com/item.htm?spm=a230r.1.14.24.1b726b1esqEGU2&id=538662293049&ns=1&abbucket=15#detail

https://item.taobao.com/item.htm?spm=a230r.1.14.18.2f9b6b1ejD3Ujo&id=562985601445&ns=1&abbucket=15#detail

[Einar Thorsrud]

Hi,

Unfortunately, I am not able to reproduce this, and I do not have any explanation for what you are seeing.

I see from the text printed after reset that the records are not written (Found x valid records), so after the problem occurs all you really see is the echoing from your terminal, and nothing seems to happen on the nRF side. Could it be a UART issue? Or has an error occurred on the nRF side? What state is the nRF in if you check from the debugger?

I am not able to open any of the links you provided, but it is not important since it seems like a copy of the nRF52832 DK. Just one last HW related question. Which nRF52832 variant is on the DK (what is the chip marking)?