The board specifics can than be seen in the output window. Select the board (if not done already) and hit the device capabilities button. We can now fire up Visual Studio and view the Device explorer window the board should be visible there as well. If the board doesn't show then a reset (Black button on board) should do it. Please set the frequency to match to what has been set in mcuconf.h (for the STM32F401RE it is 84MHz) and the Stimulus port to 0 and than hit start. Once these are connected and nanoFramework is flashed using the STM32 ST-LINK Utility the device should be visible in the Printf via SWO viewer function in the ST-LINK utility. USB D+ -> PA12 on CN10 (outer row 6th pin from top) USB D-> PA11 on CN10 (outer row 7th pin from top) I prepared a custom made a 4-wire jumper to USB cable by cutting off one end (Type A part) and figuring out the required D+, D-, 5V and GND. If it is chosen to activate LSE as this is a for more accurate clock for RTC, the board.h file needs to be adjusted accordingly to use 32768 frequency for LSE. This is reflected in the mcuconf.h in both nanoBooter and nanoCLR paths. Plus X2 is mounted so we do have an LSE as well. The board MB1136 C-02 is configured to use ST-LINK MCO as clock input for HSE so we have an HSE of 8 MHz. Further information on the Nucleo64 boards can be found in the user manual UM1724 on the ST side ( The board used here is of revision c as can be found on the board's lower backside sticker. The board can be purchased from various sources and should be about 20 euros. The board used in this community contribution is the NUCLEO64_F401RE board from ST.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |