TI AM67A / J722S Documentation Map: Datasheet, TRM, SDK, Errata and the Edge AI Documents

Engineers starting with the AM67A lose time before they lose anything else: the information exists, but it is not obvious which document holds it, several documents are published under a different chip's name, and two official pages answer the same question differently. This page is that map — which document answers which question, where the naming confusion comes from, and which source wins when official sources disagree. Every link below was opened and verified on 5 September 2026.

Which document answers which problem

The naming problem: AM67A, AM67, J722S, TDA4VEN

This is why the page exists. The same silicon reaches you under at least five names.

The root cause: each layer uses a different name.

What this means in practice:

• Searching for "AM67A TRM" finds the document but not the name inside it. Opening the TRM and searching AM67A returns zero hits; you have to search AM67 or J722S.
• There is no ti.com/product/J722S page — it returns 404. J722S is a document and software name, not a name TI sells under.
• There is no Yocto machine called am67. meta-ti contains only j722s-evm and j722s-evm-k3r5, while the same directory holds am68-sk and am69-sk. So this inconsistency is specific to this part, not a family-wide convention.
• In mainline Linux, every SoC-level device tree file carries the k3-j722s* name. Files named am67a are board-level (BeagleY-AI). k3-j722s.dtsi landed in v6.9; k3-am67a-beagley-ai.dts in v6.12.
• No RTOS or standalone MCU+ SDK is published under the AM67A name. The MCU side ships only inside the J722S SDK.

Seeing J722S in a document does not mean you are reading about the wrong chip. But the reverse does not hold either: because J722S is the superset, not every feature described in a J722S document exists on the AM67A. The datasheet warns about this explicitly and tells you to constrain software to the features of the target production device.

Silicon documents

Datasheet — SPRSPA3B

AM67x Processors, SPRSPA3B, March 2024, revised June 2026. https://www.ti.com/lit/ds/symlink/am67a.pdf

Answers: feature list, the variant comparison table (Table 4-1), speed grades, operating conditions, Power-On Hours, thermal resistance, eFuse programming conditions, power sequencing, pin list, package and order-code decoding.

Watch for:

• One document covers two parts (AM67 and AM67A). The feature list is the union of both; which feature belongs to which part is readable only from Table 4-1.
• This is why the ti.com/product/AM67 page can show "4 TOPS" — it comes from the shared feature block, and the AM67 part has no deep-learning accelerator.
• Revision matters: revision B removed statements that revision A contained. An older copy on your disk may be carrying wrong information.

Technical Reference Manual — SPRUJB3D

J722S/TDA4VEN/TDA4AEN/AM67 Processor Silicon Revision 1.0 TRM, SPRUJB3D, March 2024, revised August 2026. https://www.ti.com/lit/zip/sprujb3

Answers: block internals (VPAC sub-modules, DMPAC engines, R5F subsystems), memory map, register definitions, which features are unsupported.

Watch for:

• TI does not offer this document as a PDF. ti.com/lit/pdf/sprujb3 does not work; only the ZIP path exists, and the archive is roughly 44 MB. Inside it you get SPRUJB3D.pdf (2400+ pages) plus a separate register-table spreadsheet.
• To make search usable, download it and convert it to text locally; opening it in a browser and searching is not practical.
• The "Unsupported Features" headings are the most valuable and most skipped sections. A feature appearing in the datasheet does not mean the TRM supports it.
• Blocks may be named differently than in the datasheet — the datasheet uses the reference name VPAC3L where the TRM says only "VPAC".

Silicon Errata — SPRZ575A

J722S/TDA4VEN/TDA4AEN/AM67 Processor Silicon Revision 1.0 Errata, SPRZ575, Rev. A, April 2025. https://www.ti.com/lit/pdf/sprz575

Answers: known silicon behaviour that contradicts the datasheet, and the workarounds.

Watch for:

• The errata is older than the datasheet. Datasheet June 2026, errata April 2025. In the year between them the datasheet was revised twice and the errata was not.
• Before starting board design, confirm the current revision of both documents directly with TI.
• The errata's "Advisories by Modules" table is the fastest way to see which peripheral has a known problem.

Software documents — and the real trap here

This is the most practically useful section on the page.

TI publishes two separate SDK brands for the same silicon, and they do not move at the same pace. As of 5 September 2026:

So the Linux SDK carrying the AM67A name is two minor versions and fourteen months behind the one carrying the J722S name. The AM67A page also has no RTOS SDK at all; if you intend to work on the R5F or C7x side you have to go to the J722S page.

Practical consequence: a team following only ti.com/tool/PROCESSOR-SDK-AM67A may be working on an old Linux SDK and never seeing the MCU side. If you are doing serious work on the AM67A, track both pages.

• Processor SDK AM67A: https://www.ti.com/tool/PROCESSOR-SDK-AM67A
• Processor SDK J722S: https://www.ti.com/tool/PROCESSOR-SDK-J722S
• AM67A Linux SDK docs: https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/index.html
• J722S RTOS SDK docs: https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/latest/exports/docs/index.html

Software Build Sheet

The datasheet does not itself answer the question of which hardware feature is actually supported in software; in two separate places it redirects the reader to the Software Build Sheet. That document sits in the downloads tab of the SDK page.

This is the first document to open when validating an architecture plan: which core is open to application code, which peripheral has a driver, and which feature is in the "present in silicon, absent from the SDK" state are all read from here.

Edge AI and TIDL

• edgeai-tidl-tools: https://github.com/TexasInstruments/edgeai-tidl-tools
• edgeai-modelzoo: https://github.com/TexasInstruments/edgeai-modelzoo
• edgeai-gst-apps: https://github.com/TexasInstruments/edgeai-gst-apps
• edgeai-tensorlab: https://github.com/TexasInstruments/edgeai-tensorlab
• Edge AI Studio: https://www.ti.com/tool/EDGE-AI-STUDIO

Model compilation runs on a host machine and the resulting artifacts execute on the board. Which runtime version an artifact is compatible with depends on the match between these repositories' release tags and the SDK version — and if that match is not tracked, it is possible to get wrong results without any error message. The compile-side detail is covered separately in the TIDL model deployment page.

Full document inventory

Every document below was opened and verified on 5 September 2026. Revision letters and dates are the values valid that day.

Silicon and electrical

Board design

Security and production

Vision and Edge AI

Repositories

When documents disagree

Working with the AM67A, official sources contradicting each other is not the exception — it is a regular occurrence. The known contradictions and which one governs:

The general rule: datasheet for electrical and variant information, TRM for block internals, errata and Software Build Sheet for "does it actually work". The product page's parametric summary is a marketing summary and should not be used for technical decisions.

Related Spikedge pages

• TI AM67A SoC architecture — what the blocks are and how they connect
• AM67A vs AM62A processor selection — which part fits which system
• AM67A vision pipeline — where the latency goes between sensor and decision
• Linux and R5F real-time architecture — splitting work across the A53 and R5F cores
• T3 Gemstone O1 technical analysis — one AM67A board, read from its schematic

Upstream and community

• Mainline Linux device tree: k3-j722s* files; board layers k3-am67a-*
• U-Boot J722S EVM page: https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
• meta-ti Yocto layer: https://github.com/TexasInstruments/meta-ti
• Linux remoteproc: https://docs.kernel.org/staging/remoteproc.html
• Linux rpmsg: https://docs.kernel.org/staging/rpmsg.html
• TI E2E forum: https://e2e.ti.com/support/processors-group/processors/f/processors-forum