Change Legacy SPI functions to SSP
Open
Nobody has claimed this yet.
afc-bpm
afc-timing
enhancement
- Dominant language
- C
- Stars
- 46
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
There are some discussions on the NXP Forum about the SPI Legacy interface being there only for code portability between LPC20xx and LPC17xx chips. All new designs are recommended to use SSP interfaces, which can operate in SPI mode.
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 locating the firmware's SPI Legacy interface and the SSP interfaces, then review how the current SPI mode is used. Compare the relevant call sites and hardware configuration before determining the scope of replacing the legacy functions; done means new designs use SSP in SPI mode without breaking existing functionality.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100