2 ms·
Do you have much experience with gdb+openocd+<generic SWD/JTAG>? Aside from a couple chip vendor's IDEs (Analog Devices and Atmel, both at a previous employer)
by bacon_waffle 6y ago
Do you have much experience with gdb+openocd+<generic SWD/JTAG>?
Aside from a couple chip vendor's IDEs (Analog Devices and Atmel, both at a previous employer), I've always used the open source stack for embedded debugging and found it adequate. Just wondering what I'm missing out on?
While there are certainly some rough edges in the OSS stack, they've been no worse than the commercial solutions I've tried. And at least in principle, I can fix issues in the OSS tooling.
- ferruck 6y agoThis is a night/day comparison. With Trace32 and its scripting possibilities you can achieve things that GDB can only dream of. Access to the internals (registers, memory, etc.), flashing, altering at run time, watching, the list goes on. Many things can be done via GDB, too, but it's often not very ergonomic (for example write access to certain memory mapped registers). No hate here, I use GDB for "normal" debugging and love it, but for hardware debugging Trace32/Lauterbach is just a different world. Maybe the only thing to hate about Trace32 is its very clumsy UI. I'd rather use a TUI than their Motif/Qt based one.