F. St
3940116fca
Comment out DOLPHIN_DEED line, because it was causing the build to fail
|
2 年之前 | |
|---|---|---|
| icons | 3 年之前 | |
| model | 3 年之前 | |
| swd_scripts | 3 年之前 | |
| .gitignore | 3 年之前 | |
| LICENSE.txt | 3 年之前 | |
| README.md | 3 年之前 | |
| adi.c | 3 年之前 | |
| adi.h | 3 年之前 | |
| application.fam | 3 年之前 | |
| jep106.c | 3 年之前 | |
| jep106.h | 3 年之前 | |
| jep106.inc | 3 年之前 | |
| swd_probe_app.c | 2 年之前 | |
| swd_probe_app.h | 3 年之前 | |
| usb_uart.c | 3 年之前 | |
| usb_uart.h | 3 年之前 |
README.md
ARM SWD (Single Wire Debug) Probe
Modern microcontrollers have support for the two wire debug interface SWD, which makes wiring a lot simpler. When reverse engineering, finding these two pins is a los easier than with JTAG, where you had to wire up twice or more pins. However, finding the two pins is still a bit of work, which gets simplified even more with this application.
This application tries to detect a valid SWD response on the wires you have picked and beeps when you have found the correct pins, showing the detected ID register and, more important, the SWD pinout. It doesn't matter which two pins you choose, just pick any two from the GPIOs on the breakout header.
To achieve this, the application sends packets and scans the response on all pins and elaborates the pins within a few retries. Using some kind of bisect pattern reduces this number to a hand full of tries, yielding in a seemingly instant detection.
For the user it is as simple as a continuity tester - wire up your two test needles (or accupuncture needles), connect the obvious GND pin and probe all test pads. Now it depends on your bisect capabilities finding all pad combinations, how long it will take this time.
https://cdn.discordapp.com/attachments/954430078882816021/1071603366741938176/20230205_022641.mp4
Discussion thread: https://discord.com/channels/740930220399525928/1071712925171056690