From dcbcea67cd6af933fd5134210b13f18b133ee14f Mon Sep 17 00:00:00 2001
From: zwbrbr <40235756+zwbrbr@users.noreply.github.com>
Date: Wed, 22 Aug 2018 10:49:36 +0100
Subject: [PATCH] Basic top of page and DFU tip

---
 Board-Nucleo-F767ZI.md | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 Board-Nucleo-F767ZI.md

diff --git a/Board-Nucleo-F767ZI.md b/Board-Nucleo-F767ZI.md
new file mode 100644
index 0000000..75beb56
--- /dev/null
+++ b/Board-Nucleo-F767ZI.md
@@ -0,0 +1,22 @@
+Status "not officially supported but should be fully functional" as of 2018-08.  Pre-built DFU binaries are [available](https://micropython.org/download#other) for this board.
+
+# Pages elsewhere
+
+ * [mBed page](https://os.mbed.com/platforms/ST-Nucleo-F767ZI/)
+ * [ST's page for this Nucleo](https://www.st.com/content/st_com/en/products/evaluation-tools/product-evaluation-tools/mcu-eval-tools/stm32-mcu-eval-tools/stm32-mcu-nucleo/nucleo-f767zi.html)
+ * [ST's page for this MCU](https://www.st.com/en/microcontrollers/stm32f767zi.html)
+
+# Features
+
+ * STM32F767ZI (LQFP-144) at up to 216 MHz
+ * 2MiB flash, 512KiB RAM
+ * three user LEDs
+ * one user button
+ * USB OTG
+ * Ethernet port (probably not yet supported by uPy)
+
+# Flashing
+
+Probably requires newer OpenOCD than 0.9.0, which complained "Cannot identify target as a STM32 family" despite getting a device ID.
+
+To steer the target into DFU mode, pull `BOOT0` high (connect CN11 pin 7 to CN11 pin 16; see the mBed page for pretty diagrams) while plugging the STLink USB into the host.  Then use the usual DFU flashing described in the README.
\ No newline at end of file