AURIX ADS, Flasher, and TriCore debug

​

Prepare the project and tools

1. Install ADS and CMake. You can provide a compatible external TriCore GCC toolchain directory, but ADS is still required for its build utilities. Ninja is preferred when installed; the build wrapper can use ADS make instead.
2. Confirm that the project contains .cproject and an extracted, nonempty Libraries/iLLD/ directory. In ADS, use Add iLLD if the library is missing.
3. Check that the project has a usable External-GCC configuration with the target CPU and linker settings. Setup prefers an External-GCC Debug configuration and falls back to Release. For TC4xx, a recognized target CPU setting is required; supply a valid GCC linker script if the project does not already contain one.
4. Save any needed outputs outside build/: setup’s verification build deletes that directory. Review existing CMake files and build/flash wrappers before proceeding, because setup replaces its generated files.

​

Generate and check the build

Prepare this ADS/iLLD project for CLI builds on Windows. Check .cproject,
the extracted iLLD, compiler, and target linker script. Generate the build
and flash wrappers, then build the target without flashing it. Report
missing tools or configuration before proceeding.

.\build.cmd

​

Configure AURIX Flasher

​

Program and verify startup

1. Connect and power the intended target using its board instructions. Close competing programming or debugger sessions.
2. Confirm that build/app.hex is the successful build for that target and that flash.cmd uses the installed flasher on this machine.
3. Ask Embedder to run the configured command and check the programming result:
   Use the configured flash.cmd to program build/app.hex on the confirmed
   local AURIX target. Report the flasher result, then check the firmware's
   expected boot indicator or UART output. Do not change programming settings
   or choose another connected target to bypass an error.
   

​

Keep the project commands

​

Troubleshoot

• Setup unavailable: run Embedder on Windows with local access to the project and ADS tools.
• Missing iLLD: extract the library into Libraries/iLLD/; an empty directory is insufficient.
• External-GCC or TC4xx configuration rejected: correct the CPU configuration and provide the intended GCC linker script.
• ADS not found: provide its absolute installation path, including when selecting the limited edition explicitly.
• Flasher path unconfigured: install AURIX Flasher and set the wrapper’s executable path before programming.
• HEX file missing: fix the build and confirm build/app.hex before retrying.
• Programming succeeds but no boot: check the flasher’s start/reset settings, board power, and firmware output without assuming another flash is necessary.

​

Debug TriCore over TCF

​

Requirements

• Windows only. DAS, MCD, and the agent do not run elsewhere.
• Infineon DAS installed (free download from infineon.com/DAS). The agent reaches the target through it.
• Either an AURIX Development Studio install (which bundles the agent) or Embedder’s managed agent (see below).
• An ELF built with symbols. Without the ELF the agent cannot resolve source lines or globals.

​

The agent Embedder uses

​

Connect and set a breakpoint

import json

aurix.connect(elf="build/App.elf", entry="core0_main", core=0)

bp = aurix.breakpoint("Cpu0_Main.c", 82)
if not bp["planted"]:
    raise RuntimeError(f"breakpoint did not bind: {bp.get('plant_error')}")

r = aurix.continue_until_break(timeout_seconds=15)
if r["timed_out"]:
    raise RuntimeError("target never reached the breakpoint")

frames = aurix.stack()["frames"]
counter = aurix.eval("g_counter")
aurix.disconnect()

print(json.dumps({
    "success": True,
    "summary": f"hit {frames[0]['file']}:{frames[0]['line']} with g_counter={counter}",
    "data": {"pc": r["stop"]["pc"], "cores_halted": len(r["stop"]["suspended_cores"])},
}))

• aurix.connect(elf, device=None, entry='core0_main', core=0, svd=None, flash=False, timeout_seconds=30.0, agent_path=None) spawns the agent, registers the ELF for symbols and lines, and halts the target. flash=True programs the ELF at launch; the default attaches to whatever is on the target. Check image_check["matches"] in the reply before trusting anything. When it is false, the running firmware differs from the ELF, and symbols will resolve confidently against code that is not executing.
• aurix.breakpoint(file, line, condition=None) returns {id, planted, plant_error?, ...}. Always check planted; a breakpoint that did not bind never fires and the next continue simply times out. condition is evaluated in the harness (round-tripped stop → eval → resume), so avoid conditions in hot loops.
• aurix.continue_until_break(timeout_seconds=15.0, core=None) returns {ok, timed_out, stop} where stop includes core, pc, reason, hit_breakpoint, and suspended_cores. On timeout the target stays halted for inspection.
• aurix.eval(expression, core=None, frame=None), aurix.read_memory / aurix.write_memory, aurix.read_register / aurix.read_registers / aurix.write_register, aurix.disassemble, aurix.find_symbol, and aurix.step / aurix.next / aurix.finish / aurix.step_instruction cover state inspection and single stepping.

​

Cores, not threads

​

What this backend refuses

• No watchpoints. The MCD layer ignores TCF AccessMode, so a data watchpoint would never trigger. Break at each write site instead.
• No load_file or execute. There is no GDB command line. Flash with AURIX Flasher (or connect(flash=True)), and use eval / read_memory / write_register in place of ad-hoc GDB commands.
• No threads or RTOS tasks. Use aurix.cores().
• No locals enumeration. Read locals one at a time with aurix.eval("name", frame=frames[0]["id"]).
• No RTT or ITM through this backend. The AURIX TCF helper does not expose either transport.

​

Session cleanup and the hardware queue

​

Verified target