search

damogranlabs / VS-Code-STM32-IDE

Use VS Code as STM32 IDE with CubeMX
MIT License
247 stars 52 forks source link

texane/stlink support #21

Closed Hamid-Najafi closed 5 years ago

Hamid-Najafi commented 5 years ago

I'm using texane/stlink in osx. Correctly osx is not on os type. add this after that.

Edit: Modifying includePath from makefile and adding uC type define is enough. like this: "defines": [ "STM32F407xx 1" ], (flashing .BIN file can be done separately)

schperplata commented 5 years ago

Please see this issue and my comment regarding osx support.

Anyway, please, when you open an issue, write it in a way me and others can understand it. Currently I don't even know what the real problem is and I don't plan spending time debugging unclear issue reports. :)

schperplata commented 5 years ago

Update: osx support added by om2kw, please check if your problem is still relevant.

Hamid-Najafi commented 5 years ago

Sorry for that, you’re right. This program uses OpenOCD while I requested to add texane/stlink support. Another this is that after setting include path, i also have to define uC model in 'c_cpp_properties.json’ to fix vscode issues

schperplata commented 5 years ago

This program uses OpenOCD while I requested to add texane/stlink support.

As I only use stlink, currently there is no plan to extend support for other tools. It can be done for sure, but quite a lot of work is needed to port all configurations, tasks and other features to support other tools.

Another this is that after setting include path, i also have to define uC model in 'c_cpp_properties.json’ to fix vscode issues

I am not sure I understand what you mean or what is the problem. Of course you must set inlude paths, so VS Code, GCC and other tools know where to search for files. And if your project (code in files) demands some predefines, than of course, you also need to add this to 'c_cpp_properties.json'

Hamid-Najafi commented 5 years ago

I am not sure I understand what you mean or what is the problem. Of course you must set inlude paths, so VS Code, GCC and other tools know where to search for files. And if your project (code in files) demands some predefines, than of course, you also need to add this to 'c_cpp_properties.json'

2019-06-04_01-00-24

schperplata commented 5 years ago

Now I see. Your issue has nothing to do with this project.

Please see the main page, docs and examples.