Skip to content

Commit 15751a9

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 15751a9

5 files changed

Lines changed: 149 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 support (for EV charging Use cases)
31+
- |__SDK_BUILD_MACHINE__|

‎source/linux/Demo_User_Guides/EV_charging_Demo_User_Guide.rst‎

Lines changed: 117 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,117 @@
1+
.. _EV_charging_Demo_User_Guide-label:
2+
3+
############################################
4+
AM62L EVSE - User Guide
5+
############################################
6+
7+
Introduction
8+
============
9+
10+
Electric Vehicle Supply Equipment (EVSE) systems require sophisticated control mechanisms to support multiple charging standards and protocols.
11+
The TIDA-010939 reference design addresses this complexity by providing a comprehensive front-end controller solution that serves as the central
12+
communication module for EV charging operations.
13+
14+
This reference design combines the AM62L processor with the MSPM0G3507 microcontroller to create a versatile platform supporting both AC and
15+
DC charging across global standards including Combined Charging System (CCS), Guobiao/Tuijian (GB/T), and Charge de Move (CHAdeMO).
16+
17+
The AM62L processor runs the EV charging software stack on Linux, handling digital communication with electric vehicles,
18+
Ethernet and wireless connectivity for backend communications, and display capabilities for human-machine interface (HMI) integration.
19+
The MSPM0G3507 microcontroller manages critical analog handshakes with electric vehicles and safety functions, including control pilot signaling,
20+
proximity detection, and temperature monitoring of charging connectors.
21+
22+
The reference design provides multiple communication interfaces—CAN, RS-485, RS-232, and Ethernet—enabling control of power conversion units,
23+
external metering devices, and other peripherals.
24+
25+
The TIDA-010939 reference design is referred to as **AM62L-EVSE-DEV-EVM** throughout this documentation.
26+
27+
.. note::
28+
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>`_.
29+
30+
This guide is intended for software engineers and system integrators who are:
31+
32+
* Porting existing EV charging solutions to the AM62L-EVSE-DEV-EVM platform
33+
* Developing custom EV charging applications using the AM62L Processor SDK
34+
* Integrating the platform with existing charging infrastructure
35+
36+
This documentation assumes you have an existing EV charging software stack ready for integration. If you do not have a charging stack,
37+
consider evaluating `EVerest <https://everest.github.io/>`_, an open-source EV charging software platform.
38+
39+
----
40+
41+
SDK Overview
42+
============
43+
44+
The latest AM62L Processor SDK provides software support for the AM62L-EVSE-DEV-EVM, enabling all communication interfaces
45+
required for EV charging applications. The SDK facilitates rapid development and deployment of EV charging solutions on this hardware platform.
46+
47+
The EVSE-specific SDK image :file:`tisdk-evse-image` extends the standard TI SDK image :file:`tisdk-default-image` with additional
48+
packages and configurations required for the AM62L-EVSE-DEV-EVM to function properly.
49+
50+
----
51+
52+
Quick Start with Pre-built Image
53+
================================
54+
55+
For quick evaluation and testing, download the latest pre-built WIC image: `tisdk-evse-image-rt-am62lxx-evm-11.02.08.02.rootfs.wic.xz <https://dr-download-draft.ext.ti.com/software-development/software-development-kit-sdk/MD-YjEeNKJJjt/11.02.08.02-REDRAFT/tisdk-evse-image-rt-am62lxx-evm-11.02.08.02.rootfs.wic.xz>`_
56+
57+
After downloading and flashing the image to your SD card, proceed directly to testing the communication interfaces by following the
58+
procedures in the `AM62L-EVSE-DEV-EVM Software User Guide <https://www.ti.com/lit/pdf/SLUUDH5>`_.
59+
60+
----
61+
62+
Building the SDK with Yocto
63+
===========================
64+
65+
This section describes how to build the EVSE WIC image from source using the Yocto Project build system.
66+
Follow the standard :ref:`Processor SDK - Building the SDK with Yocto <building-the-sdk-with-yocto>` and build for the EV charging Use case.
67+
68+
----
69+
70+
Testing Communication Interfaces
71+
================================
72+
73+
The AM62L-EVSE-DEV-EVM provides multiple communication interfaces essential for EV charging applications:
74+
75+
* **PLC (Power Line Communication)** - For ISO 15118 high-level communication
76+
* **CAN** - For communication with power conversion units and vehicle networks
77+
* **RS-485** - For industrial protocol communication with metering devices
78+
* **RS-232** - For legacy device communication
79+
80+
Complete testing procedures, pinout information, and example configurations for all communication interfaces are documented in the `AM62L-EVSE-DEV-EVM Software User Guide <https://www.ti.com/lit/pdf/SLUUDH5>`_.
81+
82+
----
83+
84+
Additional Resources
85+
====================
86+
87+
* `AM62L-EVSE-DEV-EVM Software User Guide <https://www.ti.com/lit/pdf/SLUUDH5>`_ - Complete hardware setup, testing procedures, and system architecture
88+
* `AM62L-EVSE-DEV-EVM User Guide <https://www.ti.com/lit/ug/slvudn0/slvudn0.pdf>`_ - Hardware user guide
89+
* `TIDA-010939 Reference Design <https://www.ti.com/tool/TIDA-010939>`_ - Hardware reference design documentation
90+
* `AM62L Processor Product Page <https://www.ti.com/product/AM62L>`_ - AM62L processor specifications and resources
91+
* `AM62L Product Overview <https://www.ti.com/lit/po/sprt790/sprt790.pdf>`_ - AM62L processor overview
92+
* `AM62L Device Academy <https://dev.ti.com/tirex/explore/node?node=A__AEIJm0rwIeU.2P1OBWwlaA__AM62L-ACADEMY__6F61DO6__LATEST>`_
93+
* `EVerest Open Source Charging Stack <https://everest.github.io/>`_ - Open-source alternative for users without an existing EV charging software stack
94+
95+
96+
----
97+
98+
99+
Glossary
100+
========
101+
102+
.. glossary::
103+
104+
CCS
105+
Combined Charging System - A fast-charging standard for electric vehicles supporting both AC and DC charging.
106+
107+
CHAdeMO
108+
Charge de Move - A DC fast-charging standard developed in Japan for electric vehicles.
109+
110+
EVSE
111+
Electric Vehicle Supply Equipment - The infrastructure and equipment used to supply electric energy for charging electric vehicles.
112+
113+
GB/T
114+
Guobiao/Tuijian - Chinese national standards for electric vehicle charging, including GB/T 20234 (connectors) and GB/T 27930 (communication protocol).
115+
116+
PLC
117+
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: 27 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -197,6 +197,28 @@ 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 support (EV charging Use case support).
204+
205+
.. tabs::
206+
207+
.. tab:: Build EVSE RT-Linux SD card Image
208+
209+
.. code-block:: console
210+
211+
$ git clone https://git.ti.com/git/arago-project/oe-layersetup.git tisdk
212+
$ cd tisdk
213+
$ ./oe-layertool-setup.sh -f configs/processor-sdk/<oeconfig-file>
214+
$ cd build
215+
$ . conf/setenv
216+
$ MACHINE=<machine> ARAGO_RT_ENABLE=1 bitbake -k tisdk-evse-image
217+
218+
.. important::
219+
220+
EVSE (EV Charging) image uses RT-Linux and is not supported on Linux.
221+
200222
.. ifconfig:: CONFIG_sdk in ('JACINTO','j7_foundational')
201223

202224
|__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 +401,8 @@ The build system places the "Build Output" relative to :file:`deploy-ti`
379401
+------------------------------+----------------------------------------------------------------+----------------------------+
380402
| tisdk-jailhouse-image | images/<machine>/tisdk-jailhouse-image-<machine>.rootfs.tar.xz | Jailhouse Filesystem |
381403
+------------------------------+----------------------------------------------------------------+----------------------------+
404+
| tisdk-evse-image | images/<machine>/tisdk-evse-image-<machine>.rootfs.tar.xz | EV Charging Filesystem |
405+
+------------------------------+----------------------------------------------------------------+----------------------------+
382406
| tisdk-base-image | images/<machine>/tisdk-base-image-<machine>.rootfs.tar.xz | Minimal Target Filesytem |
383407
+------------------------------+----------------------------------------------------------------+----------------------------+
384408
| tisdk-thinlinux-image | images/<machine>/tisdk-thinlinux-image-<machine>.rootfs.tar.xz | Minimal Target Filesytem |
@@ -749,10 +773,10 @@ and IPK packages in the deploy-ipks folder.
749773

750774
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.
751775
You can call the following command from yocto's build directory to get the path to the workdir of your recipe.
752-
776+
753777
.. code-block:: console
754-
755-
MACHINE=<machine> bitbake-getvar -r <recipe-name> WORKDIR --value
778+
779+
MACHINE=<machine> bitbake-getvar -r <recipe-name> WORKDIR --value
756780
757781
.. rubric:: Forced Re-compilation
758782
:name: Forced Re-compilation

0 commit comments

Comments
 (0)