Skip to content

Conversation

@yogeshhegde
Copy link

Add initial documentation for building EV charging WIC image on AM62L using yocto.

Preview can be found here - https://yogeshhegde.github.io/processor-sdk-doc/processor-sdk-linux-AM62LX/esd/docs/master/linux/Demo_User_Guides/EV_charging_Demo_User_Guide.html

@github-actions
Copy link

New warnings found with rstcheck:

source/linux/Demo_User_Guides/EV_charging_Demo_User_Guide.rst:5: (INFO/1) Duplicate explicit target name: "am62l-evse-dev-evm software user guide".
source/linux/Demo_User_Guides/EV_charging_Demo_User_Guide.rst:5: (INFO/1) Duplicate explicit target name: "am62l-evse-dev-evm software user guide".
source/linux/Demo_User_Guides/EV_charging_Demo_User_Guide.rst:5: (INFO/1) Duplicate explicit target name: "am62l-evse-dev-evm software user guide".

Copy link
Member

@cshilwant cshilwant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are few valid warnings from vale which needs to be resolved - https://github.com/TexasInstruments/processor-sdk-doc/pull/618/files

The TIDA-010939 reference design is referred to as **AM62L-EVSE-DEV-EVM** throughout this documentation.

.. note::
For complete hardware setup, testing procedures, and system architecture details, refer to the `AM62L-EVSE-DEV-EVM Software User Guide <https://www.ti.com/lit/pdf/SLUUDH5>`_.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

the link appears to be currently broken. Is that expected?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it is expected since it is under review and yet to be published.

@StaticRocket
Copy link
Member

@github-actions
Copy link

New warnings found with rstcheck:

source/linux/Demo_User_Guides/EV_charging_Demo_User_Guide.rst:103: (INFO/1) Duplicate explicit target name: "am62l-evse-dev-evm software user guide".

Add initial documentation for building EV charging WIC image
on AM62L using yocto.

Signed-off-by: Yogesh Hegde <[email protected]>
Copy link
Member

@cshilwant cshilwant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Better to highlight this EV Charging User Guide under Key Release References for AM62L [0]

[0] - https://github.com/TexasInstruments/processor-sdk-doc/blob/master/source/devices/AM62LX/linux/Release_Specific_Release_Notes.rst?plain=1#L57

$ ./oe-layertool-setup.sh -f configs/processor-sdk/<oeconfig-file>
$ cd build
$ . conf/setenv
$ MACHINE=<machine> ARAGO_RT_ENABLE=1 bitbake -k tisdk-evse-image
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
$ MACHINE=<machine> ARAGO_RT_ENABLE=1 bitbake -k tisdk-evse-image
$ MACHINE=am62lxx-evm ARAGO_RT_ENABLE=1 bitbake -k tisdk-evse-image

The code-blocks is under ifconfig of AM62L. So, better to have this predefined

+------------------------------+----------------------------------------------------------------+----------------------------+
| tisdk-jailhouse-image | images/<machine>/tisdk-jailhouse-image-<machine>.rootfs.tar.xz | Jailhouse Filesystem |
+------------------------------+----------------------------------------------------------------+----------------------------+
| tisdk-evse-image | images/<machine>/tisdk-evse-image-<machine>.rootfs.tar.xz | EV Charging Filesystem |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on the yocto build instructions above, shouldn't this be?

Suggested change
| tisdk-evse-image | images/<machine>/tisdk-evse-image-<machine>.rootfs.tar.xz | EV Charging Filesystem |
| tisdk-evse-image | images/<machine>/tisdk-evse-image-rt-<machine>.rootfs.tar.xz | EV Charging Filesystem |

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants