No more libswd
That was a silly library, full of middleware and memory leaks. Debugging libswd was a good way to get familiar enough with SWD to write a replacement really quickly :P This still doesn't work reliably, it seems to have the same unsynchronization bug that the old code was having. But it's much smaller and easier to understand now!
Showing
- testjig/production/arm_debug.cpp 274 additions, 171 deletionstestjig/production/arm_debug.cpp
- testjig/production/arm_debug.h 42 additions, 26 deletionstestjig/production/arm_debug.h
- testjig/production/libswd.h 0 additions, 673 deletionstestjig/production/libswd.h
- testjig/production/libswd_bin.c 0 additions, 172 deletionstestjig/production/libswd_bin.c
- testjig/production/libswd_bitgen.c 0 additions, 84 deletionstestjig/production/libswd_bitgen.c
- testjig/production/libswd_bus.c 0 additions, 390 deletionstestjig/production/libswd_bus.c
- testjig/production/libswd_cmd.c 0 additions, 506 deletionstestjig/production/libswd_cmd.c
- testjig/production/libswd_cmdq.c 0 additions, 252 deletionstestjig/production/libswd_cmdq.c
- testjig/production/libswd_core.c 0 additions, 111 deletionstestjig/production/libswd_core.c
- testjig/production/libswd_dap.c 0 additions, 563 deletionstestjig/production/libswd_dap.c
- testjig/production/libswd_drv.c 0 additions, 287 deletionstestjig/production/libswd_drv.c
- testjig/production/libswd_error.c 0 additions, 248 deletionstestjig/production/libswd_error.c
- testjig/production/libswd_log.c 0 additions, 163 deletionstestjig/production/libswd_log.c
- testjig/production/production.ino 14 additions, 7 deletionstestjig/production/production.ino
Loading
Please register or sign in to comment