From c6afe12d19ae8ea4a214be2d6a1624c34287a301 Mon Sep 17 00:00:00 2001
From: rusefillc <48498823+rusefillc@users.noreply.github.com>
Date: Fri, 8 Oct 2021 00:51:02 -0400
Subject: [PATCH] Created Proteus F767 programming instructions (markdown)

---
 Proteus-F767-programming-instructions.md | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
 create mode 100644 Proteus-F767-programming-instructions.md

diff --git a/Proteus-F767-programming-instructions.md b/Proteus-F767-programming-instructions.md
new file mode 100644
index 00000000..f622daaf
--- /dev/null
+++ b/Proteus-F767-programming-instructions.md
@@ -0,0 +1,15 @@
+Too many of Proteus 0.6 with F767 are behaving strangely in terms of initial programming. Maybe we have a hardware design issue? Maybe we are missing something?
+
+Anyway looks like there is a working procedure.
+
+1) use STM32CubeProgrammer software https://www.st.com/en/development-tools/stm32cubeprog.html
+
+2) connect via USB while holding PROG button
+
+3) make sure you have "STM32 BOOTLOADER" driver not "STM Device in DFU Mode". If necessary update/install driver from C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\Drivers\DFU_Driver
+
+4) connect STM32CubeProgrammer via USB, follow https://github.com/rusefi/rusefi/wiki/HOWTO-nDBANK to reset nDBANK flag
+
+5) close STM32CubeProgrammer, unplug USB cable, plug USB cable, open STM32CubeProgrammer. STM32CubeProgrammer is finicky you really have to restart it between steps
+
+6) 
\ No newline at end of file