Repository navigation
Latest stm32h7xx_hal.h file causes intellisense errors #675
Description
I was getting lots of intellisense errors (especially on uint32_t variables) when I tried to set up my own libDaisy submodule (yes I did git submodule update --init --recursive). However, when I replace the libDaisy\Drivers\STM32H7xx_HAL_Driver\Inc\stm32h7xx_hal.h file from the current commit of libDaisy with the older commit of libDaisy in DaisyExamples those intellisense errors go away. So my current solution has been to do just that and replace this file with an older version. This works but should be fixed or perhaps there is still something I am not doing.
Activity
stephenhensley commentedon Jan 13, 2026
I've been experiencing this to varying degrees lately, and it hadn't occurred to me to check which versions of libDaisy I was using in the different projects.
Could very well be related to this. It was mostly
uint32_t, and for some reason, thedaisy::Systemclass that seemed to be recurring issues.I was thinking this was an issue with my local configurations, but since it seems to be affecting others I'll move this up in my priorities to address a bit.
Since we've switched to using submodules for the drivers simply swapping out the file with an older version isn't viable anymore, but I'm sure there is some combination of VS Code settings (likely via the
c_cpp_properties.jsonin your project that can resolve the issue).An interesting note: a while ago I started putting together a cross-platform project that had libDaisy in it, and didn't include a c_cpp_properties file at all. I don't recall running into these intellisense errors in that case.
Are/were you experiencing this with libDaisy as the VS Code workspace, and/or from your outer project workspace?
If the latter, would you mind sharing your
.vscode/c_cpp_properties.jsonfile?stephenhensley commentedon Oct 12, 2026
I have resolved this within libDaisy (via #717) and the DaisyBlinkProject repo.
I have a similar fix in progress for DaisyExamples that I expect to wrap up this week (I'm making a few other tweaks to improve working with that repo in VS Code at the same time).