Charge SOM / recent questions #59
Merged
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
mhei
reviewed
Jul 22, 2025
docs/source/hardware.rst
Outdated
| The i.MX93 on the Charge SOM provides several I2C interfaces: | ||
|
|
||
| +----------+-----------+--------------+-------------+-----------------+ | ||
| | Hardware | Linux | Used by CSOM | Used by EVB | Clock frequency | |
Member
There was a problem hiding this comment.
We should try to avoid introducing more and more different abbreviations, so I'd recommend to use "Charge SOM" here instead of "CSOM". Also I'd use "Single Channel DC Carrier Board" instead of "EVB".
docs/source/hardware.rst
Outdated
| The following devices on the Charge SOM are connected to I2C3: | ||
|
|
||
| * PMIC (0x25) | ||
| * EEPROM (0x50, 0x58) |
Member
There was a problem hiding this comment.
Maybe we can fold the lists directly in the table above?
docs/source/troubleshooting.rst
Outdated
|
|
||
| The signal CHSTOP_IN is connected to the i.MX93 SoC and could be used to gracefully stop the charging process. So it is not designed | ||
| for timing critical use cases. Instead use the SAFETY_ESTOPx signals, which are connected to the safety processor to realize realtime | ||
| emergency stop behavior. |
Member
There was a problem hiding this comment.
Maybe we should add a note that this work is pending, at the moment, there is no EVerest module which connects such a GPIO to the graceful stop command.
docs/source/troubleshooting.rst
Outdated
| - 2 | ||
| - SoM | ||
| - `imx93-charge-som.dtsi <https://github.com/chargebyte/linux/blob/v6.6.23-2.0.0-phy-cb/arch/arm64/boot/dts/freescale/imx93-charge-som.dtsi>`_ | ||
| * - Charge SOM Single Channel DC carrier board |
Member
There was a problem hiding this comment.
nit: I'd spell "Carrier Board" with upper case first letters
Signed-off-by: Stefan Wahren <stefan.wahren@chargebyte.com>
lategoodbye
force-pushed
the
everest/charge_som_recent_questions
branch
2 times, most recently
from
c7bcd5c to
c81731e
Compare
Signed-off-by: Stefan Wahren <stefan.wahren@chargebyte.com>
Signed-off-by: Stefan Wahren <stefan.wahren@chargebyte.com>
lategoodbye
force-pushed
the
everest/charge_som_recent_questions
branch
from
c81731e to
b8d0362
Compare
mhei
approved these changes
Jul 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Recently a customer discovered some empty spots in the documentation (mostly hardware related, which isn't covered by the datasheets).