2024-03-21 01:54 PM
Hello,
we had a play with the memory tool to configure the memory regions (the linking to the OCTOSPI configuration, etc is neat), however we ran into the following issue:
When using the tool, the internal RAM is configured as `Device` memory, rather than normal memory. Which in turn disallows unaligned accesses to memory.
Unfortunately, even with `-mno-unaligned-access` we still get some register-indirect unaligned accesses to malloced memory.
Also we deal with some packed structs, so need unaligned access to RAM.
In the Cortex configuraiton I can see the configuration options, but they are all greyed out
How can I change the memory type in the memory tool from device to normal?
2024-03-25 07:11 AM
Hello @malte.vesper
Could you please provide your IOC in order to push further the investigation.
I will be waiting for your feedback .
THX
Ghofrane
2024-03-26 01:02 AM
Hello,
There is no need of IOC file. I've reproduced the symptom and identified the root of the issue.
The issue is not related to the memory tool and is present even when one manually configures the MPU regions (in CORTEX_M33 or CORTEX_M33_S panel). The generated code MPU_Config() is incomplete and the MPU regions remain in the default value: device memory.
We are trying to fix this problem in the next STM32CubeMX release.
BR
Jingyi
2024-03-26 01:17 AM
Hello @malte.vesper
Thanks again for your contributions .
Internal ticket number: 176981 (This is an internal tracking number and is not accessible or usable by customers).
I'll keep you posted with the updates.
KR,
Ghofrane
2024-04-01 12:27 PM
Thanks for spending the time to reproduce. looking forward to the fix.