Nuvoton Launches Nu-Link3-Pro: World's First Programming Debug Analyzer with Integrated Logic Analysis, 110 MHz ETM Trace, MicroPython Offline Programming, I3C and CAN FD
Nuvoton's Nu-Link3-Pro folds six-channel logic analysis, I3C and CAN FD bridging, MicroPython-scripted offline programming and key-never-leaves Secure Provisioning into one debugger/programmer, with ETM real-time trace raised from 96 MHz to 110 MHz and a control bus for automated test equipment.
Nuvoton Technology introduced the Nu-Link3-Pro debugger and programmer on 15 October 2026, describing it as the world's first programming debug analyzer with integrated logic analysis. Compared with the previous-generation Nu-Link2-Pro, the upgrade runs along four lines: a move to USB Type-C, an ETM real-time instruction trace frequency raised to 110 MHz, newly added I3C and CAN FD bus support, and the consolidation of six-channel logic analysis, MicroPython-scripted offline programming and key-never-leaves-the-device Secure Provisioning into a single unit. For teams that develop embedded systems and program them at volume, the parameter that matters least is any single number; what matters is that these capabilities now sit in one box, and that shifts the boundary between the engineering bench and the production floor.
Announcement and Positioning
According to Nuvoton's press release (15 October 2026, Hsinchu), the Nu-Link3-Pro is positioned as a programmer and debugger for embedded system developers, covering programming and debugging across the full NuMicro microcontroller family. The upgrade directions published on the product and comparison pages fall into four groups:
- Bus Monitor: upgraded from the Nu-Link2-Pro's data-only monitoring to a logic analyzer function, with real-time digital signal analysis of up to six channels in the open-source PulseView software.
- Security: upgraded from key/certificate handling to Secure Provisioning — the private key is generated inside the Nu-Link3-Pro and held in a hardware key store, while a hardware encryption engine handles certificate issuance and encrypted programming, so the key never leaves the device.
- Automation Programming: upgraded from offline programming to built-in MicroPython, executing a MAIN.py script stored on a microSD card without modifying the firmware.
- Interface coverage: the Nu-Link2-Pro supported UART, SPI, I²C, RS-485, CAN, USB HID and microSD; the Nu-Link3-Pro adds I3C and CAN FD on top of that set.
Hardware and Debug Specifications
The Nu-Link3-Pro inherits the Nu-Link2-Pro's debug and programming framework while lifting several key specifications. The product and tool pages allow a point-by-point comparison:
- ETM real-time instruction trace: 96 MHz maximum on the Nu-Link2-Pro, raised to 110 MHz (roughly 15 percent higher), brought out through a 20-pin Cortex Debug + ETM connector.
- Debug interfaces: SWD, Manchester and ETM instruction trace; Arm DAPLink and pyOCD support; unlimited breakpoints and step execution.
- Power and levels: programmable output VDD held at 1.8, 2.5, 3.3 and 5.0 V; target VDD input range of 1.8–5.5 V; the unit can be powered over Micro USB or by the target board through the SWD interface.
- Physical interface: a full move to USB Type-C, which Nuvoton credits with improved connection stability; the Virtual COM Port is retained.
- Offline image storage: USB flash drive, SD card and built-in SPI flash all remain available.
What 110 MHz buys in practice is a denser sampling window on fast cores: combined with ETM, it captures a more complete instruction sequence around a failure. On cached platforms such as the M33, M55 and M7, trace depth often decides the outcome of a debugging session more than breakpoint count does.
Logic Analysis: Six Channels and the sigrok Ecosystem
The logic analysis feature connects to external circuits through a dedicated bridge connector (CON.6) on the device, and captures and decodes signals in PulseView, the graphical front end of the open-source sigrok signal analysis stack. The underlying libsigrokdecode library currently ships 131 protocol decoders (source: sigrok.org protocol decoder list), covering I²C, SPI, UART, CAN, JTAG, USB and other common buses, and the decoders stack: an I²C decoder can be layered under an EEPROM or sensor decoder, annotating a raw waveform all the way up to register names and field values.
Putting capture inside the debugger changes the order of investigation. Locating a communication fault used to mean reading serial logs first, adding code instrumentation next, and only then reaching for a logic analyzer; with both program execution and bus timing visible in the same session over one SWD connection, faults such as a non-responding I²C slave or mismatched SPI timing are resolved faster. The limit deserves stating: Nuvoton does not publish the sample rate or capture depth of this logic analysis function, so its role remains bus-level troubleshooting inside the debugger rather than replacing bench instruments sold on high sample rates and deep memory. Selection should be checked against the actual speed of the target bus.
I3C and CAN FD: Built for Automotive and Industrial Payloads
The two new bus interfaces are the part of this upgrade closest to concrete applications, and the step up in speed and frame length is well documented:
- I3C: the MIPI Alliance I3C white paper puts raw bit rate at 12.5 Mbps in baseline SDR mode at a 12.5 MHz clock, with HDR modes at 25, 27.5 and 39.5 Mbps and effective data rates up to roughly 33.3 Mbps after transaction control bytes are excluded, against a typical I²C ceiling of 3.4 Mbps in Hs mode. I3C also retains compatibility with legacy I²C devices and supports dynamic address assignment.
- CAN FD: TI's application note "Getting Started with the MCAN (CAN FD) Module" states that classic CAN tops out at 1 Mbps with an 8-byte payload per frame, while CAN FD raises the data phase to 5 Mbps (8 Mbps on some devices) and expands the payload to 64 bytes.
Once both speed and frame length step up, logs and breakpoints alone become insufficient: longer frames open a wider time window per transaction, and a faster data phase leaves less timing margin, so many faults are visible only in the waveform. Because the Nu-Link3-Pro also acts as a USB-to-serial data bridge over I²C, I3C, SPI, CAN FD and RS-485, and can analyze traffic on those interfaces, bridging, firmware upgrade and waveform capture happen within a single connection.
Production Floor: Scripted Offline Programming and Secure Flashing
Production capability is where the Nu-Link3-Pro separates most clearly from its predecessor, and where its move from engineering tool to production equipment is grounded:
- In-circuit programming: selectable SWD output levels of 1.8, 2.5, 3.3 and 5.0 V, drag-and-drop flash programming, and the ISP Programming Tool.
- Offline programming: press-to-start operation; an Automated Programmer header (control bus) for integration with automated test equipment; images stored on a USB flash drive, SD card or built-in SPI flash; power from Micro USB or from the target board through SWD.
- Scripted logic: built-in MicroPython, so a custom MAIN.py on a microSD card rewrites the entire offline programming flow without firmware changes, fitting complex automated test equipment and dedicated mass-production environments.
- Secure programming: the private key is generated inside the device and stored in a hardware key store, with a hardware encryption engine handling certificate issuance and encrypted programming so the key never leaves the device; Nuvoton states the capability can be customized to the target chip and application, with project assessment and technical support.
Within Nuvoton's NuDeveloper toolchain the path is visible end to end: Nu-Link adapters and NuMaker evaluation boards on the hardware side, NuEclipse IDE and BSPs on the software side, AI-assisted tools such as NuCodeGen and NuTRM, and NuML Studio and NuVoiceAI for models and voice (source: Nuvoton 2026 seminar material). The more complete the toolchain, the more "no tool change from development to volume production" becomes the default path — and the Nu-Link3-Pro is the node connecting its two ends.
HSY Perspective
The dividing line in this release is not 110 MHz; it is that a debugger has taken on production responsibility for keeping the private key inside the device. Three published details connect into one story. Security moves from the Nu-Link2-Pro's key and certificate handling to Secure Provisioning, where the key is generated in the device, held in a hardware key store and used by a hardware engine for certificate issuance and encrypted programming. The interface set gains I3C and CAN FD, the buses automotive and industrial designs are migrating to. The programming path hands flow logic back to customer scripts through built-in MicroPython. All three point the same way: a production line needs one unit that can verify buses, inject keys and follow a customer's own sequence, not three boxes each covering one segment. As CRA and automotive security requirements write key lifecycle into compliance checklists, whether a programming tool supports secure injection moves from an engineering detail to a gate on the project plan.
The boundary of that judgment matters. It holds where a customer genuinely has volume key injection or certificate issuance requirements, at a scale that warrants automated test equipment or control-bus integration. In small-volume work without security requirements, I3C and CAN FD decoding and six-channel waveforms still decide the purchase. Secure Provisioning is described as a service customized per chip and application and subject to project assessment, so its coverage across NuMicro parts should be read from an actual assessment, not assumed to be out-of-the-box across the family. Pricing and lead time are unpublished, and both feed straight into production tooling budgets and schedules.
The indicator worth tracking next is enquiry structure: if customers begin combining development debug and volume programming into a single enquiry, the integrated path has been accepted on the procurement side. If secure injection continues to arrive as a separate option late in a project, the value of this generation of tools will be realized considerably later.
Sources: Nuvoton Technology press release (15 October 2026, nuvoton.com); Nu-Link3-Pro product and features pages (nuvoton.com); Nuvoton Debugger and Programmer comparison page; Nuvoton 2026 seminar material "NuDeveloper Ecosystem" (TW6); sigrok.org protocol decoder list (131 decoders); MIPI Alliance "Introduction to MIPI I3C" white paper; TI application note "Getting Started with the MCAN (CAN FD) Module".
