Skip to content

Commit 64bd6af

Browse files
yogeshhegdeyogeshhegde
committed
feat(linux): Add initial documentation for EV Charging User Guide
Add initial documentation for building EV charging WIC image on AM62L using yocto. Signed-off-by: Yogesh Hegde <y-hegde@ti.com>
1 parent 1693a08 commit 64bd6af

5 files changed

Lines changed: 168 additions & 3 deletions

File tree

‎configs/AM62LX/AM62LX_linux_toc.txt‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -130,5 +130,6 @@ linux/How_to_Guides_Hardware_Setup_with_CCS
130130
linux/How_to_Guides/Hardware_Setup_with_CCS/AM62Lx_EVM_Hardware_Setup
131131
linux/Demo_User_Guides/index_Demos
132132
linux/Demo_User_Guides/TI_LVGL_Demo_User_Guide
133+
linux/Demo_User_Guides/EV_charging_Demo_User_Guide
133134

134135
linux/Documentation_Tarball

‎source/devices/AM62LX/linux/Release_Specific_Yocto_layer_Configuration.rst‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,3 +26,6 @@ has the following configuration files in the :file:`configs/processor-sdk` direc
2626
* - :file:`processor-sdk-scarthgap-nonqt-11.02.08.02-config.txt`
2727
- Used for building Yocto based filesystem
2828
- |__SDK_BUILD_MACHINE__|
29+
* - :file:`processor-sdk-scarthgap-evse-11.02.08.03-config.txt`
30+
- Used for building Yocto based filesystem with `AM62L-EVSE-DEV-EVM <https://www.ti.com/lit/ug/slvudn0/slvudn0.pdf>`_ support (for EV charging Use cases)
31+
- |__SDK_BUILD_MACHINE__|

‎source/linux/Demo_User_Guides/EV_charging_Demo_User_Guide.rst‎

