-
Notifications
You must be signed in to change notification settings - Fork 3
Arduino_UnifiedStorage::debuggingModeEnabled
and InternalStorage::readPartitions()
report different number of partitions
#45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
topic: code
Related to content of the project itself
type: imperfection
Perceived defect in any part of project
Comments
Full Serial Monitor for three relevant test cases on both the Portenta H7 and Portenta C33 are presented below. Portenta H7
Portenta C33
Note:
|
PR #39 rewrites functionality of the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
topic: code
Related to content of the project itself
type: imperfection
Perceived defect in any part of project
The Arduino_UnifiedStorage library provides the following two ways to access information about the partitions on the Internal storage, both of which are exhibited in SimpleStorageWriteRead.ino:
Arduino_UnifiedStorage::debuggingModeEnabled = true;
std::vector<Partition> partitions = InternalStorage::readPartitions();
InternalStorage::readPartitions()
is called to retrieve a list of partition configurations from the internal storage of the device. This is stored as a dynamically resizable array of objects, in this casepartitions
However, each approach has its own reality as to what partitions exist. As an example, if we format the Portenta H7 Internal storage to have a single 12MB FAT partition (by uploading the AUS_SPIS_FORMAT_001 sketch):
partitions
vector (as defined above) shows that only one partition existsThere should be no difference between the number of partitions reported by both approaches.
The text was updated successfully, but these errors were encountered: