Add support for Keil Studio Pack in Visual Studio Code #19
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…d of 4 in vesc_usart.c
…d of 4 in vesc_usart.c
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed on Discord, I've set up a platform-agnostic development environment using Visual Studio Code.
Compilation is successful for Mac OS aarch64 and Linux x86_64 at this point. Check
vcpkg-configuration.jsonfor compiler / toolchain details.The output .hex file has been successfully flashed to PintV LCM and the board / lights function as intended.
Basic instructions for setting up Visual Studio Code are included in README.md
I created build targets for each device as opposed to toggling comments like
#define <device>as well as the ability to select Debug/Release configurations for eachscreenshot.2024-11-07.at.5.40.09.PM.mov
Versioning can be done by editing
VERSIONvariable inLCM_Light_Control_IO_WS2812_New.csolution.ymlTo be clear, removing the defines for each device version has no effect on
vesc_usart.cand the functions that require FIRMWARE_ID as Iit's defined inLCM_Light_Control_IO_WS2812_New.csolution.ymlOutput .hex files somewhat match your current naming scheme, ex. v2_1_4_PINTV.hex v2_1_4_GTV.hex etc