Connect your MCU to ST-Link just like they have connected the Nucleo's MCU to it.Īs for boot configurations, there are three selectable options, easiest it to stick with the Main Flash and tie Boot0 to GND, but I do not know your requirements so it is up to you to choose. So I can recommend you to connect SWO as well, can be useful later. The Printf via SWO Viewer displays the printf data sent from the target through SWO. The additional SWO pin is used for debug purposes, you can access printed data with the printf function through this pin with ST-Link Utility. Overview The STM32 Nucleo-144 board provides an affordable and flexible way for users to try out new concepts and build prototypes with the STM32 microcontroller, choosing from the various combinations of performance, power consumption and features. Especially the part where the ST-Link is connected to the controller on the board.īy ST Microelectronics, SWCLK, SWDIO, NRST and SWO (and GND of course) are connected to the target MCU. The second thing I would recommend you is to open the STM32F411 Nucleo board's reference manual and look at the schematics. What else I'm missing here? Should I do anything with BOOT0 or BOOT1 pins?įirst of all, you are right, if your board has already got a supply voltage source you do not have to connect ST-Link's VDD pin. ![]() I've tested "almost" everything with oscilloscope and tester and everything seems okay. Here's the general pinout configuration of the MCU here: ![]() Please refer to this table I've taken from the official datasheet: Also I'm giving 3.3 V to VIN pin of MCU, means that I don't need to connect VDD (PIN 1 of stlink). Not sure if I should connect SWO pin as it's set as "reserved" (Why?).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |