This directory contains scripts used with Lauterbach's TRACE32 on the Texas Instruments AM62 SOC. Supported hosts will be Windows, Linux, and Mac.

The TRACE32 image used on AM62 is composed of:
	- A base image using the TRACE32_R_2021_09_000141911 release from https://www.lauterbach.com/frames.html?download_trace32.html
	  -- Targets installed were ARM, PRU
	  -- TRACE32 daily builds since Q4-2021 (>= N.2021.11.000141993) will support AM62
	- TI example scripts, cmm-am62x.7z, unzipped into the install directory

The supported TRACE32 system.cpu names used in scripts are:
	; A53 (1x4) : AM625X (core.assign 1. 2. 3. 4.)
	; CR5 (1x1) : AM625X-CR5
	; CM4 (3x1) : AM625X-CM4-SMS0 AM625X-CM4-SMS1 AM625X-CM4-BLAZAR
	; PRU (1x2) : AM625X-ICSS0 (core.assign 1. 2.)

The system supports AM62x HW features:
	- basic debug on all cores (load/run, step/break, view, dap-sample-based-trace)
	- advanced processor trace on all cores to on chip buffers and to off chip receivers
	  -- ETM on the Cortex-A53 + Cortex-M4, Cortex-R5
	  -- ITM on Cortex-M4
	  -- SNOOPER-DAP trace on all cores Cortex-A, Cortex-R, Cortex-M, ICSS/PRU.
	- System trace
	  -- Coresight STM messages
	- Peripheral suspend when a core is halted
	- Cross triggering via CTI/CTM networks
	- All standard TRACE32 features
	  -- Trace and sample-based analysis 
	  -- Code coverage
	  -- Performance profiling
	  -- Awareness for AM62 HLOS (Linux, QNX) : RTOS (FreeRTOS, SafeRTOS, TIRTOS)
	  -- All standard features ..., ..., ...

Directory/Files:
	bsdl : BSDL support for test and flashing
	burn_flash: controller-based flasher
	notes: Information on cptracer and suspend-router features
	x_gel_to_cmm:
		pdk_rtos_test: scripts to launch PDK examples via JTAG which use TI system firmware
		memtester: simple memtesters to validate DDR
		<other>: TI validation scripts used to initialize power, clocks and DDR typically used with bare metal development
	logic analyzer: Scripts used with TRACE32 addon logic and analyzer extensions: ciprobe, iprobe, probe, integrator
	am62x_win_launcher.ts2 : standard Windows t32start compatible launcher

Getting started:
	A first-time user on the EVM should see example videos then mimic them:
		Running the x_gel_to_cmm/am62_allcoretype_connect.cmm script
			This initializes the platform and brings up basic debug for all cores.
			If you don't have licenses for all the cores comment out the ones not desired
	Early board checkout and RTOS development likely use files in x_gel_to_cmm
		A custom board can be added at this level.
	The script files offer increase over the life of the chip so check for CDDS updates









 

