diff --git a/doc/rpi3_jtag.md b/doc/rpi3_jtag.md
index 4c1d3f2..5332685 100644
--- a/doc/rpi3_jtag.md
+++ b/doc/rpi3_jtag.md
@@ -104,6 +104,10 @@ reset_config trst_only
 
 [Source](https://movr0.com/2016/09/02/use-raspberry-pi-23-as-a-jtagswd-adapter/)
 
+
+* @todo Find out about bcm2835gpio_speed_coeffs
+
+
 Target configuration: rpi3_target.cfg
 
 ```
@@ -136,6 +140,12 @@ $_TARGETNAME configure -event gdb-attach { halt }
 
 [Source #1](https://electronics.stackexchange.com/questions/249008/how-to-use-rpi-2-to-debug-rpi-model-b-via-jtag-with-openocd/419724#419724), [source #2](https://sysprogs.com/tutorials/preparing-raspberry-pi-for-jtag-debugging/), [source #3](http://openocd.org/doc/html/Reset-Configuration.html), [source #4](http://infocenter.arm.com/help/topic/com.arm.doc.faqs/ka3854.html)
 
+* @todo Check the expected tap id:
+> If an SoC provides a JTAG debug interface and contains any CoreSight debug components (including any Cortex processor) you should expect to see the standard JTAG IDCODE of a single CoreSight SWJ-DP as one TAP on the JTAG chain.
+
+* @todo JTAG gives 0x4ba0_0c77 instead of expected 0x07b7_617f
+
+
 ## Run OpenOCD, GDB and attach to target
 
 Need to verify if the following bug is still valid: