Part Number: TDA4VM

How to reduce the EthFW initialization time to avail CPSW H/W Switch functionality as soon as possible after the core boot up in Vision Apps use-case?

Part Number: TDA4VM

How do I enable CAN channels on Gateway/Ethernet Switch/Industrial (GESI) expansion card when using J721E EVM from Linux A72?

This FAQ walks the user through setting up an industrial networking EtherCAT system in CODESYS using an AM6xx MainDevice and one-or-more AM64x/AM243x SubDevice(s). Instructions are provided to set up MainDevice, SubDevice(s), and build the project & visualization in CODESYS Development System to control test LEDs on the SubDevice(s) from the MainDevice

Software versions tested in this documentation:

AM62x Processor SDK version: ti-processor-sdk-linux-rt-am62xx-evm-09.00.00.03 & ti-processor-sdk-linux-rt-am62xx-evm-08.06.00.45: https://www.ti.com/tool/PROCESSOR-SDK-AM62X#downloads

AM243x MCU+ SDK version: mcu_plus_sdk_am243x_08_05_00_24 (as of this writing, the AM243x-LP (HSFS) EtherCAT example demo does not work on MCU+ SDK 08_06. AM243x-EVM does not have this issue): https://www.ti.com/tool/download/MCU-PLUS-SDK-AM243X/08.05.00.24

Code Composer Studio version: Match CCS version to the version listed in the MCU+ SDK: https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/latest/exports/docs/api_guide_am243x/CCS_SETUP_PAGE.html#autotoc_md21

CODESYS Development System: CODESYS Development System V3 3.5.19.10:

(US store) https://us.store.codesys.com/codesys.html 

(International store) https://store.codesys.com/en/

CODESYS Control for Linux ARM64 SL: CODESYS Control for Linux ARM64 SL 4.9.0.0.package & CODESYS Control for Linux ARM64 SL 4.2.0.0.package:

(US store) https://us.store.codesys.com/codesys-control-for-linux-arm-sl-bundle.html 

(International store)

Old Link: https://store.codesys.com/en/codesys-control-for-linux-arm-sl-bundle.html 

Updated Link: https://us.store.codesys.com/codesys-control-for-linux-arm-sl-1.html 

System set up instructions overview (clickable links):

1. Set up AM6xx EtherCAT MainDevice
2. Set up AM64x/AM243x EtherCAT SubDevice(s)
3. Build project in CODESYS desktop software, build visualization, & test system

Demo:

Part Number: TDA4VM

How to run OpenVX Host on R5F and a node to run on A72 (Linux) as target?

Part Number: AM623

Champs,

Customer's asking what will happen if the decoupling caps on the CAP* nets below are not installed correctly? Will the device's behavior be well defined in this case (i.e. fail to boot etc) or would it be more sporadic based on operating mode? They are preparing manufacturing test definition and wondering about scenarios such as

1. DNP incorrectly.  
2. One or more of the caps are damaged due to handling and result in:
   1. open
   2. short
3. Is there any defined behavior for wrong values  of the capacitors that can be captured in testing?

Thank you

Michael

(applicable to all TI Sitara and Jacinto devices such as AM62x, AM62Ax, AM64x, AM65x, and so on)

Symptoms

When doing a Yocto build as per SDK instructions for example of the SDK default image like this...

MACHINE=am62xx-evm bitbake -k tisdk-default-image

...the build starts, but then after a while it no longer seems to proceed in any way at all. The progress display showing which tasks are running and their status do not update. When checking CPU loading/activity (for example, using the 'htop' utility), there is no significant system loading. This seems to happen especially when building larger images (such as the tisdk-default-image vs. the tisdk-base-image), especially with later/newer SDKs such as SDK v8.6 or SDK v9.0.

For example, the build console can look like this (with no changes for hours):

NOTE: recipe python3-tensorflow-lite-2.8.0-r0: task do_compile: Started
NOTE: recipe open62541-1.0.1+gitAUTOINC+e4309754fc-r0: task do_compile: Started
NOTE: recipe powervr-graphics-5.8-r1: task do_compile: Started
NOTE: recipe gtk+3-3.24.14-r0: task do_compile: Started
NOTE: recipe glmark2-20191226+AUTOINC+72dabc5d72-r0.arago0: task do_compile: Started

Issue Analysis, Discussion, and Solutions

Yocto builds, especially those for more complex/larger recipes can use a significant amount of system resources. This is the case when heavy build parallelism is enabled - which it is by default. In case the Yocto build process attempts to use more memory (RAM) than available, the Linux Kernel out-of-memory (OOM) killer which is a process in charge of preventing processes from exhausting the build machine's memory will terminate critical Yocto build processes, in a way that goes undetected by the Yocto build itself, leaving the overall build hanging. To see if your build is indeed affected by this issue, terminate your Yocto build (CTRL+C for multiple times should do the trick), and then search the Kernel log for signs of the OOM killer having become active. If your Kernel log looks like the below example with recent entries, then your build failure was likely due to the OOM killer.

$ sudo dmesg | grep oom
[sudo] password for a0797059:
[3024499.564459] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1001.slice/session-2.scope,task=Cooker,pid=2364037,uid=1001
[3024499.564480] Out of memory: Killed process 2364037 (Cooker) total-vm:1302284kB, anon-rss:36840kB, file-rss:0kB, shmem-rss:24kB, UID:1001 pgtables:2284kB oom_score_adj:0
[3085219.883311] xz invoked oom-killer: gfp_mask=0x140dca(GFP_HIGHUSER_MOVABLE|__GFP_COMP|__GFP_ZERO), order=0, oom_score_adj=0
[3085219.883338]  oom_kill_process.cold+0xb/0x10
[3085219.883342]  __alloc_pages_may_oom+0x117/0x1e0
[3085219.883473] [  pid  ]   uid  tgid total_vm      rss pgtables_bytes swapents oom_score_adj name
[3085219.883492] [    668]   108   668     3706       32    65536      179          -900 systemd-oomd
[3085219.884409] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1001.slice/session-2.scope,task=cc1plus,pid=3120743,uid=1001
[3085219.884423] Out of memory: Killed process 3120743 (cc1plus) total-vm:4242032kB, anon-rss:4094828kB, file-rss:0kB, shmem-rss:0kB, UID:1001 pgtables:8232kB oom_score_adj:0

The issue can be addressed by either increasing the amount of RAM available for the build (adding physical RAM modules, increasing swap space, not loading the build machine with other tasks), or since this may not always be practical, by re-configuring the Yocto build parallelism to build less things in parallel. Note that the earlier example was from a build machine with 64GB of RAM, 20 CPU cores, building an AM64 SDK v9.0 tisdk-default-image, demonstrating that this also may happen if you think you have a rather powerful machine.

Yocto build parallelism is controlled through the BB_NUMBER_THREADS and PARALLEL_MAKE variables, and those settings can be easily changed by updating (uncommenting and changing) the following section in the build's conf/local.conf file:

#
# Parallelism Options
#
# These two options control how much parallelism BitBake should use. The first
# option determines how many tasks bitbake should run in parallel:
#
# BB_NUMBER_THREADS ?= "1"
#
# The second option controls how many processes make should run in parallel when
# running compile tasks:
#
# PARALLEL_MAKE ?= "-j 1"
#
# For a quad-core machine, BB_NUMBER_THREADS = "4", PARALLEL_MAKE = "-j 4" would
# be appropriate for example
#
# NOTE: By default, bitbake will choose the number of processeors on your host
# so you should not need to set this unless you are wanting to lower the number
# allowed.
#

In case of build issues, try setting BB_NUMBER_THREADS to "1" for debug purposes, and see if the build can now proceed with this. Note that before re-trying your build you may first need to manually clean/kill any remaining Yocto processes that may still be running on your machine (like bitbake-server). If this works, then you can then try to find a more suitable (faster) setting for this variable which still works on your given machine by using a value that is less than the number of CPUs available (but larger than 1).

Part Number: AM62A3-Q1

Hi TI expert,

The SOC AM62A define the standard SPI interface by SPI_CS, SPI_CLK, SPI_D0, SPI_D1. 

If our slave device need to get MISO and MOSI data line, how will we used the D0 and D1 data line. Dose it programable? Can the D0 be the MISO or MOSI? 

I have the below queries regarding the DEVICS_ID 

1. Is there a device ID available that I can read?
2. Can you guide me how to read the device ID?
3. Is the ID unique for each device?
4. Is there an ID that is unique to each device?

Part Number: AM625

Hello,

Do we have a specification on the max drive strength/ power that AM625 can drive for both the HF crystal as well as 32 KHz oscillator? I didn't see it specified in the data sheet and customer wants to make sure they're within the drive strength guidelines for the processor.

Munan

I am using a Sitara processor with a Linux core, a time sync router, and a PRU subsystem (AM62x, AM64x, AM65x). I want to synchronize the Linux system time with an IEP timer in the PRU subsystem. How do I do it?

We will use AM64x for this example, but the same concepts will apply to all of the processors.

.

AM64x Time Sync Router: reference [FAQ] AM64x: What is the Time Sync Router for? How do I use it?

AM62x Time Sync Router: reference [FAQ] AM62: What is the Time Sync Router for? How do I use it?

For more information about other Sitara multicore subjects, reference [FAQ] Sitara multicore development and documentation. More information about PRU specifically can be found in the PRU Development subsection.