Forum Replies Created
-
AuthorPosts
-
MystikReasonsParticipant
It works now. Thank you!
MystikReasonsParticipantUpdate: This is not only working with private functions. Just tried a private struct and it’s also not showing up
MystikReasonsParticipantI’ve extended the sample project with two functions, one declared in the private sector and one in the public sector.
I’ve sent the project via the support to you.
Steps to reproduce it:
- Create a function inside the class (.hpp file) one private and one public
- Change to the .cpp file and try to use the Clang IntelliSense autocomplete
You will see that only the public function is showing up
I’m using VisualGDB build 3039 with Visual Studio 2019 Preview 4.4
- This reply was modified 5 years, 7 months ago by MystikReasons.
MystikReasonsParticipantGood to know that the ST-Links v3 is backwards compatible.
Thank you for the answer.
MystikReasonsParticipantThank you for the fast fix. It works now
MystikReasonsParticipantI’ve created an sample project and could also there reproduce this issue.
I’m sending the example project via the support to you.
MystikReasonsParticipantI can confirm that it now works. Thank you!
MystikReasonsParticipantSame issue here. As a workaround you can rightclick your project in the solution explorer and there should be the VisualGDB project properties window.
MystikReasonsParticipantI found that the inline assembler for v5 is mostly supported: http://www.keil.com/support/man/docs/armcc/armcc_chr1359124246466.htm
The not supported commands can be found here: http://www.keil.com/support/man/docs/armcc/armcc_chr1359124246684.htm
But my errors have other commands so it should support them.
MystikReasonsParticipant@danielone I have the same problem: https://sysprogs.com/w/forums/topic/keil-armcc-features-error/
It seems that the Keil compiler in VC doesn’t support the ASM keyword (assembly inline)
This is the description of the error from keil http://www.keil.com/support/man/docs/ARMERR/armerr_dom1365070466238.htm:
1114: this feature not supported on target architecture/processor
Example when compiled with armcc –cpu 4T:
int main(void) {
int a,b,c;
__asm {
QADD a,b,c
}
return(a);
}results in an error message because the saturated add instruction is only supported in ARMv5TE and later.”
But I don’t know why its not supported because I use the default compiler version 5 in Keil and in Visual Studio too.
- This reply was modified 5 years, 8 months ago by MystikReasons.
- This reply was modified 5 years, 8 months ago by MystikReasons.
MystikReasonsParticipantI’ve uploaded the video here: https://www.youtube.com/watch?v=Ox7whToGYJQ
I’m using Visual Studio 2019 with VisualGDB build 3009 and I could confirm this problem on two different computers with different screen sizes
MystikReasonsParticipantI think you didn’t read my second post or you misunderstood it.
My question was about the intellisense window with their options at the bottom showing up for auto complete suggestions:
If you have deactivated the thunderbolt symbol “Suggest names as you type them” then it’s difficult to get to those options for the intellisense window (see screenshot #1) because it won’t show up normally.
I had to do something like this to even get the window up:
bm280->
first then the window showed up and at this point I could change those options (inside the autocomplete window).Would it be possible to add these options under the IntelliSense Settings window of the VisualGDB Project Properties too?
This would be in my opinion the first place if you search for options for the intellisense.
- This reply was modified 5 years, 8 months ago by MystikReasons.
Attachments:
You must be logged in to view attached files.MystikReasonsParticipantUpdate: I found the option that the clang intellisense is always showing up (“Suggest name as you type them”).
You can ignore my two questions above.
But my new question: I had to write “exp: foo->” so I can see the window and make adjustments. Is there another window where I can edit those options?
If not would it be possible to add those options inside the “VisualGDB project properties” under the IntelliSense Settings?
This would be in my opinion the first place if you search for options for the intellisense
PS: You did an amazing job with the intellisense, I really like it. Props on you! 😉
- This reply was modified 5 years, 8 months ago by MystikReasons.
- This reply was modified 5 years, 8 months ago by MystikReasons.
MystikReasonsParticipantYou were right it was a build error and now it works again. Thanks
MystikReasonsParticipantUpdate2: The Clang Intellisense (also the Advanced one) doesn’t recognize my class but VC++ Intellisense does so I’m going to use this until I know the reasons for the error marks
-
AuthorPosts