Incorrect partition table data returned by `stse_data_storage_get_partitioning_table()` on STSAFE-A110

[parmi93]

    uint8_t total_zone_count = 0;
    
    stse_data_storage_get_total_partition_count(&stse_handle, &total_zone_count);
    
    stsafea_data_partition_record_t data_partition_record_table[10] = {0};
    
    stse_data_storage_get_partitioning_table(
            &stse_handle,
            total_zone_count,
            data_partition_record_table, 
            10
    );

Content of data_partition_record_table after calling stse_data_storage_get_partitioning_table():

According to the datasheet AN5762 (table 5), the first record (data_partition_record_table[0]) appears to be correct.

The second record (data_partition_record_table[1]) is mostly correct, except for the data_segment_length field, which is 677 instead of the expected 700 according to the datasheet.

The remaining six records appear to be completely incorrect. They seem to contain corrupted or invalid data.

My device is an STSAFE-A110. Is this behavior expected?

[nils-cercariolo-st]

Hello,
The issue here comes down to using 10 as a fixed value for the Partitioning_table_length argument.

When using stse_data_storage_get_partitioning_table, the length expected is the number of bytes, not how many partitions we want to query.

Using below snippet will fix your issue.

uint16_t data_partition_record_table_length = sizeof(data_partition_record_table);
stse_data_storage_get_partitioning_table(
		&stse_handle,
		total_zone_count,
		data_partition_record_table,
		data_partition_record_table_length
);

Thank you for noticing it, if it made you confused then I'll improve the documentation on it.

For further information, please refer to this example , particularly at apps_print_data_partition_record_table which is a higher level API and you will see best practice of using this function.

[parmi93]

Thanks. The documentation suggested that Partitioning_table_length referred to the number of elements in the array (i.e., its length) rather than its total size in bytes, especially since the parameter name uses the term length instead of size, which typically have different meanings in programming.

In general, “length” refers to the number of elements in a collection (e.g., the number of entries in an array), while “size” usually refers to the amount of memory occupied, expressed in bytes. This distinction is important, as confusing the two can easily lead to incorrect buffer allocation or misuse of APIs.

Additionally, the documentation in the “Use-case example” is incorrect, as the function stse_data_storage_get_partitioning_table() is called with three arguments instead of four (the Partitioning_table_length parameter is missing). The PR #83 fixes both issues.

[nils-cercariolo-st]

Hi, fully agree with you, it's an oversight from our side, will try to check if this is also in other places. Thanks !

For the example, the actual code where to look at was more here. Where we correctly call all four arguments.