Northeastern-Electric-Racing / Northeastern-Electric-Racing/Embedded-Base
Add hardware/project key to each project makefile and drivers
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Current Features
Right now, we have drivers that are hard set to individual stm32 types - they are not cross compatible
Desired Additional Features
We should be able to pass some sort of key or macro from each project that can be read by drivers to include the right files. Probably will need to explore how best to add this, and then update each driver to have #ifdefs to include the proper file.
NOTE: possibly will become redundant or obsoleted by #139 . so unless its super easy mayeb wait until progress is made on that ticket to begin this if still desired
Screenshots (as needed)
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing each project makefile and the drivers that are currently hard-coded to individual STM32 types. Check issue #139 first, since this work may become redundant. Define the hardware/project key or macro approach and update the affected drivers so they select the correct files; done means projects can use the shared drivers across supported STM32 types without hard-coded incompatibilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system, embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100