Forum Replies Created
-
Posts
-
I didn’t try this yet, but I think I found the issue: I’m using a “third party” toolchain (GNU Tools ARM Embedded) which was installed in “C:\Program Files (x86)\GNU Tools ARM Embedded\[…]” so I was getting a lot of warnings that GDB gets confused by spaces in the pathname. I made a symbolic link to it at C:\gcc to get rid of those warnings, and when I switched the toolchain all of the red squigglies went away and IntelliSense seems to be happy again. So – maybe that was it.
It’s a Makefile-based project. I should point out, though, that RCC_PLL_ON, RCC_LSI_ON, and RCC_HSE_ON are in the same file as RCC_PLLSOURCE_HSE. Furthermore, when I launched Visual Studio this morning to get to work, the state is different. Example – when I took that screen shot, it was able to find RCC_HSE_ON; this morning it is not. Also this morning I see that in this line:
HAL_GPIO_WritePin(LED_RED_GPIO_Port, LED_RED_Pin, GPIO_PIN_RESET); // Clear red LED
IntelliSense is able to find LED_RED_Pin (line 76 of main.h), but not LED_RED_GPIO_Port (line 77 of main.h). So that’s weird. Every LED pin interaction I’ve looked at is like this – IntelliSense can find all of the _Pin defines, but none of the _Port defines, despite them all being bunched together in the same file.
Sure, here’s a screenshot of the errors:
[caption id="" align="alignnone" width="1916"]
screenshot of intellisense errors[/caption]Remember that the 137 errors here are all IntelliSense; this is a successful build with 0 errors and 0 warnings otherwise. The last error is “Error: too many errors emitted, stopping now.”
I can confirm all of this, I had the exact same experience upgrading from VS 2015 to 2017.
One of the fancy improvements in VS 2017 is supposed to be faster startup time, so I feel like it’s just being a bit aggressive with extensions but it would be nice if there was a “yeah I got it, quit bugging me” option in the warning!
—
Elliott
As far as I can tell, I’m not using Resharper or anything like it. Certainly not intentionally, and this is a clean install of Visual Studio – I don’t use it for anything else at the moment so there shouldn’t be extraneous plugins.
One other data point – while I was using the trial version of VisualGDB, I went through the project setup process 8-10 times using slightly different methods and had this happen 2-3 times, which is what leads me to wonder if it’s something I’m doing in the project setup that leads to this.
