8/10/2023 0 Comments Visual studio code runs on m1![]() Regardless of the compiler, you should be able to run the Cortex Debug configuration in the “Run and Debug” menu of VS Code. The debugging uses openocd also installed via the Toolchain links above (and the older mand/homebrew method). (I personally have the habit of manually running the make commands myself, but still using VS code / Cortex Debug to attach the debugger. You can then try the build task once more.Īlso, it is possible to use VS Code for editing the code, and running the debugger without using the tasks for compiling. I recommend uninstalling the gcc-arm-embedded with homebrew, and using the installer linked above to install the toolchain. ![]() If you’re successfully compiling the Blink example, it’s likely that libDaisy was compiled already with the older version of the compiler, and you will eventually hit random, unknown warnings, and errors. I’m fairly certain the STM32 HAL files in libDaisy do not compile properly with the new version at this time. In any case, you may run into issues with v11 toolchain of the arm compiler. This should also be the same as doing the Terminal->Run Build Task (Cmd-Shift-B) menu option. Task build (from any of the example folders) should work the same as running make clean make in your terminal. What version of the hardware and OS are you using (Intel/ARM, and MacOS version)? It’s been a little while since I’ve gone through everything on MacOS. VS Code should be using the same tools that get used when invoking the program via the command line in a terminal.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |