3 ms·
Yeah embedded debugging is an absolute PITA, even with OpenOCD + JTAG exposing a remote gdb server to the target it's just always been so fragile in my experien
by zen_1 4y ago
Yeah embedded debugging is an absolute PITA, even with OpenOCD + JTAG exposing a remote gdb server to the target it's just always been so fragile in my experience. Like reloading a changed executable causing gdb to segfault sometimes, and you need to restart every part of the debug chain (device being debugged, openocd, gdb) in order to get back to working on the problem you were originally trying to solve.
- 0x0203 4y agoI hadn't seen OpenOCD yet, so thanks for that. On the boards I'm currently playing with, while they technically have JTAG, it's pin muxed with pins used for the sd card. So I'd have to build a new u-boot to reconfigure the right pins, and get an adapter to break the right jtag pins out of the sd slot, and figure out booting from emmc or spi since I'm currently booting everything from the sd card... QEMU seemed much easier!
- zen_1 4y agoOpenOCD is a massive godsend for any kind of board bringup/embedded development. While I can't speak for your board specifically, if the pin assignment is software reconfigurable (and is reset to sd-card access on reboot!) and you're not using the SD card once your program is running, you could reconfigure the pins in software and then wait for a JTAG debugger to attach (by having an infinite loop you use openOCD to continue past). Of course if you can debug your issue using QEMU that's indeed much easier, thanks Fabrice!