View NUCLEO-F042K6_8656361.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

october 2015 docid028406 rev 1 1/31 1 um1956 user manual stm32 nucleo-32 boards introduction the stm32 nucleo-32 board (nucleo-f031k6, nu cleo-f042k6, nucleo-f303k8, nucleo-l031k6) provides an affordable and flexible way for users to try out new concepts and build prototypes with stm32 microcontrolle rs, choosing from the various combinations of performance, power consumption and feat ures. the arduino nano connectivity support makes it easy to expand the functionality of the nucleo-32 open development platform with a wide choice of specialized shields. the stm32 nucleo-32 board does not require any separate probe as it integrates the st-link/v2-1 debugger/programmer. the nucleo-32 board comes with the stm32 comprehensive software hal library together with various packaged software examples, as well as direct access to mbed online resources at http://mbed.org. figure 1. stm32 nucleo-32 board 1. picture not contractual www.st.com
contents um1956 2/31 docid028406 rev 1 contents 1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 2 product marking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3 ordering information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 4 conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5 quick start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5.1 getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5.2 system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 6 hardware layout and configurat ion . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 6.1 embedded st-link/v2-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 6.1.1 drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 6.1.2 st-link/v2-1 firmware upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 6.2 power supply and power selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 6.2.1 power supply input from usb connector . . . . . . . . . . . . . . . . . . . . . . . . 15 6.2.2 external power supply inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 vin or +5v power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 +3v3 power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17 6.2.3 external power supply output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 6.3 leds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 6.4 push button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 6.5 jp1 (idd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6.6 osc clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6.7 usart virtual communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 6.8 solder bridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 6.9 arduino nano connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 7 electrical schematics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 appendix a mechanical dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
docid028406 rev 1 3/31 um1956 contents 3 8 revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
list of tables um1956 4/31 docid028406 rev 1 list of tables table 1. ordering information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 table 2. on/off conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 table 3. sb1 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 table 4. external power sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 table 5. osc clock configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 table 6. virtual communication configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 table 7. solder bridges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 table 8. arduino nano connectors on nucleo-f031k6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 table 9. arduino nano connectors on NUCLEO-F042K6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 table 10. arduino nano connectors on nucleo-f303k8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 table 11. arduino nano connectors on nucleo-l031k6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 table 12. document revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
docid028406 rev 1 5/31 um1956 list of figures 5 list of figures figure 1. stm32 nucleo-32 board. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 figure 2. hardware block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 figure 3. top layout view of the nucleo-32 board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 figure 4. bottom layout view of the nucleo-32 board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 figure 5. usb composite device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 figure 6. nucleo-f031k6, nucleo-f 042k6, nucleo-f303k8 pin assignment . . . . . . . . . . . . 25 figure 7. nucleo-l031k6 pin assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 figure 8. nucleo-32 board top view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 figure 9. mcu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 figure 10. st-link/v2-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 figure 11. nucleo-32 board mechanical dimensions in millim eter. . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
features um1956 6/31 docid028406 rev 1 1 features ? stm32 microcontrollers in 32-pin packages ? extension with arduino nano connectivity ? mbed-enabled (http://mbed.org) ? on-board st-link/v2-1 debugger/programmer ? usb re-enumeration capabilit y, three different interf aces supported on usb: ? virtual com port ? mass storage ? debug port ? flexible board power supply: ? usb vbus ? external source ? three leds: ? usb communication (ld1), powe r led (ld2), user led (ld3) ? reset push button ? supported by wide choice of integrated development environments (ides) including iar ? , keil ? , gcc-based ides (ac6: sw4stm32,...)
docid028406 rev 1 7/31 um1956 product marking 30 2 product marking evaluation tools marked as "es" or "e" are not yet qualified and therefore they are not ready to be used as reference design or in production. any consequences deriving from such usage will not be at st charge. in no event, st will be liable for any customer usage of these engineering sample tools as reference design or in production. "e" or "es" marking examples of location: ? on the targeted stm32 that is soldered on the board (for illu stration of stm32 marking, refer to the section ?package characte ristics? of the stm32 datasheet at www.st.com ). ? next to the evaluation tool ordering part number, that is stuck or silk-screen printed on the board.
ordering information um1956 8/31 docid028406 rev 1 3 ordering information the order codes and the respective ta rgeted stm32 are listed in the below table 1 . the meaning of nucleo-txxxky co dification is as follows: ? txxx describes the stm32 pr oduct line (t for f or l) ? k describes the pin count (k for 32 pins) ? y describes the code size (8 for 64k, 6 for 32k) the last six characters (e.g.: l031k6) of this order code, are printed on a sticker placed at the top or bottom side of the board. table 1. ordering information target stm32 order code stm32f031k6t6 nucleo-f031k6 stm32f042k6t6 NUCLEO-F042K6 stm32f303k8t6 nucleo-f303k8 stm32l031k6t6 nucleo-l031k6
docid028406 rev 1 9/31 um1956 conventions 30 4 conventions table 2 provides the conventions used for the on and off settings in the present document. in this document the reference is ?stm32 nucleo-32 board? for all information that is common to all sale types. table 2. on/off conventions convention definition jumper jpx on jumper fitted jumper jpx off jumper not fitted solder bridge sbx on sbx connections closed by solder or 0 ohm resistor solder bridge sbx off sbx connections left open
quick start um1956 10/31 docid028406 rev 1 5 quick start the stm32 nucleo-32 board is a low-cost and easy-to-use development kit used to quickly evaluate and start a development with an stm32 microcontroller in lqfp32 or ufqfpn32 package. before installing and using the product, acce pt the evaluation prod uct license agreement that can be found at www.st.com/epla. for more information on the stm32 nucleo-32 board and to access the demonstration software, visit the www.st.com/stm32nucleo webpage. 5.1 getting started follow the sequence below, to configure the stm32 nucleo-32 board and launch the demonstration software: ? check solder bridge position on the board, sb1 off, sb14 on (internal regulator), jp1 on (idd) selected. ? for a correct identification of all device interfaces from the host pc and before connecting the board, install the nucleo usb driver, available at www.st.com/stm32nucleo. ? connect the nucleo-32 board to a pc with a usb cable ?type a to micro-b? through usb connector cn1 to power the board. the red led ld2 (pwr) and ld1 (com) light up and green led ld3 blinks. ? remove the jumper placed between d2 (cn3 pin 5) and gnd (cn3 pin 4). ? observe how the blinking frequency of the green led ld3 changes, when the jumper is in place or when it is removed. ? the demonstration software and several software examples on how to use the nucleo- 32 board features, are available at www.st.com/stm32nucleo webpage. ? develop your own application using available examples. 5.2 system requirements ? windows (xp, 7, 8) ? usb type a to micro-b usb cable
docid028406 rev 1 11/31 um1956 hardware layout and configuration 30 6 hardware layout and configuration the nucleo-32 board is based on a 32-pin stm32 microcontroller in lqfp or ufqfpn package. figure 2 illustrates the connections be tween the stm32 and its per ipherals (st-link/v2-1, push button, led, and arduino nano connectors). figure 3: top layout view of the nucleo-32 board and figure 4: bottom layout view of the nucleo-32 board show the location of these features on the nucleo-32 board. figure 2. hardware block diagram 06y9 (pehgghg 67/,1.9 670 0lfurfrqwuroohu 5(6(7 0lfur 86% ,2 ,2 % 567 $ugxlqr1dqr frqqhfwru /(' /' $ugxlqr1dqr frqqhfwru
hardware layout and configuration um1956 12/31 docid028406 rev 1 figure 3. top layout view of the nucleo-32 board u2 stm32 microcontroller cn1 st-link micro b usb connector ld1 (red/green led) com ld2 ( red led ) power b1 reset button ld3 ( green led ) cn2 st-link swd connector (reserved) sb1 power confi g uration sb2 connect vcp tx to st-link sb3 connect vcp rx to st-link sb4 connect pf0/pc14 to mco sb6 connect pf0/pc14 to d8 sb5 co nn ect pf 0/ p c 14 to x1 sb7 connect pf1/pc15 to x1 sb8 connect pf1/pc15 to d7
docid028406 rev 1 13/31 um1956 hardware layout and configuration 30 figure 4. bottom layout view of the nucleo-32 board 6.1 embedded st-link/v2-1 the st-link/v2-1 programming and debugging to ol is integrated in the nucleo-32 board. the st-link/v2-1 makes the nucleo-32 board mbed enabled. the embedded st-link/v2-1 supports only the swd for stm32 devices. for information about debugging and programming features refer to: st-link/v2 in-circuit debugger/programmer for stm8 and stm32 (um1075 user manual), which describes in detail all the st-link/v2 features. the new features supported by st-l ink/v2-1 versus st-link/v2 are: ? usb software re-enumeration ? virtual com port interface on usb ? mass storage interface on usb ? usb power management request for more than 100ma power on usb cn4 arduino nano connector cn3 arduino nano connector jp1 idd m easu r e m e n t sb14 3.3v regulator output sb18 connect d4 to a4 sb16 connect d5 to a5 sb11 connect 670 pin 16 to gnd sb15 connect d13 to ld3 sb17 connect mco to pa0 sb10 connect vdd to 670 pin 5 sb13 connect gnd to 670 pin 32 sb12 connect boot0 to gnd sb9 st-link reset
hardware layout and configuration um1956 14/31 docid028406 rev 1 the features not supported on st-link/v2-1 are: ? swim interface ? minimum supported application voltage limited to 3v known limitation: ? activating the readout protection on the stm32 target, prevents the target application from running afterwards. the target readout protection must be kept disabled on st- link/v2-1 boards. the embedded st-link/v2-1 is directly connec ted to the swd port of the target stm32. 6.1.1 drivers the st-link/v2-1 requires a dedicated usb driver, which, for windows xp, 7 and 8, can be found at www.st.com . in case the stm32 nucleo board is connected to the pc before the driver is installed, some nucleo interfaces may be declared as ?unknown? in the pc device manager. in this case the user must install the driver files (refer to figure 5 ) and from the device manager update the driver of the connected device. note: prefer using the ?usb composite device? handle for a full recovery. figure 5. usb composite device 6.1.2 st-link/v2-1 firmware upgrade the st-link/v2-1 embeds a firmware upgrade mechanism for in-situ upgrade through the usb port. as the firmware may evolve during th e life time of the st-link/v2-1 product (for example new functionalitie s added, bug fixes, suppo rt for new microcontro ller families), it is recommended to visit www.st.com before starting to use the stm32 nucleo-32 board and periodically, to stay up-to-date wi th the latest fi rmware version.
docid028406 rev 1 15/31 um1956 hardware layout and configuration 30 6.2 power supply and power selection the power supply is provided either by the host pc through the usb cable, or by an external source: vin (7v-12v), +5v (5v) or +3v3 power supply pins on cn4. in case vin, +5v or +3v3 is used to power the nucleo-32 boa rd, this power source must comply with the standard en-60950-1: 2006+a11/2009, and must be safety extra low voltage (selv) with limited power capability. in case the power supply is +3v3, the st-link is not powered and cannot be used. 6.2.1 power supply input from usb connector the nucleo-32 board and shield board can be powered from the st-link usb connector cn1. note that only the st-link part is po wer supplied before the usb enumeration, as host pc only provides 100 ma to the boards at that time. during the usb enumeration, the nucleo-32 board requires 300 ma of current to the host pc. if the host is able to provide the required power, the targeted stm32 microcontroller is powered and the red led ld2 is turned on, thus the nucleo-32 board and its shield can consume a maximum of 300 ma current and not more. if the host is not able to provide the required current, the targeted stm32 microcontroller and the shield board are not power supplied. as a consequence the red led ld2 stays turned off. in such case it is mandatory to use an external power supply as explained in the next section 6.2.2: external power supply inputs . sb1 is configured according to the maximum cu rrent consumption of the board. sb1 can be set on to inform the host pc that the ma ximum current consumpt ion does not exceed 100 ma (even when arduino nano shield is plugged). in such condition usb enumeration will always succeed since no more than 100 ma is requested to th e host pc. possible configurations of sb1 are summarized in table 3 . warning: if the maximum current consumption of the nucleo-32 board and its shield board exceed 300 ma, it is mandatory to power the nucleo-32 board, using an external power supply connected to vin, +5v or +3v3. note: in case the board is powered by a usb char ger, there is no usb enumeration, so the led ld2 remains set to off permanently and the tar get stm32 is not powered. in this specific case the sb1 must be set on, to allow the target stm32 to be powered anyway. table 3. sb1 configuration solder bridge state power supply allowed current sb1 off (default) usb power through cn1 300ma max sb1 on 100ma max sb1 (on/off) vin, +3v3 or +5v power for current limitation refer to ta ble 4
hardware layout and configuration um1956 16/31 docid028406 rev 1 6.2.2 external power supply inputs the nucleo-32 board and its shields boards can be powered in three different ways from an external power supply, depending on the voltage used. the three power sources are summarized in the ta b l e 4 . vin or +5v power supply when powered from vin or +5v, it is still possible to use st-link for communication for programming or debugging only, but it is mand atory to power the boar d first, using vin or +5v, then to connect the usb cable to the pc. by this wa y the enumeration will succeed anyway, thanks to the external power source. the following power sequence procedure must be respected: 1. check that sb1 is off 2. connect the external power source to vin or +5v 3. power on the external power supply 7v< vin < 12v to vin, or 5v for +5v 4. check red led ld2 is turned on 5. connect the pc to usb connector cn1 if this order is not respected, the board may be powered by vbus first, then by vin or +5v, as the following risks may be encountered: 1. if more than 300 ma current is needed by the board, the pc may be damaged or current supply can be limited by pc. as a consequence the board is not powered correctly. 2. 300 ma is requested at enumeration (since sb1 must be off) so there is risk that request is rejected and enumeration does no t succeed if the pc cannot provide such current. consequently the board is not power supplied (led ld2 remains off). table 4. external power sources input power name connector pin voltage range max current limitation vin cn4 pin 1 7v to 12v 800ma from 7v to 12v only and input current capability is linked to input voltage: 800ma input current when vin=7v 450ma input current when 7vvin>9v less than 300ma input current when vin>10v +5v cn4 pin 4 4.75v to 5.25v 500ma st-link not powered +3v3 cn4 pin 14 3v to 3.6v - st-link not powered and sb14 and sb9 must be off.
docid028406 rev 1 17/31 um1956 hardware layout and configuration 30 +3v3 power supply using the +3v3 (cn4 pin 14) directly as power input, can be interest ing, for instance, in case the 3.3v is provided by a shield board. in this case the st-link is not powered, thus programming and debug features are not available. when the board is powered by +3v3 (cn4 pin 14), the solder bridge sb14 and sb9 (nrst) must be off. 6.2.3 external pow er supply output when powered by usb or vin, the +5v (cn4 pin 4) can be used as output power supply for an arduino nano shield. in this case, the maximum current of the power source specified in table 4: external power sources must be respected. the +3.3v (cn4 pin 14) can be used also as power supply output. the current is limited by the maximum current capa bility of the regulato r u3 (500 ma max). 6.3 leds the tricolor led (green, orange, red) ld1 (com) provides information about st-link communication status. ld1 default color is red. ld1 turns to green to indicate that communication is in progress between the pc and the st-link/v2-1, with the following setup: ? slow blinking red/off: at powe r-on before usb initialization ? fast blinking red/off: after the first correct communication between pc and st- link/v2-1 (enumeration) ? red on: when initialization between pc and st-link/v2-1 is completed ? green on: after a successful target communication initialization ? blinking red/green: during communication with target ? green on: communication finished and successful ? orange on: communication failure user ld3: the green led is a user led connected to arduino nano signal d13 corresponding to stm32 i/o pb3 (pin 26). refer to table 8 , ta b l e 9 and table 10 for concerned stm32: ? when the i/o is high value, the led is on ? when the i/o is low, the led is off pwr ld2: the red led indicates that the stm32 part is powered and +5v power is available. 6.4 push button b1 reset: the push bu tton is connected to nrst, and it is used to reset the stm32.
hardware layout and configuration um1956 18/31 docid028406 rev 1 6.5 jp1 (idd) jp1, labeled idd, is used to measure the stm32 microcontroller consumption by removing the jumper and connecting an ammeter. ? jp1 on: stm32 is powered (default). ? jp1 off: an ammeter must be connected to measure stm32 current. if there is no ammeter, stm32 is not powered. 6.6 osc clock u2 pin 2 and pin 3 can be used as osc clock input or can be used as arduino nano d8 and d7 gpio. there are four ways to configure the pins corresponding to different stm32 mcus and clock usage (refer to table 5 ). boards with stm32lxxx are delivered with 32.7 68 khz crystal (x1). associated capacitors and solder bridges (c12, c13, sb4 to sb8) are configured to support lse by default. boards with stm32fxxx are delivered wit hout crystal (x1). associated capacitors (c12,c13) are not populated and sb4 to sb8 are configured to support hsi by default. 6.7 usart virtual communication thanks to sb2 and sb3, the usart interface of stm32 available on pa2 (tx) and pa15 (rx), can be connected to st-link/v2-1. when u sart is not used it is possible to use pa2 as arduino nano a7. refer to table 6 . table 5. osc clock configurations solder bridge stm32 clock configuration sb4 sb17 sb6 sb8 sb5 and sb7 on off off on off stm32fxxx mco from st-link connected to oscin (pf0) (1) 1. in applications, where vcp is used for commu nication at speed higher than 9600 bauds, it may be needed to use this solder bridge configuration, to use 8mhz clock (mco from st-link) to get a more precise frequency. off off on on off hsi configuration (default configuration) off on off off off stm32lxxx mco from st-link connected to ckin (pa0) (1) off off off off on 32k lse mounted on x1 (default configuration) off off on on/off off all arduino nano d7 connected to pf0 / pc14 off off on/off on off arduino nano d8 connected to pf1 / pc15
docid028406 rev 1 19/31 um1956 hardware layout and configuration 30 6.8 solder bridges table 6. virtual communication configuration bridge state (1) 1. the default configuration is reported in bold style. description sb2 off pa2 is connected to cn4 pin 5 as arduino nano analog input a7 and disconnected from st-link usart. on pa2 is connected to st-link as virtual com tx (default). sb3 off pa15 is not connected. on pa15 is connected to st-link as virtual com rx (default). table 7. solder bridges bridge state (1) description sb10 (vref+) on vref+ on stm32 is connected to vdd. off vref+ on stm32 is not connected to vdd and is provided by pin 13 of cn4. sb15 (ld3-led) on green user led ld3 is connected to d13 of arduino nano signal. off green user led ld3 is not connected. sb9 (nrst) on the nrst signal of st-link is connected to the nrst pin of the stm32. off the nrst signal of st-link is not connected to the nrst pin of the stm32, when used external power (+3v3, +5v) as power supply. sb11(pb2/vss) on pin 16 of stm32 (u2) is connected to vss. off pin 16 of stm32 (u2) is not connected to vss, and used as gpio pb2 for stm32f031. sb13(pb8/vss) on pin 32 of stm32 (u2) is connected to vss. off pin 32 of stm32 (u2) is not connected to vss, and used as gpio pb8 for stm32f031. sb12(pb8 /boot0) on pin 31 of stm32 (u2) is connected to gnd via 10k pull-down and used as boot0. off pin 16 of stm32 (u2) is not connected and is gpio pb8 for stm32f042. sb16 on stm32 pb6 is connected to cn4 pin 7 for i2c sda support on arduino nano a5. in such case stm32 pb6 does not support arduino nano d5 and pa6 must configured as input floating. off cn4 pin 7 is used as arduino nano analog input a5 without i2c support and cn3 pin 8 is available as arduino nano d5.
hardware layout and configuration um1956 20/31 docid028406 rev 1 6.9 arduino nano connectors cn3 and cn4 are male connectors compatible with arduino nano standard. most shields designed for arduino nano can fit to the stm32 nucleo-32 board. caution: the i/os of stm32 are 3.3 v compatible instead of 5 v for arduino nano. table 8 , table 9 , table 10 and table 11 show the pin assignments of each stm32 on arduino nano connectors. figure 6 and figure 7 show arduino nano connectors assignment for nucleo-f031k6, NUCLEO-F042K6, nucleo-f303k8 and nucleo-l031k6. sb18 on stm32 pb7 is connected to cn4 pin 8 for i2c scl support on arduino nano a4. in such case stm32 pb7 does not support arduino nano d4 and pa5 must be configured as input floating. off cn4 pin 8 is used as arduino nano analog input a4 without i2c support and cn3 pin 7 is available as arduino nano d4. 1. the default configuration is reported in bold style. table 7. solder bridges (continued) bridge state (1) description table 8. arduino nano connectors on nucleo-f031k6 connector pin number pin name stm32 pin function left connector cn3 1 d1 pa9 usart1_tx (1) 2 d0 pa10 usart1_rx (1) 3 reset nrst reset 4 gnd - ground 5d2pa12 - 6 d3 pb0 tim3_ch3 7d4 (5) pb7 - 8d5 (5) pb6 tim16_ch1n (2) 9 d6 pb1 tim14_ch1 10 d7 (3) pf0 - 11 d8 (3) pf1 - 12 d9 pa8 tim1_ch1 13 d10 pa11 spi_cs (4) || tim1_ch4 14 d11 pb5 spi1_mosi || tim3_ch2 15 d12 pb4 spi1_miso right connector cn4 1 vin - power input
docid028406 rev 1 21/31 um1956 hardware layout and configuration 30 cn4 2 gnd - ground 3 reset nrst reset 4 +5v - 5v input/output 5 a7 pa2 adc_in2 6 a6 pa7 adc_in7 7a5 (5) pa6 adc_in6 || i2c1_scl 8a4 (5) pa5 adc_in5 || i2c1_sda 9 a3 pa4 adc_in4 10 a2 pa3 adc_in3 11 a1 pa1 adc_in1 12 a0 pa0 adc_in0 13 aref - avdd 14 +3v3 - 3.3v input/output 15 d13 pb3 spi1_sck 1. only one usart is available and it is shared between arduino nano and vcp. the selection is done by remapping (no need to change the hardware configuration). 2. d5 pwm on inverted channel timer 16. 3. d7/d8 shared with osc_in/osc_out. 4. spi_cs is made by gpio. 5. limitations on a4 and a5, d4 and d5 related to i2c configuration are explained in section 6.8: solder bridges according to sb16/sb18 setting. table 9. arduino nano connectors on NUCLEO-F042K6 connector pin number pin name stm32 pin function left connector cn3 1d1pa9 usart1_tx 2 d0 pa10 usart1_rx 3 reset nrst reset 4 gnd - ground 5d2pa12 - 6 d3 pb0 tim3_ch3 7d4 (1) pb7 - 8d5 (1) pb6 tim16_ch1n (2) table 8. arduino nano connectors on nucleo-f031k6 (continued) connector pin number pin name stm32 pin function
hardware layout and configuration um1956 22/31 docid028406 rev 1 cn3 9 d6 pb1 tim14_ch1 10 d7 (3) pf0 - 11 d8 (3) pf1 - 12 d9 pa8 tim1_ch1 13 d10 pa11 spi_cs (4) || tim1_ch4 14 d11 pb5 spi1_mosi || tim3_ch2 15 d12 pb4 spi1_miso right connector cn4 1 vin - power input 2 gnd - ground 3 reset nrst reset 4 +5v - 5v input/output 5a7pa2 adc_in2 (5) 6 a6 pa7 adc_in7 7a5 (1) pa6 adc_in6 || i2c1_scl 8a4 (1) pa5 adc_in5 || i2c1_sda 9 a3 pa4 adc_in4 10 a2 pa3 adc_in3 11 a1 pa1 adc_in1 12 a0 pa0 adc_in0 13 aref - avdd 14 +3v3 - 3.3v input/output 15 d13 pb3 spi1_sck 1. limitations on a4 and a5, d4 and d5 related to i2c configuration are explained in section 6.8: solder bridges according to sb16/sb18 setting. 2. d5 pwm on inverted channel timer 16. 3. d7/d8 shared with osc_in/osc_out. 4. spi_cs is made by gpio. 5. a7 exclusive with vcp_tx. table 9. arduino nano connectors on NUCLEO-F042K6 (continued) connector pin number pin name stm32 pin function
docid028406 rev 1 23/31 um1956 hardware layout and configuration 30 table 10. arduino nano c onnectors on nucleo-f303k8 connector pin number pin name stm32 pin function left connector cn3 1 d1 pa9 usart1_tx 2 d0 pa10 usart1_rx 3 reset nrst reset 4 gnd - ground 5d2pa12 - 6 d3 pb0 tim3_ch3 7d4 (1) 1. limitations on a4 and a5, d4 and d5 related to i2c configuration are explained in section 6.8: solder bridges according to sb16/sb18 setting. pb7 - 8d5 (1) pb6 tim16_ch1n (2) 2. d5 pwm on inverted channel timer 16. 9 d6 pb1 tim3_ch4 10 d7 (3) 3. d7/d8 shared with osc_in/osc_out. pf0 - 11 d8 (3) pf1 - 12 d9 pa8 tim1_ch1 13 d10 pa11 spi_cs (4) || tim1_ch4 4. spi_cs is made by gpio. 14 d11 pb5 spi1_mosi || tim17_ch1 15 d12 pb4 spi1_miso right connector cn4 1 vin - power input 2 gnd - ground 3 reset nrst reset 4 +5v - 5v input/output 5 a7 pa2 adc1_in3 (5) 5. a7 exclusive with vcp_tx. 6 a6 pa7 adc2_in4 7a5 (1) pa6 adc2_in3 || i2c1_scl 8a4 (1) pa5 adc2_in2 || i2c1_sda 9 a3 pa4 adc2_in1 10 a2 pa3 adc1_in4 11 a1 pa1 adc1_in2 12 a0 pa0 adc1_in1 13 aref - avdd 14 +3v3 - 3.3v input/output 15 d13 pb3 spi1_sck
hardware layout and configuration um1956 24/31 docid028406 rev 1 table 11. arduino nano connectors on nucleo-l031k6 connector pin number pin name stm32 pin function left connector cn3 1 d1 pa9 usart2_tx (1) 1. only one usart is available and it is shared between arduino nano and vcp. the selection is done by remapping (no hardware configuration to change). 2 d0 pa10 usart2_rx (1) 3 reset nrst reset 4 gnd - ground 5d2pa12 - 6 d3 pb0 tim2_ch3 7d4 (2) 2. limitations on a4 and a5, d4 and d5 related to i2c configuration are explained in section 6.8: solder bridges according to sb16/sb18 setting. pb7 - 8d5 (2) pb6 tim21_ch1 9 d6 pb1 tim2_ch4 10 d7 (3) 3. d7/d8 shared with osc32_in/osc32_out. pc14 - 11 d8 (3) pc15 - 12 d9 pa8 tim2_ch1 13 d10 pa11 spi_cs (4) || tim21_ch2 4. spi_cs is made by gpio. 14 d11 pb5 spi1_mosi || tim22_ch2 15 d12 pb4 spi1_miso right connector cn4 1 vin - power input 2 gnd - ground 3 reset nrst reset 4 +5v - 5v input/output 5 a7 pa2 adc_in2 (5) 5. pa2 exclusive with vcp_tx. 6 a6 pa7 adc_in7 7a5 (2) pa6 adc_in6 || i2c1_scl 8a4 (2) pa5 adc_in5 || i2c1_sda 9 a3 pa4 adc_in4 10 a2 pa3 adc_in3 11 a1 pa1 adc_in1 cn4 12 a0 pa0 adc_in0 13 aref - avdd 14 +3v3 - 3.3v input/output 15 d13 pb3 spi1_sck
docid028406 rev 1 25/31 um1956 hardware layout and configuration 30 figure 6. nucleo-f031k6, nucleo-f04 2k6, nucleo-f303k 8 pin assignment figure 7. nucleo-l03 1k6 pin assignment 06y9 9,1 *1' 1567 9 3$ 3$ 3$ 3$ 3$ 3$ 3$ 3$ $5() 9 3% 3$ 3$ 1567 *1' 3$ 3% 3% 3% 3% 3) 3) 3$ 3$ 3% 3% ' ' 1567 *1' ' ' ' ' ' ' ' ' ' ' ' 9,1 *1' 1567 9 $ $ $ $ $ $ $ $ $5() 9 ' &1 &1 $ugxlqr 18&/(2)[[[.[ 06y9 3$ 3$ 1567 *1' 3$ 3% 3% 3% 3% 3& 3& 3$ 3$ 3% 3% 9,1 *1' 1567 9 3$ 3$ 3$ 3$ 3$ 3$ 3$ 3$ $5() 9 3% 18&/(2/[[[.[ ' ' 1567 *1' ' ' ' ' ' ' ' ' ' ' ' 9,1 *1' 1567 9 $ $ $ $ $ $ $ $ $5() 9 ' &1 &1 $ugxlqr
electrical schematics um1956 26/31 docid028406 rev 1 7 electrical schematics figure 8. nucleo-32 board top view 13 top mb1180 c.2 10/12/2015 title: size: reference: date: sheet: of a4 revision: nucleo32 project: rev b: sb14 changed to jp1 jumper for easy idd measurement, and enlarge board length; cn1 usb pn changed to micro-b for device. rev c: add sb18/sb16 for connecting d4/d5 to a4/a5 rev c.2: correct silkscreen d7/d8 on sb6 and sb8 mco vcp_tx swclk swdio vcp_rx nrst u_mcu_32 mcu_32.schdoc tms tck mco nrst stlk_rx stlk_tx swo u_st_link_v2-1 st_link_v2-1.schdoc
um1956 electrical schematics docid028406 rev 1 27/31 figure 9. mcu 23 mcu mb1180 c.2 10/12/2015 title: size: reference: date: sheet: of a4 revision: nucleo32 project: c23 100nf c13 4.3pf c12 4.3pf c7 100nf c11 100nf r21 10k pa4 pa5 pa6 pa7 pa11 pa12 pa9 pa10 pa0 pa1 pa15 pa3 pa13 pa14 pa2 pa8 pb5 pb6 pb7 pb1 pb3 pb0 pb4 a0 a1 a3 d3 a2 a7 a5 a6 a4 d4 mco vcp_rx vcp_tx vdd l1 bead swclk swdio pf0 pf1 /pc14 /pc15 avdd c24 100nf vdd sb5 sb7 sb13 sb8 sb10 sb6 d0 d11 d13 d12 d9 d1 d5 sb11 pf0/pc14 2 pf1/pc15 3 pa0 6 pa1 7 pa2 8 pa3 9 pa4 10 pa5 11 pa6 12 pa7 13 pb0 14 pb1/npor 15 pb2/vss2 16 pa8 18 pa9 19 pa10 20 pa11 21 pa12 22 pa13 23 pa14 24 pa15 25 pb4 27 pb5 28 pb6 29 pb7 30 pb8/vss3 32 nrst 4 vdda/vref+ 5 vdd2/vdd_usb 17 pb3 26 boot0/pb8/ph3 31 vdd3 1 u2 mcu_lqfp32/qfn32 d10 d2 d6 d8 d7 sb12 boot0 avdd +3v3 +5v a0 a1 a2 a3 a4 a5 d0 d1 d2 d4 d3 d5 d6 d7 d8 d9 d10 nrst vin d13 d12 d11 arduino connector 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 cn3 header 15x1_male 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 cn4 header 15x1_male a6 a7 nrst pa0 pa1 pa2 pa3 pa4 pa5 pa6 pa7 pa8 pa9 pa10 pa11 pa12 pb0 pb1 pb3 pb4 pb5 pb6 pb7 avdd aref 1 2 ld3 green r23 510 sb15 pf0 pf1 extension connectors vin c22 10uf(25v) c25 10uf e5v d3 stps2l30a +3v3 c9 1uf_x5r_0603 c8 100nf c10 100nf +5v vdd ld2 red r22 1k c14 1uf_x5r_0603 e5v d4 bat60jfilm u5v_st_link nrst nrst b1 kss221g x1 nx3215sa-32.768k-exs00a-mu00525 closed for l021, l031,l433 c 1 3 4 . 3p f s b5 s b7 x 1 nx3215 sa -32.768k-ex s0 0 open for f042,f031,f303 sb14 sb4 vin 3 vout 2 1 tab 4 u6 ld1117s50tr en 1 gnd 2 vo 4 nc 5 gnd 0 vi 6 pg 3 u3 ld39050pu33r vo sb17 jp1 ph127h10102jng-2/3/1.5 sb16 sb18 pb6 pb7
electrical schematics um1956 28/31 docid028406 rev 1 figure 10. st-link/v2-1 33 stlink/v2-1 mb1180 c.2 10/12/2015 title: size: reference: date: sheet: of a4 revision: nucleo32 project: 1 2 x2 nx3225gd 8mhz exs00a-cg04874 usb_dm usb_dp stm_rst t_jtck t_jtck t_jtdo t_jtdi t_jtms stm_jtms stm_jtck osc_in osc_out t_nrst ain_1 usb st-link u5v com pwr board ident: pc13=0 t_jtck t_jtms swclk swdio t_swdio_in led_stlink led_stlink tms tck tck/swclk tms/swdio mco mco t_jrst nrst t_nrst stlink_rx sb3 sb2 stlk_rx stlk_tx stlink_tx usb_dm usb_dp t_swo swo t_swo red _green 2 1 3 4 ld1 ld_bicolor_cms r1 1k5 r2 100k r18 100 r19 100 r17 0 r5 100 r20 100 r13 10k[n/a] r9 100k r6 100k r16 10k r14 4k7 r12 4k7 c2 100nf c5 100nf c3 20pf[n/a] c21 10pf c20 10pf c4 100nf u5v usb_renumn usb_renumn r11 2k7 r10 4k7 +3v3_st_link +3v3_st_link +3v3_st_link +3v3_st_link +3v3_st_link +3v3_st_link +3v3_st_link pwr_ext +3v3_st_link vo d1 bat60jfilm d2 bat60jfilm c18 1uf_x5r_0603 c17 10nf_x7r_0603 c16 1uf_x5r_0603 5 1 2 gnd 3 4 bypass inh vin vout u4 ld3985m33r c15 100nf c19 100nf +3v3_st_link 3 2 1 t1 9013 r4 10k r3 36k u5v r8 100 +3v3_st_link e5v e5v vbat 1 pa7 17 pc13 2 pa12 33 pc14 3 pb0 18 pc15 4 jtms/swdio 34 oscin 5 pb1 19 oscout 6 vss_2 35 nrst 7 pb2/boot1 20 vssa 8 vdd_2 36 vdda 9 pb10 21 pa0 10 jtck/swclk 37 pa1 11 pb11 22 pa2 12 pa15/jtdi 38 pa3 13 vss_1 23 pa4 14 pb3/jtdo 39 pa5 15 vdd_1 24 pa6 16 pb4/jntrst 40 pb12 25 pb5 41 pb13 26 pb6 42 pb14 27 pb7 43 pb15 28 boot0 44 pa8 29 pb8 45 pa9 30 pb9 46 pa10 31 vss_3 47 pa11 32 vdd_3 48 u5 stm32f103cbt6 u5v ilim = 510ma isc= 1.2ilim to 1.5ilim = 612ma to 765ma r15 10k u5v_st_link r7 2.7k c6 4.7uf c1 100nf pwr_enn sb1 swd +3v3_st_link 1 2 3 4 5 cn2 [n/a] stm_jtms stm_jtck sb9 in 1 in 2 on 3 gnd 4 set 5 out 6 out 7 fault 8 u1 st890cdr vbus 1 dm 2 dp 3 id 4 gnd 5 shield 6 usb_micro-b receptacle shield 7 shield 8 shield 9 exp 10 exp 11 cn1 1050170001
docid028406 rev 1 29/31 um1956 mechanical dimensions 30 appendix a mechanical dimensions figure 11. nucleo-32 board mechanical dimensions in millimeter
revision history um1956 30/31 docid028406 rev 1 8 revision history table 12. document revision history date revision revision details 14-oct-2015 1 initial version.
docid028406 rev 1 31/31 um1956 31 important notice ? please read carefully stmicroelectronics nv and its subsidiaries (?st?) reserve the right to make changes, corrections, enhancements, modifications, and improvements to st products and/or to this document at any time without notice. purchasers should obtain the latest relevant in formation on st products before placing orders. st products are sold pursuant to st?s terms and conditions of sale in place at the time of o rder acknowledgement. purchasers are solely responsible for the choice, selection, and use of st products and st assumes no liability for application assistance or the design of purchasers? products. no license, express or implied, to any intellectual property right is granted by st herein. resale of st products with provisions different from the information set forth herein shall void any warranty granted by st for such product. st and the st logo are trademarks of st. all other product or service names are the property of their respective owners. information in this document supersedes and replaces information previously supplied in any prior versions of this document. ? 2015 stmicroelectronics ? all rights reserved

▲Up To Search▲

Price & Availability of NUCLEO-F042K6

	To Download NUCLEO-F042K6 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .