I've just noticed, there was a press release about them:http://www.st.com/web/en/news/n3742
I see that they are called Nucleo-32
It is a bit of a shame they aimed to be so Nano-like.
The Nano has 30 pins (2x15), which is a bit annoying; AFAIK, 30pin DIL sockets are not easy or cheap to get (none at Farnell, RS, etc)
Two more pins would be a 32-pin socket, which are 'cheap as chips' (or 'cheap as french fries', I guess, in some parts of the world).
The boards use a 32pin MCU target. There are three signals, connecting the MCU to the ST-LINK/V2-1 MCU (SDIO, SWCLK and VCP RX), which aren't on the DIL pins. So those could have made those available as 'optional' pins on the same pitch and spacing as the 30-pin DIL.
VCP RX would have been very useful on the DIL header to be available as a USART (VCP Tx is available on the 2x15 pin DIL header).
Their are a bunch of useful documents, for example for the STM32F303 Nucleo-32 board:http://www.st.com/web/catalog/tools/FM1 ... 7/PF262544
The most useful seems to be "UM1956 User manual. STM32 Nucleo-32 boards
", which contains the schematics, and key to the board layout.
Like 'big Nucleo's" it has an ST-LINK/V2-1, which uses an STM32F103CBT6. This connects to the MCU's SWD pins, and
has a USART connection too.
A small piece of the product plan might be published on the schematic.
It has the comment "closed for L021, L031,L433 open for F042,F031,F303" next to the crystal.
So it appears that there will be 6 MCU's on that PCB.
The crystal (X1) is a 32KiHz. The STM32F's won't have that external crystal.
STM32Fxxx can be be driven by the HSI, or the ST-LINK/V2-1 'MCO' signal
When the crystal is not
connected, Arduino Nano-pins D7 and D8 are connected to the unused crystal oscillator pins, which I assume are set up as normal GPIOs. So the STM32Fs have two more useful I/O pins than the STM32Ls.
I like the mbed-style upload on Nucleo's; they look like a small flash drive. Upload a binary-program using a file browser, command-line copy command, or any program (e.g. web browser) which can write a file, and upload is done. "Simples". This is so much simpler than using avrdude, ST-LINK-drivers, or texanes ST-LINK software. The STLINK/V2-1 implements a USB virtual comm port, so it could be as easy to talk to it from a host PC as an Arduino.
The STM32F3 is a very impressive part. It uses the same CPU as a Cortex-M4 (with hardware floating point) and much improved peripherals compared to the STM32F103. For example, the STM32F303 has 5Msps ADCs, compared to 1Msps for STM32F103, DACs, analogue comparators, and a programmable gain Op Amp).