topic Re: SJA1105 Configuration in S32K

SJA1105 Configuration

jianghao — Mon, 20 Apr 2026 11:02:03 GMT

Using the GMAC interface of S32K344 to connect with SJA1105, according to the manual, after enabling the auto-negotiation function on the RGMII port, and then sending a complete "static configuration table" to SJA1105 via the SPI interface, it is possible to adaptively obtain the actual 2.5/25/125 MHz clocks required by the RGMII port. Thus, it is possible to adaptively determine whether manual dynamic clock frequency division is needed to obtain 125 MHz/25 MHz/2.5 MHz clocks?

Re: SJA1105 Configuration

PavelL — Thu, 23 Apr 2026 14:04:16 GMT

Hello @jianghao ,

I think there is a small terminology mix-up here regarding Auto‑Negotiation vs. RGMII interface clocking.

Auto‑Negotiation is not a function of RGMII. RGMII is just the parallel MAC↔MAC / MAC↔PHY interface (data + source‑synchronous clocks). The link partner “Auto‑Negotiation” (speed/duplex capability exchange) happens on the PHY line side (e.g., 100BASE‑TX / 1000BASE‑T / 100BASE‑T1 etc.), not on the RGMII pins. In other words, S32K344 EMAC and SJA1105 do not “negotiate” speed over RGMII in the way SGMII/PCS-based links can.

The SJA1105 is an SPI-managed switch; you must load a static configuration after reset/power-up, and this configuration defines per-port interface mode and operational parameters. The typical software model is “configure and keep,” with only limited dynamic updates at runtime.

If your S32K344 EMAC ↔ SJA1105 connection is a MAC‑to‑MAC (PHY-less) RGMII link, the usual approach is to treat it as a fixed link and keep it at a chosen speed (S32K344 EMAC doesn't support 1Gbps).

Best regards,

Pavel

Re: SJA1105 Configuration

jianghao — Fri, 24 Apr 2026 10:14:39 GMT

@PavelL Thanks, I understand.