Skip to content
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

[stm32] Place stack in SRAM by default on H7, add lbuild option #1100

Merged
merged 2 commits into from
Dec 13, 2023

Conversation

chris-durand
Copy link
Member

The DTCM is not accessible by regular DMA on H7 devices, which leads to DMA transfer errors when DMA buffers are allocated on the stack. The default stack location is changed to the D1 SRAM. An lbuild option is added to select the stack location between SRAM and DTCM.

@chris-durand
Copy link
Member Author

@salkinium Do you have an idea how to fix the MacOS CI? There is some Python problem:

    import jinja2		# template engine
    ^^^^^^^^^^^^^
ModuleNotFoundError: No module named 'jinja2'
scons: *** [generated/xpcc/identifier.hpp] Error 1

jinja2 is not found, but only when building the XPCC examples.

@salkinium
Copy link
Member

salkinium commented Nov 18, 2023

The macOS Image Release was upgraded from 20231018.14 -> 20231025.2. In the process the pre-installed Python version is 3.12.0, while we install 3.11.6.
The issue is that the XPCC SCons integration calls the builds via a python3 command line, which points to 3.12.0, while jinja2 is only installed for 3.11.6.

The solution is to fix the XPCC SCons integration to use the same Python interpreter that it was called with and not delegate to the shell environment for it. 🙄

@salkinium
Copy link
Member

salkinium commented Dec 12, 2023

Gentle boop @chris-durand

chris-durand and others added 2 commits December 13, 2023 13:39
The DTCM is not DMA-capable on H7 devices. An lbuild option is added to
select the stack location between SRAM and DTCM.
Copy link
Member

@salkinium salkinium left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@salkinium salkinium merged commit 825e53e into modm-io:develop Dec 13, 2023
13 checks passed
@salkinium salkinium added this to the 2023q4 milestone Dec 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants