Reading QSPI on Portenta Machine Control

Official Hardware Portenta Family Portenta H7
1

Hello all :slight_smile:

While working with the Portenta H7 Machine control I now have a new question. I have implemented the storing of important parameters in the QSPI and this has worked for months on up to 10 Portentas. But now I observe more and more often on one or two devices that the first readout of the QSPI (in setup()) fails. With manually saving the parameters again and reading it out, it works again. Here the read message are just weird signs and not the previous saved parameters.
So the code itself works for weeks and also reading and writing is working like intended. But once after some time the QSPI is like "deleted" or the space is replaced with weird "ÿ" signs. But that's really bad for my application, because the device need the saved parameters.

I know that the QSPI has a limited writing number, but I am not reaching this number.

I use this function for reading:
FlashIAPBlockDevice blockDevice(m_limits.start_address, m_limits.available_size);
…
blockDevice.read(buffer, 0, dataSize);

The question is, is the QSPI damaged? If yes, then why? How can I prevent this, because the QSPI is essential for my application? What can cause these two problems?

I hope someone can help me.
:slight_smile:

2

Which core are you using?
Could you share the sketch?

3

I managed to implement it to the real QSPI. In the question the storage medium was the Flash Memory. So with using the "QSPIFBlockDevice" library everything is working and the problem has not occured until now :slight_smile:

1 Like
4

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.