Agent skill · NVIDIA
jetson-customize-mgbe
Enable Jetson Thor 25G/10G/1G MGBE QSFP via kernel-DT overlay. Do NOT use for UPHY lane allocation or ODMDATA edits.
What it needs
About 4k tokens when loaded.
What this skill does
Customize MGBE / 25G QSFP Overview Thor T264 exposes mgbe0..mgbe3. On a custom carrier, the 25G QSFP cage (or 10G / 1G fiber path) is wired to one of them through SerDes — with or without an external MDIO PHY in front of the cage. This skill renders the kernel-DT overlay that pairs the BPMP allocation with kernel-side status="okay" + PHY plumbing on &mgbeN. Out of scope: UPHY lane allocation — owned by /jetson-customize-uphy. Refuse if the chosen uphy1-config-N doesn't allocate the target MGBE. All ODMDATA tokens (mgbeN-speed-, sub-node mgbeNstatus=) — owned by /jetson-customize-uphy in its single atomic ODMDATA commit. This skill MUST NOT touch ODMDATA=. Output is one commit to the composite custom overlay .dts in the bspsources/ hardware repo. /jetson-build-source compiles the composite to .dtbo and owns its Makefile + flash-conf registration. When to invoke The user says "enable 25G", "configure QSFP", "set MGBE PHY mode", "wire MGBE to QSFP", or asks to bring up a 10G / 1G fiber path. Cold boot succeeds but ip link show mgbe<N> reports state DOWN or NO-CARRIER on the configured controller, OR the controller never appears at all. jetson-customize-uphy ran with uphy1-config-8 (or another config allocating MGBE) and you now need to bring up the per-controller side. Prerequisites: Active profile selected with referencedevkit: (Thor) + customcarrier: blocks. <source.rootpath>/LinuxforTegra/.git exists (/jetson-init-source). /jetson-derive-carrier has run — carrier flash-conf fork is in the overlay tracker. /jetson-customize-uphy chose a UPHY config that allocates the target MGBE controller's lanes (uphy1-config-8 on Thor for MGBE0..3 25G). Source-of-truth docs registered or supplied at prompt: Adaptation Guide, Module Design Guide, SoC TRM. When customcarrier: is present, both documents.customcarrierschematic AND documents.customcarrierpinmuxxls are REQUIRED. Refuse the run if either is missing — MGBE routing on a custom carrier cannot be guessed. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills NVIDIA/jetson-customize-mgbe