Currently I use PIC32MX MCUs in my projects, but my new projects are going to have ATSAME5 MCUs onboard. On the PIC32MX I use a 5-pin interface to program and debug using a PICkit4 tool. The signals that I always used with PIC32MX are VCC, GND, MCLR/VPP, DATA-IO/PGD and CLOCK/PGC. For new projects I am going to use ATSAME5 MCUs, and I plan to keep using a 5-pin interface, by using VCC, GND, RESETn, SWDIO and SWCLK. I want to confirm if these group of 5 signals are really enough to program and debug the ATSAM MCUs, because it will be my first project with an ARM core.
Electronic – Migrating from PIC32MX to ATSAM MCU – SWD interface doubt
armmicrocontroller
Related Topic
- External crystal not working but internal clock worked normaly in PIC18F45K22
- Transfer variables through SWD with Segger J-Trace without using SWO interface
- Electronic – Hand-made interface to SWD to write flash of ARM chip
- Electronic – ST-Link debugger/programmer failed to find STM32L152 MCU on designed PCB
- Electronic – Getting fast performance from a STM32 MCU
- Electronic – OpenOCD child process termination: Wrong device detected
Best Answer
Yes you're right, since the SAM E5 family is ARM Cortex based, the 5 signals you mention are the one you need to program a target device in "Serial Wire" mode:
That's what I have on several designs and it works well (AT SAM and STM32).
But if you want extended debugging features you need to add some more signals. The many documentations about ARM Cortex programming interfaces might help you:
Extract from the ARM Keil documentation: