Part Number: TDA4VM
Tool/software:
Is there a way to compare any TI SOC capabilities with another TI SOC?
Part Number: TDA4VL-Q1
Tool/software:
How to use SDL_ESM_config to do configure ESM parameters? Which bit is mapped to which ESM event?
Part Number: AM625, AM623, AM620-Q1, AM625-Q1, AM625SIP, AM62A7, AM62A7-Q1, AM62A3, AM62A3-Q1, AM62A1-Q1, AM62D-Q1, AM62P, AM62P-Q1, AM62L, AM6442, AM6441, AM6422, AM6422, AM6412, AM6411, AM2434, AM2432, AM2431,
Tool/software:
Hi TI experts,
Please provide guidelines for using RGMII interface
Recommendations while using TI EPHY for RGMII interface
Part Number: Part Number: AM625, AM623, AM620-Q1, AM625-Q1, AM625SIP, AM62A7, AM62A7-Q1, AM62A3, AM62A3-Q1, AM62A1-Q1, AM62D-Q1, AM62P, AM62P-Q1, AM62L, AM6442, AM6441, AM6422, AM6422, AM6412, AM6411, AM2434, AM2432, AM2431,
Tool/software:
Hi TI experts,
Please provide guidelines for using RMII interface
Recommendations while using TI EPHY for RMII interface
Part Number: AM62P
Tool/software:
This FAQ will talk about how one should perform basic debugging when facing Linux Display Related issues on AM62P / AM62x / AM62L / AM62A.
In case the debugging doesn't help resolve the issue, follow the Best Practices section to include necessary information while posting your queries on E2E forum.
The FAQ is regularly updated to provide the most current information. We recommend reviewing the FAQ periodically for the latest updates.
Part Number: AM6442
Tool/software:
Hi TI Experts,
Can you share the external LVCMOS Digital Clock Source specifications and guidelines while using external LVCMOS clock input as the processor clock source for
MCU_OSC0
Part Number: J7200XSOMXEVM
Tool/software:
How to enable USB2.0 in UBOOT?
Criticality
High
Hardware Devices and Revisions Affected
AM62x, AM62Ax, AM62Dx, AM62Px: SDK 10.1 and earlier
AM67, AM67A: SDK 11.0 and earlier
Description
The primary role of the Device Management (DM) R5F core is to run the DM task. Non-DM code running on the DM R5F should not interfere with the DM task. That means non-DM tasks should not crash the DM R5F core, block the DM task from running, corrupt DM memory, etc.
Under certain conditions, the ipc_rpmsg_echo_linux project will crash the DM R5F after 49 days of continuous operation. After the DM R5F crashes, device management (DM) and power management (PM) requests fail. This can render the device inoperable until a power cycle resets the DM R5F. This behavior can be fixed by updating the firmware running on the DM R5F.
Both SPL and SBL bootflows can be affected:
Part Number: AM62L
Tool/software:
HI TI experts,
I have the below queries regarding LVCMOS hysteresis
LVCMOS IOs that support (implements) hysteresis
LVCMOS IOs hysteresis specifications
Enabling LVCMOS IOs hysteresis
Parts Discussed in Thread: AM62x, AM62Ax, AM62Dx, AM62Px, AM67, AM67A
The primary role of the Device Management (DM) R5F core is to run the DM task. However, there may be other non-DM code running on the DM R5F, alongside the DM task. The firmware running on the DM R5F core is initialized during boot time, either during SPL boot or SBL boot.
For more information about SPL boot and SBL boot, refer to the processor academy > Multicore > Boot flows: SBL vs SBL
AM62x || AM62Ax || AM62Px
When using the Linux SPL bootflow, the quickest way to check what binary is running on the DM R5F is to find the source file that is built into the tispl.bin file. But how to figure out which binary file is getting used? It depends on how the u-boot files are built.
Other FAQs
This is a helper FAQ for RE: [FAQ] DM R5F can crash in certain conditions: AM62x, AM62Ax, AM62Dx, AM62Px, AM67, AM67A question "SPL boot: How to find the DM R5F binary that is built into tispl.bin".
