[DOC] Update I3C integration specifications regarding PID and DCR registers#1023
[DOC] Update I3C integration specifications regarding PID and DCR registers#1023clayton8 wants to merge 3 commits into
Conversation
Added requirements for setting I3C core's PID and DCR registers to unique values and clarified static address programming.
There was a problem hiding this comment.
Pull request overview
This PR updates the I3C integration documentation to clarify requirements for PID/DCR register configuration and static address programming. The changes add important guidance for integrators to ensure proper I3C ENTDAA mode operation and static address configuration.
Changes:
- Added requirement for unique PID and DCR register values to support I3C ENTDAA mode
- Clarified that static addresses are disabled on reset and must be programmed by MCU firmware if needed
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Clarify recommendations for setting unique PID and DCR values in I3C configuration.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| 6. It is the integrator’s responsibility to correctly set the I3C core’s PID and DCR registers to unique values to support I3C ENTDAA mode. If two devices on the bus share the same PID, DCR, and BCR values, ENTDAA will fail. Unique values can be assigned in one of two ways: | ||
| 1. FW: Before enabling the I3C core, MCU FW can program these registers with the appropriate values for the device. This is the recommended solution for PID and DCR. | ||
| 2. HW: Modify the I3C RDL and regenerate the I3C core RDL collateral. This is not recommended for PID since each device should strive for unique PIDs. This is OK for DCR since the device type is typically a fixed value. | ||
| 7. The I3C static address is disabled on reset. If your design requires a static address before dynamic address assignment occurs, the MCU must program the static address as part of the I3C configuration flow. |
There was a problem hiding this comment.
The line has a trailing space after "flow." which should be removed for consistency with markdown formatting best practices.
| 7. The I3C static address is disabled on reset. If your design requires a static address before dynamic address assignment occurs, the MCU must program the static address as part of the I3C configuration flow. | |
| 7. The I3C static address is disabled on reset. If your design requires a static address before dynamic address assignment occurs, the MCU must program the static address as part of the I3C configuration flow. |
There was a problem hiding this comment.
I do like to remove trailing whitespaces... but other than this change I'd approve the PR :)
Added requirements for setting I3C core's PID and DCR registers to unique values and clarified static address programming.