Create an I3C Trait
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- rust
- Domain
- embedded-iot
Research direction
Start by reviewing the existing CAN Trait and the public I3C specification linked in the issue. Use the discussion to determine whether the work belongs in an extra crate and which bus, addressing, and interrupt capabilities the API must represent. Done would require an agreed design rather than a defined implementation target.
Written by the indexing model from the issue text.
Description
We should think about how a I3C Trait may be implemented. This may be done like the CAN Trait in an extra crate allowing breakage and only when it really stabilized to be merged into the core hal.
Currently there aren't a lot of IC's using the protocol, but it seems to get adoption. Major Suppliers have started incorporating it into their new designs, including NXP, STM, Renesas, Nordic Semi, Espressif, Texas Instruments, Bosch and Microchip. See here for a list.
This is supposed to be a place where we can discuss how this might be implemented. The specification can be found here. However it can only be accessed by providing an E-Mail Adresse and then only the public version instead of the member version.
The protocol itself is combining the advantages of I2C and SPI. It is downwards compatibel to I2C and starts adressing like it, however when it is clear that only the an I3C device is adressed it switches to a push pull architecture to enable higher transfer speeds like SPI. There is also an option to send an interupt over the Bus for Devices, which should probably be represented in the API. It does however only support 7 Bit Adressing for the I2C compatibility mode.
- Dominant language
- Rust
- Stars
- 2.7k
- Forks
- 282
- PR merge metrics
- No merged PRs in 30d
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.
More from rust-embedded/embedded-hal
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
rust-embedded/embedded-hal#742 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
rust-embedded/embedded-hal#747 · 5 comments · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
rust-embedded/embedded-hal#746 · 2 comments · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
rust-embedded/embedded-hal#745 · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
rust-embedded/embedded-hal#744 · 1 comment ·
All issues in rust-embedded/embedded-hal
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100