topic S32E2 JTAG Daisy Chain Support and Debugger Configuration in S32Z/E

S32E2 JTAG Daisy Chain Support and Debugger Configuration

smp9 — Tue, 02 Dec 2025 09:18:26 GMT

Hi everyone,
I am evaluating the S32E2 architecture for a multi-node system and I have a question regarding debug interface topology.
We are planning a design that includes 3 S32E2 devices on a single board. We would like to daisy chain them on a single JTAG interface (IEEE 1149.1).
Could you please confirm the following:
Daisy Chain Support: Does the S32E2 silicon fully support standard JTAG daisy chaining? Are there any known errata or limitations when chaining multiple identical S32E2 units?
Tooling Support: Does the S32 Design Studio (S32DS) environment and the standard NXP debug probes support configuring a chain of identical devices? specifically, is there a mechanism to address target devices by their position in the chain to handle the duplicate JTAG ID conflicts?
Any pointers to reference designs or application notes detailing multi-device debugging for the S32 platform would be appreciated.
Thanks!

Re: S32E2 JTAG Daisy Chain Support and Debugger Configuration

Joey_z — Tue, 02 Dec 2025 10:44:16 GMT

hi,smp9

Thank you for contacting us.

I will help you to check this information.

Joey

Re: S32E2 JTAG Daisy Chain Support and Debugger Configuration

Joey_z — Wed, 03 Dec 2025 02:57:43 GMT

hi,smp9

Thank you for contacting us.

1.Refer to the Reference Manual,the architectural intent behind this definition is defined in the Arm CoreSight Architecture 2.0 document. The CoreSight specification allows each debug target to support only some of the functionality defined by the authentication interface.

2.S32 Design Studio (S32DS) and NXP S32 Debug Probe support JTAG debugging, while S32 Debug Probe supports single-target connections.

Hope this can help you.

Joey