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

AC6 symbol export to .clangd file missing #187

Open
ReinhardKeil opened this issue Jan 31, 2025 · 3 comments
Open

AC6 symbol export to .clangd file missing #187

ReinhardKeil opened this issue Jan 31, 2025 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@ReinhardKeil
Copy link
Collaborator

The .clangd file should contain a list of AC6 specific compiler symbols.

This list is generated using AC6 compiler.

@jkrech
Copy link
Collaborator

jkrech commented Feb 18, 2025

@thorstendb-ARM Note, I am seeing the compiler symbols in a project for the STMicroelectronics::STM32U585AIIx (Cortex-M33) but not for an STMicroelectronics::STM32F207IGHx (Cortex-M3). Please check whether there is code executed only for certain processors.

@thorstendb-ARM thorstendb-ARM moved this from Backlog to In progress in CMSIS Solution Extension Feb 24, 2025
@thorstendb-ARM
Copy link
Collaborator

Found:

  • M33 (STM32U5) project runs
  • M3 (STM32F200) "Create new Solution" project also runs
  • M3 (STM32F200) "UV2CSolution converted" does not run

Difference:

  • uv2csolution converted project did not have "build-types" node in csolution.yaml file

@jkrech
Copy link
Collaborator

jkrech commented Feb 24, 2025

Good catch. Adding a build-type fixed my project for Cortex-M3 (STMicroelectronics::STM32F207IGHx).
Is there a reason for depending on an existing build-type?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: In progress
Development

No branches or pull requests

3 participants