While I am not Frederic, I can sort of address the DISCO board weirdness. I have a number of these going back to the F0. It came with a link and examples to two libraries. This was STM's first attempt into arduino land by attempting to make a SPL interface to Arduino Shileds. The other examples were for microbus.palmerr wrote:Frederic,
I've been looking through your variant files for MCU Port to Arduino pin mappings while working on a "Black STM32F407VET6" variant - as we've described on the Wiki http://wiki.stm32duino.com/index.php?title=STM32F407.
The Nucleo board is fairly straightforward with its Uno V3 style headers.
With the Disco Board
- what was the reasoning behind starting with the inner pins on both sides, and the the outer pins?
- how hard did you try to match Uno-style Dxx standards for functions (e.g. SPI, I2C, UART)?
Thanks for any guidance you can provide on how to make the variants as easy to use as possible for programmers.
from the readme - the Arduino shield boards were :
Code: Select all
Bluetooth BEE shield board,NFC ,Sparkfun MIDI shield board ST MEMS DIL24 board STEVAL-MKI108V2 board.
Code: Select all
ADC_Click, BLUETOOTH_Click, BUZZ_Click, DIGIPOT_Click, RTC_Click and IDC10 EasyLED boards. IDC10 LCD board "COG 2x16 LCD" is used as display board in some examples.
What is also interesting is some of the ST examples (Mostly Nucleo) can also control an Adafruit 1.8" TFT Joystick shield with microSD based on the ST7735R TFT controller. This product seems to date to 2012 and is product 802. (currently out of stock.)
Why I bring this up here is these boards seem to be the ones that the ST labs use to create code examples for. So are the best documented. While they are the reverse (mostly using SPL) of say the Arduino Dxx standards, they do show (as of 2012, when I took the seminar classes.) the way ST thought the Arduino pins should be mapped.
I have mentioned this subject before, but I do think it is important in the understanding of how ST and the ST engineers look at things like pin mapping.