I'm using the Nulink Pro debugger (Nuvoton Nu-Link Debug Adapter) with the Kiel IDE . The Keil IDE has a debug printf to use with Keil's Ulink debugger (which we don't have). I'm currently using the Nu-Link debugger through the Keil IDE. Can I use the debug printf with my current setup.
The Nu-link debugger connects over the following pins: ICE_DAT, ICE_CLK, reset and power. So it doesn't have a SWO pin. So does that mean that the debug printf won't work with my setup.
The links you've attached are for cortex-m3. Our controller is a Nuvoton 120Le3bn which is a cortex M0. Hope that doesn't matter. I use the step debug with Keil and we connect the controller The debug printf.
Not sure how I'd know what core you're using.
Does the Cortex-M0 have an ITM unit? I don't think so, so you're going to have to push your debug data out a USART or something, and printf()/putchar() data out that channel by fixing the hosting via serial.c/retarget.c
www.arm.com/.../at_-_advanced_debug_of_cortex-m_systems.pdf "Trace (ETM, ITM, DWT) not available on Cortex-M0"
If your debug adapter is Segger's JLink (or "compatible"), you can use their Real Time Terminal (RTT), which use only two debug pin. RTT is applicable for all cores started from M0.
segger.com/jlink-real-time-terminal.html