2023-09-13 09:36 AM
The otherwise excellent STM32CubeMX tool has a bug in its Configuration Report output (reached via the File > Generate Report command). In the Peripherals and Middlewares Configuration section of the report, the left and right columns of the output are reversed or (more likely) line-wrapped.
See attached screen shot for an example -- this continues for many pages.
I could not find a better way to report this, so could the developer of this STM32CubeMX tool please to look into this issue, because it makes the report output very awkward to interpret.
Note that the STM32CubeIDE suffers from the same problem; it probably uses the same report generator.
Thanks in advance on behalf of all your customers.
-- David Adams
Solved! Go to Solution.
2023-09-14 12:42 AM
@Issamos , @Sarra.S : here is a summary of the findings.
The Report generator creates an off-by-one label/value mismatch after each "Power Domain:" label in the report. The "Power Domain:" label itself never has a value (which is probably the source of the problem), causing subsequent label/value pairs to be shifted one position, such that the labels end up in the right-hand column and their values in the left-hand column on the next line. See this screen shot:
Attached please find a freshly generated .ioc file to reproduce the problem. (The filename has an extra .txt extension to match its extension to its inferred MIME type -- remove the .txt before opening in STM32CubeMX.)
This was generated with STM32CubeMX 6.9.0 for an MCU type STM32MP157CAD3, with no changes after the new project was created. Use File > Generate Report to create the report.
The problem manifests itself after each "Power Domain:" label throughout the report. The full PDF report generated from this project is also attached for further inspection.
@Sarra.S : could you please forward this to the developers responsible for the STM32CubeMX software? Also note that the same issue applies to the reports generated by STM32CubeIDE, probably using the same report generator.
Thanks,
-- David
2023-09-14 03:01 AM - edited 2023-09-14 03:02 AM
Hello @tarmasr,
I have reproduced the same issue by starting a new project from scratch with your configurations!
Thank you for bringing this to our attention, I have reported this issue internally (161430: Internal ticket number)
Thank you!
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.