diff --git a/Symbolic-Debugging-for-STM32.md b/Symbolic-Debugging-for-STM32.md
index da2440c..895ad2c 100644
--- a/Symbolic-Debugging-for-STM32.md
+++ b/Symbolic-Debugging-for-STM32.md
@@ -30,9 +30,8 @@ The Nucleo-F401RE board also has two "ST-LINK" jumpers that need to be removed t
 
 **Note:** I anchored the wires by weaving them through adjacent holes, when soldering to the pyboard so that the stress of moving the boards didn't wiggle the wire. The wire is at its most vulnerable point where it is soldered to the board.
 
-![Wiring of ST-Link to PYBV10](https://drive.google.com/file/d/0B6fVhttwRUumejBuRnFNSm5NSXc/view?usp=sharing)
-or 
-[Wiring of ST-Link to PYBV10](https://drive.google.com/file/d/0B6fVhttwRUumejBuRnFNSm5NSXc/view?pli=1)
+![pyBoard wired to a ST-LINK on a Nucleo-F401RE](http://forum.micropython.org/download/file.php?id=159)
+
 
 ##symbolic debugging 
 Symbolic debugging is useful for checking out the interface to hardware - single stepping through each line of code, and looking at the registers/variables. Symbolic debugging often relies on a toolchain that can be difficult to get right - so often its more pain to setup and debug the debugger than it is to use other methods.