6/6/2023 0 Comments Segger sam ice driver![]() ![]() Their tools are all multi-platform and their standalone debugger, Ozone, is amazing. I started using the J-Link adapters a few years ago on one project which already had them and have not looked back. I spent a lot of time avoiding J-Link because of the price and because I preferred to use open software and vendor tools. There is something to be said for a single unified interface to use with practically all the devices you work with. This frustrating environment instability opens the door to vendors such as Segger, who make their own JTAG/SWD adapters, provide excellent support and whose tools work with many different vendors. Let me tell you: nothing is more frustrating than finally getting an embedded system to exhibit a bug under a debug environment and something between the debugger software/ide (gdb, eclipse, etc.), OpenOCD, the vendor driver and the vendor adapter getting out of sync, dropping the debug connection and requiring a hardware restart to try again. I often have trouble with OpenOCD and vendor tools (mostly ST-Link, Olimex, OpenSDA, etc.), particularly with debugging. That being said, my experience with vendor tools is that they are substandard, quick and dirty tools. Using the vendor's recommended tool is usually the path of least resistance, as the vendor will support their adapter, their recommended software will work with their adapter and things should be documented reasonably well, making things as smooth as possible. While it's true that you can use practically anything to connect to the port and manipulate the SWD interface, most vendors will have their own "flavour" of adapter. The physical interface between the PC you're using to develop/debug and the JTAG/SWD port of the micro is the adapter. ARMs use either JTAG or SWD, and most common microcontroller ARM cores are the Cortex series, which are almost exclusively programmed and debugged over SWD.īoth JTAG and SWD are well defined, and most vendors describe how to enter and manipulate the Debug Access Port (DAP) which is how you usually access the internal buses, CPU, memories and peripherals.
0 Comments
Leave a Reply. |