Lines changed: 140 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,140 @@
1+
.. _EV_charging_Demo_User_Guide-label:
2+
3+
###########################################################
4+
AM62L Electric Vehicle Supply Equipment (EVSE) - User Guide
5+
###########################################################
6+
7+
************
8+
Introduction
9+
************
10+
11+
Electric Vehicle Supply Equipment (EVSE) systems require sophisticated control mechanisms to support multiple charging standards and protocols.
12+
The `TIDA-010939`_ reference design addresses this complexity by providing a comprehensive front-end controller solution that serves as the central
13+
communication module for EV charging operations.
14+
15+
This reference design combines the `AM62L MPU`_ with the `MSPM0 MCU`_ to create a versatile platform supporting both AC and
16+
DC charging across global standards including Combined Charging System (CCS), Guobiao/Tuijian (GB/T), and Charge de Move (CHAdeMO).
17+
18+
The `AM62L MPU`_ runs the EV charging software stack on Linux, handling digital communication with electric vehicles,
19+
Ethernet and wireless connectivity for backend communications, and display capabilities for human-machine interface (HMI) integration.
20+
The `MSPM0 MCU`_ manages critical analog handshakes with electric vehicles and safety functions, including control pilot signaling,
21+
proximity detection, and temperature monitoring of charging connectors.
22+
23+
The reference design provides multiple communication interfaces—CAN, RS-485, RS-232, and Ethernet—enabling control of power conversion units,
24+
external metering devices, and other peripherals.
25+
26+
The `TIDA-010939`_ reference design is referred to as **AM62L-EVSE-DEV-EVM** throughout this documentation.
27+
28+
.. note::
29+
30+
For complete hardware setup, testing procedures, and system architecture details, refer to the `AM62L-EVSE-DEV-EVM Software User Guide`_.
31+
32+
This guide is intended for software engineers and system integrators who are:
33+
34+
* Porting existing EV charging solutions to the `AM62L-EVSE-DEV-EVM`_ platform
35+
* Developing custom EV charging applications using the |__SDK_FULL_NAME__|
36+
* Integrating the platform with existing charging infrastructure
37+
38+
This documentation assumes you have an existing EV charging software stack ready for integration. If you do not have a charging stack,
39+
consider evaluating `EVerest`_, an open-source EV charging software platform.
40+
41+
----
42+
43+
************
44+
SDK Overview
45+
************
46+
47+
|__SDK_FULL_NAME__| provides software support for the `AM62L-EVSE-DEV-EVM`_, enabling all communication interfaces
48+
required for EV charging applications. The SDK facilitates rapid development and deployment of EV charging solutions on this hardware platform.
49+
50+
The EVSE-specific SDK image :file:`tisdk-evse-image` extends the standard TI SDK image :file:`tisdk-default-image` with additional
51+
packages and configurations required for the `AM62L-EVSE-DEV-EVM`_ to function properly.
52+
53+
----
54+
55+
********************************
56+
Quick Start with Pre-built Image
57+
********************************
58+
59+
For quick evaluation and testing, download the latest pre-built WIC image: |__SDK_DOWNLOAD_URL__|
60+
61+
After downloading and flashing the image to your SD card, proceed directly to testing the communication interfaces by following the
62+
procedures in the `AM62L-EVSE-DEV-EVM Software User Guide`_.
63+
64+
----
65+
66+
***************************
67+
Building the SDK with Yocto
68+
***************************
69+
70+
This section describes how to build the EVSE WIC image from source using the Yocto Project build system.
71+
Follow the standard :ref:`Processor SDK - Building the SDK with Yocto <building-the-sdk-with-yocto>` and build for the EV charging Use case.
72+
73+
----
74+
75+
********************************
76+
Testing Communication Interfaces
77+
********************************
78+
79+
The `AM62L-EVSE-DEV-EVM`_ provides multiple communication interfaces essential for EV charging applications:
80+
81+
* **PLC (Power Line Communication)** - For ISO 15118 high-level communication
82+
* **CAN** - For communication with power conversion units and vehicle networks
83+
* **RS-485** - For industrial protocol communication with metering devices
84+
* **RS-232** - For legacy device communication
85+
86+
Complete testing procedures, pinout information, and example configurations for all communication interfaces are documented in the `AM62L-EVSE-DEV-EVM Software User Guide`_.
87+
88+
----
89+
90+
********************
91+
Additional Resources
92+
********************
93+
94+
* `AM62L-EVSE-DEV-EVM Software User Guide`_ - Complete hardware setup, testing procedures, and system architecture
95+
* `AM62L-EVSE-DEV-EVM`_ User Guide
96+
* `TIDA-010939`_ Reference Design - Product page, specifications and resources
97+
* `AM62L MPU`_ Product Page - AM62L MPU specifications and resources
98+
* `AM62L Product Overview`_
99+
* `AM62L Device Academy`_
100+
* `EVerest`_ Open Source EV Charging Stack
101+
102+
103+
.. _AM62L-EVSE-DEV-EVM Software User Guide: https://www.ti.com/lit/pdf/SLUUDH5
104+
105+
.. _AM62L-EVSE-DEV-EVM: https://www.ti.com/lit/ug/slvudn0/slvudn0.pdf
106+
107+
.. _TIDA-010939: https://www.ti.com/tool/TIDA-010939
108+
109+
.. _AM62L MPU: https://www.ti.com/product/AM62L
110+
111+
.. _EVerest: https://everest.github.io/
112+
113+
.. _AM62L Device Academy: https://dev.ti.com/tirex/explore/node?node=A__AEIJm0rwIeU.2P1OBWwlaA__AM62L-ACADEMY__6F61DO6__LATEST
114+
115+
.. _AM62L Product Overview: https://www.ti.com/lit/po/sprt790/sprt790.pdf
116+
117+
.. _MSPM0 MCU: https://www.ti.com/product/MSPM0G3507
118+
119+
----
120+
121+
122+
Glossary
123+
========
124+
125+
.. glossary::
126+
127+
CCS
128+
Combined Charging System - A fast-charging standard for electric vehicles supporting both AC and DC charging.
129+
130+
CHAdeMO
131+
Charge de Move - A DC fast-charging standard developed in Japan for electric vehicles.
132+
133+
EVSE
134+
Electric Vehicle Supply Equipment - The infrastructure and equipment used to supply electric energy for charging electric vehicles.
135+
136+
GB/T
137+
Guobiao/Tuijian - Chinese national standards for electric vehicle charging, including GB/T 20234 (connectors) and GB/T 27930 (communication protocol).
138+
139+
PLC
140+
Power Line Communication - Technology that enables data transmission over existing power cables, used in ISO 15118 for vehicle-to-grid communication.

‎source/linux/Demo_User_Guides/index_Demos.rst‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,7 @@ The SDK supports the following Out-Of-Box demo-applications
1919
TI_LVGL_Demo_User_Guide
2020
AM62D_Dsp_Offload_User_Guide.rst
2121
AM62D_2DFFT_User_Guide.rst
22+
EV_charging_Demo_User_Guide.rst
2223

2324
.. ifconfig:: CONFIG_sdk in ('j7_foundational')
2425

‎source/linux/Overview/_Processor_SDK_Building_The_SDK.rst‎

Lines changed: 23 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -197,6 +197,24 @@ The MACHINE can be set to |__SDK_BUILD_MACHINE__|, for example.
197197
$ echo 'TI_EXTRAS="tie-jailhouse"' >> conf/local.conf
198198
$ MACHINE=<machine> ARAGO_RT_ENABLE=1 bitbake -k tisdk-jailhouse-image
199199
200+
.. ifconfig:: CONFIG_part_variant in ('AM62LX')
201+
202+
* The command below will build the :file:`tisdk-evse-image`, which is the
203+
Processor SDK image with arago filesystem and `AM62L-EVSE-DEV-EVM <https://www.ti.com/lit/ug/slvudn0/slvudn0.pdf>`_ support (EV charging Use case support).
204+
205+
.. code-block:: console
206+
207+
$ git clone https://git.ti.com/git/arago-project/oe-layersetup.git tisdk
208+
$ cd tisdk
209+
$ ./oe-layertool-setup.sh -f configs/processor-sdk/<oeconfig-file>
210+
$ cd build
211+
$ . conf/setenv
212+
$ MACHINE=<machine> ARAGO_RT_ENABLE=1 bitbake -k tisdk-evse-image
213+
214+
.. important::
215+
216+
EVSE (EV Charging) image uses RT-Linux and is not supported on Linux.
217+
200218
.. ifconfig:: CONFIG_sdk in ('JACINTO','j7_foundational')
201219

202220
|__SDK_FULL_NAME__| uses the 'oe-layersetup' tool to configure the meta layers. If you do not have the Linux SDK package installed:
@@ -379,6 +397,8 @@ The build system places the "Build Output" relative to :file:`deploy-ti`
379397
+------------------------------+----------------------------------------------------------------+----------------------------+
380398
| tisdk-jailhouse-image | images/<machine>/tisdk-jailhouse-image-<machine>.rootfs.tar.xz | Jailhouse Filesystem |
381399
+------------------------------+----------------------------------------------------------------+----------------------------+
400+
| tisdk-evse-image | images/<machine>/tisdk-evse-image-<machine>.rootfs.tar.xz | EV Charging Filesystem |
401+
+------------------------------+----------------------------------------------------------------+----------------------------+
382402
| tisdk-base-image | images/<machine>/tisdk-base-image-<machine>.rootfs.tar.xz | Minimal Target Filesytem |
383403
+------------------------------+----------------------------------------------------------------+----------------------------+
384404
| tisdk-thinlinux-image | images/<machine>/tisdk-thinlinux-image-<machine>.rootfs.tar.xz | Minimal Target Filesytem |
@@ -749,10 +769,10 @@ and IPK packages in the deploy-ipks folder.
749769

750770
Please note that the output of a recipe can be in another folder under :file:`arago-tmp-[toolchain]/work` directory, depending on the defines of the recipe.
751771
You can call the following command from yocto's build directory to get the path to the workdir of your recipe.
752-
772+
753773
.. code-block:: console
754-
755-
MACHINE=<machine> bitbake-getvar -r <recipe-name> WORKDIR --value
774+
775+
MACHINE=<machine> bitbake-getvar -r <recipe-name> WORKDIR --value
756776
757777
.. rubric:: Forced Re-compilation
758778
:name: Forced Re-compilation

0 commit comments

Comments
 (0)