-
Notifications
You must be signed in to change notification settings - Fork 236
Failed to generate IntelliSense configuration with STM8 Core #1489
Comments
You can get more verbose log by setting {
"arduino.logLevel": "verbose"
} |
same +1 |
i guess we need to fix it ourselves, since neither microsoft nor ST seems interrested to help |
You may want to try #1494. It fixes the issue for m5stack for me. |
yes, i did not think of it, but it is a common problem indeed, I'll give a try and not thank microsoft nor ST for the non existing support |
ST, a company which probably lost a huge part of it market share with the disaster of last months (welcome 1000% increase on 10 year old MCU), but still hasn't understood the importance of support. i feel like it's going to be a (well desserved) "good riddance" soon |
Hi @0x0fe. I'm uable to reproduce this issue because I don't have a license for the compiler used by the STM8 tools. However, based on the earlier discussion #1494 may fix your issue, which will be included in an upcoming release. You can try it now by installing the VSIX manually from this CI build. Does that fix your issue? |
Thank you for checking on the issue. I am going to try it soon when i have a chance to get back at this design, regarding the STM8 compiler "license", I think you can request one anytime here (it is automated via email) : |
I had to quit completely VScode (force quit) then i restarted it, retried the VSIX installing, and it worked. This kind of buggy inconsistence is pretty consistent with microsoft style i would say. |
well, sadly it not only did not solve the problem, it also completely broke the extension, the "verify" command does not exist anymore, cannot even build. It is also burning a lot of CPU cycles when i open the directory, without any report in OUTPUT, it is quite not acceptable to have sudden huge CPU usage without any justification or report. |
Thanks for letting me know. We found some breaking issues in the release
candidate (unrelated to this particular fix) that are causing activation to
fail, which we hope to fix next week.
…On Sat, Apr 30, 2022, 3:48 PM 0x0fe ***@***.***> wrote:
[image: image]
<https://user-images.githubusercontent.com/89607149/166125083-76a8dd48-355f-4905-8f0c-2aaca9e3f3a7.png>
—
Reply to this email directly, view it on GitHub
<#1489 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABVINJF55NS77WWH2IAMXWLVHW2DPANCNFSM5S7V672A>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
This issue has been automatically marked as stale because it has been inactive for 30 days. To reactivate the issue, simply post a comment with the requested information to help us diagnose this issue. If this issue remains inactive for another 7 days, it will be automatically closed. |
Hi @0x0fe. v0.4.12 of the extension available on the VS Code marketplace, which fixes the activation issues described above. Let me know if you are still having issues with STM8 development. Otherwise, this issue will be automatically closed. |
This issue has been automatically marked as stale because it has been inactive for 30 days. To reactivate the issue, simply post a comment with the requested information to help us diagnose this issue. If this issue remains inactive for another 7 days, it will be automatically closed. |
This issue has been automatically closed due to inactivity. If you are still experiencing problems, please open a new issue. |
To reproduce the issue, install STM8 core https://github.com/stm32duino/Arduino_Core_STM8 from the board manager, select any example, one of the two boards as target, and hit "Verify".
Is there a way to get some log? no long on console(s) no log in the build directory... We really shoudl get more meaningful debug on the verify and intellisense because it does fail and to fix it we have to know why.
I did my best to recreate a c_cpp_properties.json but it did not solve the problem.
N.B. the target here is a custom target, but the problem is exactly the same with the targets provided with the core.
The text was updated successfully, but these errors were encountered: