-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Everest/charge som add git submodules #41
Merged
Merged
Conversation
This file contains 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
Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Martin Lukas <[email protected]>
Signed-off-by: Martin Lukas <[email protected]>
…-830) Signed-off-by: Fabian Hartung <[email protected]>
…ner. This link just point to the autogenerated genindex.html from Sphinx and is empty. Furthermore we don't need the "Show source" link in the sidebar. This only shows the raw data of the current shown page (refs EVEREST-380) Signed-off-by: Martin Lukas <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
…EVEREST-929) Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Add documentation for "Firmware" chapter (refs EVEREST-929) Signed-off-by: Mohannad Oraby <[email protected]>
Signed-off-by: Martin Lukas <[email protected]>
Add hardware chapter (refs EVEREST-929)
Signed-off-by: Fabian Hartung <[email protected]>
Add "Order Code" and "Safety Notes" section (refs EVEREST-929)
Add documentation for "EVerest charging stack" chapter (refs EVEREST-929) Signed-off-by: Mohannad Oraby <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Adjust the README.rst file
* Add initial Troubleshooting chapter Signed-off-by: Stefan Wahren <[email protected]>
Add documentation for "Development" chapter (refs EVEREST-929) Signed-off-by: Mohannad Oraby <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
…A-2672) (#13) getting_started.rst: - Added new section "Firmware Update" firmware.rst: - Added new section "Updating from chargebyte’s proprietary charging stack to EVerest-based charging stack" - Added new section "Release Images vs Development Images" - Added new section "Firmware Update Considerations" troubleshooting.rst - Improved answer to question about firmware update from chargebyte proprietary stack and EVerest stack Signed-off-by: Fabian Hartung <[email protected]>
…038) (#14) Additionally, added some important notes before downloading the firmware image. Signed-off-by: Fabian Hartung <[email protected]>
…EVEREST-181) Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Add 0.11.0 changes
Signed-off-by: Rajnish Baldha <[email protected]>
Adjusted the appearance to align with the main website's design.
Introduce Charge SOM User Guide This introducd the initial version of the Charge SOM User Guide, which only contains "Getting Started". Signed-off-by: Stefan Wahren <[email protected]>
Signed-off-by: Stefan Wahren <[email protected]>
This adds a sphinxbuild link check workflow, which triggers on every pull request or could be manually triggered. Signed-off-by: Stefan Wahren <[email protected]>
Since there are strange issues with anchors in restructured text on Github, we better disable this checks. Signed-off-by: Stefan Wahren <[email protected]>
Add link check workflow for Charge Control C
Signed-off-by: Stefan Wahren <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Moritz Barsnick <[email protected]>
Signed-off-by: Moritz Barsnick <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
…generic_chapters Charge SOM: Introduce generic chapters
… issues Signed-off-by: Fabian Hartung <[email protected]>
As long as the mountpoint graphic is generic move it to the includes. Signed-off-by: Stefan Wahren <[email protected]>
These screenshots are product specific, but are used from a generic include. While at this use PNG instead of JPG. Signed-off-by: Stefan Wahren <[email protected]>
Signed-off-by: Stefan Wahren <[email protected]>
Charge SOM: Add firmware chapter
…-and-debugging Charge SOM: Add logging and debugging section
Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
barsnick
approved these changes
Mar 17, 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.
With git submodules, it is possible to share common content between the user guides.