From 28a5d22cd49d9a467a44c878118b85b3348fe3c2 Mon Sep 17 00:00:00 2001 From: Dave Hylands Date: Wed, 28 Oct 2015 10:24:42 -0700 Subject: [PATCH] Updated Board STM32F745 Discovery (markdown) --- Board-STM32F745-Discovery.md | 28 +++++++++++++++++++++++++--- 1 file changed, 25 insertions(+), 3 deletions(-) diff --git a/Board-STM32F745-Discovery.md b/Board-STM32F745-Discovery.md index 95309a0..1a29bca 100644 --- a/Board-STM32F745-Discovery.md +++ b/Board-STM32F745-Discovery.md @@ -1,7 +1,7 @@ Cortex M7 STM32F746G -* Home - http://www.st.com/stm32f7-discovery +* [STM32F7 Discovery Home Page](http://www.st.com/stm32f7-discovery) * [STM32F746xx Datasheet](http://www.st.com/st-web-ui/static/active/en/resource/technical/document/data_brief/DM00037955.pdf) -* [STM32F74xxx Reference Manual] +* [STM32F74xxx Reference Manual](http://www.st.com/web/en/resource/technical/document/reference_manual/DM00124865.pdf) * [Board User Manual](http://www.st.com/st-web-ui/static/active/en/resource/technical/document/user_manual/DM00190424.pdf) ###Features### @@ -32,8 +32,30 @@ The board doesn't provide a convenient way to enter DFU mode. There are several DFU mode is available on the USB FS connector (CN13) * You can short the pads where R42 would be installed (it isn't installed by default) and press the reset button. You should now be able see the board when using ```dfu-util -l``` * I chose to install a switch between the MCU side of R42 and 3.3v (see picture below). -* You can install the initial micropython image using the STLINK interface, and then use pyb.bootloader() to enter DFU mode from the REPL. +* You can install the initial micropython image using the STLINK interface, and then use pyb.bootloader() to enter DFU mode from the REPL. See the [[Building st-flash|Building-st-flash]] page for some instructions on how to build st-flash. Here is a link to a photo of [my modified STM32F7 Disocvery Board](https://www.dropbox.com/s/bbypmt8tennczh7/STM32F7-Discovery.jpg?dl=0) The white wire connects to R42. CN13 has a USB cable plugged into it. The FTDI board is plugged into D0 (RX) and D1 (TX). The red wire connects to 3.3v on R39. + +###REPL### +UART1 from the STM32F7 is connected to the stlink MCU, and until USB-serial is working, the software is configured to have a REPL on UART1. The stlink MCU acts as a USB serial dongle. + +I use the following file (which I call 49-stm32.rules): +``` +# 0483:5740 - STM32F4/F7 Dsicovery in USB Serial Mode +ATTRS{idVendor}=="0483", ATTRS{idProduct}=="5740", ENV{ID_MM_DEVICE_IGNORE}="1" +ATTRS{idVendor}=="0483", ATTRS{idProduct}=="5740", ENV{MTP_NO_PROBE}="1" +SUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="5740", MODE:="0666" +KERNEL=="ttyACM*", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="5740", MODE:="0666" + +# 0483:df11 - STM32F4/F7 Discovery in DFU mode +SUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="df11", MODE:="0666" +``` +and install it using: +``` +sudo cp 49-stm32.rules /etc/udev/rules.d +sudo udevadm control --reload-rules +sudo udevadm trigger +``` +That covers off DFU mode and the USB-serial link from CN14 (labelled USB ST-LINK, mini B connector). CN13 (labelled USB_FS, micro B connector) goes directly to the F7. \ No newline at end of file